[
https://issues.apache.org/jira/browse/RYA-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101619#comment-16101619
]
ASF GitHub Bot commented on RYA-323:
------------------------------------
Github user amihalik commented on the issue:
https://github.com/apache/incubator-rya/pull/183
@isper3at Can you look at this too. This PR is required to enable one of
the main use cases for the geo:nearby function that you're working on
> Enable Multi Var Geo Functions
> ------------------------------
>
> Key: RYA-323
> URL: https://issues.apache.org/jira/browse/RYA-323
> Project: Rya
> Issue Type: Improvement
> Components: sail
> Reporter: Aaron Mihalik
> Assignee: Aaron Mihalik
>
> Currently, all Rya GeoSPARQL functions must have at least one parameter as a
> constant, eg:
> {code}
> ?point geo:asWKT ?wkt .
> FILTER(geof:sfWithin(?wkt, "POLYGON(( ... ))"^^geo:wktLiteral))
> {code}
> however, there is no good reason for this. In fact, we will later want to
> support functions that take in two variables. For instance, a previous set
> of statement patterns will resolve a wkt, then I want to pass that wkt value
> into the function, eg:
> {code}
> <myEntity> <hasLocation> ?point .
> ?point geo:asWKT ?wkt1 .
> ?point geo:asWKT ?wkt2 .
> FILTER(geof:near(?wkt2, ?wkt1))
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
