Geohash Generator

What it does

The Geohash Generator produces spatial index strings in three systems: classic geohashes (base-32 strings like u4pruyd), H3 hexagonal indices, and z/x/y web tile coordinates. Choose the precision level (1–12), generate up to 1,000 values per run, and reuse a seed for reproducible fixtures.

Common use cases

• Geo API fixtures — index values for testing endpoints that accept or return geohashes, H3 cells, or tile references.
• Spatial database testing — keys for geohash-prefixed lookups and H3-bucketed aggregation tables.
• Map tile logic — z/x/y triples for testing tile URLs, caching keys, and zoom-level math.
• Teaching spatial indexing — show how precision length maps to cell size across the three systems.

Settings

• Type — geohash, H3 index, or tile coordinates (a preset for each).
• Precision — 1 to 12; each extra geohash character shrinks the cell (~5 characters ≈ city block scale, 9 ≈ meters). For tiles this maps to zoom-appropriate coordinates.
• How many — 1 to 1,000 values, exportable as text, CSV, or JSON.
• Seed — identical seed + settings = identical values.

Privacy note

Values are generated locally in your browser and never uploaded. They index random synthetic locations — no real places, devices, or people — so they’re safe in tests, logs, and documentation.

FAQ

What’s the difference between geohash and H3? Geohash divides the world into nested rectangles encoded as base-32 strings — simple, prefix-searchable. H3 uses hexagons, which have more uniform neighbor distances — better for aggregation and movement analysis.

What precision should I use? Match your real system. As anchors: geohash 5 ≈ ~5 km cells, 7 ≈ ~150 m, 9 ≈ ~5 m. Test one level above and below your production choice.

Can I get the underlying coordinates too? Generate matching lat/lon data with the Coordinate or Geo Points tools — seeded runs keep the fixtures consistent side by side.