Add support for geo: URI in "Goto coordinates..."

[jech]

While going for a walk, I wrote down the geo: URL of a feature that is badly tagged. While taking the bus back home, I open Vespucci, choose Find in the bottom-right menu, paste the geo: URL... and Nominatim answers Not found.

How do I point Vespucci at a geo: URL?

(The workaround is to paste the geo: URL into Organic Maps (OM), then choose Open in another app in OM, anc choose Vespucci.)

[simonpoole]

The basic assumption is that the geo: URL is somewhere in an app of browser on device, then you just have to click it.

If you have it as pure text it is somewhat more involved, paste it in to the "Go to coordinates" modal in the location menu, remove geo: and anything trailing the coordinates in the URL and click OK.

[jech]

The basic assumption is that the geo: URL is somewhere in an app of browser on device, then you just have to click it.

Unfortunately, most Android applications don't clickify geo: URLs.
Thanks for your answer.

If you have it as pure text it is somewhat more involved, paste it in to the "Go to coordinates" modal in the location menu, remove geo: and anything trailing the coordinates in the URL and click OK.

Two thoughts:

1. shouldn't the modal be able to parse various formats of coordinates, including geo: URLs?
2. why do we need two distinct menu entries (Find and Go to coordinates)? In most other applications, there's just a single search entry, and coordinate pairs in a number of formats are automatically recognised.

[simonpoole]

The goto coordinate function already handles lots of different formats and that's why I'm wary of adding more complexity, but all of them are either simple string parsing or mathematical conversions that directly return coordinates.

The 'Find' function on the other hand geocodes addresses and names via external APIs and is not the same thing at all.

[jech]

I see, thanks for your answer.

[simonpoole]

Currently I just think it is a bit of an edge case but I'll keep the request around.