Bob Cameron
2021-04-22 22:49:57 UTC
For interest only. The weblink below is for a site that creates Garmin
navigating device maps based on OSM data and in the process generates an
error list that affect routing etc.
https://alternativaslibres.org/errors/errors_Australia.zip
Partial of the readme included in fileset;
/This is a short description of the errors listed in the files contained
in errors.zip. All these errors can cause routing to fail or that some
elements in the map are not displayed correctly. For each error listed,
ID of the wrong element and a link to download the area into JOSM or
view it in a web browser is given. If you want to improve the quality of
the maps, please spend some time fixing some of these errors.//
/
/Roundabouts.txt: Roundabout XXX starts/ends/forks at...: indicates that
a way or a set of ways tagged as junction=roundabout is/are not closed
or has a portion going out/coming in the roundabout.
/
/Flares.txt: this file groups different problems affecting the roads
that connect a roundabout with other roads.//
Arcs.txt: Similar arcs XXX and YYY at...: indicates that XXX and YYY
ways are overlapping.//
Oneway_roads.txt: this file groups different problems affecting oneway
roads, going to/coming from nowhere.//
Turn_restriction.txt: this file groups different problems affecting turn
restrictions. Problems can be the lack or excess of any of the turn
restrictions elements or some of them not connecting the others.//
//
Motorway_exits.txt: motorway_junction nodes must be placed on roads with
a ref tag, in order to process them correctly as motorway exits. This
file collects those motorway exits positioned on ways lacking ref tag.//
//
Multipolygon.txt: errors in relations of type multipolygon or boundary,
such as intersecting ways, polygons with rol inner that are not inside a
polygon with role outer, multipolygons which elements don't make a
closed polygon, etc.//
//
HouseNumbers.txt: errors related to house numbers. This information is
necessary in order to be able to search by addresses./
navigating device maps based on OSM data and in the process generates an
error list that affect routing etc.
https://alternativaslibres.org/errors/errors_Australia.zip
Partial of the readme included in fileset;
/This is a short description of the errors listed in the files contained
in errors.zip. All these errors can cause routing to fail or that some
elements in the map are not displayed correctly. For each error listed,
ID of the wrong element and a link to download the area into JOSM or
view it in a web browser is given. If you want to improve the quality of
the maps, please spend some time fixing some of these errors.//
/
/Roundabouts.txt: Roundabout XXX starts/ends/forks at...: indicates that
a way or a set of ways tagged as junction=roundabout is/are not closed
or has a portion going out/coming in the roundabout.
/
/Flares.txt: this file groups different problems affecting the roads
that connect a roundabout with other roads.//
Arcs.txt: Similar arcs XXX and YYY at...: indicates that XXX and YYY
ways are overlapping.//
Oneway_roads.txt: this file groups different problems affecting oneway
roads, going to/coming from nowhere.//
Turn_restriction.txt: this file groups different problems affecting turn
restrictions. Problems can be the lack or excess of any of the turn
restrictions elements or some of them not connecting the others.//
//
Motorway_exits.txt: motorway_junction nodes must be placed on roads with
a ref tag, in order to process them correctly as motorway exits. This
file collects those motorway exits positioned on ways lacking ref tag.//
//
Multipolygon.txt: errors in relations of type multipolygon or boundary,
such as intersecting ways, polygons with rol inner that are not inside a
polygon with role outer, multipolygons which elements don't make a
closed polygon, etc.//
//
HouseNumbers.txt: errors related to house numbers. This information is
necessary in order to be able to search by addresses./