How to bing geospatial point from sql to stardog

Support
1 
MAPPING <urn:r2m2l_3657b6d8_a79a_4698_b3fb_e54f0e7eb746_1223895>
FROM SQL {
  SELECT *
  FROM `Hackathon_Exercise`.`adsb_signal`
}
TO {
  ?subject a geo:hasGeometry .
  ?subject <http://api.stardog.com/adsb_signal#aircraft_id> ?aircraft_id .
  ?subject <http://api.stardog.com/adsb_signal#altitude> ?altitude_double .
  ?subject <http://api.stardog.com/adsb_signal#ground_speed> ?ground_speed_double .
  ?subject <http://api.stardog.com/adsb_signal#heading> ?heading_double .
  ?subject <http://api.stardog.com/adsb_signal#latitude> ?latitude_double .
  ?subject <http://api.stardog.com/adsb_signal#location> ?location .
  ?subject <http://api.stardog.com/adsb_signal#longitude> ?longitude_double .
  ?subject <http://api.stardog.com/adsb_signal#ref-aircraft_id> ?ref_aircraft_id .
  ?subject <http://api.stardog.com/adsb_signal#signal_id> ?signal_id .
  ?subject <http://api.stardog.com/adsb_signal#signal_timestamp> ?signal_timestamp_dateTime .
  ?subject rdf:type :adsb_signal
} WHERE {
  BIND(StrDt(?altitude, xsd:double) AS ?altitude_double)
  BIND(StrDt(?ground_speed, xsd:double) AS ?ground_speed_double)
  BIND(StrDt(?heading, xsd:double) AS ?heading_double)
  BIND(StrDt(?latitude, xsd:double) AS ?latitude_double)
  BIND(StrDt(?longitude, xsd:double) AS ?longitude_double)
  
  BIND(StrDt(?signal_timestamp, xsd:dateTime) AS ?signal_timestamp_dateTime)
  BIND(template("http://api.stardog.com/adsb_signal/signal_id={signal_id}") AS ?subject)
  BIND(template("http://api.stardog.com/aircraft/aircraft_id={aircraft_id}") AS ?ref_aircraft_id)
}

I want to update the binding of location which is point such that i can use geosparql queries

2

Hi Dipanjan,

In general, to support geospatial queries, the geospatial data needs to be represented using the right class and properties. In your mappings, this would be something like:

?subject a geo:Geometry .
?subject wgs:lat ?latitude_double.
?subject wgs:long  ?longitude_double.
...

See also our docs for details.
Moreover, geospatial queries are currently not supported to be evaluated over Virtual Graphs. As a result, you would need to materialize the virtual data into a database (with spatial.enabled=true) first.

Best regards
Lars