UODI encodes transport demand — road, air, maritime, rail, subterranean, orbital — into a fixed 15-block machine-readable string. No schema agreement. No middleware. Any parser reads any conforming string.
No common format. Road, air, maritime, rail, and emerging infrastructures each carry demand in proprietary APIs. A parser cannot read a demand string from a different domain without prior bilateral schema agreement. This doesn't scale.
Premature identity exposure. Every existing system requires the buyer to disclose exact origin, destination, and identity before receiving a single offer. This enables price discrimination before competition begins.
No embedded integrity. Modified demand strings are indistinguishable from originals. Silent corruption and spoofing in M2M pipelines have no detection mechanism at the encoding layer.
UODI solves all three simultaneously: one positional format any parser reads, anonymous broadcast with cryptographic commitment, integrity check in every string.
ORIG and DEST encode 3D geospatial coordinates in exactly 16 characters using the format [GEOHASH_12][SIGN][ZZZ].
The geohash is right-padded with underscores to 12 characters. Fewer characters = less precision = more privacy. The padding character is unambiguous: underscore is not in the geohash alphabet.
The Z-axis encodes altitude above ground (+), depth below surface (−), or ground level (0) in metres. The same format covers drone delivery pads at +120m, tunnel logistics at −15m, and orbital demand via the ::TRAJ extension.
In Phase 1, DEST is set to ???????????????? — fully incognito. After bilateral handshake, the exact 3D coordinate is disclosed and verified against the CHK4 commitment.
| Mode | Example | Precision | Use Case |
|---|---|---|---|
| Exact | AR69Y7PGXQWT+120 | ~3.7 cm | Drone pad · robotic docking |
| Reduced | AR69Y7PG____0000 | ~610 m | City block |
| Vague | AR69Y7______0000 | ~±20 km | Region · pre-handshake |
| Incognito | ???????????????? | None | Locked until handshake |
UODI v1.2 is fully specified and production-ready. The reference validator, canonical examples, and complete specification are available on GitHub. Patent licensing, commercial certification, and implementation partnerships available through the author.