The other week OSMAnd gave me some weird instructions to get off of State Route 9 onto 2nd Street in Snohomish (screenshot of the area below). The instructions said to “stay right” which seemed like it was treating the exit as a fork in the road instead of an exit.
The actual signage there calls it an exit, although it doesn’t have a number like exits on I5. How should the tags on the trunk links be adjusted so navigation properly announces this as an exit instead of describing it as a fork?
I don’t know if it’s “proper”, but here in Ontario we have a bunch of highway=motorway_junction nodes on trunks, including noref=yes if applicable
e.g. Node: 495598206 | OpenStreetMap or Node: 169 (366469779) | OpenStreetMap or Node: 1616233549 | OpenStreetMap
But having just tried it, exiting at 495598206 (noref=yes) gets listed in OsmAnd as “turn slightly right” 
Routing via Node: 19 (1511904402) | OpenStreetMap (on trunk, has a ref) also gives “keep right”.
So maybe it’s also an OsmAnd thing?
OSRM says “take the ramp on the right”, GraphHopper says “keep right and take 35 toward [destination]”, Valhalla says “take exit 19”
Thanks for the detailed info. I didn’t know OSM had online routing with different engines like that. I’ve edited the specific node to my original post in case that helps, something else new I learned could be done today. 
Similar to your example Valhalla and OSRM say to take the ramp or exit. So I guess it’s an OSMAnd thing.
Is there a way for me to experiment with different tags in OSMAnd without committing changes to the map and having to wait a month for the next update? Not sure if changes done in the editor will be used for routing on the device.
An issue has been opened here: Routing instructions: keep right (fork) instead of take exit on the right · Issue #21296 · osmandapp/OsmAnd · GitHub
Might be helpful if some folks could contribute samples.
