Emergency Response & Civil Protection

Dispatch and responding units need a compact, unambiguous incident reference that survives voice, text, and software handoff. Point pin links, coordinates, street descriptions, or landmark phrases.

The caller, dispatch operator, and responding unit can pass one compact location reference through their existing communication channels. A full SRL carries the location; a height-aware point can add a vertical reference when the incident is above or below ground. The receiving tool decodes the target, while dispatch decisions and the incident record remain in the response system.

Scenarios and variations

• Incident and event location handoff.
• Victim or casualty location.
• Rendezvous points and disaster-zone positions.

Teams must communicate the bounded extent of a flood, fire edge, contamination zone, damage area, or public warning area rather than a single point. One marker plus verbal explanation, hand-drawn map screenshots, or GIS layers unavailable to all participants.

Teams can share the represented boundary rather than sending a point and explaining the extent again. For a chemical incident, the reference can identify the area covered by a public instruction. For a flood or damage assessment, it can identify the reported affected area. Available point-radius or polygon representations can be chosen to suit the intended meaning; richer protection volumes are planned.

Scenarios and variations

• Flood extent and damage-area boundaries.
• Contamination and public warning regions.
• A chemical-alert radius for a keep-windows-closed instruction.
• Exclusion areas around a reported incident.

The SRL references the area supplied by the responsible source. It does not predict a plume, simulate flooding, or certify a hazard model.

Wildfire coordination often needs to reference fire perimeters, drop zones, access corridors, hotspots, and exclusion regions while individual aircraft or field units may only be reachable by radio. Voice descriptions, map screenshots, local sector names, coordinates read over radio, or GIS layers visible only to part of the operation.

A ground team can describe a bounded drop target or fire-edge region as a compact reference, dictate it over radio, and have it repeated back and logged. A compatible receiving tool reconstructs the represented geometry. A rectangle can express a regular target with length, width, and orientation; a polygon can express an irregular boundary, and a route can carry the supplied access path.

Scenarios and variations

• Fire perimeters and hotspots.
• Air-tanker drop targets and drop strips.
• Access corridors and exclusion regions.
• Staging footprints and equipment pads.

This describes geometry handoff. Aircraft assignment, drop authorization, and incident command remain separate workflows.

Search and rescue or field-control teams need bounded sectors and exclusion regions that multiple actors can interpret consistently. Paper-map markings, screenshots, improvised polygons, or verbally described perimeters.

A search coordinator can pass the represented sector boundary to another team without depending on a particular screenshot or map application. The same reference can be read back, attached to an assignment, or retained in the operation log. Rectangles and squares fit regular sectors; polygons fit irregular ones. Later volume geometries can cover cases where the vertical extent is part of the assignment.

Scenarios and variations

• Search-and-rescue sectors.
• Area handoff between field teams.
• Exclusion regions and temporary restricted areas.

Teams need to share the route or corridor itself, including a detour around a blocked road, not only destination points. Turn-by-turn text, screenshots, proprietary route links, or repeated radio instructions.

The operator selects the intended path and shares it as a route reference. Recipients receive the ordered path rather than only the start and destination. This is useful when several crews must follow the same detour or approach, particularly when a road closure makes an ordinary destination link incomplete. A direct link is available for a simpler two-position connection.

Scenarios and variations

• Evacuation paths and emergency access routes.
• A chosen detour around a blocked road.
• Approach paths to rendezvous and casualty-transfer positions.

The path is supplied by the operator or an external system. SpatialGlobe does not calculate a road-network route or verify that the path is passable.

A staging area, equipment pad, or temporary work zone needs a clear boundary. A point plus a verbal size estimate or a rough drawing can leave teams interpreting the intended extent differently.

A staging reference can carry the footprint itself: location, size, and orientation where the geometry supports them. A square is useful for a regular provisioning area with equal sides; a rectangle suits an elongated equipment or landing footprint, and a polygon describes an irregular boundary. The reference can move from the coordinator to field teams and into an assignment document without redrawing the zone in each tool.

Scenarios and variations

• Temporary material and equipment staging areas.
• Helicopter landing footprints.
• Regular operational pads.
• Square assembly or provisioning areas.

A referenced footprint does not establish landing suitability or operational approval.

A moving vehicle, vessel, aircraft, or response unit may need to report not only position, but direction and distance or speed. Repeated point updates plus voice explanation such as 'moving north fast' or tool-specific telemetry unavailable across systems.

A vector combines an anchor position, direction, and magnitude. Depending on the selected mode, the magnitude describes distance or speed. This lets recipients interpret the report as a movement-related state rather than guessing direction from several unrelated point messages. It is useful for a vehicle or vessel report and can accompany the separate unit identity and observation time.

Scenarios and variations

• Position, direction, and speed of a responding vehicle.
• Directional reports from vessels, trains, and aircraft.
• Distance or displacement reports from field units.

Current vector anchors are at ground level. Full altitude-aware tracking and time-aware trajectories are planned; a vector is not a continuous telemetry service.

Callers and operators sometimes need a shorter transmissible reference when payload, voice bandwidth, or relay conditions are constrained, including a crash away from a marked trail or ski run. Manual abbreviations, repeated coordinate reading, or lossy shorthand without measured behavior.

An injured caller can read a shortened Emergency Code to an operator, who supplies the required location context to reconstruct the position. This reduces the length of the location handoff while preserving an explicit reconstruction process. The operator must handle ambiguity or input clarification when necessary. A full SRL remains the alternative when a self-contained location reference is preferable.

Scenarios and variations

• Accidents away from a marked trail or ski run.
• Wilderness and avalanche rescue location relay.
• Short voice, radio, or message-based incident references.

Emergency Codes require spatial context and have reconstruction limits. They are not a certified emergency-service standard.