Looks like the GPS points finally caught up with how routes 35 & 36 are actually shaped. The system is automatically complaining the road is missing as it curves, rather than the straight shot it currently is. Several others and myself have already changed the road, then changed it back when the map editor system decided it was right and we were wrong. That being said, it finally agrees we were right in the first place. It looks like I should be able to fix it for real this time, but I wanted to keep everyone in the loop as to what’s going on with the intersection. I’m intentionally leaving the PR open. The intersection is this one: https://www.waze.com/editor/?lon=-74.05188&lat=40.29107&zoom=7&layers=BFTFFTTTTTTFTTTTFTTTTFT
EDIT 20 Feb 0913: I’ve made the changes and actually decided to go ahead a close the PR since it is now solved. I’ve attached a screenshot of the PR since now it will disappear from the map.
Just an FYI - SR-35 has actually recently been straightened at this junction, as seen here, but the aerial images are out of date. The overwhelming majority of GPS points in the WME also suggest a much straighter path for SR-35, and the current configuration of it along the old aerials will undoubtedly cause more problem pins. I’ve driven by here several times recently and can guarantee with certainty that the curve in SR-35 is no longer there.
Maybe there’s a bug in the engine that assesses those problem pins?
On a side note, is there any way to note the map that roads in an area have been recently configured and should not be changed back to the outdated aerials?
At this point, I’m not sure what to do. It seems like no matter what, the map editor will keep complaining the road is wrong. Personally, I’m tired of fighting with the system, only to have to change it every other week.
One option is, in my opinion, is to lock them. This way only level 5 editors can change. Since, we are mentioning in this forum and most of the level 5 editors check this forums often that they would be be aware.
