Taiwan | Data Improvements #101
Labels
map feedback edits
maproulette
missing features/tags
quality checks
ie quality rules
road network
taiwan
Project description
Goal
Improving the map quality in Taiwan by sharing tasks that can help fix data errors and/or add certain kinds of features.
How to participate
Anyone is welcome to contribute to this project by participating in our MapRoulette challenges. Here is the extended documentation for using MapRoulette. Note that sometimes additional instructions are provided within the challenges. We also strongly encourage you to follow the OSM editing good practices and common tagging methods for Taiwan.
When appropriate, TomTom will also work on the tasks. If they are more suited to be solved without organized help, we will indicate as such in the overview and leave them for interested mappers with local knowledge to complete the tasks.
Here is the current set of challenges.
Active Challenges
Fix Building & Highway Intersections
Identify and fix, if needed, cases where a way with tag highway=* intersects with a building.
Fix Intersecting Buildings
Identify and fix, if needed, situations where a building intersects with another building at the same layer.
Fix Spiky Buildings
If an error is found, use preferred OpenStreetMap editor to make corrections, ensuring the buildings reflect their real geometry.
Road network challenges
Identify and add if needed, one or more missing ways.
Edits based on Map Feedback
We will 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 that could be made, provided they do not conflict with others’ edits and a local source is available:
Highways
Addresses
POIs (Points of Interest)
Land use
Buildings
Water
Railways
Ferry Lines
Inactive Challenges
Isolated Highways Challenges
Click to expand
These are tasks comprising of situations when a way with tag highway=* is not connected to the rest of the road network. Analyze and, if needed, connect the way to another way with tag highway=*.
Quality check challenges
Click to expand.
Invalid Lane Tag
The tag lanes=* on ways with tag highway=* indicates the amount of lanes on the road at hand. The value for the lanes tag should be only one of the following numbers: 1, 1.5, 2, 3, 4, 5, 6, 7, 8, 9, 10. Any other value is incorrect and should be fixed.
Tag area=yes on object without feature type
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
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
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).
Invalid Mini-Roundabout
Mini-roundabouts are a special kind of roundabout with the same rules as other roundabouts, but present as painted circles rather than physical circles. There might also be a low, fully traversable dome or island that vehicles can drive across. Road traffic flows in one direction around a point in the middle, and the traffic in the roundabout has right-of-way. A mini-roundabout is recorded using the tag highway=mini_roundabout.
Polygon has self-intersection
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
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.
Spiky buildings
Buildings with extremely sharp angles will be identified and corrected if needed.
Polygon is not closed
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.
Geographical scope
Data improvements will be made across the whole country.
Announcements
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.
How to find TomTom's edits
All edits made by our team have the hashtag #tt or #tomtom.
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:
The text was updated successfully, but these errors were encountered: