You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
h3 values examples -859b436ffffffff ,859b5dd7fffffff ,859b5dc7fffffff
I created hex boundary by using h3ToGeoBoundary(perh3index['key'],true) and when i map them on map they create long horizontal distorted hex(as shown in image).
Can I know how to resolve this incorrect hex boundary conversion issue?
The text was updated successfully, but these errors were encountered:
This is a rendering issue, not an issue with library output. The library guarantees output within standard lat/lng bounds (-180 to 180 longitude, -90 to 90 latitude), but many renders have poor results for polygons that cross the antimeridian.
To fix in Javascript, see this function: https://observablehq.com/@nrabinowitz/mapbox-utils#fixTransmeridian - it takes the coordinates on the east (negative) side of the antimeridian and turns them into non-standard values > 180 degrees, which generally renders correctly.
h3 values examples -859b436ffffffff ,859b5dd7fffffff ,859b5dc7fffffff
![image](https://user-images.githubusercontent.com/89127319/189703001-164f37cc-19a0-43c5-a8b7-cfde3c479fbb.png)
I created hex boundary by using h3ToGeoBoundary(perh3index['key'],true) and when i map them on map they create long horizontal distorted hex(as shown in image).
Can I know how to resolve this incorrect hex boundary conversion issue?
The text was updated successfully, but these errors were encountered: