simonpoole left a comment (openstreetmap/openstreetmap-website#1807)
May I point out that modifying geo URIs to support anything else that WGS84
coordinates is not, lets say, a great idea.
It would change a single, easy to support, universally the same URI format, in
to something for which you have no idea of if the consuming application will
actually support it or not. The case of using OLCs adds a notch of silliness to
that as the decoded OLC data would _just _work_ in a regular geo: URI. I would
note that the geo URI specification does actually provide for a different CRS,
but it doesn't make any sense to exercise that.
It's a not totally unreasonable _make things easy_ change to support geo: URI
as input to the search box simply as an alternative way to input coordinates
without having to copy them out of the URI, however that is a bit off topic
here (I added support for that in Vespucci a while back
https://github.com/MarcusWolschon/osmeditor4android/pull/2758).
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-2868673481
You are receiving this because you commented.
Message ID:
<openstreetmap/openstreetmap-website/issues/1807/2868673...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
