Kartografer wrote:

Since different conditions result in different penalties, and since these values can be changed at any time, mixing penalized segment properties such as road type transition penalties in an area can result in unexpected and/or unstable routing results.

IMO this is a general page on penalties, and getting into more specifics on how to map parking lots and private developments should be kept on separate pages.

'https://wazeopedia.waze.com/wiki/USA/Routing_penalties#Road_configurations' wrote:Waze will penalize a route (which forms a U-turn) with two left turns in less than 52.49 ft (16 m) in right-hand traffic jurisdictions or with two right turns in less than 52.49 ft (16 m) in left-hand traffic jurisdictions.

ojlaw wrote:i thought the decision point for U-turns was exactly 15m and we used 14m to disallow and 16m to allow in case editors were not using a script to show exact segment length. is that correct?

U-turn minimum template page wrote:The gap in the two thresholds is due to metric and imperial rounding issues, so a buffer was built into this setting to prevent unexpected results

ojlaw wrote:just wondering if we would be better served documenting the exact number and then explaining why 14m and 16m are used

Kartografer wrote:Isn't this basically what the private installations page already talks about? My draft says now that PR, PLR and OR have different transition penalties. I could see adding maybe one sentence after my note about default nav settings to say

Since different conditions result in different penalties, and since these values can be changed at any time, mixing penalized segment properties such as road type transition penalties in an area can result in unexpected and/or unstable routing results.

IMO this is a general page on penalties, and getting into more specifics on how to map parking lots and private developments should be kept on separate pages.