GeoSPARQL Module

[Greg Albiston <ga...@mail.com>]

Hello,

Just to update on the work for the GeoSPARQL module.

I've setup the previous property and filter functions from the
jena-spatial module. These can be used with both Lat/Lon geo predicates
and the geometry literals of GeoSPARQL. There are also some additional
filter functions added for convenience, e.g. convert lat/lon values to
geometry literals and calculating distances.

A spatial index is used for these functions on a per dataset basis. If
the spatial index is available then the GeoSPARQL property functions
will use it. The GeoSPARQL property functions will also do a fall back
test for geo predicates if no geometry literals are found so there is
some accomodation for those wanting to stay with geo predicates, but
only a few spatial relations are valid for point-point relations.

Methods for converting datasets to GeoSPARQL structure are also
included. I've also tried to incorporate Bruno's previous feedback with
more consistent ExprEvalExceptions within the functions.

I will send out a message on the users mailing list to invite people to
test the GitHub project as there was some interest in assisting.

What is the process for creating the new module within Jena?

Thanks,

Greg

Re: GeoSPARQL Module

[Marco Neumann <ma...@gmail.com>]

no worries Greg, good to see progress and plenty of new features in the
latest version of spatial data support in Apache Jena. Are currently all
filter functions listed in the documentation supported in the latest Apache
Jena release?

In the Apache Jena GeoSPARQL 3.17 release I am using here the filter
function spatialF:convertLatLon doesn't seem to work as intended for
binding new variables. Is Andy now working mostly on the Jena geosparql
release? If so I will direct my question to Andy.

Marco

On Wed, Jan 30, 2019 at 10:55 AM Greg Albiston <ga...@mail.com> wrote:

> Hi Marco,
>
> I've just realised I put "Bruno" in the below email when I was actually
> referring to your feedback.
>
> Apologies for the mistake,
>
> Greg
>
>
> -------- Forwarded Message --------
> Subject: GeoSPARQL Module
> Date: Wed, 30 Jan 2019 10:26:13 +0000
> From: Greg Albiston <ga...@mail.com> <ga...@mail.com>
> Reply-To: dev@jena.apache.org
> To: dev@jena.apache.org
>
> Hello,
>
> Just to update on the work for the GeoSPARQL module.
>
> I've setup the previous property and filter functions from the
> jena-spatial module. These can be used with both Lat/Lon geo predicates
> and the geometry literals of GeoSPARQL. There are also some additional
> filter functions added for convenience, e.g. convert lat/lon values to
> geometry literals and calculating distances.
>
> A spatial index is used for these functions on a per dataset basis. If
> the spatial index is available then the GeoSPARQL property functions
> will use it. The GeoSPARQL property functions will also do a fall back
> test for geo predicates if no geometry literals are found so there is
> some accomodation for those wanting to stay with geo predicates, but
> only a few spatial relations are valid for point-point relations.
>
> Methods for converting datasets to GeoSPARQL structure are also
> included. I've also tried to incorporate Bruno's previous feedback with
> more consistent ExprEvalExceptions within the functions.
>
> I will send out a message on the users mailing list to invite people to
> test the GitHub project as there was some interest in assisting.
>
> What is the process for creating the new module within Jena?
>
> Thanks,
>
> Greg
>
>

-- 


---
Marco Neumann
KONA