Re: [Virtuoso-users] geospatial selection: st_distance vs. st_intersects

Hi Markus, If you are seeing this behaviour from isql then why not provide the command line out of the query executions showing this behaviour ? As this works for me against our LOD Cloud Cache server: SQL> SPARQL PREFIX rdfs: PREFIX ogc:

Re: [Virtuoso-users] geospatial selection: st_distance vs. st_intersects

Hi Hugh, I used the isql CLI provided by Virtuoso to run the queries and to my knowledge premature termination of query evaluation by Anytime does not apply there. (Please correct me if I am mistaken.) Regards, Markus On 16/01/15 02:41, Hugh Williams wrote: > Hi Markus, > > I ran the query a

Re: [Virtuoso-users] geospatial selection: st_distance vs. st_intersects

Hi Markus, I ran the query against our LOD Cloud Cache server hosting 60+billion LOD datasets (http://lod.openlinksw.com) including the LGD datasets, and found the query with Filter A returned 4 results as you indicated returning immediately. Running the query with Filter B it takes appreciably

[Virtuoso-users] geospatial selection: st_distance vs. st_intersects

Hi, testing some geospatial SPARQL queries using a build of the latest commit from the developt/7 branch (thus VOS OpenSource 07.10.3211)on the LinkedGeoData Dumps from Sep 9 2014 ([1]) I encountered unexpected discrepancy between the selectiveness of st_intersects versus giving an upper bound t