[
https://issues.apache.org/jira/browse/JENA-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466110#comment-17466110
]
Greg Albiston commented on JENA-2230:
-------------------------------------
Thank you for adding this in. It is a big step closer to {{fuseki-geosparql}}
not being needed (and possibly the data loading command moving to {{jena-cmd
}}or equivalent).
About GeoSPARQL's handling of update, it is only the spatial index that is a
concern. The rest of the functionality checks the dataset on-demand as part of
the SPARQL query engine's property and filter functions.
When setting up the {{fuseki-geosparql}} application, it wasn't clear, or
documented as far as I could tell, how to hook into update queries to add or
remove geometries to the spatial index. At the time, the JTS library only
offered a read-only (after setup) StrTree and a write QuadTree (with the latter
requiring additional filter checks for validity). Since Fuseki at the time
required a restart when using inferencing with updates, the same approach was
followed for the use of spatial indexes and the StrTree selected.
The JTS spatial indexes have a common interface, so switching to one of the
alternatives should be straightforward and several more have been implemented
since (see {{{}org.apache.jena.geosparql.spatial.SpatialIndex in GeoSPARQL
module and org.locationtech.jts.index [JTS
library|https://locationtech.github.io/jts/javadoc/org/locationtech/jts/index/package-frame.html]{}}}).
It then just comes down to how the SPARQL query engine notifies of update
queries, so these can be passed to the spatial index. The spatial index is
stored in the Dataset Context during setup and provided to the property and
filter functions during querying.
If I can be pointed in the right direction then I can look to resolve updating
the spatial index?
> Assembler for GeoSPARQL
> -----------------------
>
> Key: JENA-2230
> URL: https://issues.apache.org/jira/browse/JENA-2230
> Project: Apache Jena
> Issue Type: New Feature
> Components: GeoSPARQL
> Affects Versions: Jena 4.3.2
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 4.4.0
>
>
> An assembler for the GeoSPARQL engine.
> This is for {{jena-geosparql}}, making it a loadable module for Jena and
> usable with any Fuseki server.
> jena-fuseki-geosparql and its command line are unchanged.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
