168
Open · versioned · tested

Geographic interoperability, from source geometry to executable platform geography.

The geography a buyer requested, the geometry that was supplied, the canonical H3 representation, the circles or IDs a platform actually executed, and the geography used for reporting are usually five different objects. This knowledge base documents every conversion between them — with containment rules, approximation classes, units, tolerances, and the edge cases that break them.

The canonical pipeline
51
Content pages
18
Conversion methods
105
Edge cases
3
Cell systems
Evidence

Open working-group questions, answered with a number you can regenerate.

Each row pairs a live interoperability question with a measurement from the conversion tools and the exact command that reproduces it — the claim and its receipt in one place.

  1. #1Is an H3 ↔ S2 conversion lossless enough to treat as a lookup? (WG §8)

    No. One res-8 H3 cell → 4 S2 cells (overreach 3.61 km²) → 12 H3 cells (overreach 9.73 km², underreach 0.06 m²). Cross-grid conversion is geometry, not a lookup — the case for MUST-reject over silent conversion.

    h3_to_s2 { cell: 882a100d67fffff, s2Level: 13, mode: cover } → s2_to_h3 { …, res: 8 }full evidence →
For AI agents & crawlers

Point your agent at this knowledge base and let it learn the standard.

The entire corpus is published in machine-ingestible form. Fetch one file for everything, or crawl page-by-page — every page is available as clean markdown by appending .md to its /docs/ path.

Sections