Belize | Data Improvements

[marjanvandekauter-tomtom]

Project description

Goal

To improve the map quality in Belize, we propose to make data improvements by sharing challenges, and when appropriate, fixing data errors, and adding or editing certain kinds of geometry.

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.

Challenges

Quality check challenges

Click to expand.

• Not connected highway

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

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.

• 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).

• 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.

Geometry challenges

Click to expand.

• Missing Roads

Data analysis done by TomTom suggests that there should be a road or track here in OSM, but it is missing.

Geographical scope

Data improvements will be made across the whole country.

Announcements

The geometry challenges were announced in the OSM Central America Telegram group.

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

• Maxar
• Esri
• Bing

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:

• join the conversation in the OSM Central America Telegram group (see Announcements),
• email osm@tomtom.com.

[ghost]

https://donate.openstreetmap.org 😄