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

### Discussed in https://github.com/uber/h3/discussions/546 Originally posted by **dipeshmr** December 3, 2021 In h3-go there is a method called SetToLinkedGeo which returns LinkedGeoPolygon but i want GeoPolygon type so that i...

Currently, the polyfill function only includes hexagons whose center is within the polygon. Would be good to support different polyfill needs: 1. center within the input polygon 2. input polygon...

As discussed offline, we think there are a few improvements we could make in how we do performance benchmarks for H3: - use some standard benchmarking framework instead of rolling...

I wonder if there's some way we can collect and monitor benchmark performance, like https://github.com/marketplace/actions/continuous-benchmark or https://werat.dev/blog/running-benchmarks-for-pull-requests-via-github-actions/? _Originally posted by @isaacbrodsky in https://github.com/uber/h3/pull/524#pullrequestreview-776504456_

help wanted

It seems that the column Average Hexagon Edge Length (km) in the [restable](https://h3geo.org/docs/core-library/restable/) is undershooting the actual length of the hexagon edges. The Average Hexagon Area (km2) column seems correct...

(Originally: uber/h3-py#202) This polygon (nb: in degrees, not radians) causes `polygonToCells` to return `E_FAILED` (at resolution 5, probably true for other resolutions): ``` { {-74, -120}, {-74, 0}, {-74, 120},...

As mentioned in https://github.com/uber/h3/pull/518#issuecomment-927444306.

Adds a test driver for bytesandbrains/h3-pg#56 to the core library for debugging this type of polygon that currently has a very high estimation.

[This SO question](https://stackoverflow.com/a/68166990/380487), and others where people asked for a radius lookup, made me think that there might be value in a circle-fill function that produced more accurate "cells in...

As mentioned in this issue, do we want to come up with and use a good, standard short variable name for `LatLng` variables? - `ll`? - `g`?