SpatialGlobe
Maps E-Codes

3 applications

← All applications

Aviation & Drone Operations

Air operations need both surface targets and geometry above the ground. Existing point, footprint, route, and vector references cover useful individual handoffs. Prisms, airspace volumes with explicit height limits, specialized runway geometry, and time-aware trajectories are planned extensions for richer aviation workflows.

These applications describe spatial handoffs and integration patterns. Geometry marked as planned is still in development. Operational decisions remain with the people and systems using the reference.

Application

← Aviation & Drone Operations

Landing Surfaces With Extent and Orientation

Landing surfaces are operational objects with extents and orientation, not only points. Coordinates plus verbal notes or aviation-specific local tooling.

An available rectangle can describe a regular landing footprint with size and orientation, and a height-aware point can supply a position reference. Planned runway and landing-strip geometry can carry more specific surface and aviation semantics. These references can help ground and air teams discuss the same intended surface while aircraft suitability, terrain assessment, and authorization remain external responsibilities.

Scenarios and variations

  • Temporary and emergency landing surfaces.
  • Regional, bush, mountain, and expeditionary airstrips.
  • Glider outlanding fields.
  • Snow, ice, glacier, and tactical landing strips.

Specialized runway geometry is planned. A footprint reference is not a statement that a surface is safe or approved for landing.

Application

← Aviation & Drone Operations

A Drone Operating Area With Height Limits

Exclusion and corridor semantics are often 3D and operationally time-sensitive. Aviation overlays and specialized system boundaries.

A drone assignment can refer to an operating volume with a defined footprint and lower and upper height limits. A planned prism or airspace geometry can express that complete spatial boundary. Current polygons, routes, and height-aware points can carry related surface or position references, but do not together establish an encoded airspace volume. The volume reference can be shared between a pilot, the task system, and compatible software.

Scenarios and variations

  • Drone operating areas with lower and upper height limits.
  • Temporary flight restrictions and exclusion regions.
  • Vertical and horizontal flight corridors.
  • Tower, shaft, and RF-sensitive protection volumes.

Prisms, explicit airspace volumes, and 3D corridors are planned. A geometric boundary does not itself provide flight authorization or air-traffic deconfliction.

Application

← Aviation & Drone Operations

Flight Movement, Search Paths, and Later Replay

Air and UAV systems often need movement and path semantics, not only repeated isolated positions. Telemetry-specific playback objects and platform-specific trajectory layers.

Existing vectors and routes provide compact components for a movement-related handoff. A route carries a supplied ordered path; a vector carries direction and magnitude at its anchor. A time-aware trajectory is a separate planned extension for sequences whose timing matters. Receiving aviation or analysis systems would supply the associated observations, predictions, and operational interpretation.

Scenarios and variations

  • Aircraft and drone movement reports.
  • Airborne search patterns and supplied approach paths.
  • Telemetry histories, replay, and predictive movement interpretations.
  • Compact start-to-destination handoffs.

Current vectors have ground-level anchors. These references do not implement flight prediction, a full altitude-aware track, or autonomous collision avoidance.

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