-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEA] Support for ST_Distance and ST_contains #231
Comments
Thanks a lot for filing an issue! I'd love to implement both of these features in the near future. Our team will also be talking about it at our next meeting. |
Thanks! This is very important for us in cyber, as we pivot a lot of analysis around geo dimensions. This would help accelerate that workflow dramatically, as well as any inference based on analytic results based on this refinement. It also offers an opportunity to potentially enrich network data with geospatial attributes at line rate for us during ETL.
Jonathan Flack, Principal Systems Architect
BROADBRIDGE NETWORKS
www.broadbridgenetworks.com • jf@broadbridgenetworks.net
[m] +1 310-359-3510
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Thursday, May 28, 2020 1:01 PM, H. Thomson Comer ***@***.***> wrote:
Thanks a lot for filing an issue! I'd love to implement both of these features in the near future. Our team will also be talking about it at our next meeting.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#231 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALHQB2LFOWEZOJG6C3PSJP3RT27KJANCNFSM4NNLANPQ).
|
Hi @jonathanflack, a series of questions:
Thanks! |
Mark,
J |
Hi, @jonathanflack ! I'm implementing the features you requested, and I need to know how best to expose them for your use cases. I am assuming you want python APIs. Could you write an example of how you might expect to consume this API? |
This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. |
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d. |
Is there any ongoing development on this particular feature? It looked like @cwharris got started, but looking through the latest code in |
This issue has been labeled |
@jonathanflack we already have a vectorized Haversine distance API which can calculate geographical point-to-point distances. Is this useful for your ST_distance usage? |
This issue has been labeled |
This PR contributes to #231 , computes distances between pairs of linestrings. Authors: - Michael Wang (https://github.com/isVoid) Approvers: - Mark Harris (https://github.com/harrism) - Paul Taylor (https://github.com/trxcllnt) - Vyas Ramasubramani (https://github.com/vyasr) URL: #510
…nce` (#558) Implements 2D point-point L2 distance. Also renamed folder `distances` into `distance` Contributes to #231 Authors: - Michael Wang (https://github.com/isVoid) Approvers: - H. Thomson Comer (https://github.com/thomcom) - Robert Maynard (https://github.com/robertmaynard) - Mark Harris (https://github.com/harrism) URL: #558
This PR adds point to linestring distance. Contributes to #231 Authors: - Michael Wang (https://github.com/isVoid) - Bradley Dice (https://github.com/bdice) Approvers: - H. Thomson Comer (https://github.com/thomcom) - Mark Harris (https://github.com/harrism) URL: #573
…ython bindings (#660) This PR adds multi-point and multi-linestring support to `point_linestring_distance`. The c++ API **always** supports multi-variant of the geometry type, since any single-geometry type can be wrapped with a `counting_iteartor` for its underlying geometry offset. The column API accepts a `std::optional` for the geometry offset inputs. If not provided, they are considered single geometry by default. A `multigeom_dispatcher` is used to generalize the runtime to compile optional information. This PR also builds python bindings for `point_linestring_distance`. First, the cython bindings is created with a backported `optional` module from cython 3.0 to support the above `std::optional` API. The cython APIs also made use of the dynamic typing property of python to allow geometry offsets to be optional arguments. The python API is the first examplar of a computing API accepting GeoSeries as input. For simplicity, we assume `GeoSeries` only contains single type geometry and there is no mixing of `points` and `multipoints`. Contributes to #231 Follow up to #573 Authors: - Michael Wang (https://github.com/isVoid) - Bradley Dice (https://github.com/bdice) Approvers: - Mark Harris (https://github.com/harrism) - H. Thomson Comer (https://github.com/thomcom) URL: #660
Closing as we have tracker issues for ST_Distance and a milestone for DE9. Thanks for submitting! |
We need to quickly calculate the distance between two points in geospatial for high volume network traffic where the geoIP data is known. Additionally looking to reduce result data according to arbitrary selections using standard selections. Optimized for geoPoint would be ideal.
ST_contains for arbitrary lasso, rectangle or circular selections in geospatial. Should return boolean. See OpenGIS Simple Features Implementation Specification for SQL 1.1. s2.1.1.2 // s2.1.13.3 - same as within(geometry B, geometry A)
ST_distance returns the minimum 2D Cartesian (planar) distance between two geometries, in projected units (spatial ref units). See OpenGIS Simple Features Implementation Specification for SQL 1.1.
These are standard geospatial operators, so no alternatives have been considered.
No additional context.
#231 (comment)
The text was updated successfully, but these errors were encountered: