Can libspatialjoin handle new WKT literals?

[ktk]

I want to calculate an intersect with a polygon I bind on my own, using the new spatialjoin:

PREFIX ogc: <http://www.opengis.net/rdf#>
PREFIX osmrel: <https://www.openstreetmap.org/relation/>
PREFIX geo: <http://www.opengis.net/ont/geosparql#>
PREFIX osm: <https://www.openstreetmap.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX osmkey: <https://www.openstreetmap.org/wiki/Key:>
PREFIX qlss: <https://qlever.cs.uni-freiburg.de/spatialSearch/>
SELECT DISTINCT ?osm_id ?shape WHERE {
  # Define a square polygon (2 km x 2 km) around Zurich HB
  BIND("POLYGON((8.529 47.375, 8.549 47.375, 8.549 47.395, 8.529 47.395, 8.529 47.375))"^^geo:wktLiteral AS ?polygon)

  SERVICE qlss: {
    _:config qlss:algorithm <libspatialjoin> ;
             qlss:left ?polygon ;
             qlss:right ?shape ;
             qlss:payload ?osm_id ;
             qlss:joinType <intersects> .
    {
      osmrel:1682248 ogc:sfContains ?osm_id .
      ?osm_id osmkey:building ?building .
      ?osm_id rdf:type osm:way .
      ?osm_id geo:hasGeometry/geo:asWKT ?shape .
    }
  }
}

https://qlever.cs.uni-freiburg.de/osm-planet/87Loiz

Not sure what I'm doing wrong, any ideas?

[hannahbast]

@patrickbr It seems that the parsing of WKT literals that are not contained in the original index does not work. Can you confirm this?

(I tried it with an envelope that is contained in the original index and that worked. But as soon as I change this envelope a little bit, it no longer works.)

[patrickbr]

Yes, I have tested this, this is indeed the case. I am working on a fix.

[patrickbr]

Feel free to test this PR draft which should fix this issue: #1941

[ktk]

Thanks I don't have a machine that builds QLever in a reasonable amount of time so will wait for the merge :)

[ktk]

Works great now, thanks!

[joka921]

As the PR that fixes this has been merged into the master branch, I am closing this for now.