I will get location coordinates of user , which I will pass in Overpass API to get Nearby hospitals, Then with the name of Nearby Hospitals , I will use Github API to download CDM which I have already saved to a repo .The CDM will be downloaded in app & will be stored in SQL Database in app.
But For this approach hospital name must be the same as that saved in github
I have done experimenting this approach & it was working correctly in app.
But for this, I need to take care for name to be same from overpass API response & that saved on github.
I have planned to scrap hospitals CDM statewise, I will start from California & will scrap around 40 hospitals of each state , By the end of this program I will have scraped data of around 2000 Hospitals as there are 50 States in US.
@Darshpreet2000, please can you give a detail on what you will be doing this week and when you will be free for the call. Also we will decide on the repos name, for now just keep working on your github repos. We shall mirror it. Also provide the links here so I track your progress.
I like the idea of the CI for running say daily so we get updated data.
This is my Gitlab Repo, I have scrapped data of 4 hospitals for trial, I have created a CI pipeline which automatically scrap data on push to repository.
But currently everything is running under one job, I want to seperate into multiple jobs without installing package again, I need to look for this.
Also , I will create a process file which parses all CDM to correct column names ,this will also run from pipeline.
You can contact me anytime you want but please tell me time beforehand
and your android app? We’re going to fork, then remove the fork relationship, so you’ll need to fork again. You’ll make Merge Requests against our repo. Does this sound good to ya? You can commit a gitlab-ci config file and set things up and make merge requests against that file.
The last might be the latest in many cases. So, if something was published in 2018, it might still be correct for now, as prices likely didn’t change in 2019 and the 2020 updates have not happened. Your repo should be able to keep history of all those, so that you can later do some pricing analytics