Repository navigation
Query for Location/Venue #6
Description
Brainstorming the proposed extension of querying for venues. The proposal https://indieweb.org/Micropub-brainstorming#Query_for_places uses q=geo=uri or :uri which seems confusing. I'd personally rather pass through individual parameters, lat, lon, u to query for.
q=geo&lat=10&lon=20 etc
Suggesting two return variables...
geo, indicating a default suggestion for the location and venues, indicating a series of possible venue suggestions. Not all sites would implement both. So, this would allow for simple location retrieval or a venue picker for check-ins to a url.
Return format for location would be name, lat, lon, optionally a full h-adr.
Activity
dshanske commentedon Dec 20, 2018
I have implemented a basic version of this for testing.
It supports the variables lat and lon or a single variable uri for geo URIs. There are two returns, venues or geo. Geo is a suggested location, venues would be a list of possible nearby venues. I am not returning any yet. And my return doesn't include specific properties for the location, even though I outlined that above. Just a name property.
{
"venues":[],
"geo":{
"name":"Queens, NY, USA","latitude":"xxxx","longitude":"yyyyy"}
}
dshanske commentedon Feb 16, 2019
It should be label, not name on the return as it is supposed to be an h-adr
dshanske commentedon Mar 3, 2019
Expanding on this thought to propose the following query choices..In all cases, q must equal geo, but, optional query parameters should be either:
or:
I think allowing both of these would be preferable.
dshanske commentedon Mar 3, 2019
Outlined an example return. All returns would follow the common properties of an h-adr object with only label and latitude/longitude being mandatory. The visibility property would reflect the experimental location-visibility Micropub property outlined on the extensions page.
{ "geo": [ "label" : "123 Main Street", "latitude": "18.1123", "longitude": "-72.1933", "visibility": "public", ], "venues": [ { "label" : "Main Street Apothecary", "latitude": "18.1123", "longitude": "-72.1931", "url": "https://example.com/venues/apothecary", }, { "label" : "Main Street Market", "latitude": "18.1123", "longitude": "-72.1931", "url": "https://example.com/venues/market", }, ] }swentel commentedon Mar 6, 2019
The Drupal module now supports q=geo too. Geo is returned, if anything is found of course. Venues not yet, but that will come once I started on Indigenous supporting venues selection.
swentel commentedon Mar 6, 2019
Oh, re: query parameters - I'd love to just keep one format. Currently latitude and longitude as query params are used in the Drupal module too. Makes it less complex imo.
swentel commentedon Mar 7, 2019
As for 'venues' property in the response, maybe that should be 'places' ?
dshanske commentedon Mar 8, 2019
I'm fine with it being places. No one has implemented it yet anyway.
Also, I prefer the individual parameters myself.
swentel commentedon Mar 8, 2019
Ok, the Drupal module documents to return an array of 'places' now, see swentel/indieweb#393
swentel commentedon Dec 3, 2019
Indigenous supports the 'places' parameter in the upcoming release. If places are found, the location name field will have suggestions from the location query response.
dshanske commentedon Jul 25, 2020
Feedback at Micropub Popup Session 2020 was that this requires more research to document use cases and prior art. Furthermore, the venues property should use h-card, not h-adr syntax.
dshanske commentedon Jul 26, 2020
The use cases for this particular query would be twofold: