subject:"\[Virtuoso\-users\] ST_Intersects with complex shapes"

Re: [Virtuoso-users] ST_Intersects with complex shapes

2017-08-23 Thread Hugh Williams

Hi Raul,I note your Virtuoso build is a 07.20.3214 build from early 2016 , whereas the latest builds are 3219, available from:	https://github.com/openlink/virtuoso-opensourcethus I would suggest compiling and building from this latest archive and rerun the query to see if the problem persists ...
Best RegardsHugh WilliamsProfessional ServicesOpenLink Software, Inc.      //              http://www.openlinksw.com/Weblog   -- http://www.openlinksw.com/blogs/LinkedIn -- http://www.linkedin.com/company/openlink-software/Twitter  -- http://twitter.com/OpenLinkGoogle+  -- http://plus.google.com/100570109519069333827/Facebook -- http://www.facebook.com/OpenLinkSoftwareUniversal Data Access, Integration, and Management Technology Providers

On 22 Aug 2017, at 12:12, Raul Palma  wrote:Hi,I found a similar issue in my virtuoso to the one described in this thread: https://www.mail-archive.com/virtuoso-users@lists.sourceforge.net/msg07127.htmlI have a large dataset with complex shapes (only polygons and multipolygons). Virtuoso 42000 Error GEO..: for after check of geo intersects, some shape types (e.g., polygon rings and curves) are not yet supported However, It does not seem to be unsupported shape.I have only Polygon and Mulipolygon in the datasets.  My endpoint is here: https://www.foodie-cloud.org/sparql For instance this query (with a rectangular polygon), returns error: PREFIX geo:  SELECT *FROM WHERE {?geometry geo:asWKT ?x .  FILTER(bif:st_intersects (?x, bif:st_geomFromText("POLYGON((16.292724609375 50.6472835493678,21.434326171875 50.6472835493678,21.434326171875 49.768404561217075,16.292724609375 49.768404561217075,16.292724609375 50.6472835493678))"))) .}limit 10 If I shrink slightly the query polygon from the left side: 16.292724609375 to 16.380615234375, it works.  PREFIX geo:  SELECT *FROM WHERE {?geometry geo:asWKT ?x .  FILTER(bif:st_intersects (?x, bif:st_geomFromText("POLYGON((16.380615234375 50.6472835493678,21.434326171875 50.6472835493678,21.434326171875 49.768404561217075,16.380615234375 49.768404561217075,16.380615234375 50.6472835493678))"))) .}limit 10 If I query the area corresponding to the difference it works as well.  Do you have an idea what is the problem?Thanks in advance,Raul Raul Antonio Palma de Leon, PhDSemantic Technologies CoordinatorNetwork Services DivisionPoznań Supercomputing and Networking Center ul. Jana Pawła II 1061-139 Poznanphone: (+48 61) 858-51-40fax: (+48 61) 852-59-54mobile: +48514620992skype: rapw3k   
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Re: [Virtuoso-users] ST_Intersects with complex shapes

2015-05-20 Thread Hugh Williams

HI Oliver,

This is has not been resolved yet by development and have a requested it be 
scheduled  …

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.  //  http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers

> On 18 May 2015, at 12:23, Olivier Dalang  wrote:
> 
> Hi,
> 
> Nothing new on this ?
> 
> Thanks !
> 
> Olivier
> 
> 
> 2014-11-11 3:56 GMT+01:00 Hugh Williams  >:
> Hi Oliver,
> 
> Thanks, yes with the queries provided I do get the same error,  so we are 
> looking into the cause …
> 
> SQL> SPARQL PREFIX geo:  >  PREFIX virtrdf: 
>  > PREFIX :  > INSERT DATA{ GRAPH > {:data1 
>geo:geometry"POLYGON((12.332352 45.439447,12.332362 
> 45.439456,12.332305 45.439457,12.332339 45.439436,12.332352 
> 45.439447))"^^virtrdf:Geometry . } };
> 
> Done. -- 1 msec.
> SQL> SPARQL PREFIX geo:  >  PREFIX :  >   SELECT  ?subject ?geom FROM > WHERE   { ?subject geo:geometry ?geom . 
> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31 45.41, 
> 12.38 45.48)") ) ) };
> 
> *** Error 42000: VD [Virtuoso Server]GEO..: for after check of geo 
> intersects, some shape types (e.g., polygon rings and curves) are not yet 
> supported
> at line 25 of Top-Level:
> SPARQL PREFIX geo:  >  PREFIX :  >   SELECT  ?subject ?geom FROM > WHERE   { ?subject geo:geometry ?geom . 
> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31 45.41, 
> 12.38 45.48)") ) ) }
> SQL>
> 
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.  //  http://www.openlinksw.com/ 
> 
> Weblog   -- http://www.openlinksw.com/blogs/ 
> 
> LinkedIn -- http://www.linkedin.com/company/openlink-software/ 
> 
> Twitter  -- http://twitter.com/OpenLink 
> Google+  -- http://plus.google.com/100570109519069333827/ 
> 
> Facebook -- http://www.facebook.com/OpenLinkSoftware 
> 
> Universal Data Access, Integration, and Management Technology Providers
> 
>> On 10 Nov 2014, at 09:10, Olivier Dalang > > wrote:
>> 
>> Hi,
>> 
>> [Hugh] What is the actual “select ..” query you are running, please provide 
>> actual queries so no assumptions are being made.
>> 
>> Here are the full queries that cause the problem :
>> 
>> STEP 1 (entering data)
>> 
>> PREFIX geo: > > 
>> PREFIX virtrdf: > >
>> PREFIX : >
>> INSERT DATA{
>>  GRAPH > {
>> :data1geo:geometry"POLYGON((12.332352 45.439447,12.332362 
>> 45.439456,12.332305 45.439457,12.332339 45.439436,12.332352 
>> 45.439447))"^^virtrdf:Geometry .
>>  }
>> }
>> 
>> STEP 2 (select query)
>> 
>> PREFIX geo: > > 
>> PREFIX : >
>>  
>> SELECT  ?subject ?geom
>> FROM>
>> WHERE   {
>> ?subject geo:geometry ?geom .
>> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31 
>> 45.41, 12.38 45.48)") ) )
>> }
>> 
>> Are you able to reproduce the problem ?
>> 
>> Thanks !
>> 
>> Olivier Dalang
>> ---
>> Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch 
>> EPFL CDH DHLAB  / CM 2 271
>> Station 10 / CH-1015 Lausanne
>> Tel. +41 21 693 02 46 
>> 
> 
> 
> --
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/29042

Re: [Virtuoso-users] ST_Intersects with complex shapes

2015-05-18 Thread Olivier Dalang

Hi,

Nothing new on this ?

Thanks !

Olivier


2014-11-11 3:56 GMT+01:00 Hugh Williams :

> Hi Oliver,
>
> Thanks, yes with the queries provided I do get the same error,  so we are
> looking into the cause …
>
> SQL> SPARQL PREFIX geo:   PREFIX
> virtrdf:  PREFIX : <
> http://test/#> INSERT DATA{ GRAPH  {:data1
> geo:geometry"POLYGON((12.332352 45.439447,12.332362 45.439456,12.332305
> 45.439457,12.332339 45.439436,12.332352 45.439447))"^^virtrdf:Geometry . }
> };
>
> Done. -- 1 msec.
> SQL> SPARQL PREFIX geo:   PREFIX :
>    SELECT  ?subject ?geom FROM WHERE   {
> ?subject geo:geometry ?geom . FILTER( bif:st_intersects (
> ?geom, bif:st_geomfromtext("BOX(12.31 45.41, 12.38 45.48)") ) ) };
>
> *** Error 42000: VD [Virtuoso Server]GEO..: for after check of geo
> intersects, some shape types (e.g., polygon rings and curves) are not yet
> supported
> at line 25 of Top-Level:
> SPARQL PREFIX geo:   PREFIX : <
> http://test/#>   SELECT  ?subject ?geom FROM WHERE   {
> ?subject geo:geometry ?geom . FILTER( bif:st_intersects (
> ?geom, bif:st_geomfromtext("BOX(12.31 45.41, 12.38 45.48)") ) ) }
> SQL>
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.  //  http://www.openlinksw.com/
> Weblog   -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter  -- http://twitter.com/OpenLink
> Google+  -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
> On 10 Nov 2014, at 09:10, Olivier Dalang  wrote:
>
> Hi,
>
> [Hugh] What is the actual “select ..” query you are running, please
>> provide actual queries so no assumptions are being made.
>
>
> Here are the full queries that cause the problem :
>
> STEP 1 (entering data)
>
> PREFIX geo: 
> PREFIX virtrdf: 
> PREFIX : 
> INSERT DATA{
> GRAPH  {
>:data1geo:geometry"POLYGON((12.332352 45.439447,12.332362
> 45.439456,12.332305 45.439457,12.332339 45.439436,12.332352
> 45.439447))"^^virtrdf:Geometry .
> }
> }
>
> STEP 2 (select query)
>
> PREFIX geo: 
> PREFIX : 
>
> SELECT  ?subject ?geom
> FROM
> WHERE   {
> ?subject geo:geometry ?geom .
> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31
> 45.41, 12.38 45.48)") ) )
> }
>
> Are you able to reproduce the problem ?
>
> Thanks !
>
> Olivier Dalang
> ---
> Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch
> EPFL CDH DHLAB  / CM 2 271
> Station 10 / CH-1015 Lausanne
> Tel. +41 21 693 02 46
>
>
>
>
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Re: [Virtuoso-users] ST_Intersects with complex shapes

2014-11-10 Thread Hugh Williams

Hi Oliver,

Thanks, yes with the queries provided I do get the same error,  so we are 
looking into the cause …

SQL> SPARQL PREFIX geo:   PREFIX 
virtrdf:  PREFIX :  
INSERT DATA{ GRAPH  {:data1geo:geometry
"POLYGON((12.332352 45.439447,12.332362 45.439456,12.332305 45.439457,12.332339 
45.439436,12.332352 45.439447))"^^virtrdf:Geometry . } };

Done. -- 1 msec.
SQL> SPARQL PREFIX geo:   PREFIX : 
   SELECT  ?subject ?geom FROM WHERE   {   
  ?subject geo:geometry ?geom . FILTER( bif:st_intersects ( ?geom, 
bif:st_geomfromtext("BOX(12.31 45.41, 12.38 45.48)") ) ) };

*** Error 42000: VD [Virtuoso Server]GEO..: for after check of geo intersects, 
some shape types (e.g., polygon rings and curves) are not yet supported
at line 25 of Top-Level:
SPARQL PREFIX geo:   PREFIX : 
   SELECT  ?subject ?geom FROM WHERE   {   
  ?subject geo:geometry ?geom . FILTER( bif:st_intersects ( ?geom, 
bif:st_geomfromtext("BOX(12.31 45.41, 12.38 45.48)") ) ) }
SQL>

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.  //  http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers

> On 10 Nov 2014, at 09:10, Olivier Dalang  wrote:
> 
> Hi,
> 
> [Hugh] What is the actual “select ..” query you are running, please provide 
> actual queries so no assumptions are being made.
> 
> Here are the full queries that cause the problem :
> 
> STEP 1 (entering data)
> 
> PREFIX geo:  > 
> PREFIX virtrdf:  >
> PREFIX : >
> INSERT DATA{
>   GRAPH > {
>  :data1geo:geometry"POLYGON((12.332352 45.439447,12.332362 
> 45.439456,12.332305 45.439457,12.332339 45.439436,12.332352 
> 45.439447))"^^virtrdf:Geometry .
>   }
> }
> 
> STEP 2 (select query)
> 
> PREFIX geo:  > 
> PREFIX : >
>  
> SELECT  ?subject ?geom
> FROM>
> WHERE   {
> ?subject geo:geometry ?geom .
> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31 
> 45.41, 12.38 45.48)") ) )
> }
> 
> Are you able to reproduce the problem ?
> 
> Thanks !
> 
> Olivier Dalang
> ---
> Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch 
> EPFL CDH DHLAB  / CM 2 271
> Station 10 / CH-1015 Lausanne
> Tel. +41 21 693 02 46 
> 



smime.p7s
Description: S/MIME cryptographic signature
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Re: [Virtuoso-users] ST_Intersects with complex shapes

2014-11-10 Thread Olivier Dalang

Hi,

[Hugh] What is the actual “select ..” query you are running, please provide
> actual queries so no assumptions are being made.


Here are the full queries that cause the problem :

STEP 1 (entering data)

PREFIX geo: 
PREFIX virtrdf: 
PREFIX : 
INSERT DATA{
GRAPH  {
   :data1geo:geometry"POLYGON((12.332352 45.439447,12.332362
45.439456,12.332305 45.439457,12.332339 45.439436,12.332352
45.439447))"^^virtrdf:Geometry .
}
}

STEP 2 (select query)

PREFIX geo: 
PREFIX : 

SELECT  ?subject ?geom
FROM
WHERE   {
?subject geo:geometry ?geom .
FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31
45.41, 12.38 45.48)") ) )
}

Are you able to reproduce the problem ?

Thanks !

Olivier Dalang
---
Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch
EPFL CDH DHLAB  / CM 2 271
Station 10 / CH-1015 Lausanne
Tel. +41 21 693 02 46



2014-11-08 17:25 GMT+01:00 Hugh Williams :

> Oliver,
>
> > On 4 Nov 2014, at 14:11, Olivier Dalang 
> wrote:
> >
> > Hi,
> >
> > I tested this right now on today's Version 7.1.1-dev.3211-pthreads as of
> Nov  4 2014 (051e91d2029a3e90a854539ed83c30e889460847)
> >
> > I'm not really sure about what's happening, my data set is a bit complex
> and I've trouble finding which feature exactly cause some problems. When
> trying to reproduce the error, I ran into the problem even with normal
> polygons. It seems it's more depending on the coordinates than on the type
> of shapes.
> >
> > Here's the query :
> >
> > PREFIX geo: 
> > PREFIX : 
> >
> > SELECT  ?subject ?geom
> > FROM
> > WHERE   {
> > ?subject geo:geometry ?geom .
> > FILTER( bif:st_intersects ( ?geom,
> bif:st_geomfromtext("BOX(12.31 45.41, 12.38 45.48)") ) )
> > }
> >
> > It works with this data :
> >
> > PREFIX geo: 
> > PREFIX virtrdf: 
> > PREFIX : 
> > INSERT DATA{
> >   GRAPH  {
> >  :data0geo:geometry"POINT(12.332352
> 45.439447)"^^virtrdf:Geometry .
> >   }
> > }
> >
> > It doesn't work with this data (I get the "Virtuoso 42000 Error GEO..:
> for after check of geo intersects, some shape types (e.g., polygon rings
> and curves) are not yet supported" error when using the select query
> above). Note that if I change the BOX in the select query so that it
> doesn't intersect the data, I get no error (and of course no result)
> >
> > ...
> >  :data1geo:geometry"POLYGON((12.332352
> 45.439447,12.332362 45.439456,12.332305 45.439457,12.332339
> 45.439436,12.332352 45.439447))"^^virtrdf:Geometry .
> > ...
> >
> >
>
> [Hugh] What is the actual “select ..” query you are running, please
> provide actual queries so no assumptions are being made.  I assume the
> insert query is:
>
> SPARQL PREFIX geo:  PREFIX
> virtrdf:  PREFIX : <
> http://test/#> INSERT DATA{ GRAPH  { :data2
> geo:geometry"POLYGON((0 0,0 1,1 1,1 0,0 0))"^^virtrdf:Geometry . }};
>
> but the select query is unclear to me ???
>
> > The strange thing is that I get no error with this data even when the
> BOX intersects the polygon in the SELECT query ("BOX(-1 -1,1 1)"), even if
> it's the same type of geometry.
> >
> > ...
> >  :data2geo:geometry"POLYGON((0 0,0 1,1 1,1 0,0
> 0))"^^virtrdf:Geometry .
> > ...
> >
> >
> > While testing, I ran into another family of queries where I get the same
> error.
> >
> > This query works properly (intersection1 is true and intersection2 is
> false) :
> >
> > SELECT
> >   (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0
> 10,10 10,10 0,0 0))"), bif:st_geomfromtext("POLYGON((0 0,0 5,5 5,5 0,0
> 0))") ) as ?intersection_test_1 )
> >   (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0
> 10,10 10,10 0,0 0))"), bif:st_geomfromtext("POLYGON((20 20,20 25,25 25,25
> 20,20 20))") ) as ?intersection_test_2 )
> > WHERE{
> > }
>
> [Hugh] I can recreate the error running this query:
>
> SQL> SPARQL SELECT (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0
> 0,0 10,10 10,10 0,0 0))"), bif:st_geomfromtext("BOX(0 0,5 5)") ) as
> ?intersection_test_1 ) (  bif:st_intersects(
> bif:st_geomfromtext("POLYGON((0 0,0 10,10 10,10 0,0 0))"),
> bif:st_geomfromtext("BOX(20 20,25 25)") ) as ?intersection_test_2 ) WHERE{
> };
>
> *** Error 42000: VD [Virtuoso Server]GEO..: for after check of geo
> intersects, some shape types (e.g., polygon rings and curves) are not yet
> supported
> at line 40 of Top-Level:
> SPARQL SELECT (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0
> 10,10 10,10 0,0 0))"), bif:st_geomfromtext("BOX(0 0,5 5)") )

Re: [Virtuoso-users] ST_Intersects with complex shapes

2014-11-08 Thread Hugh Williams

Oliver,

> On 4 Nov 2014, at 14:11, Olivier Dalang  wrote:
> 
> Hi,
> 
> I tested this right now on today's Version 7.1.1-dev.3211-pthreads as of Nov  
> 4 2014 (051e91d2029a3e90a854539ed83c30e889460847) 
> 
> I'm not really sure about what's happening, my data set is a bit complex and 
> I've trouble finding which feature exactly cause some problems. When trying 
> to reproduce the error, I ran into the problem even with normal polygons. It 
> seems it's more depending on the coordinates than on the type of shapes.
> 
> Here's the query :
> 
> PREFIX geo:  
> PREFIX : 
>  
> SELECT  ?subject ?geom
> FROM
> WHERE   {
> ?subject geo:geometry ?geom .
> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31 
> 45.41, 12.38 45.48)") ) )
> }
> 
> It works with this data :
> 
> PREFIX geo:  
> PREFIX virtrdf: 
> PREFIX : 
> INSERT DATA{
>   GRAPH  {
>  :data0geo:geometry"POINT(12.332352 
> 45.439447)"^^virtrdf:Geometry .
>   }
> }
> 
> It doesn't work with this data (I get the "Virtuoso 42000 Error GEO..: for 
> after check of geo intersects, some shape types (e.g., polygon rings and 
> curves) are not yet supported" error when using the select query above). Note 
> that if I change the BOX in the select query so that it doesn't intersect the 
> data, I get no error (and of course no result)
> 
> ...
>  :data1geo:geometry"POLYGON((12.332352 45.439447,12.332362 
> 45.439456,12.332305 45.439457,12.332339 45.439436,12.332352 
> 45.439447))"^^virtrdf:Geometry .
> ...
> 
> 

[Hugh] What is the actual “select ..” query you are running, please provide 
actual queries so no assumptions are being made.  I assume the insert query is:

SPARQL PREFIX geo:  PREFIX 
virtrdf:  PREFIX :  
INSERT DATA{ GRAPH  { :data2geo:geometry"POLYGON((0 0,0 
1,1 1,1 0,0 0))"^^virtrdf:Geometry . }};

but the select query is unclear to me ???

> The strange thing is that I get no error with this data even when the BOX 
> intersects the polygon in the SELECT query ("BOX(-1 -1,1 1)"), even if it's 
> the same type of geometry.
> 
> ...
>  :data2geo:geometry"POLYGON((0 0,0 1,1 1,1 0,0 
> 0))"^^virtrdf:Geometry .
> ...
> 
>  
> While testing, I ran into another family of queries where I get the same 
> error. 
> 
> This query works properly (intersection1 is true and intersection2 is false) :
> 
> SELECT
>   (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 
> 10,10 0,0 0))"), bif:st_geomfromtext("POLYGON((0 0,0 5,5 5,5 0,0 0))") ) as 
> ?intersection_test_1 )
>   (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 
> 10,10 0,0 0))"), bif:st_geomfromtext("POLYGON((20 20,20 25,25 25,25 20,20 
> 20))") ) as ?intersection_test_2 )
> WHERE{
> }

[Hugh] I can recreate the error running this query:

SQL> SPARQL SELECT (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 
10,10 10,10 0,0 0))"), bif:st_geomfromtext("BOX(0 0,5 5)") ) as 
?intersection_test_1 ) (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 
0,0 10,10 10,10 0,0 0))"), bif:st_geomfromtext("BOX(20 20,25 25)") ) as 
?intersection_test_2 ) WHERE{  };

*** Error 42000: VD [Virtuoso Server]GEO..: for after check of geo intersects, 
some shape types (e.g., polygon rings and curves) are not yet supported
at line 40 of Top-Level:
SPARQL SELECT (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 
10,10 0,0 0))"), bif:st_geomfromtext("BOX(0 0,5 5)") ) as ?intersection_test_1 
) (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 10,10 0,0 
0))"), bif:st_geomfromtext("BOX(20 20,25 25)") ) as ?intersection_test_2 ) 
WHERE{  }
SQL> 

So we have something to look into for this query form as “polygons” are 
supported, as in the online examples at:


http://virtuoso.openlinksw.com/tutorials/sparql/SPARQL_Tutorials_Part_10/SPARQL_Tutorials_Part_10.html#(1)

Regards
Hugh

> 
> This other query doesn't work (same error as above), but it's identical from 
> a geometric point of view :
> 
> SELECT
>   (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 
> 10,10 0,0 0))"), bif:st_geomfromtext("BOX(0 0,5 5)") ) as 
> ?intersection_test_1 )
>   (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 
> 10,10 0,0 0))"), bif:st_geomfromtext("BOX(20 20,25 25)") ) as 
> ?intersection_test_2 )
> WHERE{
> 
> }
> 
> 
> Can you confirm the issues ?
> I got quite confused with all those queries/testing...
> 
> Best regards,
> 
> Olivier
> 
> 
> 2014-11-04 3:03 GMT+01:00 Hugh Williams :
> Hi Oliver,
> 
> Are you able to provide a sample dataset and query to demonstrate the error 
> being encountere

Re: [Virtuoso-users] ST_Intersects with complex shapes

2014-11-04 Thread Olivier Dalang

Hi,

I tested this right now on today's Version 7.1.1-dev.3211-pthreads as of
Nov  4 2014 (051e91d2029a3e90a854539ed83c30e889460847)

I'm not really sure about what's happening, my data set is a bit complex
and I've trouble finding which feature exactly cause some problems. When
trying to reproduce the error, I ran into the problem even with normal
polygons. It seems it's more depending on the coordinates than on the type
of shapes.

Here's the query :

PREFIX geo: 
> PREFIX : 
>
> SELECT  ?subject ?geom
> FROM
> WHERE   {
> ?subject geo:geometry ?geom .
> FILTER( bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX(12.31
> 45.41, 12.38 45.48)") ) )
> }


It works with this data :

PREFIX geo: 
> PREFIX virtrdf: 
> PREFIX : 
> INSERT DATA{
> GRAPH  {
>:data0geo:geometry"POINT(12.332352
> 45.439447)"^^virtrdf:Geometry .
> }
> }


It doesn't work with this data (I get the "Virtuoso 42000 Error GEO..: for
after check of geo intersects, some shape types (e.g., polygon rings and
curves) are not yet supported" error when using the select query above).
Note that if I change the BOX in the select query so that it doesn't
intersect the data, I get no error (and of course no result)

...
>:data1geo:geometry"POLYGON((12.332352 45.439447,12.332362
> 45.439456,12.332305 45.439457,12.332339 45.439436,12.332352
> 45.439447))"^^virtrdf:Geometry .
> ...



The strange thing is that I get no error with this data even when the BOX
intersects the polygon in the SELECT query ("BOX(-1 -1,1 1)"), even if it's
the same type of geometry.

...
>:data2geo:geometry"POLYGON((0 0,0 1,1 1,1 0,0
> 0))"^^virtrdf:Geometry .
> ...




While testing, I ran into another family of queries where I get the same
error.

This query works properly (intersection1 is true and intersection2 is
false) :

SELECT
> (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 10,10 0,0
> 0))"), bif:st_geomfromtext("POLYGON((0 0,0 5,5 5,5 0,0 0))") ) as
> ?intersection_test_1 )
> (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 10,10 0,0
> 0))"), bif:st_geomfromtext("POLYGON((20 20,20 25,25 25,25 20,20 20))") ) as
> ?intersection_test_2 )
> WHERE{
> }


This other query doesn't work (same error as above), but it's identical
from a geometric point of view :

SELECT
> (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 10,10 0,0
> 0))"), bif:st_geomfromtext("BOX(0 0,5 5)") ) as ?intersection_test_1 )
> (  bif:st_intersects( bif:st_geomfromtext("POLYGON((0 0,0 10,10 10,10 0,0
> 0))"), bif:st_geomfromtext("BOX(20 20,25 25)") ) as ?intersection_test_2 )
> WHERE{
>
> }



Can you confirm the issues ?
I got quite confused with all those queries/testing...

Best regards,

Olivier












2014-11-04 3:03 GMT+01:00 Hugh Williams :

> Hi Oliver,
>
> Are you able to provide a sample dataset and query to demonstrate the
> error being encountered. Also confirm the Virtuoso version being used
> (virtuoso-t -?) or which git archive you have built against ?
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.  //  http://www.openlinksw.com/
> Weblog   -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter  -- http://twitter.com/OpenLink
> Google+  -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
> On 3 Nov 2014, at 12:08, Olivier Dalang  wrote:
>
> Hi !
>
> The bif:ST_Intersects function throws an error when used on some type of
> shapes. Here's the error message :
>
> GEO..: for after check of geo intersects, some shape types (e.g., polygon
>> rings and curves) are not yet supported" on query...
>
>
> It indeed happens when working on polygons with inner rings.
>
>
> Here, I'm using the ST_Intersect function to filter returned features to
> my map bounding frame:
>
> FILTER (
> bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX({{xmin}} {{ymin}},
> {{xmax}} {{ymax}})") )
> )
>
> I'm almost sure this used to work some weeks ago or at least did not
> return errors (probably it silently ignored inner rings ?).
>
> In my case, I don't really mind about inner rings, I'd actually be happy
> with a bif:st_mbb_intersect function (mbb for minimum bounding box),
> which would even be lighter to compute. Is there such a function ? Or a
> function to return the bounding box of a geometry ?
> Or is there a way to make bif:st_intersects work again on all types of
> shapes ?
>
> Thanks in advance for your help !
>
>
> Olivier Dalang
> ---
> Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch
> EPFL CDH DHLAB  / CM 2 271
> Station 10 / CH-1015 Lausanne
> Tel. +41 21 693 02 46
>
>
>
>
>
>

Re: [Virtuoso-users] ST_Intersects with complex shapes

2014-11-03 Thread Hugh Williams

Hi Oliver,

Are you able to provide a sample dataset and query to demonstrate the error 
being encountered. Also confirm the Virtuoso version being used (virtuoso-t -?) 
or which git archive you have built against ?

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.  //  http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers

> On 3 Nov 2014, at 12:08, Olivier Dalang  wrote:
> 
> Hi !
> 
> The bif:ST_Intersects function throws an error when used on some type of 
> shapes. Here's the error message :
> 
> GEO..: for after check of geo intersects, some shape types (e.g., polygon 
> rings and curves) are not yet supported" on query...
> 
> It indeed happens when working on polygons with inner rings.
> 
> 
> Here, I'm using the ST_Intersect function to filter returned features to my 
> map bounding frame:
> 
> FILTER (
> bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX({{xmin}} {{ymin}}, 
> {{xmax}} {{ymax}})") )
> )
> 
> I'm almost sure this used to work some weeks ago or at least did not return 
> errors (probably it silently ignored inner rings ?).
> 
> In my case, I don't really mind about inner rings, I'd actually be happy with 
> a bif:st_mbb_intersect function (mbb for minimum bounding box), which would 
> even be lighter to compute. Is there such a function ? Or a function to 
> return the bounding box of a geometry ?
> Or is there a way to make bif:st_intersects work again on all types of shapes 
> ?
> 
> Thanks in advance for your help !
> 
> 
> Olivier Dalang
> ---
> Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch 
> EPFL CDH DHLAB  / CM 2 271
> Station 10 / CH-1015 Lausanne
> Tel. +41 21 693 02 46 
> 
> 
>  
> --
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users



smime.p7s
Description: S/MIME cryptographic signature
--
___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

[Virtuoso-users] ST_Intersects with complex shapes

2014-11-03 Thread Olivier Dalang

Hi !

The bif:ST_Intersects function throws an error when used on some type of
shapes. Here's the error message :

GEO..: for after check of geo intersects, some shape types (e.g., polygon
> rings and curves) are not yet supported" on query...


It indeed happens when working on polygons with inner rings.


Here, I'm using the ST_Intersect function to filter returned features to my
map bounding frame:

FILTER (
bif:st_intersects ( ?geom, bif:st_geomfromtext("BOX({{xmin}} {{ymin}},
{{xmax}} {{ymax}})") )
)

I'm almost sure this used to work some weeks ago or at least did not return
errors (probably it silently ignored inner rings ?).

In my case, I don't really mind about inner rings, I'd actually be happy
with a bif:st_mbb_intersect function (mbb for minimum bounding box), which
would even be lighter to compute. Is there such a function ? Or a function
to return the bounding box of a geometry ?
Or is there a way to make bif:st_intersects work again on all types of
shapes ?

Thanks in advance for your help !


Olivier Dalang
---
Digital Humanities Lab (DHLAB) - http://dhlab.epfl.ch
EPFL CDH DHLAB  / CM 2 271
Station 10 / CH-1015 Lausanne
Tel. +41 21 693 02 46
--
___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

Re: [Virtuoso-users] ST_Intersects with complex shapes

[Virtuoso-users] ST_Intersects with complex shapes

9 matches

Site Navigation

Mail list logo

Footer information