Name the world.

Every point you drop is a real, valid 4D-ID: a discrete global grid cell plus a unique descriptor, minted in your browser. Nothing here touches the live namespace; identities are yours, in this tab.

Demo 1 · address

Address → identity

Type any address. It is geocoded, anchored to its H3 cell, and given a persistent name you can resolve again.

Demo 2 · geodata

Geodata → identities

Drop a GeoJSON of points or polygons (buildings, assets, sensors). Each feature is minted as a named entity and appears on the globe. No file? Generate a sample block.

Demo 3 · the grid

Cells: the name is the address

A discrete global grid cell is the name, the partition key, the route, and the level of detail at once. Toggle the grid and zoom: cells subdivide, and each shows how many identities it holds.

World

Your named world

0 identities minted

Click any point for its context envelope. Drag to pan, right-drag or ctrl-drag to tilt, scroll or +/− to zoom, H for world view, N for north-up.

What just happened

Address geocoded to lat/long.
Lat/long resolved to an H3 discrete-global-grid cell.
A 4D-ID minted: 4did:h3:<cell>:<uuid>.
Address registered as an identified_as relation, so it resolves next time.
Anchored and plotted at global scale.

This is exactly what the reference resolver does server-side. Here it runs in your browser so the namespace stays clean.