Sort of the inverse: Instead of searching to find locations, click a location to find a nearby item. Google does this, I'm told.
This seems somewhat like a "reverse" search, but actually search already biases by location. So the query should be pretty easy I think.
The difficult parts will be as follows:
Nearby places will be multiple, it may be unclear which the user wants
Nearby places will not exactly be where the user clicks
Nearby places rendered on the map might not show up in search results (and vice versa)
When the user clicks, it needs to hit the network to find nearby places. This might be slow, and the user might not even need it; they might just be trying to add an arbitrary location with their own description.
Possible solutions:
When a user clicks, they bring up a blank description, with a dropdown box that slow-loads with suggested nearby locations.
Different UI for bringing up "blank" vs "search nearby". So the second category can be slow but the user is actually looking for the information that's slow coming.
Pre-load nearby search results as the user scrolls and zooms, so nearby right-click finds are instant.
Sort of the inverse: Instead of searching to find locations, click a location to find a nearby item. Google does this, I'm told.
This seems somewhat like a "reverse" search, but actually search already biases by location. So the query should be pretty easy I think.
The difficult parts will be as follows:
Possible solutions: