5 applications

← All applications

Addressing & Visitor Access

A venue address can bring someone to the right property while leaving the actual destination unresolved. A spatial reference can identify the entrance, parking area, or supplied approach path that completes the arrival. Inside a building, a 3D point with a radius can identify a room-level destination on a specified floor. The same idea also helps where a dependable street address is missing.

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.

Homes and Entrances Without Reliable Addresses

When a home has no reliable street address, identifying it can require a nearby landmark, distance and direction, building colors, and neighboring businesses. Residents describe a public landmark, distance and direction, door and building colors, adjacent properties, or nearby businesses in free text or conversation.

The reference can designate the home, its entrance, or a receiving footprint. This is useful wherever landmarks and free-text directions otherwise carry the final part of the address. Documented examples include residential registration in Bolivia and account-opening guidance in Ghana, with different local practices. The spatial reference can accompany the existing address description and remain usable in subsequent service visits.

Scenarios and variations

  • Home or entrance identification without reliable street names or numbers.
  • Delivery, utility connection, and home-visit destinations.
  • Residential location fields in registration and administrative workflows.

A spatial reference locates a home. It does not establish proof of residence or acceptance by a bank or public authority.

Point sharing with E-Codes

A home or entrance position can be relayed as an E-Code if the recipient is given an appropriate neighborhood or locality context. Check the reconstructed position and whether the represented precision suits the entrance. A full SRL remains preferable when the reference must travel without context or act as a persistent location key.

How E-Codes use location context →

Rooms, Floors & Indoor Destinations

A visitor may have the correct building address while still needing to find a particular room or floor. A 3D point adds a height or floor reference to the horizontal position, and its radius marks an area at that level. The result can identify a useful area inside the room, not just its door or an isolated pin.

Place the center within the intended room and choose a radius that marks the relevant indoor area. A meeting room, waiting area, or service destination can then have a compact spatial reference without tracing every outside wall. The same reference can travel in an invitation, appointment message, maintenance order, or assistance request, alongside the room name and access instructions.

A later building-plan workflow would let users store and geographically align their plans, zoom into a floor, and create these references directly from the drawing. Identifying the destination is already useful on its own. Guiding someone through corridors, stairs, and elevators additionally requires a navigable building model and a way to determine the visitor's position indoors.

Scenarios and variations

  • Meeting rooms and indoor visitor destinations.
  • Reception, waiting, and handoff areas on a specified floor.
  • Service and maintenance destinations inside a building.
  • A room-level reference shared with emergency or assistance teams.
  • Later precise selection from geographically aligned building plans.

3D points with a height or floor value and radius are available. The radius marks a horizontal area at that level; exact wall boundaries and room volumes need their corresponding geometry. Room labels, floor-numbering conventions, and access instructions remain application context. Building-plan storage and alignment are planned SpatialGlobe services. Indoor positioning and navigation require additional application functions; they are not supplied by the SRL alone.

The Right Parking Area on the Invitation

An invitation or ticket identifies the venue but may not identify the intended parking footprint or the entry edge drivers should use. Venue address links, annotated parking screenshots, local parking labels, and separate verbal access instructions.

An invitation can carry a QR-encoded SRL for the intended parking footprint, including its entry edge where applicable. An additional route reference can describe the chosen approach. Visitors and organizers then have a concrete arrival target to share, rather than repeatedly interpreting a venue-wide address and a parking screenshot. The same handoff can be reused in visitor instructions and event messages.

Visitors can see which area the organizer has designated for parking and locate themselves relative to that footprint when a parking sketch is unclear. A compatible mobile application could confirm whether their current position is inside the footprint or let them use it as a personal geofence, with a notification when they enter or leave the area.

Scenarios and variations

  • QR-encoded parking footprints on invitations and tickets.
  • The intended parking entry edge.
  • A separately supplied approach path and entrance position.
  • Checking a visitor's current position against the designated parking footprint.
  • Personal geofence notifications in a compatible mobile application.

A route reference describes the supplied path; it does not calculate a driving route. Position checks and geofence notifications require additional application functions; they are not yet implemented as SpatialGlobe services. Position accuracy and the footprint boundary must be considered when confirming whether a visitor is inside the area.

Point sharing with E-Codes

An organizer can relay an entrance or meeting-point position as an E-Code. A city or surrounding region is usually more than sufficient as receiving-side context; it need not be limited to the event grounds. On a mobile device, the receiver can use their current position with a suitable search radius, avoiding manual area selection. The receiver checks the recovered position and resolves any ambiguity. The parking footprint, entry edge, and approach path still need their full geometry references. A full SRL is convenient on a ticket or invitation that must work without reconstruction context.

How E-Codes use location context →

A Defined Curbside Parking Section

A street address does not identify the intended parking band or placement area along a curb. Instructions often rely on a pin, a street name, and a separate description of the permitted section.

An available rectangle can represent the intended surface with length, width, and orientation. The same reference can accompany visitor information or a placement instruction. A dedicated strip is a planned option when the elongated operating-area meaning deserves additional semantics. The geometric designation stays separate from parking permissions, current availability, and traffic rules.

Scenarios and variations

  • Curb-aligned parking bands on straight streets.
  • Vehicle and accessible-parking footprints.
  • Regular truck, trailer, or bus placement areas.

Shared Event Areas for Service Teams

Event teams need different physical targets for visitors, suppliers, medical services, and operations. These targets are often distributed as annotated site plans, local labels, and repeated messages.

An organizer can issue distinct references for a supplier entrance, an unloading area, a medical-service position, and a gathering zone. Each partner receives the relevant geometry with the operational instruction. References can appear in documents and messages or on QR labels. Changes to assignments, opening hours, and permissions remain in the event-management workflow.

Scenarios and variations

  • Supplier entrances and service approach paths.
  • Delivery footprints and temporary service areas.
  • Medical-service positions and assembly zones.

Point sharing with E-Codes

Service teams can exchange individual rendezvous, entrance, or medical-service positions as E-Codes within an explicitly supplied event-area context. The receiver checks the recovered position; work areas, assembly-zone boundaries, and access paths remain full SRL references.

How E-Codes use location context →