PesachZ wrote:Only because pass asked is to stop disallowing the u-turns at dead end nodes, so that they can see if their fix is working, and tweak it to work better anytime, its found to have failed.
Taco909 wrote:Unless we are in the UK, we are not supposed to do this anymore... we've been asked in multiple threads by various global champs and Waze staffers.
Validator needs to ignore the u-turn, and the "Q" function in JNF needs to be changed so it likewise ignores u-turns if they are at a dead-end.
To the contrary there is no reason to believe that all of the Google map data suppliers entered into agreements that include using the data for waze.ditchi56 wrote:- there's no reason to remove the link to Google maps since Google own Waze, they're not going to object to their own property being enhanced?
OpenStreetMaps is certainly not copyright free. See here and here.ditchi56 wrote:- there's no reason to remove the link to OpenStreetMap since that prides itself on being copyright-free?
sketch wrote:As for the early instructions, IMO it's better as an editor to lay the departing segment just next to, but not directly coincident with, the continuing segment.Taco909 wrote:Likewise, there may be some cases where it is desired to execute the turn instruction early, but to overlay the departing segment onto the feeder segment for a short distance.
Understood. I agree that the closure feature would remain deeply flawed even if we never used narrow angles on the map.sketch wrote:I will not edit the map to enable a feature that doesn't really work anyway. That feature needs a lot of work, and it's not up to us to fix it.
Users browsing this forum: rccoros