Nick Rabinowitz

See [my response here](https://github.com/uber/h3-py/issues/206#issuecomment-1005958213) - this needs to be better documented, but the H3 `polyfill` function only works at present with shapes with width < 180 degrees of longitude. We...

This is not a warning I've seen when building locally, so I imagine it's compiler-specific. Looking at the code, it's a reasonable warning - the compiler very likely cannot statically...

Can you paste in the inputs you're using? This is hard to diagnose from the screenshots. My suspicion, however, is that you're running into [this issue](https://github.com/uber/geojson2h3/issues/25) - it looks like...

`const geojson = geojson2h3.h3SetToFeature(this.hexagons[0])` seems wrong, the input should be an array of strings, this looks like just a string. `geojson2h3.h3SetToFeatureCollection(Object.keys(this.hexagons), ...)` seems wrong, because `this.hexagons` is an array of...

To be clear, is the issue: - You have a small polygon that crosses the antimeridian with points outside the `-180 - 180` range, or - You have a polygon...

Looks like we need to update the docs to reflect the implementation - I thought the 180 degree constraint was in the docs :(. The challenge here is that we...

> What is the current workaround for this issue? The best workaround I'm aware of is to divide your input polygon into multiple sub-polygons by longitude, and fill each one...

I'm not sure I entirely understand the use case, but let me try to respond: - All H3 indexes provided by `geoToH3` are calculated mathematically in constant time. This is...

> Adapt H3 zoom levels to roughly match web mercator zoom levels. This would be like H3 area at zoom level x == sqr(Web Meractor Tile Pyramid meter / pixel...

Thanks for the clarification @sahrk > Maybe it would be worth generating a table of the range of areas by resolution? Agreed - I think @isaacbrodsky had a script to...