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

ASF GitHub Bot commented on JENA-1277:
--------------------------------------

Github user rvesse commented on the issue:

    https://github.com/apache/jena/pull/205
  
    We should already have support for most of the trigonometric functions 
built into ARQ as extension functions - 
https://github.com/apache/jena/tree/59e5e06c85c98c9c65a9c1addbc4252626e9d061/jena-arq/src/main/java/org/apache/jena/sparql/function/library/leviathan
    
    For example:
    
    ```
    sparql --data ~/Documents/Work/Datasets/minimal.nt "SELECT 
(<http://www.dotnetrdf.org/leviathan#sin>(90) AS ?x) { }"
    ------------------------
    | x                    |
    ========================
    | 0.8939966636005579e0 |
    ------------------------
    ```
    
    Notes:
    
    - Inverse functions are named as `sin-1` etc.
    - function arguments are expected to be radians
    - convenience functions `degreesToRadians` and `radiansToDegrees` are 
provided


> 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.15#6346)

Reply via email to