The situation with my data is not so bad !
Doing SPARQL query on rdf:type of my 2 main classes works fine (I have only
a handful of user entered RDF classes, the rest are copies of Internet RDF
data ).
And strangely, I get correct float data for this particular triple in the
original post:
<http://semantic-forms.cc:1952/ldp/1640450652251-3388247986206631>
<http://www.w3.org/2003/01/geo/wgs84_pos#long>
*"4.77962"*^^<http://www.w3.org/2001/XMLSchema#float> .
So my binary TDB database is corrupted, but once again, I'm able to recover
the important data.
And that 's an opportunity to test TDB2 ...
Jean-Marc Vanel
<http://semantic-forms.cc:9112/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me>
+33
(0)6 89 16 29 52
Le sam. 1 janv. 2022 à 22:36, Andy Seaborne <[email protected]> a écrit :
>
>
> On 01/01/2022 20:50, Andy Seaborne wrote:
> >
> >
> > On 01/01/2022 19:45, Jean-Marc Vanel wrote:
> >> During TDB initialization, I get this warning :
> >> WARN o.apache.jena.sparql.expr.NodeValue - Datatype format exception:
> >> "4,77962"^^xsd:float
> >>
> >> But I am unable to detect the incorrect triple , with this query :
> >> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
> >> SELECT * WHERE {
> >> ?S ?P "4,77962"^^xsd:float .
> >> }
> >>
> >> I also tried this:
> >> SELECT * WHERE {
> >> ?S ?P ?O.
> >> FILTER ( STR(?O) = "4,77962" )
> >
> > Try
> >
> > FILTER ( CONTAINS(STR(?O), "779") )
> >
> >> }
> >>
> >> This uses the latest jena Version 4.3.2 , with TDB 1 .
> >> I suspect this bad data prevents geosparl queries from getting any
> >> result.
>
> "4,77962"^^xsd:float has no value.
>
> So if you are using geo, you have a lat without a long or viceversa.
> It's not legal data and will not be indexes or in the results of a
> geo-spatial query.
>
> >
> > Did it work in a previous version?
> > Did you load the TDB database with 4.3.2?
> > Does it work with TDB2?
> > Does the original data have a comma in a float?
> >
> > Andy
> >
> >>
> >> Jean-Marc Vanel
> >> <
> http://semantic-forms.cc:1952/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me>
>
> >>
> >> +33 (0)6 89 16 29 52
> >> Twitter: @jmvanel , @jmvanel_fr
> >>
>
