Madrid Post Offices Import
- 1 Goals
- 2 Schedule
- 3 Import Data
- 4 Data Preparation
- 5 Data Import Workflow
The goal is to manually merge and import the postal office information from the Madrid city council database, see: Import_Ayuntamiento_Madrid (in spanish)
In Madrid there are 118 amenity=post_office in OSM. The dataset from the city council contains all 80 offices from the postal operator "Correos". It contains useful information like: opening hours, address, phone, email and url.
Existing hand mapped information will not be replaced by the import without on-the-ground verification.
- September 26 2016: We started the preparation and the discussion. See the discussion in the talk-es list (in spanish)
- October 1: [We started the import http://osm.unizar.es:6543/project/26]
- October ?: We finish doing the QA after the import
- October ?: Notify talk-es with a small report
The original dataset is xml format. It includes a total of 80 spots.
We'll use the xml file for processing. You can download the data here.
ODbL Compliance verified: YES
The license can be consulted here (in Spanish). It requires attribution of the source, so all nodes and the changeset will include source=Ayuntamiento de Madrid. The Madrid City Council (Ayuntamiento de Madrid) is already on the contributors list.
After sending the report with the problems and errors found during the drinking water import, including a section about the license, got a response from the "Subdirección General de Transparencia del Ayuntamiento de Madrid" (the data owner), and they confirmed me that we comply with their attribution clause using their data in OSM if we clearly specify the source and the source:date, the way it was done on the Madrid_Drinking_Water_Import. And they do like the work we are doing :) Kresp0 (talk) 13:29, 16 October 2016 (UTC)
The import will be done manually, using the Tasks Manager, so it can be assigned to different volunteers. JOSM will be used to edit the data.
Data Reduction & Simplification
Some corrections are made with the data conversion script madridxml2osm. Some of the fields aren't relevant and will be ignored.
Here are the original fields, their meaning and how they will be converted to the resulting OSM file:
|Original Fields||Meaning||OSM tag||Comments|
|ID-ENTIDAD||Internal reference number||Not used|
|NOMBRE||Name||We extract the ref=* from this field.||Contains the branch office number (número de sucursal)|
|DESCRIPCION-ENTIDAD||Description||description=*||Part of description=*|
|HORARIO||Timetables||opening_hours=*||Manual processing done: https://ethercalc.org/3wf87iuqhnzh|
|EQUIPAMIENTO||Additional info about the postal office||description=*||Part of description=*|
|TRANSPORTE||Nearest bus and metro stations||Not used|
|DESCRIPCION||Description||description=*||Part of description=*|
|ACCESIBILIDAD||Wheelchair access. 0 = no access, 1 = some kind of access||wheelchair=yes or wheelchair=no||They all are set to 0, but that is not correct acording to Correos. We'll call to each office to know or will not add that information.|
|CONTENT-URL||URL||Not used, we'll set url=https://www.correos.es for all offices.|
|NOMBRE-VIA||Name of the street, without the prefix.||addr:street=*||Part of addr:street=*|
|CLASE-VIAL||Street prefix||addr:street=*||Part of addr:street=*|
|TIPO-NUM||kind of housenumber||Not used|
|COORDENADA-X||Coordinate X||Not used|
|COORDENADA-Y||Coordinate Y||Not used|
We added the following tags:
We will use the following changeset tags:
- comment=#Madrid_post_offices_import and any notes that the mapper may add.
- source=Ayuntamiento de Madrid
- url=https://wiki.openstreetmap.org/wiki/Madrid_Post_Offices_Import (this page)
- created_by=JOSM/version (This tag is created automatically by JOSM)
Data is in xml format. We already:
- Converted it to OSM format using the madridxml2osm data conversion script
- Manually drawn the working area using JOSM and saved as geojson
- Uploaded the working area to the TM
- Splitted the osm file to have one file for each task on the TM using the osmboxes script
Data Import Workflow
Import will be undertaken by experienced OSM volunteers, following a strict workflow.
The import will be discussed in the Talk-Es list.
As most (if not all) of the volunteers will be Spanish speaking, they can follow the detailed workflow in Spanish language on the TM.
The workflow will be as follows:
- 1. Install the TODO list JOSM plugin if the volunteer don't have it.
- 2. Create, if we don't have one yet, an import specific user account, like username_madrid_post_offices_import (you will need a different email address from the account you used for your regular OSM account). Change the OSM username to that specific account in the JOSM preferences.
- 3. Configure JOSM to allow remote access.
- 4. Login into the Tasks Manager.
- 5 Select one square to work on.
- 6 Open the OSM data and the post offices data by clicking on the JOSM button and the link on the extra instructions.
- 7 Select all nodes on the post offices layer and add them to the ToDo list. For each node we'll:
- On the addr:street=*, fix the name to match the current OSM street name
- Conflate the node data with the building/node if there is already one or create a new one if not. Don't replace existing hand mapped information without on-the-ground verification.
- 8. After the import is done, there will be a review process using the TM.
In case of any trouble, JOSM reverter will be used.