My Level: 4
Reason for request: Want to announce exit as per the green signs that say East and West rather than “turn right on Sheppard Avenue East”. This is confusing to drivers since the turn is signed as West. There is adjacent UR. I propose to add a microsegment like I did here:
https://www.waze.com/editor/?env=usa&lon=-79.38160&lat=43.72749&zoom=10&segments=505557386
Alternative would be AGC.
Unlocked. Your first example on Lawrence Ave with the microsegment is going to cause routing issues at some point if it hasn’t done so already. You’ve got some segments as short as 1m and some as 3m in length. The shortest segment that the map can manage is 5m, anything shorter the cross times can’t be tracked and will cause routing failures.
For an example of an appropriate segment stub for TTS purposes can be seen here:
https://www.waze.com/editor/?env=usa&lon=-122.89323&lat=49.26285&zoom=8&segments=87259173
In this case the stub is used to match the street signage. In your case you can change the segment to the name you want. Depending on the text string you want to use, you may need to use the ramp segment type to ensure the text doesn’t show on the map. In any case, please ensure you add a map comment as these stub segments are a hack that we should be able to remove once we have more control over TTS.
Fixed. Please check. The example given was done with local champ review and before map comments. I’ve added one now.
I’ve taken a slightly different strategy here based on your comments about segment length. Let me know your thoughts. I think it is a better hack.
That solution you’ve implemented will work from a TTS perspective. Do you know how busy this intersection is? I would be concerned that adding those segments may still screw up cross time tracking. Why not just add a normal ramp segment where the solid line starts for the right turn and give that the appropriate name? I typically don’t suggest AGCs as I believe they are over-used, particularly short ones like this, but I think it’s appropriate in this case to give the correct TTS to match the BGS. I’ve also adjusted your example to have segment lengths at least 5m in length.
I wasn’t sure it met the criteria so was hoping to get guidance on whether to use an AGC. It is probably better here as you suggested. I’ve updated the intersection. Please relock. This is a fairly busy intersection.
In the example location, I think tucking the road segment in close is more aesthetically pleasing. The curved AGC doesn’t match the road. I can understand how the original microsegments might not provide proper cross times but I don’t see how that would have a significant effect on routing. I would imagine it would be implemented with a very small default cross time which would make the segment very “fast” but that would be offset by the short length.
Adjust the connector segments in your example as you wish. It would probably need to be looked at in the app to see how it looks, but at those distances, I think the way I drew it should be OK. In terms of how this affects routing, it can cause complete failures, not just cross time tracking issues, just complete failures either not using the junctions at all, or causing “Uh oh” routing timeouts.
I didn’t suggest the AGC in the first place as I wasn’t sure what you were needing to change to get what you were looking for.
I’ve relocked the segments.