Biggiejohn wrote:jeanphilippedrouin78 wrote:It seems that in my area someone crossed that line and it doesn't help anyone stuck with a lot of navigation errors.
I would say that if you lock a segment, you better be 100% certain that the position of every road, every name and every turn is 100% accurate, and be willing and able to maintain that segment if anything changes.
AndyPoms wrote:Things I regularly lock:
- High value roads (these are limited access for the most part) & their ramps (once named properly)
- Overly complex intersections (once routing is working properly)
- New construction that does not match the aerial photo (so new editors/IGN don't delete and redraw to match photo)
- Areas subject to repeated unnecessary changes (i.e. two editors going back and forth on split vs. unsplit)
- Changes as documented on the Connecticut Construction wiki page (so new editors don't accidentally reconnect things)
- Areas subject to vandalism
I respond to PMs & unlock requests in the forum within 24 hours (usually less).
jasonh300 wrote:Also, remember that it's possible that someone of a lower level locked those roads, and then joe01romano came through and did some editing, and upon saving, inadvertently raised the lock level.
Sorry it was me and you're right it was rude. Could you please accept my apology. Do you have any suggestion in how I should turn your attention into map problems in order to have the maximum efficiency?EECGeek wrote:One thing I don't like is whoever is reporting errors, some have been somewhat rude.
WeeeZer14 wrote:Sounds like he is editing both Waze maps and Google Maps at the same time. So neither is getting his full attention.
Now if a copyright infringement claim comes up, it could look like data was copied between the two systems since the same person made the edits in both places.
Users browsing this forum: Google [Bot], Google Feedfetcher