Best Editing Practices being ignored (at-grade connectors)

I noticed that existing connectors (at-grade “ramps”), many of which I have drawn, are being changed by area managers in North Carolina in violation of the Best Editing Practices.

http://www.waze.com/wiki/index.php/At-Grade_Connectors#How_to_label_the_connector_type

The connector segment’s type should be set based on the lowest of the types of roads it connects.
Ex: Street to Minor Highway should be Street type.
Ex: Minor Highway to Primary Street should be Primary Street type.
Ex: Primary Street to Primary Street should be Primary Street type.

When these connectors/ramps are not between regular street types, (for most situations) the connector should also not be a regular street type. There is a very good reason for this: It will affect routing, because for long distances, waze will try to avoid these regular streets. In this and other areas where you artifically switch back and forth between road types or have incorrect road types, it will affect routing.

Thanks.

Do you have an example and was it me?

https://www.waze.com/editor/?zoom=7&lat=35.18382&lon=-80.75645&layers=BFTFTTTTTTFTFTTFTTTTFT&segments=62713200,66177640
(I fixed it and then changed one of them back, since it was an example of what I have found.)

Sorry for the delay in this post, but are at grade connectors even really necessary for this intersection. It is just a small island that is dividing the main road. I am of the opinion it doesn’t really need a seperate connector for it.

The islands are small, but the deviation distance and angles seem to beg for connectors. I’m pretty sure this would generate automated map errors.

I haven’t seen an island that small generate one but that doesn’t mean it wouldn’t. Just not my experience.

I can attest to firsthand knowledge of intersections like this causing problems. It causes a system error about the roads being too far apart. I’ve fixed maybe 15 or so in the San Antonio/Austin areas. The system catches Wazers GPS using the grade connectors and recognizes there is not a road there, thus generating the error. I don’t go around actively changing them, I just wait for the system to generate the report and I’ll fix it then. Why mess with something that’s not broken?

In any case, if the connectors are going to remain for any period of time, their type should be changed :slight_smile:

LOL. My level isn’t high enough to fix the other one. Can someone with (4) change it to “primary” please?

Fixed.

This editor is still ignoring Best Editing Practices. He has taken the intersection we discussed at length and fixed as a result of this thread and changed it back. This time he has locked them, so I can’t fix them. He has done this to multiple intersections, some which were my work, and all which I fixed the last time. This is not just in Charlotte, but I’ve seen more than I can count in Raleigh too. These Best Editing Practices have been in place for at least a year and we’ve been told that lower street types have an effect on long distance routing.

the intersection I’ve referenced here: https://www.waze.com/editor/?zoom=7&lat=35.18382&lon=-80.75645&layers=BFTFTTTTTTFTFTTFTTTTFT&segments=62713200,66177640

another example
https://www.waze.com/editor/?zoom=6&lat=35.18363&lon=-80.75614&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=62713200,66177640

ONE I WAS ABLE TO FIX, BUT HE CHANGED and LOCKED IMMEDIATELY AFTER
https://www.waze.com/editor/?zoom=6&lat=35.23342&lon=-80.84753&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=63348397

https://www.waze.com/editor/?zoom=6&lat=35.90164&lon=-78.78998&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=65118731

https://www.waze.com/editor/?zoom=6&lat=35.94538&lon=-78.83665&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=63610568,63341645

https://www.waze.com/editor/?zoom=6&lat=35.94913&lon=-78.83726&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=63415203,35015161,63415163

For reference, here is my original post and reasoning from July 2012:

I went ahead and fixed them back.

First two permalinks were the same intersection. I updated that one. (txemt started with the list after those two :wink: )

Thanks everyone!

He undid your work again, on these two intersections. I can’t fix because he locked them.

https://www.waze.com/editor/?zoom=6&lat=35.90164&lon=-78.78998&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=65118731

https://www.waze.com/editor/?zoom=6&lat=35.20463&lon=-80.83468&layers=BFTFFTTTTTTFTTTTFTTTTFT&segments=63601635,70323250

Refixed.

On the second link I fixed the turn right hand turn restriction as well on the one heading north. I am not even sure if we need a separate turning lane on that one. I haven’t seen any automatic UR’s being generated there but that could be I might not have seen them.

Locked, but needs to be primary street. Thanks!
https://www.waze.com/editor/?zoom=6&lat=35.23892&lon=-80.8255&layers=BFTFFTTTTTTTTTTTFTTTTFT&segments=36123671
https://www.waze.com/editor/?zoom=6&lat=35.2426&lon=-80.77872&layers=BFTFFTTTTTTTTTTTFTTTTFT&segments=63598104
https://www.waze.com/editor/?zoom=6&lat=35.23607&lon=-80.77395&layers=BFTFFTTTTTTTTTTTFTTTTFT&segments=63698478

Fixed

https://www.waze.com/editor/?zoom=6&lat=35.1841&lon=-80.76128&layers=BFTFFTTTTTTTTTTTFTTTTFT&segments=66790429,66790420
THANKS!

Fixed.