Thailand | Data Improvements #144
Assignees
Labels
Comments
|
The 'Sources for editing' section updated with the below information-
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Project description
Goal
Improving the map quality in Thailand 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 in the descriptions. We also strongly encourage you to follow the OSM editing good practices.
Here is the current set of challenges.
Challenges
Quality check challenges
Click to expand.
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.
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.
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).
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.
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.
Buildings with extremely sharp angles will be identified and corrected if needed.
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 relation with the same role form a self-intersecting polygon.
Identify and fix, if needed, situations where a building intersects with another building at the same layer.
Fix cases where highway junctions are incorrectly or imprecisely mapped to improve overall OpenStreetMap (OSM) route network quality by solving real errors in the data. Ensuring that highway junctions are connected within OSM is crucial for optimized routing. When road elements are disconnected or imprecisely mapped, it can degrade the navigation experience for routing applications that rely on OSM data, leading to inefficient directions, delays, and potential navigation errors.
Missing Highway Surface
Click to expand.
Add Surface to Highway
The goal of this challenge is to identify and add missing surface tags on a road network. We queried OSM for ways with certain highway=* values where the surface tag was missing.
Connect Isolated Highways
Click to expand.
-Connect Isolated Highways
Leads are generated based on analysis of highway classifications and their connection to the rest of the road network, you can 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.
Edits based on User 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 to 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
Missing feature and tag challenges
Click to expand.
Thailand - Fix inconsistent bridge and tunnel tagging
Identify and fix cases where the bridge or tunnel has an incorrect tag.
Thailand - Missing Access Tag
Missing access tag was detected after comparison OSM with TomTom's map database.
Thailand - Add Missing Buildings
Map missing buildings: Locate and add missing buildings that could be residential, commercial, or other structures.
Thailand - Map Missing Roads and Buildings
Improve the OSM data by adding roads and buildings that are missing in the urban area of Bangkok, Thailand.
Missing Water features challenges
Click to expand.
We have identified potential leads by comparing water features in OpenStreetMap (OSM) with TomTom’s map database. The challenge focuses on various types of water features, including small ponds and puddles.
Intersecting feature challenges
Click to expand.
-Thailand - Fix Inconsistent Highway Intersections
We used a modified version of Osmose check 1250 – objects intersection, with certain situations, such as pedestrian paths, removed from the scope. The objective is to identify and fix cases where highways intersect without a common node.
-Thailand - Fix Building and Water Intersections
We generate the leads after a spatial comparison of water features and buildings available in OSM, please identify and fix, if needed, situations where a water feature intersects with a building.
Geographical scope
Data improvements can be found across the whole country.
Announcements
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
The text was updated successfully, but these errors were encountered: