Hi Dave, I think something like this is a very good idea, and these look like useful primitives. IMO when it comes to geospatial queries, the devil is in the details. For example, at some point we'll have someone asking for double-precision lat/lon points (GPS is not that accurate, but some applications use computed/simulated points, or combine GPS data with local position). Polygons are sometimes defined as having "holes", etc. It may be worthwhile to take some direction from OGC standards like GeoSPARQL.
Just an initial $0.02. Ideally, the extension would be simple for developers to use and understand (as this is), while also being somewhat future-proof and playing well with standards. Josh On Thu, Jul 22, 2021 at 2:44 PM David Bechberger <d...@bechberger.com> wrote: > One of the common requests from customers and users of TinkerPop is to add > support for geographic based searches (TINKERPOP-2558 > <https://issues.apache.org/jira/browse/TINKERPOP-2558>). In fact many > TinkerPop enabled database vendors such as DataStax Graph and JanusGraph > have added custom predicates and libraries to handle this request. As a > query language framework it would make sense for TinkerPop to adopt a > common geo-predicate framework to provide standardization across providers > and to support this as part of the TinkerPop ecosystem. > > In consultation with some others on the project we have put together a > proposed scheme for supporting this in TinkerPop which I have documented in > a gist here: > https://gist.github.com/bechbd/70f4ce5a537d331929ea01634b1fbaa2 > > Interested in hearing others thoughts? > > Dave >
