David Ellis

> > I think it would be a useful debugging tool (and a useful teaching aide, as well) if the 20 icosahedron faces could be exposed from the API with...

Hi @dipeshmr this question doesn't make too much sense to me? If you take a set of hexagons, and then convert that into a LinkedGeoPolygon, then converted it into the...

So part of this is simply the relative memory consumption of bare C versus Java with its object wrapping (the difference between the C and Java tests on how fine...

@willcohen that would definitely work around this issue for the time being, but the current polyfill is pretty bad in both space and time usage (it was just the simplest...

When was that switched from heap to stack and why?

@isaachier That's not a good motive to put allocation on the stack for arrays, in my mind. You'll get strange stack overflows at some point where a simple refactor of...

So this is a Node.js library using the CommonJS module system. If you want to get it in the browser, you need to bundle it with a shim of some...

Fully client side like you suspect. It's not hard to add that shim, but `h3-js` and `geojson2h3` do not do this by themselves because there are 3 different "run Node.js...

So all of the browser-shim tools require you to use Node.js to generate a browser-only JS file. But I mentioned Browserify because I personally find it the easiest to work...

So that error is expected. Currently geojson2h3 only supports [`Polygon` and `MultiPolygon`](https://github.com/uber/geojson2h3#geojson2h3featuretoh3setfeature-resolution-options--arrays trying) features. If you change that to Polygon instead of Point, that might "fix" it, but the proper...