afs commented on issue #1953: URL: https://github.com/apache/jena/issues/1953#issuecomment-1630333819
> I'm pretty sure that GeoSPARQL isn't part of the default Fuseki distribution yet, There is `jena-fuseki-geosparql`, a build of Fuseki with `jena-geosparql`. It has different command line options which is one factor that stops common integration. If the dataset is coming from an assembler, the extension mechanism [FusekiAutoModule](https://jena.apache.org/documentation/fuseki2/fuseki-modules.html) could be used. That can also include a command line entry point that either (1) generates an assembler for later use (2) writes an assembler that is picked up by the module (3) or creates a datastructure with the details that the module picks up (preference - the latter so in-memory, no disk use at all works.). > tdbquery only considers a TDBDataset? Yes. Assembling needs a starting point in the case of more than one description in a file. `tdbquery` is doing that based on type. The `sparql` command can take a configuration with any single dataset setup. A feature is needed to specific the starting point of building the dataset. ---- GeoSPARQL is sufficient different in its feature set and needs that there needs to be a community around it to maintain and evolve the GeoSPARQL support. See also: #1344 which has several suggestions but hasn't come to a clear consensus on direction. -- 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]
