Use cases
The parking area on an invitation. A drop target over radio. The item inside a warehouse container. SpatialGlobe gives people and compatible systems a compact way to refer to the actual geometry behind the task.
Location IDs across domains
← Use casesAny full SRL can serve as a location ID in a database. Think of it as a georeferenced counterpart to a UUID: one compact identifier with position and shape built in. This is a shared advantage across all proposed applications below.
The geometry determines the location ID. The same geometry data and encoding settings produce the same SRL. Two independent systems using SpatialGlobe can therefore obtain the same location ID without first exchanging or coordinating a database ID.
Selected examples
← Use casesStart with a situation. Follow any example for the full explanation, related scenarios, and geometry options.
A QR code carries the intended parking footprint and entry edge. Guests receive a concrete arrival target, with a separate approach path when needed.
Explore this application →Also: E-Codes for point sharing with context.
A ground team shares the represented drop footprint over radio. Compatible tools recover the same target, including its size and orientation.
Explore this application →An injured caller relays a short Emergency Code. Dispatch supplies spatial context to reconstruct the position, with clarification when needed.
Explore this application →Also: E-Codes for point sharing with context.
A planned prism or airspace volume describes where the operation is intended to take place, including the lower and upper height boundaries.
Planned geometry Explore this application →Military units share the supplied route as a full SRL. Individual waypoint positions can also be relayed as E-Codes with suitable receiving-side context. The route code can even be written on paper or a hand as a backup if the journey is interrupted.
Explore this application →Also: E-Codes for point sharing with context.
The planned precision path addresses an item’s local 3D position, dimensions, and orientation within its storage container and high-bay environment.
Planned geometry Explore this application →A vector report carries position, direction, and distance or speed. The same pattern applies to vehicles and field units.
Explore this application →Also: E-Codes for point sharing with context.
The shipment order carries a position or oriented handoff footprint, so external partners can recover the intended target beyond yard-local labels.
Explore this application →A temporary material or equipment area becomes a shared spatial reference with a clear position and boundary that teams can reuse in instructions.
Explore this application →Also: E-Codes for point sharing with context.
E-Codes in context
← Use casesEmergency Codes can also be useful for a military waypoint, an event rendezvous, or a field observation when the receiver has a suitable, explicitly supplied location context. That might be a bounded operating area or a reference position with a search radius.
A convoy can relay individual waypoint positions as E-Codes within its agreed operating area. Waypoint labels and their order travel separately; a full route SRL carries the path itself.
The receiver must check the reconstructed position and resolve ambiguity when needed. A familiar area name alone does not guarantee recovery. E-Codes share positions only; heights, footprints, boundaries, movement, and complete routes need their corresponding full SRL references.
All applications
← Use casesExplore 55 proposed applications across the catalog. Each topic brings together the main cases and their practical variations. Planned geometry is labeled inside each explanation.
The intended entrance, parking footprint, room, floor, or indoor arrival area.
Incidents, search sectors, warning areas, access routes, and field handoffs.
Delivery footprints, export-yard slots, material destinations, and stored products.
Convoy routes, controlled boundaries, temporary zones, and movement reports.
Landing footprints, drone operating volumes, corridors, and flight references.
Shared work zones, paths, pickup areas, and references for cooperating machines.
Manage spatial references from the whole plant to main units, utility lines, and individual items.
Reusable operational geometry beneath richer facility and scene models.
Observations, monitored regions, irrigation areas, and sensor coverage.
Compact spatial updates and geometry handoffs over constrained or intermittent links.
Berths, anchorage zones, boat emergencies, and elevated offshore handoffs.
| Application | Link | 2D point | 3D point | Polygon | Rectangle | Route | Square | Vector | E-Codes Point sharing |
|---|---|---|---|---|---|---|---|---|---|
| Addressing & Visitor Access | — | 4 | 1 | 3 | 4 | 2 | 1 | — | 3 |
| Emergency Response & Civil Protection | 1 | 6 | 1 | 4 | 4 | 2 | 2 | 1 | 5 |
| Logistics, Warehousing & Yards | — | 7 | 6 | 4 | 9 | 2 | 1 | — | 2 |
| Defense, Security & Controlled Access | 2 | 1 | — | 2 | — | 2 | — | 1 | 2 |
| Aviation & Drone Operations | — | 1 | 3 | 1 | 2 | 2 | — | 1 | — |
| Robotics & Autonomous Systems | 1 | — | 1 | 3 | 2 | 2 | 1 | 1 | — |
| Industrial Plants, Energy & Infrastructure | 2 | 9 | 7 | 11 | 9 | 4 | 4 | — | 2 |
| Digital Twins & Spatial Models | 1 | — | 2 | 2 | 2 | 1 | 1 | — | — |
| Environment, Agriculture & IoT | — | 5 | 2 | 5 | 1 | 2 | — | 2 | 2 |
| Resilient Field Communication | — | 3 | 1 | 2 | 1 | 2 | — | 1 | 2 |
| Maritime, Ports & Offshore | — | 4 | 1 | 2 | 3 | 3 | — | 1 | 2 |
Have an application in mind that we haven’t covered? Share your use case with us →
Planned SpatialGlobe services
← Use casesSRLs provide spatial inputs and references. Working with building plans, embedding a picker, searching nearby objects, and comparing external map layers require additional platform functions. The services below are planned and are not yet implemented.
Draw a footprint over a solar-panel string or equipment array and choose equal sections or a grid. The planned service generates a precise SRL for each item, keeps the items grouped in an account, and lets users reuse the layout at another position with newly generated SRLs.
Batch subdivision, grouping, and layout duplication are not yet implemented. Other regular layouts, including circular sectors, and AI-assisted extraction of irregular footprints from imagery are later extensions.
Users will be able to upload and geographically align building plans, zoom into the interior, and generate precise SRLs for locations and geometries within the building.
Plan storage, geographic alignment, and detailed indoor selection are planned SpatialGlobe features, not yet implemented. Spatial accuracy depends on the source plan and its geographic alignment.
A planned hosted picker would let a user select a location or geometry inside a partner website and return the SRL to that workflow.
Embedding, host communication, access controls, and partner configuration are additional SpatialGlobe integration features. A public third-party picker is not yet implemented.
Planned spatial queries include nearest objects, objects within a radius, and geometry-based matching. SRLs can provide the referenced inputs and results.
H3 supplies indexing and conservative candidates. Physical distances and complete matches require backend WGS84 geometry. These search services are not yet implemented.
A planned layer-query service could compare a supplied site footprint with an external flood region or administrative boundary, including overlap and containment where supported.
The SRL supplies the geometry reference. Dataset integration, geometric analysis, and the business interpretation are additional functions; the layer-query service is not yet implemented.
Next conversation
← Use casesBring the physical target, the handoff, and the systems involved. We can discuss which spatial references fit today and which extensions your workflow would need.