Nick Rabinowitz

Better option here: - add a `complete` callback option, in the PhantomJS scope, with `page` as an argument - add `page.manager` as a pointer to the SuiteManager - add `SuiteManager.endSuite()`...

I was going to say that you could do this in a custom writer, and you can, but it's more of a pain than I initially thought, and you can't...

In general, no - this is the same approach we've generally recommended for any conversion between H3 and other grid systems, as non-alignment of the grids generally makes it impossible...

Related discussion, with benchmarks for the emscripten upgrade issue: https://github.com/uber/h3-js/issues/163#issuecomment-1380986297

Thanks @4nthonylin! Closing for now - there may be other blockers for React Native or unusual environments, but hopefully this is a reasonable fix for many of the affected situations.

> @nrabinowitz The algorithm you describe won't work if the original polygon has regions that are too small/narrow to contain any cell centroids. I don't think that's true? Tracing the...

> I suppose it would take some experimentation to determine how fine to sample the points... Generally I've used the edge length at `res`. We provide a function to return...

The new modes (overlapping and full containment) are added in https://github.com/uber/h3/pull/796

See https://github.com/foursquare/h3-presto

See this answer: https://github.com/uber/h3-js/issues/158#issuecomment-1244087555 The problem in the image is a rendering issue, not an H3-js issue. H3 always provides coordinates with normalized longitudes (in the range `-180` to `180`)...