SpatialGlobe
Maps E-Codes

Technology

One spatial language.
Two code formats.

SpatialGlobe uses compact, parameterized geometry references instead of passing full geometry files, screenshots, or tool-specific annotations through every workflow.

SRLs describe locations, areas, routes, and movement in compact, shareable codes.

Emergency Codes (E-Codes) make location sharing even shorter, but require spatial context to recover the intended location.

Maximum compression

Real-world geometry. Compact enough to share.

Useful geometry is packed into short codes that are easy to share between people and systems.
Give it a try: click the map to place up to 4 markers. Then choose a geometry, adjust its parameters, and watch your SRL update as you go.

0 markers (demo maximum 4)
Geometry

Geometry in a compact code

An SRL carries a compact description of the geometry you select. Place markers, choose a shape, and adjust its settings; the code changes with your geometry.

Different geometries need different amounts of information. For the same geometry, higher precision requires a longer code.

Precision that fits

The precision you need. The brevity you want.

Code length grows with the precision you need.
Give it a try: drag the numbered markers and switch precision levels to see how closely the SRL can represent your geometry.

Precision:

Vertex offsets

Min
—
Max
—
Mean
—

Choose the precision you need

The numbered markers are the positions you choose and can move. The SRL codec fits a polygon to those positions within the possibilities of the selected precision level and code length.

The polygon corners may not sit exactly on the markers: a compact code can represent only a limited set of positions and shapes. The polygon shows the codec's best fit within those limits.

The offsets describe the distances between your marker positions and the corresponding corners of the fitted SRL geometry. Min, Max, and Mean show the smallest, largest, and average offset, not GPS accuracy.

Portable across every handoff

An SRL can leave the screen and still keep its meaning.

Read it aloud, write it down, print it, or pass it through an API. Built-in integrity checks help detect input and transmission errors.

Give it a try
Click the characters to change them and watch the map check your code. Choose Reset SRL to restore the original.

A built-in check for everyday errors

An SRL carries built-in consistency information that allows its validity to be checked. This helps detect errors introduced while typing, copying, or transmitting the code.

Many common errors can be caught, particularly changes to a single character. The check is not infallible: some altered codes can still pass the check.

Compact storage

Location ID.
One code. One database field.

Use a full SRL as a location ID: one locid field stores the spatial reference for a point, a height-aware position, a footprint, or a movement vector. Without SRLs, your application needs to serialize the geometry-specific parameters for database storage, as illustrated below.

These four records use the same two columns for four different geometry types. The title describes the example; the location ID carries its geometry.

Four location IDs. One shared record structure.
title locid
Meeting point !D6EA-DIBW-FEZT
Floor reference !FIIH-FDLG-ETFV-F7AB
Training staging area !D4I5-KINA-2SCQ-MBFY
Movement report !D4JK-IRZF-QJNU-IXLM

The same geometries, serialized into a standard database:

Meeting point · 2D point
title geometry latitude longitude radius_m
Meeting point 2D point 47.42141243987405 10.98643966461341 0.0
Floor reference · 3D point
title geometry latitude longitude radius_m vertical_value vertical_unit
Floor reference 3D point 40.71307339924734 -74.0132082267803 33.0 101.0 storey
Training staging area · Polygon
title geometry latitude_1 longitude_1 latitude_2 longitude_2 latitude_3 longitude_3 latitude_4 longitude_4
Training staging area Polygon 52.81936160618719 9.811467294550775 52.81979670200597 9.812509672660228 52.819380077057204 9.812869406186143 52.81918157976152 9.812775557231603
Movement report · Vector
title geometry latitude longitude azimuth_deg elevation_angle_deg speed_mps
Movement report Vector 51.92793128827494 8.663368718037345 37.0 45.0 27.8

The location ID advantage applies across all proposed use cases →

See how the reference moves through your business systems →

Ultra-short transport

In emergencies, every character matters.

E-Codes turn locations into ultra-short codes for voice, text, and constrained communication. Spatial context is required to recover the intended location.

Give it a try
Click the red hint in the map to generate an E-Code for your position. Change Precision to compare code length and precision.

Explore E-Codes in Geometries →

How E-Codes work

An E-Code is deliberately short. The same code can refer to different locations in different regions, so the code alone is not enough to recover the intended location.

To resolve it, provide a location context, such as a nearby town, the containing region, or a known position. “Nearby” can mean hundreds of kilometers: around 500 km or more in some tested cases. The useful range depends on the code, region, and confidence required.

E-Codes are designed to resolve uniquely within local dispatch areas when the respective area is used as location context. This assumes calls originate within that area and codes are transmitted correctly.

Contact SpatialGlobe for a 100% uniqueness check for your dispatch area and chosen code format. If your area has not been validated, verify the plausibility of each resolved location. If it does not match what you expect, refine the location context and resolve again.

This demo uses your device position to generate an E-Code. Click here to set a location context on the E-Code map and see whether the intended location is recovered.

Sign in

or

Create an account

Create a free account and confirm your email to get started.

Registration is for the Free Plan and does not start a paid subscription. If you already accepted the Disclaimer in this guest session, we save that acceptance to your new account.

Disclaimer acceptance saved

Your earlier acceptance of the Disclaimer as a guest has been saved to your new account. You do not need to accept it again unless a material update requires renewed acceptance.

Check your email

Thank you for signing up! We've sent you a verification email.

Please check your inbox and click the verification link to confirm your email address.

You can sign in as soon as you verify your email.

Email verified!

Your email address has been verified successfully.

Your account is ready. You can now sign in.

Forgot your password?

Enter your email address and we'll send you instructions to reset your password.

Check your email

We've emailed you instructions for setting your password. If an account exists with the email you entered, you should receive them shortly.

Please check your spam folder if you don't see the email in your inbox.

Set a new password

Password changed successfully

Your password has been set. You may now log in with your new password.

Development status

SpatialGlobe is available in public preview

Explore SpatialGlobe's available features as we continue testing and refining the platform. We welcome your feedback and issue reports.

Candidate and final formats

Most SRL formats are available as published candidates, but their definitions have not yet been frozen. Finalization will follow further testing and an explicit review. Codes we publish without a prefix use final, frozen format definitions.

Using code prefixes such as p1!

Codes from published candidates carry a provisional prefix such as p1!. Codes entered without a prefix are interpreted using the latest format definition.

For short-term use, the prefix is optional. Keep it when saving or sharing codes for consistent interpretation over time.

Explore the current geometry formats