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.
pumrum wrote:If you are stuck, try resetting the validator. Make sure "Exclude non-editable segments" is not checked after your reset, and set the custom filter again. Once you have verified manually that it is highlighting as expected, you can run a report. If you want to only see the custom filter results, set the "Reported as" filter to 128 (green) or 129 (blue) or 128,129 (green and blue)
berestovskyy wrote:crazycaveman wrote:Am I missing something with regards to negated regex's?
The report is cleared automatically once you change either a template or a regexp field. I guess you changed your custom check after the scan has been completed. This is my best guess. A permalink would help.
Users browsing this forum: Google [Bot], Smesh1337