[ 
https://issues.apache.org/jira/browse/JENA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036841#comment-13036841
 ] 

Laurent Pellegrino edited comment on JENA-10 at 5/20/11 2:07 PM:
-----------------------------------------------------------------

> geospatialweb is itself LGPL and it uses spatialindex which is LGPL too

Holy cow, It's a great shame :(

> should we be doing this with property functions or with FILTER functions? 

They have just added support for geo-spatial indexing in OWLIM 
(http://www.ontotext.com/owlim/geo-spatial) and they also do it by using 
property functions. I think it's a good idea to use property functions because 
it is more obvious that you are applying a specific behavior when you write 
your query.

To deal with geo-spatial data it would be nice to create a particular index 
that use a r-tree.

      was (Author: lpellegr):
    > geospatialweb is itself LGPL and it uses spatialindex which is LGPL too

Holy cow, It's a great shame :(

> should we be doing this with property functions or with FILTER functions? 

They have just added support for geo-spatial indexing in OWLIM 
(http://www.ontotext.com/owlim/geo-spatial) and they also do it by using 
property functions. I think it's a good idea to use property functions because 
it is more obvious that you are applying a specific behavior when you write 
your query.
  
> GeoARQ: a geo location property function for ARQ
> ------------------------------------------------
>
>                 Key: JENA-10
>                 URL: https://issues.apache.org/jira/browse/JENA-10
>             Project: Jena
>          Issue Type: New Feature
>          Components: ARQ
>            Reporter: Paolo Castagna
>            Priority: Minor
>
> Similarly to LARQ, we can use Lucene spatial capabilities to provide a 
> geo/spatial property function for ARQ.
> An initial and experimental implementation as proof of concept is available 
> here: https://github.com/castagna/GeoARQ
> The initial implementation can provide:
>  - ?s geoarq:nearby ( lat long ) // lat and long are in WGS 84, results are 
> sorted by some "unspecified" score
>  - ?s geoarq:nearby ( lat long dist ) // restrict withing dist km from 
> (lat,long)
>  - (?s ?d) geoarq:nearby ( lat long ) // results are sorted by distance (?d) 
> which is made available to the user
>  - (?s ?d) geoarq:nearby ( lat long dist ) 
>  - ?s geoarq:within ( lat1, long1, lat2, long2 )
> GeoARQ would be better as a separate module from ARQ (same as LARQ).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to