User:Edvac/Wikis/Lebanon Red Cross Health Facilities Import
Main page | Workflow | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The Lebanese Red Cross health facilities import is an import of 2,644 health facilities - hospitals and other health centres, pharmacies and laboratories -, covering the whole of Lebanon territory. Goal(Write a short background intro here) Healthsites.io and the Lebanese Red Cross have the goal of importing health facility data into OSM with a dedicated team of mappers, merging them with the existing data, improving their tagging and/or geolocation when needed, and dismissing those that aren't correct, using both aerial imagery and local knowledge for validation. Schedule
Import dataData descriptionThe original data consists of 2,644 health facilities as nodes, covering all muhafazah (governorates) of Lebanon, divided in 4 csv files containing the following features:
The German Red Cross has given permission to import the data into OSM. (Explain here how the data has been collected by the German Red Cross) When a node is not yet in OSM, it will be imported, after checking the tags and geolocation are correct. But when a health facility is already in OSM, it will only be imported or partially imported when it adds information to the already existing object. History of the object will be always kept, and no objects will be deleted during the import process, unless for very rare cases. BackgroundData source site: (put here url pointing to the original data) OSM Data Files(correct this:) Here you can download 4 files in zip format. Import typeThe best approach to import this data is manually by a dedicated team, with data split in 4 files, that will correspond to 4 projects in the HOT Tasking Manager. Access will be restricted to the import team. Advantages:
We will provide a link for each Tasking Manager project in a table of the import workflow wiki, with info about the total size (number of nodes) and expected time of work for each one. Data preparationData reduction & simplificationSome health facilities original info will not be shared nor imported, as they contain private data not meant for integration into an open database like OSM. Examples are names of managers, directors, their phone numbers, etc. As for simplification... (Add this when we have checked the data for assessment). Tagging plansThe original tagging is in accordance to... (add this info) Some tags of the original dataset aren't relevant (check this when having the data), so we ignore them. Here we list all the original disclosed tags, with their corresponding translation into the OSM tagging schema, plus additional tags for all objects: Hospitals
Health Centers
Laboratories
Pharmacies
All objectsApart from the specific tags for each health facility, we will add the following tag to each node: Changeset tagsWe will use the following changeset tags:
where:
Example:
Data transformation
Data transformation resultsYou can [(url for data) download here the zip file with all 2,644 resulting nodes]. Data merge workflowTeam approachThis import (data integration) will be done through the HOT Tasking Manager, and the number of team members importing the data is (place here the number). Team member will be trained to:
ReferencesFollowing the imports guidelines, this import will be discussed first in the local Lebanese OSM mailing list, and to get more feedback it will also be shared with the HOT mailing list. With the inputs from those lists, a thread will be opened in the imports list. WorkflowWe will use the JOSM editor for this import. Step by step instructionsThere are several ways to reach the same results. We have tried to find the simplest one, the less error-prone and the one that assures a higher level of consistency across different import team members. The proposed workflow is as follows:
(To be continued, once an in-depth assessment of the whole dataset is done) A detailed [(here the url) workflow wiki] can be read here. Changeset policyChangesets will be small in size, so no issues expected in this respect. Revert planIf something goes wrong, JOSM reverter will be used. ConflationConflation is explained in the import workflow wiki, in the [(one url) (Title of the section)] and [(another url) (Title of another section] sections. The import workflow will basically keep the tagging and/or location of the existing OSM health facilities, unless the German Red Cross equivalent is has more info to add, or has some other info that needs to be corrected. QAValidation of the import will be done by a second team member in the Tasking Manager. (add here categories) |