Feature Request: Reverse Geolocation #133
Labels
No labels
Code
Contacts
Design
F-Droid
IndieWeb
Location
Mastodon
Media
Pixelfed
Pleroma
Posting
Question
Reader
Tracker
Translation
Usability
bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
inhji/indiepass-android#133
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This isn't a bug report. It is a feature request, but there isn't an option for that...
https://developer.android.com/training/location/display-address
Would like to propose that the location property optionally does reverse geocoding. It can send a more detailed location property...
Specifically, the location property can be, if you use json encoding, a nested h-adr with the coordinates and details on the location.
I've been doing this on the backend, but Android has a native integration for it, it looks like.
Oh wow, this is cool. I always thought you'd need an external service for this, although I can imagine, geocoder probably connects with Google .. :)
(ps: I've added the feature request template as well)
As a follow up to this, what about an optional textbox for a textual location description as a precursor to trying to figure it out yourself?
The property is location for textual address, but if you also have coordinates you would need a nested h-adr.
What if I implement a Micropub query for the location name?
So you can query the endpoint?
So that the endpoint does the reverse geolocation based on coordinates ? That might be an option yes, especially for phones that do not support it. But let me get it working natively first.
I have the functionality, I just have to tie it to the query as outlined in the https://indieweb.org/Micropub-brainstorming#Query_for_places
https://github.com/indieweb/micropub-extensions/issues/6
I've outlined the return I've implemented in the above issue. You can query by uri=geouri or lat=&lon= and it will return a venue and a geo property. I'm only returning the geo property, which contains a name property for the suggested name right now.
Ok, there's now an optional label field and a query button to search on q=geo.
If there's a location name, it's appended to the geoUri:
It's a setting underneath 'Posts' to expose two new features.
will release tomorrow!
Yay!!