As discussed via the mailing-list [1], the Virtuoso AWS AMI (PAGO) is supposed to be “geoSPARQL-enabled”, but I’m not sure this is the case since if I try to use the GeoSPARQL function sfContains (instead of the built-in bif:st_contains) I get:
So AWS AMI 8.2 has no GeoSPARQL support enabled.
I’m now on 8.3 and GeoSPARQL seems to be enabled.
Nevertheless when I run Query 1 from Virtuoso GeoSPARQL Demo Server I get zero objects: two are expected.
Can you please debug this?
Do all of the sample GeoSPARQL queries on the Virtuoso GeoSPARQL Demo Server fail or is it just the Protected SPARQL Query Service query ? As I find it strange you indicate that your GeoSPARQL queries against your datasets work, but note those from the Virtuoso GeoSPARQL Demo Server that we use to test this functionality ? Are you loading the datasets into the same graph name or another graph name and changing the graph name in the query. Is you AWS AMI publicly accessible so we can see the actual problem queries ?
If you enable the Virtuoso Sponger Middleware you could sponge (RDF’ize) the RDF dataset directly into your local Virtuoso instance at query runtime, with the DEFINE get:soft "soft" or other Virtuoso SPARQL pragma …