Validate an H3 index
Whether a string is a valid cell index, and if not, why not.
Valid: no. "8f2a1072b59a5f7" is not an H3 cell index.
- Why
Provenance
- Computed by
- indexing.h3.validate 1.0.0, core 0.1.0
- Model
- H3 v4 (h3o 0.11)
- Accuracy
- Identical to H3 C; coordinates within 1e-12° below 88° latitude, 5e-11° nearer the poles; areas within 6e-15 relative at resolution 0 and 2e-8 at resolution 15, where the 1 m² cell's spherical excess runs out of digits
- Notes
- None
- Cites
- Uber Technologies and the H3 contributors, H3: A Hexagonal Hierarchical Geospatial Indexing System (API reference v4); Hydronium Labs, h3o: a Rust implementation of H3
Something look off?
How we got thisFormula, worked example, sources, and proof
Model: H3 v4 (h3o 0.11)
Accuracy: Identical to H3 C; coordinates within 1e-12° below 88° latitude, 5e-11° nearer the poles; areas within 6e-15 relative at resolution 0 and 2e-8 at resolution 15, where the 1 m² cell's spherical excess runs out of digits
When to use this: Use this to check H3 values in a dataset or an API response before trusting them. Paste the index in hexadecimal or decimal. The tool says whether it is a valid cell and, when it is not, what is wrong: the wrong length, characters that are not hexadecimal, a mode that marks an edge or vertex rather than a cell, or digits that cannot occur.
Limitations: This checks that the value is a well-formed cell index, not that it is the cell you meant. Directed edge and vertex indexes are valid H3 values but not cells, and are reported as not valid here. Leading zeros and letter case do not matter in hexadecimal.
Worked example: A cell index with a digit that cannot occur. Source: H3 v4 API, computed by h3o and checked against H3 C. It is golden test vector v001, and every build checks the tool still gives its answer within its tolerance.
You enter
- Index to check
- 8f2a1072b59a5f7
You get
- Valid
- no
- Why
- "8f2a1072b59a5f7" is not an H3 cell index.
Review: Not yet independently reviewed by a GIS professional.
Last verified: 2026-09-18, when a maintainer last confirmed this tool's sources at the issuer. See the sources ledger.
Status: version 1.0.0, core 0.1.0. See this tool in the verification report.
Changes
- 2026-10-14, changed: The fourteen focused H3 operations, from cell-to-latlng through edge-length, are now stable. Each is held to H3 C 4.5.0 through h3-py on 20 or more cases, and a new invariants test checks them together on hexagons and pentagons at five resolutions: centers, edges, vertexes, children, classes, distances, and areas. Results are unchanged. Changelog
Checked against: 20 golden test vectors (download the test vectors, each with its source and tolerance). See how results are checked and every source.
Sources
- H3: A Hexagonal Hierarchical Geospatial Indexing System (API reference v4), Uber Technologies and the H3 contributors, H3 4.x documentation. Indexing, inspection, traversal, hierarchy, directed edges, vertexes, and resolution tables. Read free.
- h3o: a Rust implementation of H3, Hydronium Labs, 0.11.0 (tested against H3 C). CellIndex, LatLng, Resolution. Read free.
Terms
- H3: H3 hexagonal hierarchical index
- A global grid of hexagons (and 12 pentagons) at 16 resolutions, each cell about one-seventh the area of its parent, named by a 15-character index. Source: H3 hexagonal index
H3 — H3 hexagonal hierarchical index
A global grid of hexagons (and 12 pentagons) at 16 resolutions, each cell about one-seventh the area of its parent, named by a 15-character index.
Source: H3 hexagonal index