Nick Rabinowitz

Old polyfill: New polyfill: The new one may be correct, I'd have to import the original polygon to check

> > The new one may be correct, I'd have to import the original polygon to check > > Has this polygon been added as a test case to ensure...

Still seeing errors here with the new estimator. Is there an easy-ish way to get the input for the failure cases?

If I'm understanding correctly, this is already implemented as [`directedEdgeToBoundary`](https://h3geo.org/docs/api/uniedge#directededgetoboundary). Is there something that function doesn't provide that you need for your use case?

> My goal is to draw the boundaries between cells that don't share a value in the dataset Another option here is to use [`cellsToMultiPolygon`](https://h3geo.org/docs/api/regions#cellstolinkedmultipolygon--cellstomultipolygon), which will draw a single...

Ok, I think I understand now. I apologize, I skimmed over this at first and didn't realize you were dealing directly with vertex-mode vertexes instead of lat/lng vertexes. I'm still...

> Thank you for the quick response. Couple of follow-ups: > > * Is there an anticipated release date for 4.1.0 Python bindings? > * cell_to_local_ij() is available with 4.0.x...

We've considered this - the output in this case would likely be a `directedEdge`. This isn't a high priority on the roadmap, but PRs are welcome :).

It feels to me like this is going to be a common case - the fuzzer finds uncovered code, or inputs that crash, and we want an easy way to...

I think it's the opposite, the points are always counter-clockwise. This follows the GeoJSON spec for the outer ring of polygons. Agree that we should document this, it's a fixed...