Thanks for your time!
The other topic is about working around the absence of being able to filter turns on highways (similar to u_turn_costs but on highways) which may be related to this, but I’m keen to treat the topics seperately.
This topic is about Australian country rules more generally and whether it should be in the maps dataset or implemented as a country rule.
So, in this topic, to answer your question, most states and territories in Australia have a rule like this:
40 Making a U-turn at an intersection with traffic lights
A driver must not make a U-turn at an intersection with traffic lights unless there is a U-turn permitted sign at the intersection.
Maximum penalty—20 penalty units.
Note.
Intersection and traffic lights are defined in the Dictionary.
– NSW Government, Road Rules Act 2014, Division 4 U-Turns, Clause 40
(https://legislation.nsw.gov.au/view/whole/html/inforce/2024-10-31/sl-2014-0758)
Another way to implement this would be to find every traffic light intersection in the affected state and territory and add a “No U-Turn” symbol at that intersection, even though a sign may not exist.
If that’s the preferred solution, I’d be concerned about the overhead in remembering the application of the road rules vs what’s actually evident on the road could lead to mistakes as the map data is developed and bitrot of the data.
Partly this is because this particular road rule is quite dangerous if ignored. If Graphhopper suggests to a user to follow a route then I would expect that route to be legal, at the very least. Where there is a “No U-Turn” sign that could be understandable, but where it’s a road rule with no visible prompt to the user then it’s important that the data is either correct or that there’s some other mechanism to take into account these more general regional rules when planning the route.
We’d be keen to help with this with code or testing but we don’t want to do that without first understanding the design plan for these things
Thanks again!.