Re: [Virtuoso-users] xsd:boolean in Virtuoso 7

Hi Hugh, Would: select ?o datatype(?o) from where {?s ?p ?o . filter (?o = "false"^^xsd:boolean) } return "False xsd:boolean"? Or nothing, because ?o is actually an integer? On 18 March 2014 10:44, Hugh Williams wrote: > Frans, > > On 17 Mar 2014, at 15:53, Frans Knibbe | Geodan > wrote: > >

Re: [Virtuoso-users] xsd:boolean in Virtuoso 7

Frans, On 17 Mar 2014, at 15:53, Frans Knibbe | Geodan wrote: > On 2013-11-08 7:37, Quentin wrote: >> Is it likely that Virtuoso 7 will come to support xsd:boolean without >> integer conversion? >> >> > A good question. I have just noticed that when I import boolean literals > they are conve

Re: [Virtuoso-users] Problem loading geographical data

Hi Frans, Virtuoso is not fully GeoSPARQL compliant and thus uses its own @prefix virtrdf: virtrdf:Geometry for the RDF geometry type, see: http://docs.openlinksw.com/virtuoso/rdfsparqlgeospat.html So you can insert Mutlipolygons etc as: S

Re: [Virtuoso-users] xsd:boolean in Virtuoso 7

On 2013-11-08 7:37, Quentin wrote: > Is it likely that Virtuoso 7 will come to support xsd:boolean without > integer conversion? > > A good question. I have just noticed that when I import boolean literals they are converted to integers. That's using Virtuoso 7.1. Apparently it has to do with th

[Virtuoso-users] Problem loading geographical data

Hello, I have just installed Virtuoso Open Source 7.10.3208 and now I am loading data from n-triples files. This goes well, until I get to the geographical data. Then I get the following error: *** Error 42000: [Virtuoso Driver][Virtuoso Server]RDFGE: rdf box with a geometry rdf type and a non

[Virtuoso-users] Max row length is exceeded when trying to store a string of 43 chars into a temp col

Error: Max row length is exceeded when trying to store a string of 43 chars into a temp col Query: SELECT COUNT DISTINCT (?object) where { ?object ?type } Dataset: Basekb (polisherd version of freebase) Note: It does not happen removing distin

Re: [Virtuoso-users] Literals, STR() in FILTER and query plan

Hi Hugh, sorry for the late reply. Isn't the execution time included in lines such as: "8 msec 40% cpu, 917 rnd 1810 seq 0% same seg" (from the first query report) In the reports the execution times are 8 msec, 5995 msec and 2 msec respectively. Maybe you need some more infor