You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/03 04:48:02 UTC
[jira] [Commented] (RYA-323) Enable Multi Var Geo Functions
[ https://issues.apache.org/jira/browse/RYA-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112179#comment-16112179 ]
ASF GitHub Bot commented on RYA-323:
------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-rya/pull/183
> 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)