-
Notifications
You must be signed in to change notification settings - Fork 449
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
API | distance between h3s challenging to work around #840
Comments
If you have H3 cell ids
Does that cover your use case? |
There's also |
ah @ajfriend apologies I couldn't locate this in the new docs! |
https://h3geo.org/docs/library/migration-3.x/functions/ any idea what it is in 4.x? |
@fhk I think part of the confusion on your end is that you're using the documentation for the core C library but comparing it to the Python bindings. The Java and Javascript bindings stick really close to the core C library's naming system (with all three being There's some effort to include Python in most of the pages, but that particular page does not include it. Because of this and some other ways the Python library deviates or adds extra features (such as the |
It should be easy given two h3 indexes to calculate their distance from one another, either from centroid or perhaps nearest vertices.
When making models you often want to encode start and end edges and the distance.
This is now hard as there is no centroid method on the h3?
You have to go through the whole geo_interface or hope that the outer ordering is consistent?
The text was updated successfully, but these errors were encountered: