NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum


While in driving mode and following directions/route on NavDroyd I found several instances where there were errors

e.g. a request to turn right where there was a NO Turn Right sign a roundabout showing 5 exits when 1 of those was a pedestrian entrance to a church grounds and blocked to vehicles being routed up an exit slip road thru' traffic lights and back onto an entrance slip road to a motorway instead of being roted thru' on the motorway.

I registered with OSM to edit/correct/notify the bugs but I'm totally new to OSM (though very experienced in computers, PCs, PC software and GUIs) but was unable to find options to make the corrections for the errors noted above.

How can I edit or report these errors?

Tom H

asked 08 Jun '11, 18:45

than103's gravatar image

accept rate: 0%

edited 08 Jun '11, 20:41

stephan75's gravatar image


By far and away the easiest way to mark/notify errors is to use OpenStreetBugs to mark where the error occur. How fast they are fixed will depend on how active mappers are in the local area. OpenStreetBugs is not yet integrated into the core functionality of OSM, so bugs are not immediately obvious to mappers.

Some of the problems you describe: turn restrictions, in particular, can be recognised as an 'advanced mapping technique'. This means that a certain familiarity with the basic mechanics of OSM objects and editors is needed to make such changes with confidence. For instance a typical NO RIGHT TURN requires that the way one is turning from is split at the junction point. Then the junction point ('via') the road one is turning 'from' and the road one is trying to turn in'to' are added to a turn restriction relation with the named roles. As one can see from this description its currently hard to describe this without a fair bit of OSM-specific terminology. Here is an example from my local area.

Additionally, it is useful to check that the errors genuinely exist in OSM and are not due to a partial parsing of OSM data by the application. For instance several routers ignored barrier=* tags and routed through bollards, gates etc. Another common problem with router data is that it is out-of-date and the routing problems encountered have already been fixed. A good approach is to try the route in one of the on-line routing providers (e.g., Cloudmade, OpenRouteService, Open MapQuest, Your Navigation) to see if the problem is still current. Open MapQuest is usually only minutes behind the main OSM database.

For detailed assistance with your specific issues, you can ask on the IRC channels, the Forum, or a local mailing list. The general #OSM channel on IRC is likely to be the most responsive, particularly if you can provide a permalink to the area in question.

We know that turn restrictions are not particularly well mapped. For instance I analysed the distribution of turn restrictions in Great Britain earlier in the year and many administrative districts did not have any mapped at all. So we really welcome information and contributions which can improve the OSM data in this respect.

permanent link

answered 08 Jun '11, 19:27

SK53's gravatar image

SK53 ♦
accept rate: 22%

... and further you have to investigate whether the OSM data contains already the necessary turn restrictions or similar routing relevant rules AND whether the navigating program (like NavDroyd) pays attention to that rules.

(08 Jun '11, 20:39) stephan75

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 08 Jun '11, 18:45

question was seen: 4,278 times

last updated: 08 Jun '11, 20:41

NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum