-
Notifications
You must be signed in to change notification settings - Fork 85
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
Incorrect result from polygonToCells for bigger screen/ higher dimensions #180
Comments
This isn't related to screen resolution, but to the width of the bounding box. If your polygon has an edge that crosses more than 180 degrees of longitude, we use the smaller interpretation (the alternative was to require a particular winding order, which is tricky because there isn't one standard). To work around this limitation, break large bounding boxes horizontally into two separate boxes with less than 180-degree widths. |
Thanks @nrabinowitz , I will check and will confirm here, if that works for me, thanks. |
The suggested solution worked, so I am closing this ticket. Thanks @nrabinowitz for quick support. |
Are you refering to GeoJSON? Because rfc7946:
I think at least when |
No, I'm referring to geospatial formats in general - see e.g. the discussion here. ESRI Shapefiles and other formats use clockwise order for external rings. The choice about winding order enforcement is made in the core H3 library, not |
@nrabinowitz thanks for that explanation. |
Hi team,
For bigger screens (4k resolutions -> 2560 px), this method polygonToCells is responding with wrong H3 Cells ( We are just getting bounding box as input and converting that into polygon and passing within this method to get the H3 Cells).
While we are expecting the data for Europe, Africa, Middle East etc, it is responding with opposite area's H3 Cells (North America, Japan, China etc..)
This issue starts from the resolution 2105 px. Before that till 2104 px everything works as expected.
Requested Bounding box:
15.203087,-109.629878,72.791223,110.448247 (Lat/lng)
-109.629878,15.203087,110.448247,72.791223 (Lng/Lat)
Bounding box representation on third party site - http://bboxfinder.com/
Received H3Cells:
Screenshot of Kepler:
Please let us know if you can help us on this issue. Its a bit urgent!! Thanks.
The text was updated successfully, but these errors were encountered: