qwaletee wrote:This sounds like a good addition to explore. In general, segments in box intersections and the like need to follow similar rules to AGC, which is coarsely summarized as the lower of the two highest segment types being connected.
So, for example, usually the end of an MH roadway that turns into, say, mH, will be connected at an intersection that contains another MH or a Fwy. In that case, the crossing segment needs to be MH for continuity. If for some reason the MH ended at a junction that was all mH for the other connections, the crossing segment would not need to be MH.
Also, for AGC's, it would be nice to have some more defined examples of when not to add an AGC. Possibly highlight "When in doubt, leave it out." in bold.
Or add some type of instruction saying that if an AGC, with no physical median, results in a
straight segment that is shorter than X ft/m...
SE Wisconsin is pretty crazy on them example:
This is normal to find there, and it's kind of hard for me to lay down the law, since there are a lot of places in Milwaukee where they are genuinely needed... then new editors see them, and start adding them where they aren't, and seasoned editors still have flashbacks of MP's showing up EVERYWHERE (back in WME's infancy) and start adding them. There have been a few intersections that had right turn AGC's, in rural areas, that I noticed in the client, that I'm sure wouldn't create an MP now, but Bigbear was convinced that they would show up if he removed the AGC's, so I didn't push the issue.
Then they're everywhere.