tomtom-international / open-data

This repository contains all details about TomTom Open Data's projects.
17 stars 1 forks source link

Netherlands | Data Improvements #7

Open marjanvandekauter-tomtom opened 2 years ago

marjanvandekauter-tomtom commented 2 years ago

Project description

Goal

To improve the map quality in the Netherlands, we propose to make data improvements by sharing challenges that can help fix data errors and improve the road network.

When appropriate, our team will also work on these challenges. If a challenge is more suitable to be solved without organised help, we will leave it for local users interested in completing the tasks. Challenges like this will be indicated as such in the overview below.

Additionally, we conduct edits based on map feedback.

How to participate

Anyone is welcome to contribute to this project by participating in our MapRoulette challenges. Here is the extended documentation for using MR. Note that sometimes additional instructions are provided within the challenges. We also strongly encourage you to make use of the guidelines listed in the OSM wiki category Dutch tagging guidelines while you are editing.

Here is the current set of challenges.

Challenges

Active challenges

Click to expand. - [Add Highways](https://maproulette.org/browse/challenges/41151) Identify and add if needed, one or more missing ways. - [Netherlands - Duplicated Nodes having same coordinates](https://maproulette.org/browse/challenges/41817) The objective is to identify and fix if needed, cases where duplicated nodes having same location (coordinates) should be merged. It is more regarding highways mostly, but also have tasks for ways in general (parks, buildings). We found the leads based on spatial analysis of OSM data to fetch overlapping nodes. You might be asking why introducing such type of challenge? well, we are trying to support improving the overall OpenStreetMap (OSM) route network quality by solving real errors in the data, by clearly identifying objects junctions for which nodes are used in this case. Ensuring that highway junctions are connected within OSM is crucial for optimised routing. When road elements are disconnected due to duplicated (not merged) nodes, it can degrade the navigation experience for routing applications that rely on OSM data, leading to inefficient directions, delays, and potential navigation errors. - [Netherlands - Add/Check Crossing Between Railway And Highway](https://maproulette.org/browse/challenges/42456) Identify and add if needed crossings between highways and railways. The locations that were indicated in the challenge show missing railway crossing information. This issue most often occurs in industrial areas or on roads with lower frequency of use. Adding this type of information to the OSM map will enrich the map's value in terms of safety for road users and improve the road network quality. - [Netherlands - Fix Incorrect Highway Junctions](https://maproulette.org/browse/challenges/41672): Identify and fix if needed, cases where highway junctions are incorrectly or imprecisely mapped. We improve overall OpenStreetMap (OSM) route network quality by solving real errors in the data. - [Netherlands - Fix Building and Highway Intersections](https://maproulette.org/browse/challenges/43056): Identify and fix, if needed, cases where a way with tag highway=* intersects with a building. - [Netherlands - Fix Inconsistent Bridge and Tunnel Tagging](https://maproulette.org/browse/challenges/43087): Identify and fix cases where the bridge or tunnel has an incorrect tag. - [Netherlands - Fix Building and Water Intersections](https://maproulette.org/browse/challenges/43092): Identify and fix, if needed, situations where a water feature intersects with a building. - [Netherlands - Fix Intersecting Buildings](https://maproulette.org/browse/challenges/43095): Identify and fix, if needed, situations where a building intersects with another building at the same layer. - [Netherlands - Fix Spiky Buildings](https://maproulette.org/browse/challenges/44785) This collaborative effort requires a review and possible geometry correction, as the challenge identifies buildings with potential issues due to their unusual shape. It is aimed at improving data quality, accuracy, and aesthetics of OpenStreetMap, making it a more valuable resource for a wide range of users and applications.

Inactive challenges

Click to expand. - [Connect Isolated Highways](https://maproulette.org/browse/challenges/39800) Identify and connect if needed cases where the end of the way with tag highway=* is not connected to the rest of the road network. - Missing Roads ([major roads](https://maproulette.org/browse/challenges/24103), [minor roads](https://maproulette.org/browse/challenges/24104)) Data analysis done by TomTom suggests that there should be a road or track here in OSM, but it is missing. - [Add Surface to Highway](https://maproulette.org/browse/challenges/37471) The goal of this challenge is to identify and add missing surface tags on motorways and motorway links as they represent high speed roads, and it is desirable to accurately tag the surface for these highways.  - [Not connected highway](https://maproulette.org/browse/challenges/27453) Ways with tag highway=* must be connected to the rest of the road network to ensure its continuity, e.g. for route planning. When such a way is not connected to another way with tag highway=*, an error is logged. - [Tag area=yes on object without feature type](https://maproulette.org/browse/challenges/27457) The area=yes tag is required for some closed ways when used to define a polygon. For closed ways with other tags, there is an assumption that the way defines an area. In some circumstances, a closed way may define both a closed polyline and an area. When tag area=yes is used, it is expected that one of the necessary accompanying tags is also found. - [Impossible angle in a highway](https://maproulette.org/browse/challenges/27458) In general, roads intended for vehicles should be built to maintain proper angles which ensure maneuvers and fluent traffic. Extreme, too sharp angles applied to a way may indicate errors in the road geometry. - [Invalid Turn Restriction](https://maproulette.org/browse/challenges/27460) This check identifies invalid turn restrictions. Invalid turn restrictions occur in a variety of ways, from invalid members to edge geometry issues to not being routable to wrong topology. Relations, ways and nodes in relations as well as turn restrictions are checked. A relation needs to have exactly one way with role 'from' and exactly one way with role 'to'. These ways should be linked together by at least one way with role 'via' OR with exactly one node with role 'via' (no more and no less). - [Polygon has self-intersection](https://maproulette.org/browse/challenges/27452) The necessary edits will be made to fix cases where the tag on a way indicates that the object is a polygon feature, but the way does not meet the definition of a closed way because it is self-intersecting, or ways in a relation with the same role form a self-intersecting polygon - [This multipolygon is a simple polygon](https://maproulette.org/browse/challenges/27454) Simple areas are mapped in OSM by creating a closed way and tagging it as an area object rather than a line. Relations of the type multipolygon are used to represent complex areas with holes inside or consisting of multiple disjoint areas. A multipolygon relation can have any number of ways in the role outer (the outline) and any number of ways in the role inner (the holes), and these must form valid rings to build a multipolygon. When a relation of the type multipolygon consists of only one member, which is a simple area, an error is logged. - [Polygon is not closed](https://maproulette.org/browse/challenges/23248) Features intended to be a polygon should be correctly tagged. When the tag indicates that the object should be a polygon, but the geometry is built out of a NON-closed way, an error is logged. - [Fix kW and V values for electric vehicle charging station](https://maproulette.org/browse/challenges/23320) The purpose of this challenge is to unify values for output* tags which are incorrect (there is no space between value and units).

Edits based on map feedback

Click to expand. We make improvements to OSM based on user feedback submitted for the TomTom map after comparing and ensuring that it is also valid for OSM. Here is a list of the types of edits to be made, provided they do not conflict with others’ edits and a local source is available: - Highways - Adding or correcting highways - Adding or correcting link roads - Adding or adjusting bridges, tunnels, layers, or relations - Adding or updating lanes and related properties - Adding or updating traffic signs - Adding or updating access barriers - Adding or updating turn restrictions - POIs (Points of Interest) - Adding POIs - Correcting POI locations - Adding or correcting POI information - Resolving POI-land use discrepancies - Handling POI closures - Land use - Adding land use - Modifying existing land use extent - Water - Adding or realigning rivers, streams, and lakes. - Railways - Adding railway tracks - Realigning railway tracks - Adding or adjusting railway infrastructure tags such as bridges, tunnels, level crossings - Ferry lines - Adding ferry lines - Realigning ferry lines - Adding ferry terminals These are incidental edits spread over time starting March 14, 2023. We follow local guidelines and, if needed, consult with the community before making an update.

Geographical scope

Data improvements will be made across the whole country.

Announcements

This project was announced in the Dutch user forums:

TomTom organised editing

We will follow the Organised Editing Guidelines for this project. TomTom will not make any edits until two weeks after the project announcement. Here is our Organised Editing page, including a list of our editors.

The majority of our edits in the Netherlands will be made by user Sebasawk.

How to find TomTom's edits

All edits made by our team receive the hashtag #tomtom. Edits based on user feedback additionally have the hashtag #tt_mapfeedback.

tt is a hashtag that has been used for TomTom’s edits in the past.

Sources for editing

For some OSM map edits TomTom editors will use proprietary sources for support. These will typically be in situations where there is not sufficient evidence using the available sources in OSM editors themselves. The proprietary sources will be ground-level imagery and GPS traces, both collected by TomTom's mobile mapping vans. On occasion, we will also use sources collected from a field survey by one of TomTom's sourcing specialists who have visited the location and collected data to support the required map updates.

How to reach out

If you have remarks about a specific edit of ours, please drop a comment in the changeset, and we will do our best to respond thoughtfully. Or, you can also:

kiranahiretomtom commented 8 months ago

The 'Sources for editing' section updated with the below information-

  1. Added a description of proprietary sources to support editing