h3 icon indicating copy to clipboard operation
h3 copied to clipboard

Hexagonal hierarchical geospatial indexing system

Results 154 h3 issues
Sort by recently updated
recently updated
newest added

* Hero image * Three feature images * * Zoom into H3 (non-animated) * * Census collage * * City map with red/blue (or some contrasting) color scheme (highlight some...

Hi, love this library! Any guidance on how to do something similar like h3SetToMultiPolygon, where we are tracing the edges of the active hexes, but instead of returning a multipolygon...

We should add a page on our docs discussing the privacy implications of H3

Relating to: - experimentalH3ToLocalIj - experimentalLocalIjToH3 - h3ToLocalIj.c - testH3ToLocalIj.c - localIjToH3.c - ...and a few other places Possible changes: - drop `experimental` from the name - use `cell` instead...

Hey everyone 🙂👋 I was trying to build the lib from `v3.7.1` sources and I faced this issue/warning, is it something expected ? Don't hesitate to tell me if I...

Use the following program to get result,but the result is empty `geo = { "type": "Polygon", "coordinates": [ [ [28.988443, 117.523483], [28.9885, 117.523633], [28.988448, 117.523665], [28.988331, 117.523665], [28.988303, 117.523536], [28.988443,...

Within the function names `Point` is now synonymous with lat/lon. It feels a little redundant to me to then use `GeoPoint` for the lat/lon data type. Maybe it should just...

Names RFC follow-up

Seems like this should accept a resolution rather than an index. _Originally posted by @isaacbrodsky in https://github.com/uber/h3/pull/403#discussion_r527175658_

Names RFC follow-up

Follow up with these changes after https://github.com/uber/h3/pull/403 lands. We don't need the `exact` since we'll no longer have a naming conflict with the `getEdgeLengthAvg*` functions.

Names RFC follow-up