Feature Request: Reverse Geolocation #133

Closed
opened 2018-10-16 03:38:12 +02:00 by dshanske · 11 comments
dshanske commented 2018-10-16 03:38:12 +02:00 (Migrated from github.com)

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.

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.
swentel commented 2018-10-16 09:47:42 +02:00 (Migrated from github.com)

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)

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)
dshanske commented 2018-11-15 15:00:11 +01:00 (Migrated from github.com)

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?

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?
dshanske commented 2018-11-15 15:41:46 +01:00 (Migrated from github.com)

The property is location for textual address, but if you also have coordinates you would need a nested h-adr.

The property is location for textual address, but if you also have coordinates you would need a nested h-adr.
dshanske commented 2018-11-15 16:57:02 +01:00 (Migrated from github.com)

What if I implement a Micropub query for the location name?

What if I implement a Micropub query for the location name?
dshanske commented 2018-11-15 16:57:15 +01:00 (Migrated from github.com)

So you can query the endpoint?

So you can query the endpoint?
swentel commented 2018-11-19 21:07:27 +01:00 (Migrated from github.com)

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.

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.
dshanske commented 2018-11-19 21:30:02 +01:00 (Migrated from github.com)

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

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
dshanske commented 2018-12-20 13:57:29 +01:00 (Migrated from github.com)

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.

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.
swentel commented 2019-02-16 23:26:56 +01:00 (Migrated from github.com)

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:

geo:51.019903,3.7716038,0.0;name=Melle Vogelhoek

It's a setting underneath 'Posts' to expose two new features.

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: ``` geo:51.019903,3.7716038,0.0;name=Melle Vogelhoek ``` It's a setting underneath 'Posts' to expose two new features.
swentel commented 2019-02-16 23:28:47 +01:00 (Migrated from github.com)

will release tomorrow!

will release tomorrow!
dshanske commented 2019-02-16 23:29:31 +01:00 (Migrated from github.com)

Yay!!

Yay!!
This discussion has been locked. Commenting is limited to contributors.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
inhji/indiepass-android#133
No description provided.