Various interactions can result in incorrect location
jywarren opened this issue · comments
This needs to be broken out further, but is mostly due to hard-to-predict user interface sequences. One example is:
- open the demo:
- enter
577 somerville ave
and click enter - pan slightly, moving the map center but not changing the "box" that's highlighted
- turn off "blur my location" with the checkbox
- zoom in by double clicking 5 times or so but not exactly on the marker
So, this sequence, at steps 3 and 5, drifts off the original location, but that might not be apparent to a new user of this tool. "577 Somerville Ave" is still displayed.
There are probably other similar sequences that could cause confusion.
What can we do?
1. [ ] Reverse geocode while you drag - display textual location like "Buffalo, NY" when you pan the map over that city, using getPlacenameFromCoordinates()
-- making an issue for this. That'll help a bit.
UPDATE: reverse geocoding already exists? Why isn't it working in this scenario?
OK -- reverse geocoding DOES work. It's more subtle than that.
- open the demo
- begin dragging the map, see the bottom location box fill
But then break it:
- type "germany" into the top input
- pan again, and the bottom remains "Germany"
Originally this was to ensure that the placename entered above "takes precedence" over any panning.
I think we need a different rule. Once we have a conflict -- if the map location no longer corresponds to the text location, because we:
- searched by text
- then panned
THEN we should display a notice below the map that says The map has moved away from the location you searched for. Want to _re-center on the original location_ or _update the textual description_?
With two links offering to do that with geocoding or reverse geocoding with our API.
@ebarry @mridulnagpal how does that sound? This was pretty subtle but i think this may cover a lot of possible confusing sequences!
Hi Liz, this seems like an unrelated issue, actually -- would you mind opening a new issue with this? Thank you!
@jywarren Is this still an issue?
This is done!