Import Puntos Kilometricos

Goals

The goal is to manually merge and import the highway milestones from the IDE La Rioja government website.

In La Rioja there are only one millestone in OSM. The dataset from the IDE La Rioja contais 3455. It contains useful information like: road_ref, distance, city, ref.

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

   December 20 2016: We started the preparation and the discussion. See the discussion in the talk-es list (in spanish)
   December ?: Proposal sent to the imports list
   December ?: Import started
   January ?: We finish doing the QA after the import
   January ?: Notify talk-es with a small report

Import Data Data description

The original dataset is geosjon format. I transform it to CSV and includes a total of 3455 spots.

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

ODbL Compliance verified: NO

The license can be consulted here (in Spanish). It requires attribution of the source, so all nodes and the changeset will include source=Gobierno de la Rioja. La Rioja Government (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 :) cronoser (talk) 13:30, 16 October 2016 (UTC)

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

Cumplimiento de la cláusula de atribución de los datos abiertos del Ayto. de Madrid en OSM.pdf 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 X Latitude OSM Latitude Y Longitude OSM Longitude id ref Carretera ref hightway=ref Punto kilométrico Distance Municipio Town Provincia Province

We added the following tags:

   source:date=2016-20-12
   source=IDE 

Changeset Tags

We will use the following changeset tags:

   comment=#LaRioja_puntos_kilometricos_import and any notes that the mapper may add.
   source=IDE La Rioja
   source:date=2016-20-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:

   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 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) I did not write this here Kresp0 (talk) 12:07, 10 June 2018 (UTC) Reverse plan

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