open-data icon indicating copy to clipboard operation
open-data copied to clipboard
verified publisher icon tomtom-international

Brazil | Data Improvements

Open salimbaidoun-tomtom opened this issue 3 years ago • 1 comments

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.
  • 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:
  1. The tag may be incorrect. In reality, the non-closed way should represent a linear object.
  2. 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.

Challenges

Active challenges

  • Brazil - Spiky Land Use This challenge helps refine land use features with unusual shapes in OSM, improving map clarity and avoiding potential routing or visualization issues.

  • Brazil- Disconnected Barriers from Nearby Roads which is made to focus on different types of barriers that are not connected to the highway located close to it to address connectivity and misleading access information. The tasks in this challenge were generated based on filtering out OSM data where there’s a barrier located on a highway or within 5 meters of a highway but not connected to it. All types of highway=* are included, and barriers such as bollard, block, flowerpot, crash_attenuator, kerb, log, and rock are excluded from the check.

    Inactive challenges

Click to expand.

*Brazil - Inconsistent Layer Tagging on Highways This challenge focuses on updating layer tags for highway features such as bridges and tunnels. By correcting missing or mislabeled layer tags, we improve OSM data accuracy and support safer, more reliable routing for everyone.

*Brazil - Mapping Missing Buildings and Greenspace in Belém for COP30 Climate Change Conference Supporting COP30 hosting city with missing Buildings and Roads

*Brazil - Sharp Angles on Highways Correct roads with unrealistically and odd sharp angles (less than 45 degrees).

*Brazil – Fix Incorrect Highway Junctions This challenge targets cases where highway junctions are not properly connected, such as:

  • Roads ending within 2 meters of another highway without a proper connection
  • Highway segments shorter than 0.5 meters from the junction

Only highways at the same level are included, and most obvious false positives have been filtered out.

*Brazil – Fix Inconsistent Highway Intersections This initiative aims to correct situations where highways cross but lack a shared node, which can cause navigation errors and reduce the quality of routing for all users. *Brazil - Fix Too Close Junctions This challenge identifies junctions where roads might be incorrectly positioned very close together, resulting in tiny, often unnecessary road segments (less than 50cm between junctions). This commonly occurs when roads aren't joined correctly to major ones.

Brazil - Fix Conflicting Highway and Construction Tag focused on validating and correcting roads with conflicting highway= and construction=* tags. Roads with outdated construction=* tags, even after completion, can be incorrectly rendered or excluded from navigation, routing and other types of applications, affecting OSM data usability.

*Brazil - Fix Inconsistent Highway Classification Our team identified instances where high-class roads connect to unusually low-class roads. These inconsistencies can lead to visualization and routing problems, impacting the overall reliability of OpenStreetMap. The team also analyze OSM data, pinpointing segments where a short stretch of a lower-class road is surrounded by higher-class roads. This often indicates a potential misclassification.

  • Brazil - Add Highways - São Paulo | Brasil - Inserindo Rodovias - São Paulo Missing highways can cause crucial issue for the road network and for logistics, routing, and monitoring applications used by many people.

  • Brasil - Conecte rodovias isoladas  | Brazil - Connect Isolated Highways its objective is to enhance the accuracy and reliability of global road networks. By identifying and fixing isolated highway segments, the routing and navigation for millions of users worldwide can improve.

  • Intersecting, Spiky and Missing Buildings

    • Brazil - Fix Spiky Buildings This challenge targets buildings with potentially inaccurate geometry, specifically those featuring very sharp angles (less than 15 degrees between walls meeting at a node). While most building corners are near 90 degrees, these sharp angles often indicate mapping errors.

    • Balneário Camboriú

    • Barueri

    • Brazil - Mapping Missing Buildings in Feira de Santana These 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.

    • Brazil - Fix Spiky Buildings Examine the set of potentially erroneous buildings that we’ve identified. Visit the locations on the map and assess whether the building shapes seem inaccurate.

  • Missing Roads and Airport challenge 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

  • Brazil - Add Airports types Classifying airports in OSM based on their size and service level: International, Regional, or Airfield. This will make information in OSM more accurate for travelers, logistics companies, and app developers for various applications. We've identified airports in OSM missing this classification information. Using "OurAirports" as a reference, you'll be presented with these airports and asked to categorize them based on their size (large, medium, or small). This size classification will then be used to suggest the most likely type (International, Regional, or Airfield).

    • Add Missing Highway Surface - January 2023 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.

    • Brazil - Update deprecated landuse=reservoir tags - Mato Grosso do Sul: By updating deprecated tags, you are making the OpenStreetMap data more consistent and easier to work with for OSM users.

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.

The aim is to improve the OpenStreetMap data by validating and fixing objects without tags. It is proper tagging that represents good editing practice, while objects without tags are undesirable in OpenStreetMap and should be either fixed by adding missing attributes or removed in case of duplicated or not existing objects

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

  • Brazil - Correct Too Short Highways This TomTom challenge focuses on identifying and correcting short highway segments. These short segments can cause issues with:

  • Navigation: Confusing and inaccurate driving directions.

  • Data Analysis: Skewed results for traffic patterns and routing.

  • Map Appearance: Messy and cluttered map display.

    • Brazil - Duplicated Highways OpenStreetMap (OSM) is a valuable resource for navigation, routing and mapping. However, it can sometimes contain errors, such as overlapping highways. These overlaps can cause confusion for users and inaccuracies in navigation.

    • Brazil - Disconnected Highways

To fix cases where highways intersect without a common node. Road crossings without a common node lead to navigation issues due to lack of junction's indication and affect the OSM map's usability and accuracy for all users.

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.

Announcements

The project was announced was on:

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

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

salimbaidoun-tomtom avatar May 09 '22 11:05 salimbaidoun-tomtom

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

kiranahiretomtom avatar Oct 19 '23 07:10 kiranahiretomtom