# H3 geospatial indexing system

Hacker Approved page: https://hackerapproved.com/p/h3/

12 people recommended H3 geospatial indexing system in Hacker News comments, 6 had mixed feelings and 3 criticized it, November 2025 to October 2026. It was recommended in 4 of 12 months, in 5 threads. It meets the Hacker Approved badge rule.

6 of the 12 people who recommend it commented in one thread, “Harder, Better, Faster, Stronger Version of Uber H3 in Rust”.

**Verdict:** Hexagonal spatial index valued for uniform cells, distribution across nodes and fast binning; critics note non-congruent hexagons cause overlaps and gaps across mixed resolutions.

Summary written by Claude from 25 comments.

## Why people recommend it

- Uniform cells with low distortion (2 comments in the sample): "H3 is preferred for geo analytics because it produces a more uniform spatial index with low distortion and consistent distances between cells" ([source](https://news.ycombinator.com/item?id=45804669)) "the distortion across the globe is much less, because of the way H3 creates its grid" ([source](https://news.ycombinator.com/item?id=45804628))
- Fast binning and approximate joins (2 comments in the sample): "as long as you're OK with approximation, you can speed up a lot of things by working with CellID instead of actual geometries" ([source](https://news.ycombinator.com/item?id=45804358)) "with H3 you just compute the bin, O(1) instead of O(log n" ([source](https://news.ycombinator.com/item?id=46923428))
- Easy joins without geometry work (2 comments in the sample): "the big selling point of H3 is that once you’re "in the H3 system", many operations don’t need to worry about geometry at all" ([source](https://news.ycombinator.com/item?id=46922161)) "As long as you agree on zoom level, joining two datasets with S2 and H3 is really easy." ([source](https://news.ycombinator.com/item?id=46927764))
- Easy to distribute across nodes (2 comments in the sample): "H3 works reasonably for sharding spatial joins if all of the cell resolutions have the same size" ([source](https://news.ycombinator.com/item?id=46925939)) "h3 is effectively a grid so can easily be distributed over nodes" ([source](https://news.ycombinator.com/item?id=46923135))

## What people warn about

- Non-congruent hexagons create overlaps and gaps (2 comments in the sample): "the lack of congruency in H3 hexagons can cause weird overlaps and gaps if you plot mixed resolutions naively" ([source](https://news.ycombinator.com/item?id=46921635)) "H3 is not congruent it was optimized for visualization" ([source](https://news.ycombinator.com/item?id=46921380))
- Loses accuracy through approximation (2 comments in the sample): "Yes it speeds things up but you loose accuracy." ([source](https://news.ycombinator.com/item?id=46926520)) "a much higher cell fidelity (below 1cm compared to 1m for H3" ([source](https://news.ycombinator.com/item?id=45803534))
- Poor scalability for analytical computations (2 comments in the sample): "The main disadvantage of non-congruent tiling systems like H3 is poor scalability and performance when running analytical computations." ([source](https://news.ycombinator.com/item?id=45804867)) "H3 has fixed overhead (~4.7KB/109 allocs for k=2 ring), while fallback scales linearly." ([source](https://news.ycombinator.com/item?id=46922379))

## The badge

A product earns the Hacker Approved badge when at least 10 people recommend it, recommenders outnumber critics at least 2 to 1 (mixed feelings count toward neither side), it was recommended in at least 4 of the 12 months and in at least 5 different threads, and no single thread supplies more than half of the people who recommend it. Health and money products are never badged.

## Cite as

Hacker Approved, "H3 geospatial indexing system", https://hackerapproved.com/p/h3/ (12 recommend, 6 mixed, 3 criticize; Hacker News comments, November 2025 to October 2026).

Counts updated 2 Nov 2026, with data through October 31, 2026.