[
https://issues.apache.org/jira/browse/JENA-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826081#comment-15826081
]
ASF GitHub Bot commented on JENA-1277:
--------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/205
@osma Yeah, that's what I meant tho'-- use a calculation (via `BIND`, I
guess?) of the distance (and we have [√ available to
use](https://jena.apache.org/documentation/query/library-function.html)) and
order by that. To be clear, I'm not suggesting that that's a great solution
(and I haven't thought at all about the complexities of diff coordinate
systems), just that it's better than relying on undocumented impl behavior
which can change (and WILL change with this PR! :) ).
> Spatial Queries Very Slow For Large Databases
> ---------------------------------------------
>
> Key: JENA-1277
> URL: https://issues.apache.org/jira/browse/JENA-1277
> Project: Apache Jena
> Issue Type: Improvement
> Components: Spatial
> Affects Versions: Jena 3.1.1
> Environment: Linux Ubuntu
> Reporter: samur araujo
> Assignee: Osma Suominen
> Attachments: spatial-assembler.ttl
>
>
> I loaded geonames on Jena but the spatial queries take more than 3s to
> execute. The query is below:
> PREFIX spatial: <http://jena.apache.org/spatial#>
> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
> SELECT distinct ?place
> {
> ?place spatial:intersectBox (32.55668 -117.12865 32.56668 -117.13865) .
>
> }
> The data can be downloaded here:
> https://drive.google.com/file/d/0B-fwYPJYT1GOYVVIZF9ROUxzclk/view?usp=sharing
> For small datasets the queries are executed in 200ms, very fast. I noticed
> that when I access the lucene index directly the queries are also very fast,
> about 20ms.
> The issue may be related to the pos-processing of lucene results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
