You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To improve the map quality in Brazil, we propose to make data improvements by sharing challenges that can help fix data errors, and add or edit certain kinds of geometry.
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.
How to participate
Anyone is welcome to contribute to this project. You can do so by fixing issues in MapRoulette, an application that helps you improve OpenStreetMap by completing small tasks grouped into challenges. Here is the extended documentation for using MapRoulette.
All of the challenges within this project are here.
Note that there are some additional instructions for these consistency checks in each challenge.
Challenges
Quality rules
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.
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.
Impossible angle in a highway
In general, roads intended for vehicles should be built to maintain proper angles which ensure maneuvers and fluent traffic.
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.
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
Spiky buildings
Buildings with extremely sharp angles will be identified and corrected if needed.
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 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.
Errors found can have one of two causes:
The tag may be incorrect. In reality, the non-closed way should represent a linear object.
The polygon is not closed. The tag indicates that the object is supposed to be an area, and the way is not part of any relation.
These situations should be corrected in line with the solving methods.
Missing Roads, Buildings and Parks
Click to expand.
Missing Buildings
This challenges is primarily focused on missing buildings of all types (residential, commercial, industrial…etc.) to be mapped as highlighted. Our team compared TomTom and OSM data using spatial comparisons including intersections and overlaps indexes, we have detected some areas where buildings are missing in OSM; to increase confidence level, the team compared a sample area and conducted analysis to validate some missing buildings.
The missing areas can be added by editing several buildings or individual ones; the choice will depend on reality checks and local knowledge. As you may know, you are required to use the most updated satellite and aerial imageries on the background while editing.
Missing Roads
This challenge is mainly focused on missing roads of all classes to be mapped as highlighted. Our team compared TomTom and OSM road network data using spatial comparisons including intersections and overlaps indexes, to increase confidence level, the team relied on available Imagery and selected valid missing roads.
As you may know, you are required to use the most updated satellite and aerial imageries on the background while editing.
The challenges are located in these cities:
Missing Parks
This challenges is primarily focused on Parks. Our team compared TomTom and OSM data using spatial comparisons including intersections and overlaps indexes, and we detected some areas where Parks are missing in OSM; to increase confidence level, the team compared a sample area and conducted analysis to validate some missing buildings.
As you may know, you are required to use the most updated satellite and aerial imageries on the background while editing.
The challenges are located in these cities:
When creating the park polygon, please use Tag:leisure=park
Missing Highway Surface
Click to expand.
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.
Brazil - Fix Building and Water Intersections
Our team has identified these tasks through a spatial comparison of water features and buildings available in OSM. We would greatly appreciate your review and resolution of the tasks involved, which include identifying and fixing situations where a water feature intersects with a building.
Brazil - Fix Incorrect Highway Junctions
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.
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.
This challenge helps you update the deprecated tag landuse=reservoir on water reservoirs in Brazil. The OSM wiki recommends that this tag be replaced with the tag combination natural=water + water=reservoir. You will find detailed guidelines for how to do this in the left-hand instruction panel of each task.
While editing the water bodies in this challenge, you may further improve them by correcting their outline if needed, or remove them if they no longer exist.
Other Geometry challanges
Click to expand.
Brazil - Fix Incorrect Junctions on Roundabouts
We’ve developed new checks aimed at identifying and correcting cases where two or more highways are connected to the same node on a roundabout. According to the OSM wiki documentation, highways entering and exiting a roundabout should never connect to the same node on that roundabout.
Why is this important? Fixing such situations will enable routing applications that rely on OSM data to correctly recognize the situation, providing improved guidance when entering or exiting a roundabout.
The Leads were detected based on a query of OSM data. We compared the number of highways entering and exiting a roundabout to find situations with a high number of highways or a low number of highways that are part of junction=roundabout or junction=circular. We excluded pedestrian paths, cycleways and roads that are located on different levels (bridges, tunnels).
Virtual projects
Click to expand.
Unusual and missing buildings challenges: BRA - Fix Unusual Buildings
We gather challenges related to missing and weird buildings – their size and shape is doubtful, hence see value in solving related issues and improve buildings rendering & display experience in OSM data. We, TomTom validated these tasks to confirm their nature and value.
Edits based on User Feedback
Click to expand.
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
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
Addresses
Adding or correcting addresses
Updating the position of address nodes, usually when an object has multiple addresses
Adding or correcting names of ways
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
Buildings
Adding buildings
Updating building type
Adjusting building shape
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
Geographical scope
The issues listed above will be fixed throughout the whole country.
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
Esri World Imagery
Bing Aerial
MapBox Satellite
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 'Sources for editing' section updated with the below information-
1. Removed Maxar Premium Imagery from the list as it's not available anymore in OSM
2. Added a description of proprietary sources to support editing
Project description
Goal
To improve the map quality in Brazil, we propose to make data improvements by sharing challenges that can help fix data errors, and add or edit certain kinds of geometry.
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.
How to participate
Anyone is welcome to contribute to this project. You can do so by fixing issues in MapRoulette, an application that helps you improve OpenStreetMap by completing small tasks grouped into challenges. Here is the extended documentation for using MapRoulette.
All of the challenges within this project are here.
Note that there are some additional instructions for these consistency checks in each challenge.
Challenges
Quality rules
Click to expand.
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.
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.
In general, roads intended for vehicles should be built to maintain proper angles which ensure maneuvers and fluent traffic.
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.
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
Buildings with extremely sharp angles will be identified and corrected if needed.
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).
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.
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.
Errors found can have one of two causes:
These situations should be corrected in line with the solving methods.
Missing Roads, Buildings and Parks
Click to expand.
Missing Buildings
This challenges is primarily focused on missing buildings of all types (residential, commercial, industrial…etc.) to be mapped as highlighted. Our team compared TomTom and OSM data using spatial comparisons including intersections and overlaps indexes, we have detected some areas where buildings are missing in OSM; to increase confidence level, the team compared a sample area and conducted analysis to validate some missing buildings.
The missing areas can be added by editing several buildings or individual ones; the choice will depend on reality checks and local knowledge. As you may know, you are required to use the most updated satellite and aerial imageries on the background while editing.
Missing Roads
This challenge is mainly focused on missing roads of all classes to be mapped as highlighted. Our team compared TomTom and OSM road network data using spatial comparisons including intersections and overlaps indexes, to increase confidence level, the team relied on available Imagery and selected valid missing roads.
As you may know, you are required to use the most updated satellite and aerial imageries on the background while editing.
The challenges are located in these cities:
Missing Parks
This challenges is primarily focused on Parks. Our team compared TomTom and OSM data using spatial comparisons including intersections and overlaps indexes, and we detected some areas where Parks are missing in OSM; to increase confidence level, the team compared a sample area and conducted analysis to validate some missing buildings.
As you may know, you are required to use the most updated satellite and aerial imageries on the background while editing.
The challenges are located in these cities:
When creating the park polygon, please use Tag:leisure=park
Missing Highway Surface
Click to expand.
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.Intersecting features
Click to expand.
Brazil - Fix Building and Water Intersections
Our team has identified these tasks through a spatial comparison of water features and buildings available in OSM. We would greatly appreciate your review and resolution of the tasks involved, which include identifying and fixing situations where a water feature intersects with a building.
Brazil - Fix Incorrect Highway Junctions
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.
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.
Tags
Click to expand.
This challenge helps you update the deprecated tag landuse=reservoir on water reservoirs in Brazil. The OSM wiki recommends that this tag be replaced with the tag combination natural=water + water=reservoir. You will find detailed guidelines for how to do this in the left-hand instruction panel of each task.
While editing the water bodies in this challenge, you may further improve them by correcting their outline if needed, or remove them if they no longer exist.
Other Geometry challanges
Click to expand.
We’ve developed new checks aimed at identifying and correcting cases where two or more highways are connected to the same node on a roundabout. According to the OSM wiki documentation, highways entering and exiting a roundabout should never connect to the same node on that roundabout.
Why is this important? Fixing such situations will enable routing applications that rely on OSM data to correctly recognize the situation, providing improved guidance when entering or exiting a roundabout.
The Leads were detected based on a query of OSM data. We compared the number of highways entering and exiting a roundabout to find situations with a high number of highways or a low number of highways that are part of junction=roundabout or junction=circular. We excluded pedestrian paths, cycleways and roads that are located on different levels (bridges, tunnels).
Virtual projects
Click to expand.
We gather challenges related to missing and weird buildings – their size and shape is doubtful, hence see value in solving related issues and improve buildings rendering & display experience in OSM data. We, TomTom validated these tasks to confirm their nature and value.
Edits based on User Feedback
Click to expand.
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
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
Addresses
Adding or correcting addresses
Updating the position of address nodes, usually when an object has multiple addresses
Adding or correcting names of ways
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
Buildings
Adding buildings
Updating building type
Adjusting building shape
Water
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
Geographical scope
The issues listed above will be fixed throughout the whole country.
Announcements
The project was announced was on:
May 9th, 2022 in the Brazil user forum
January 24th, 2023 in the Talk-br Mailing List, OpenStreetMap Brasil Discord and Comunidade do OpenStreetMap no Brasil forum
Map feedback: February 13th, 2023 in the Talk-br Mailing List, OpenStreetMap Brasil Discord and Comunidade do OpenStreetMap no Brasil forum
February 16th, 2023 in the Talk-br Mailing List, OpenStreetMap Brasil Discord and Comunidade do OpenStreetMap no Brasil forum
April 13th, 2023 in the Talk-br Mailing List, OpenStreetMap Brasil Discord and Comunidade do OpenStreetMap no Brasil forum
April 28th, 2023 in the Talk-br Mailing List, OpenStreetMap Brasil Discord and Comunidade do OpenStreetMap no Brasil forum
May 19th, 2023 in the Talk-br Mailing List, [OpenStreetMap Brasil Discord (https://discord.com/channels/538023117793263626/538031659023466518/1109179050678829137), Comunidade do OpenStreetMap no Brasil forum and OSM São Paulo Telegram channel
Brazil - Add Highways - Pernambuco and Brazil - Add Highways - São Paulo refill were announced in Talk-br Mailing List, Comunidade do OpenStreetMap no Brasil forum, OSM São Paulo Telegram channel and OSM Pernambuco (June 5th, 2023)
Brazil - Fix Building and Water Intersections was announced in Talk-br Mailing List, Comunidade do OpenStreetMap no Brasil forum and OpenStreetMap Pará Telegram channel (Aug 15th, 2023)
Brazil - Fix Incorrect Highway Junctions was announced in Comunidade do OpenStreetMap no Brasil forum and OpenStreetMap Telegram channel (Nov 2nd, 2023)
Brazil - Fix Incorrect Junctions on Roundabouts was announced in Comunidade do OpenStreetMap no Brasil forum and OpenStreetMap Telegram channel (Nov 3th, 2023)
Brazil - Update deprecated landuse=reservoir tags - Mato Grosso do Sul was announced in Comunidade do OpenStreetMap no Brasil forum and OpenStreetMap Telegram channel (Jan 11th, 2024)
Brazil - Mapping Missing Buildings in Feira de Santana was announced in Comunidade do OpenStreetMap no Brasil forum and OpenStreetMap Telegram channel (Feb 15th, 2024)
BRA - Fix Unusual Buildings was announced in Comunidade do OpenStreetMap no Brasil forum and OpenStreetMap Telegram channel (April 15th, 2024)
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: