Aklakan opened a new issue, #3026: URL: https://github.com/apache/jena/issues/3026
### Version 5.4.0-SNAPSHOT ### Feature This proposal is to enhance the spatial index with support for index-per-graph as well as to improve its serialization using kryo - via Apache Sedona's kryo/jts implementation. This is an incremental improvement of the existing in-memory implementation - its not a complete overhaul such as a disk-based incrementally updated transaction-aware R-tree (if someone contributed that than this issue's PR could be discarded 😄 ). The impact of this work have been evaluated and presented at the GeoLD workshop last year [proceedings](https://i3mainz.github.io/GeoLD2024/#proceedings): Simon Bin, Claus Stadler, Lorenz Bühmann, and Michael Martin [Getting practical with GeoSPARQL and Apache Jena](http://ceur-ws.org/Vol-3743/paper2.pdf) [Slides](https://i3mainz.github.io/GeoLD2024/presentations/paper2_presentation.pdf) The essence is presented on the following slides: Using a named graph per index (unsurprisingly) boots the performance when multiple graphs have geometries and only a subset is queried (slide 15):  As for serialization performance (slide 16), while index building became a bit slower, this is outweighed by near-instant loading of the spatial index:  A new `geosparql:indexPerGraph` option (boolean) is added to the `geosparql:GeosparqlDataset` assembler. The implementation has been mainly done by @LorenzBuehmann. As for compatibility, I need to check for whether it is backward compatible but I think due to the change of the serializer, existing spatial indexes would have to be rebuilt. ### Are you interested in contributing a solution yourself? Yes -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
