"Mini onramp/offramp" -- when to model with right angles?
Small roads that meet large roads between major intersections -- such as parking-lot feeder roads -- often involve an angled/curved "miniature offramp" from the main road and an angled/curved "miniature onramp" returning to it. For example:
https://www.waze.com/editor/?env=usa&lo ... 1,68884045
Representing these literally using AGC constructions, as shown in the example, is extremely popular. But is that really the best solution in most cases? I'd like to understand the tradeoffs of modeling them with AGC constructions versus ordinary right-angle junctions.
The pros of using AGC constructions include:
- Advances timing of voice alert
- "Exit" voice instruction may sometimes make more sense than "turn"
- No instruction given when joining main road, so Waze less chatty
- Matches satellite image, a more literal representation of what's there
The cons include:
- Advanced voice alert may conflict with nearby turns; distance to actual road will be off
- "Turn" instruction at "offramp" will in many (most?) cases make more sense than "exit"
- Any turn instructions at "onramp" will be for NEXT junction, not this one, possibly confusing
- New editors may view as role model for matching the satellite image even at high zoom
- Display of diagonal segments may confuse drivers if real junctions are logically right-angle
- Additional map complexity, especially when only short distances involved
I would propose a more aggressive perspective that these intersection types (do they have a name?) be preferentially modeled as right-angle junctions, with the "burden of proof" resting on the the idea of making them into mini onramp/offramp AGC-type intersections. Thoughts?
https://www.waze.com/editor/?env=usa&lo ... 1,68884045
Representing these literally using AGC constructions, as shown in the example, is extremely popular. But is that really the best solution in most cases? I'd like to understand the tradeoffs of modeling them with AGC constructions versus ordinary right-angle junctions.
The pros of using AGC constructions include:
- Advances timing of voice alert
- "Exit" voice instruction may sometimes make more sense than "turn"
- No instruction given when joining main road, so Waze less chatty
- Matches satellite image, a more literal representation of what's there
The cons include:
- Advanced voice alert may conflict with nearby turns; distance to actual road will be off
- "Turn" instruction at "offramp" will in many (most?) cases make more sense than "exit"
- Any turn instructions at "onramp" will be for NEXT junction, not this one, possibly confusing
- New editors may view as role model for matching the satellite image even at high zoom
- Display of diagonal segments may confuse drivers if real junctions are logically right-angle
- Additional map complexity, especially when only short distances involved
I would propose a more aggressive perspective that these intersection types (do they have a name?) be preferentially modeled as right-angle junctions, with the "burden of proof" resting on the the idea of making them into mini onramp/offramp AGC-type intersections. Thoughts?
Re: "Mini onramp/offramp" -- when to model with right angles