Automated edits/VTTdmt

From OpenStreetMap Wiki
Jump to: navigation, search

Summary: Mapping public electric vehicle charging stations in Torino, Venaria, Villach, and Calvià. The script will be first applied to Torino and Venaria case. Then Villach and Calvià will follow. This is part of EU funded STEVE project (http://www.steve-project.eu/index.php/en/) conducted by VTT Technical Research Centre of Finland - Digital Mapping Team.

Goals

Collecting data for existing charging stations from various sources (such as BlueTorino, Evway), and use the data to:

  • Update charging stations already in OSM with accurate and detailed data.
  • Create missing charging stations.

Following the progress of STEVE project:

  • Mapping the new charging stations built for the STEVE project (mainly ELV and moped charging stations).

Schedule

Phase 1 - Planning

Tasks:

  • Contact source companies and get their approval of using their data for charging stations in Torino, Venaria, Villach, and Calvià under ODbL license.
  • Get community approval, write documentation and tools.

Time:

June 2018 - August 2018

Status:

Undergoing

Phase 2 - Import

Tasks:

  • Import data for amenity=charging_station in Torino, Venaria, Villach, and Calvià. For new nodes, it will be an automated procedure. For possibly existing nodes, user will manually check each node to avoid duplication.

Time:

July 2018 - August 2018

Status:

Phase 3 - Maintenance

Tasks:

Time:

Status:

Import Data

Background

Provide links to your sources.

Data source site:

Data license:

Type of license (if applicable): e.g. CC-BY-SA, Public Domain, Public Domain with Attribution, etc.

Link to permission (if required): e.g. link to mail list reference url - http://lists.openstreetmap.org/pipermail/imports/2012-December/001617.html

OSM attribution (if required): http://wiki.openstreetmap.org/wiki/Contributors#yourdataprovider

ODbL Compliance verified: yes/no 

OSM Data Files

Link to your source data files that you have prepared for the import - e.g. the .osm files you have derived from the data sources.

Import Type

Identify if this is a one-time or recurring import and whether you'll be doing it with automated scripts, etc.

Identify what method will be used for entering the imported data into the OSM database - e.g. API, JOSM, upload.py, etc.

Data Preparation

Data Reduction & Simplification

Describe your plans, if any, to reduce the amount of data you'll need to import.

Examples of this include removing information that is already contained in OSM or simplifying shapefiles.

Tagging Plans

Describe your plan for mapping source attributes to OSM tags.

Changeset Tags

Describe how you'll use changeset tags in the import.

Data Transformation

Describe the transformations you'll need to conduct, the tools you're using, and any specific configurations or code that will be used in the transformation.

Data Transformation Results

Post a link to your OSM XML files.

Data Merge Overflow

Team Approach

Describe if you'll be doing this solo or as a team.

References

List all factors that will be evaluated in the import.

Workflow

Detail the steps you'll take during the actual import.

Information to include:

  • Step by step instructions
  • Changeset size policy
  • Revert plans

Conflation

Identify your approach to conflation here.

Quality Assurance