H3h3throw·Nov 21, 2018
I used this a lot when I worked at Uber. Very similar but maps to variably sized Hexagons which were nice for things like surge/dispatch algorithms: https://github.com/uber/h3
In Fast, Constant-Time Sphere Indexinguber
h3
C2018–2022
uber / h3
h3
Hexagonal hierarchical geospatial indexing system
14Distinct people
14Mentions
0Explicit recommenders
6.7KGitHub stars
What to know before exploring
What it is
Hexagonal hierarchical geospatial indexing system
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:02:44 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year14 dated mentions
Observed mentions: 2018-01-12 18:54:36 UTC to 2022-06-22 10:12:06 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesShameless plug: why not use H3 (https://github.com/uber/h3)?
In Geospatial indexing on Hilbert curvesYep, Dr. Sahr came to the office a few times when we were first getting the original version done. He implemented the core of the algorithm and we took on many of the utility methods, most of them in https://github.com/uber/h3/blob/master/src/h3lib/lib/algos.c
Then we dug in on code formatting, performance tuning (we've removed almost all of the H3IndexFat struct representation usage and switched most things to bitwise operations), and testing coverage.
As for the bindings, I don't know which will be open sourced, so I can't say more, but we had asked Dr. Sahr to make sure the API itself never allocates memory, it must be passed in allocated memory, so it's not too hard to make bindings that work with both manual memory management and garbage-collected languages.
Making the emscripten-compiled front-end Javascript "binding" was a lot of f
Read the rest
un, though. :)
There are pentagons:
> The first H3 resolution (resolution 0) consists of 122 cells (110 hexagons and 12 icosahedron vertex-centered pentagons), referred to as the base cells.
From: https://github.com/uber/h3/blob/9df3940473e2f0446cf38e22443c...
In H3: A Hexagonal Hierarchical Geospatial Indexing SystemThanks for that link.
Also found this which goes into some more detailed comparison with rectangular grids:
https://github.com/uber/h3/blob/master/docs/doxyfiles/usecas...
In H3: A Hexagonal Hierarchical Geospatial Indexing SystemI have never heard of this library before, which is surprising, because I've been looking hard for such a hexagonal privacy-fencing system for a long time!
I can't find anything that explains how the partitioning in geohex works, but the Uber system makes it clear that they are using Dr. Sahr's partitioning scheme: https://github.com/uber/h3/blob/master/docs/doxyfiles/h3inde...
In H3: A Hexagonal Hierarchical Geospatial Indexing SystemH3: A Hexagonal Hierarchical Geospatial Indexing System
140 points · Open discussion