Google Bike/Driving Route doesn't always correctly reflect PlusCode/pin

[rhigman]

Not sure if this is fixable or a Google Maps quirk, but noting for reference:

When you give Google Maps a PlusCode, it helpfully shows you a human-readable/copy-pastable address as well as displaying an appropriate pin on the onscreen map. The pin is accurate. The address may not be.

When we try to generate the Google Bike/Driving Routes from the PlusCodes, Google Maps appears to translate them under the covers into the human-readable addresses before sticking them into the Directions panel. Therefore, the destination "dots" on the map won't necessarily be where the pins are, but instead might reflect the (inaccurate) addresses.

Example: pin (accurate) displayed when clicking individual Google Maps link in app:

Vs dot (incorrect) displayed as part of Bike/Driving route:

(obviously as anonymised as I can make it, but can share the specific example privately)

[rhigman]

Coders chat:

There's probably very little we can do to change the way Google Maps works. What we can do is massage people's expectations when they hit the buttons in our app.

So if the "see whole route" button was labelled ROUTE OVERVIEW or PRE-SHIFT HIGH-LEVEL OVERVIEW or similar, people maybe won't try to use it for navigation.

And if the per-recipient buttons were labelled TAKE ME THERE! –> or similar, people might be more inclined to use those for navigation, as is the intention.