-
Notifications
You must be signed in to change notification settings - Fork 156
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] H3 or S2 Spatial indexing #390
Comments
This is a great idea and a priority for me. I can't make any guarantees but I've researched the problem some and look forward to the chance to implement it. :) |
For context: my non profit has global nautical charts for the entire world, and we run sailing races that do real time geospatial analysis on the fly. With H3 or s2, we're interested in running shortest path algorithms in real time that take into account coastlines, nautical charts and weather. This could totally change how sail drones and major ocean races operate and improve the safety of all offshore navigation. |
What are H3 and S2? |
They are both libraries for creating spatial indices. S2 is by google and converts every spot on earth to a location on a Hilbert curve. H3 splits the world into hexagons with unique ids. Both libraries have open source C/C++ implementations. |
This issue has been labeled |
This issue has been labeled |
Is your feature request related to a problem? Please describe.
Yes. We want to use H3 and S2 for pathfinding. We'd like to break the Earth up into tiny cells near the coasts, and larger cells in the oceans, and then use cuGraph to route sailboats based on the wind.
Describe the solution you'd like
A clear and concise description of what you want to happen.
We'd like to build H3 or S2 indices for huge amounts of data in parallel.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.
The text was updated successfully, but these errors were encountered: