[
https://issues.apache.org/jira/browse/JENA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036837#comment-13036837
]
Paolo Castagna commented on JENA-10:
------------------------------------
> I am also interested by this feature.
Great.
> There is a similar but older project
Geospatialweb is great and even better than the GeoARQ quick hack.
However, geospatialweb is itself LGPL and it uses spatialindex which is LGPL
too:
http://svn.gispython.org/spatialindex/spatialindex/trunk/COPYING
Also, should we be doing this with property functions or with FILTER functions?
Other issues or things to think about are: avoiding duplicates in your index,
supporting deletions and with lat/long the fact that it's not possible to index
one triple at the time... even if you can expect the triples will be close to
each others.
> 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
