Import Nigeria eHealth Borno Health Facilities
Goals
The goal is to import 508 health facilities collected by eHealth Africa for the Borno State, Nigeria. Although most of them are in Borno (484 nodes), a few of these nodes lie in border areas of the neighbour states of Adamawa (18 nodes), Gombe (5 nodes) and Yobe (1 node).
Schedule
- Preparation, discussion: This import is similar to the Kano State and to the Bauchi State health facilities imports, but includes more information.
- Import - expected to start as soon as community has solved any issues.
Import Data
Data description
The datasets are drawn and generated by eHealth Africa in the course of their mapping activities in Northern Nigeria. The organisation has performed data collections in the areas that weren't off-limits due to the NE Nigeria ongoing crisis. Moreover, a Q&A has been performed to double-check the accuracy of this data.
The original dataset consists of 509 health facilities entries, in .osm format, of which one was deleted as being a duplicated node without information, so being the total 508 nodes.
The dataset contains several field attributes already present in the Kano and Bauchi state imports, like the name of the facility, the health facility type, the ward, LGA and state to which it belongs and the ownership. But this one includes more information, like specialities and services provided, numbers of doctors and nurses, dates of surveys, etc.
Background
ODbL Compliance verified: YES
eHealth Africa has given full authorization for the use of their data with the standard authorization document of the Humanitarian OpenStreetMap Team (HOT). A scan of the document can be found here.
Import Type
The import will be done manually through one project in the HOT Tasking Manager (TM), having for each task of the project only the health facilities nodes that lie within the task tile, in a similar way as it was done for the Central African Republic UNICEF import. For each task, we will first check the eHealth nodes to be imported, and second we will assess the data already in the OSM database against the eHealth Africa one, for the merging of the eHealth data into the OSM database. The OSM mappers who will contribute to this import job will follow a detailed workflow to accomplish this.
Apart from this, and with their regular OSM accounts, these users will add road access to each facility and, in case the place where it is located is unnamed, they will also add a place node with the name of the place extracted from the facility addr:full=*, adding the source=ehealthafrica.org (health facility) tag to that place node.
Data Preparation
Data Reduction & Simplification
The data is originally in osm format, in only one file.
Tagging Plans
Each health facility will have the following tags:
Changeset Tags
We will use the following changeset tags:
- comment=eHealth Africa Borno health facilities import, #hotosm-project-946
- created_by=JOSM/version
- source=ehealthafrica.org
- import=yes
- url=https://wiki.openstreetmap.org/wiki/Import_Nigeria_eHealth_Borno_Health_Facilities
Data Transformation
Data is in osm format. We just process the osm file and convert it to a new osm file with an awk script.
Data Merge Workflow
Team Approach
Import will be undertaken by experienced OSM mappers, using an import specific OSM user account, following a workflow and working through a HOT Task Manager project similar to the ones set for the import of UNICEF health facilities, schools and water resources in Central African Republic.
References
The import will be discussed first in the Talk-Ng list and the HOT list, and then in the import list.
Workflow
You can see the workflow here.
Reverse plan
In case of any trouble, JOSM reverter will be used.
Conflation
The location of the eHealth nodes is generally correct, but following the already mentioned workflow, we will place the nodes in the exact position. For example, for a hospital compound, we will place the node more or less at the centre of it, in case it is not centered.
If other health facilities are encountered, they will be compared with the import ones and merge the data in the best possible way, keeping all info that the old ones may have. In case of doubt, a fixme tag will be placed, the issue will be reported through the comment of the task (tile) of the TM job, and the user that uploaded the old health facility node would be eventually contacted if needed.