NJ-20 & Broadway, Fair Lawn

I’m a little confused by the elevations for the four segments of NJ-20 and Broadway (no longer NJ-4 here) that intersect here: https://www.waze.com/editor/?zoom=8&lat=40.91809&lon=-74.13126&layers=TBFTFFTTTTTTTFTTTTTTTTTTTT&env=usa&segments=70941442
Broadway East is listed as Ground level. Broadway West is listed as +2. NJ-20 South is listed as -2. NJ-20 North is listed as +1.

NJ-20 (both ways) is actually at ground level (and very nearly river level: it floods here when the Passaic rises). Broadway is on a bridge over NJ-20. Both directions are on the same bridge.

Is there a reason for the odd elevations, or is this something that should be fixed?

It looks like someone just added some levels to make sure that segments didn’t accidentally intersect. You’re right about Route 20 being at river level and Broadway/Route 4 being elevated above it. Since Route 20 is locked at Rank 5, you’ll probably want to talk with Orbitc about adjustments with that one. As for Broadway/Route 4, I went in and cleaned up the elevation a bit when I helped with the other fix you needed. It’s set at +1 over SR-20 and River Rd in Paterson and Fair Lawn now for some consistency.

The Editor is NOT saving changes right now (that is IF you can log-in). See https://www.waze.com/forum/viewtopic.php?f=8&t=74906 for details.

As for elevation “Ground” used to be “0” (zero) - and we used to use to keep all roads at zero and then when there were overpasses/underpasses the road of lower type was changed. Freeways should have the longest segments with several over/underpasses - so with that set to zero, all the cross streets (typically much shorter) would be changed to either “+1” or “-1” so you don’t have to figure out the correct elevation of huge stretches of interstate (as it goes over some and under others) the numbers would get all confusing. It’s bad enough when dealing with stacked interchanges trying to keep everything organized - imagine trying to do that for every interstate or limited access road in the country.

Right. I ran into the loading problem a few minutes ago. I had a session open from last night that appeared to make changes before everything went funky and prevented logins, and I’ll double check when there appears to be news of things being back up and running.

Also, that was the intention behind me setting Broadway to be +1. With SR-20 as the most major highway in the area, that would be the one that should get the “Ground” level. It just needs a higher editor to fix a segment or two when things are back up and running since it has Rank 5 locks that were set before the current standard of elevation levels.

This is a fairly simple intersection - I would make 20 ground level and Broadway Level 1. Currently they are both Elevation 1, and that is not correct, since the system could mistakenly create junction nodes that way. Has anyone posted this to the unlock/update forum?

Also, what’s up with the unorthodox road type here? Why would we have a nameless standard road type way-finder segment followed by a longer ramp?

WME was not working earlier. And what you suggest is what what was discussed & planned, but since edits weren’t saving, it couldn’t be done.

It forces a “Keep Right” and “Keep Left” indicator other wise it would be a “Keep Left” and nothing when Waze wanted you to keep right.

Just posted this to the unlock/update forum. Thanks all for the feedback.