Missing Maps Lubumbashi Congo admin division mapping Aug15
- 1 PLEASE, DON'T EDIT LUBUMBASHI ADMINISTRATIVE LIMITS, this task has already been achieved !
- 2 Admin levels in Lubumbashi
- 3 What's been done - what still needs doing
- 4 Relation attributes
- 5 What to do
- 6 Finding the limits of each cellː
- 7 Filtering out other building, highway and landuse data
- 8 Adding in admin boundaries
- 9 Data table:
PLEASE, DON'T EDIT LUBUMBASHI ADMINISTRATIVE LIMITS, this task has already been achieved !
This document was written by Claire Halleux, based on her own experience in Lubumbashi, in order to support anyone who wanted to help integrating administrative limits in the city of Lubumbashi. Suggestions and improvements are obviously welcome. After an additional data collection session at the beginning of January 2016, the administrative boundaries edition was completed during the first half of January 2016.
Please don't edit anymore those limits if you haven't acquired any additional reliable information beyond the ones previously displayed on this page.
This work needs to be done using JOSM and relations class of objects. If you are not familiar with both of them, please start familiarising with those notions first.
Admin levels in Lubumbashi
The admin divisions in Lubumbashi are organised as:
- admin_level = 6 is the whole Lubumbashi city (there’s only one)
- admin_level = 7 are the communes of Lubumbashi (there are 7 of them)
- admin_level = 8 are the quartiers of Lubumbashi (there are around 46 of them)
- admin_level = 9 are the cellules (and some blocs) of Lubumbashi (there are nearly 400 of them)
- admin_level = 10 are the (real) blocs of Lubumbashi, we didn’t collect info about them and therefore won’t be integrating them this time.
NB: In some quartiers, the cellules can be called blocs. From now, we’ll call admin_level 9 objects “cells”.
I’ve tried to gather as much info as I had on those administrative limits in this table. The way names as they are written can vary.
What's been done - what still needs doing
I have already integrated into OSM all the levels 6, 7 and 8 data (even if some contributors happened to accidentally delete parts of it, it was each time reverted successfully).
However, it is still possible that we might find out 1 or 2 extra quartiers (level 8) as some neighbourhoods might be revised, but that should be an exception.
The level 9 data is the thing we still need to work on.
At least 40 of the cells have already been fully integrated (+ maybe 20 with the names still missing but geometry and attributes already created). There are at least 300 more still waiting.
Each cell is defined by X ways and 1 relation. The ways which are part of the relation need to carry the following attributes:
- admin_level=9 (in the case the way didn’t carry yet another admin_level < 9)
The relation needs to carry the following attributes:
In most cases, all relation members will carry the role outer.
NB: The preferred option is to create new ways (detached from existing objects such as roads, rivers… for the admin boundaries. Each administrative unit should be a closed way
What to do
In the table below, you’ll find 17 pdf files carrying the name of one or several quartiers (level 8). In each quartier’s file, you should find the description of the cells limits for this quartier.
They come in different “formats”, some are easy to read and identify, some might be much more difficult to find. Some files were even slightly “cut” by the scanner. Let’s exchange to find solutions and make it work.
We also need a place to mention on which files or quartiers we are currently working on, so we don’t duplicate the effort (see the table below).
Thanks a lot for your interest and looking forwards making this work together!
Finding the limits of each cellː
Using the relevant data sheet from the owncloud link, identify the streets that border the cell. The north, south, east and west as listed on the pdf may not be obvious as the city planning is not necessarily linear. It is useful to use the mapnik imagery layer to find these streets as you might want to filter out everything but admin divs in the data.
Filtering out other building, highway and landuse data
Open the filters panel, add a new filter and enter highway=*|building=*|landuse=*. Selecting this filter and then toggling inverse will alternately show you admin data or building, highway and landuse data.
Adding in admin boundaries
Create ways along the limits of your cell, with nodes at each corner. If there is already a way in existence, you may need to split it at the point at which your cell joins.
Once you have ways outlining your cell, you can tag your boundary by going to Presets | Relations | Boundaries. Enter the name and boundary type (this will be administrative). Then add in your Administrative Level. This will be 9 for cells (most likely) or 8 for quartiers. click New Relation.
You should now be in the Tags and Members tab. In the 'Role' box, add 'outer' for each of your ways.
Click ok and your cell or quartier is finished.
Upload with the changeset comment #MissingMaps Lubumbashi Add bloc BlocName.
We used the data table that was displayed here to coordinate until December 2015 the administrative boundaries edition work. We listed download links for the paper scans, and put our names alongside the one we were working on. It's been removed as it had become outdated (see older version of this page from December 2015).