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 Sweden, we propose to make data improvements by sharing challenges that can help fix data errors, and add or edit certain kinds of features or tags.
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 by participating in our MapRoulette challenges. Here is the extended documentation for using MR. Note that sometimes additional instructions are provided within the challenges. We also strongly encourage you to make use of the resources listed in the OSM wiki section Sweden while you are editing.
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. Extreme, too sharp angles applied to a way may indicate errors in the road geometry.
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
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.
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.
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.
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.
Missing feature, intersecting features, Junctions, and tag challenges
Sweden - Add Highways
Data analysis done by TomTom suggests that there should be a road or track here in OSM, but it is missing.
Sweden - Fix Building and Highway Intersections
Leads are generated based on a spatial comparison of highways and buildings available in the OSM data. The objective is to identify and fix, if needed, cases where a way with tag highway=* intersects with a building.
Sweden - 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.
Sweden - Fix objects without tags
This challenge, created by TomTom, aims to enhance OpenStreetMap data by identifying and fixing objects missing essential tags.
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
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
Data improvements will be made across 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
NVDB (recommended by the Swedish community, where it doesn't conflict with OSM): Swedish road authoritiy layer: “Trafikverket Road Network” (to be used for buildings and roads calibration*)
Stockholm Orthophoto
National Imagery Layer: Lantmäteriet
Lantmäteriet Historic Orthophoto 1975 & Lantmäteriet Historic Orthophoto 1960 (can be used for building alignment)
Esri World Imagery (unreliable for buildings edits in some cases), please contact the Swedish community for any more clarification
Bing Maps Aerial (unreliable for buildings edits in some cases), please contact the Swedish community for any more clarification
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:
Project description
Goal
To improve the map quality in Sweden, we propose to make data improvements by sharing challenges that can help fix data errors, and add or edit certain kinds of features or tags.
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 by participating in our MapRoulette challenges. Here is the extended documentation for using MR. Note that sometimes additional instructions are provided within the challenges. We also strongly encourage you to make use of the resources listed in the OSM wiki section Sweden while you are editing.
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.
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.
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
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.
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.
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.
Connect Isolated Highways
Click to expand.
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.
Missing feature, intersecting features, Junctions, and tag challenges
Click to expand.
Sweden - Fix inconsistent bridge and tunnel tagging
Identify and fix cases where the bridge or tunnel has an incorrect tag.
Sweden - Add Highways
Data analysis done by TomTom suggests that there should be a road or track here in OSM, but it is missing.
Sweden - Fix Building and Highway Intersections
Leads are generated based on a spatial comparison of highways and buildings available in the OSM data. The objective is to identify and fix, if needed, cases where a way with tag highway=* intersects with a building.
Sweden - 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.
Sweden - Fix Inconsistent Highway Intersections
Identify and fix cases where highways intersect without a common node.
Sweden - Fix Incorrect Junctions on Roundabouts
Identify and fix cases where two or more highways are connected to the same node on a roundabout.
Sweden - Fix objects without tags
This challenge, created by TomTom, aims to enhance OpenStreetMap data by identifying and fixing objects missing essential tags.
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
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
Data improvements will be made across the whole country.
Announcements
This project was announced in the:
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:
*Please consult the Swedish Community on any doubts of Sources usage
The text was updated successfully, but these errors were encountered: