The reference SDKs give your product the protocol engine itself: deterministic encoding, decoding, and validation that run locally, work offline, and require no API key, quota, or black box.
Loads the profile and verifies that the dataset is coherent before the engine starts answering. An integration can run from in-memory objects or from a pinned dataset cached locally.
Turns latitude and longitude into a complete OGLAP code, with the readable address, decomposed code segments, and resolved administrative context. Invalid, out-of-range, and out-of-territory coordinates are rejected explicitly.
Turns an OGLAP code back into the center coordinate of the addressed microspot, ready for a map marker, distance calculation, or place record.
Finds the smallest administrative boundary containing a code, using the dataset spatial index. Useful for attaching an address to a commune, quartier, or operational zone.
Produces a clear report before accepting a code or configuration. Fatal conditions block engine state, so stale or malformed data never degrades accuracy silently.