Closed kad-beekw closed 3 years ago
Thank you for notifying me the change. As suggested, I added the new pair of geospatial properties. It works fine on my side with your endpoint. Please double-check.
I also added sdo: (the https one) and schema: (the http one) as a default prefixes for more conventional SPARQL queries (visible in the YASGUI view).
Important note: if properties schema:position and/or schema:logo properties were used to control the display of suggestions, they need to be replaced by the sdo: versions.
@sebferre Thanks for looking into this!
I do not see the map functionality yet. This is how it looks on my side:
^ I'm expecting the "Map" tab to become active.
(This is with the online version that is tagged "Last modified May 26th, 2021" at the bottom of the web page.)
Here is the query that shows a map. To get the map, the special suggestion 'that has a geolocation' must be selected rather than individual properties for latitude and longitude. Benefits: a single selection, a trigger for the map, latitude and longitude columns are not shown in the table of results.
Thanks @sebferre ! The "has a geolocation" option works well. Closing...
Thanks for creating this great query builder!
I notice that geospatial data is specifically extracted for the Schema.org vocabulary (placed in the code where this happens).
This currently uses the old
http://schema.org/
prefix. In more recent versions, Schema.org switched to thehttps://schema.org/
prefix (notice thes
). Could variants for this new prefix be added to the Sparklis configuration? I can imagine that the old prefix will still be used by some people for some amount of time.I am specifically looking at the two geospatial properties with Schema.org prefix (
sdo:latitude
andsdo:longitude
), but the same may apply for other places in Sparklis where Schema.org may be used for other purposes.For testing purposes you can make used of the following query over our endpoint: https://rebrand.ly/yvuputi