Madrid Museums Import

Goals

The goal is to manually merge and import the museums and museums information from the Madrid city council database, see: Import_Ayuntamiento_Madrid (in spanish)

In Madrid there are 55 museums already in OSM. The dataset from the city council contains 67. It contains useful information like: name, description, opening hours, if it is accesible with a wheelchair or not, address, phone, email and url.

Existing hand mapped information will not be replaced by the import without on-the-ground verification.

Schedule

1. September 7 2016: We started the preparation and the discussion. See the discussion in the talk-es list (in spanish)
2. September 10: Proposal sent to the imports list
3. September 14: Import started
4. December 2016: We finished doing the QA after the import

Import Data

Data description

The original dataset is xml format. It includes a total of 67 spots.

We'll use the xml file for processing. You can download the data here.

Background

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:30, 16 October 2016 (UTC)

Compatibility with the ODbL was already discussed in the imports and talk-es mailing lists.

Import Type

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 Preparation

Data Reduction & Simplification

Some corrections are made with the data conversion script madridxml2osm. Some of the fields aren't relevant and will be ignored.

Tagging Plans

Here are the original fields, their meaning and how they will be converted to the resulting OSM file:

Tagging Conversion

Original Fields	Meaning	OSM tag	Comments
ID-ENTIDAD	Internal reference number		Not used
NOMBRE	Name	name=*
DESCRIPCION-ENTIDAD	Description	description=*	Part of description=*
HORARIO	Timetables	opening_hours=*	Manual processing needed
EQUIPAMIENTO	Additional info about the museum	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	Can be changed manually to wheelchair=limited
CONTENT-URL	URL	url=*	Only if JOSM likes the url
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
NUM	housenumber	addr:housenumber=*
PLANTA	Floor		Not used
PUERTA	Door		Not used
ORIENTACION	Orientation		Not used
LOCALIDAD	City	addr:city=*
PROVINCIA	Province	addr:province=*
CODIGO-POSTAL	Post code	addr:postcode=*
BARRIO	Suburb	addr:suburb=*
DISTRITO	District	addr:district=*
COORDENADA-X	Coordinate X		Not used
COORDENADA-Y	Coordinate Y		Not used
LATITUD	Latitude	OSM Latitude
LONGITUD	Longitude	OSM Longitude
TELEFONO	phone	phone=*
FAX	Fax	fax=*
EMAIL	Email	email=*
TIPO	Kind		Not used

We added the following tags:

• tourism=museum
• source:date=2014-03-12
• source=Ayuntamiento de Madrid

Changeset Tags

We will use the following changeset tags:

• comment=#Madrid_museums_import and any notes that the mapper may add.
• source=Ayuntamiento de Madrid
• source:date=2014-03-12
• url=https://wiki.openstreetmap.org/wiki/Madrid_Museums_Import (this page)
• created_by=JOSM/version (This tag is created automatically by JOSM)

Data Transformation

Data is in xml format. We already:

1. Converted it to OSM format using the madridxml2osm data conversion script
2. Manually drawn the working area using JOSM and saved as geojson
3. Uploaded the working area to the TM
4. Splitted the osm file to have one file for each task on the TM using the osmboxes script

Data Import Workflow

Team Approach

Import will be undertaken by experienced OSM volunteers, following a strict workflow.

References

The import will be discussed in the Talk-Es list and in the Imports list.

Workflow

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_museums_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 museums data by clicking on the JOSM button and the link on the extra instructions.

• 7 Select all nodes on the museums layer and add them to the ToDo list. For each node we'll:
  • Edit the description=* to be less than 256 characters
  • On the addr:street=*, fix the name to match the current OSM street name
  • opening_hours=* has to be translated from spanish to opening_hours=* format
  • If the museum is subterranean, a tag layer=-1 will be added
  • Add entrance=main if there is none and optionally additional entrance=yes
  • Add operator=* if known.
  • Conflate the node data with the museum 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.

Updates

Each year I'll download the dataset, do a diff and update the data to OSM manually. Until I get bored. Kresp0 (talk) 17:31, 7 September 2016 (UTC)

Reverse plan

In case of any trouble, JOSM reverter will be used.