Maritime, Ports & Offshore

The port address or harbor name does not identify the specific berth, quay section, or anchorage area assigned to a vessel. Crews receive berth labels, port plans, coordinates, and verbal directions.

A rectangle can describe a regular berth footprint and its orientation; a polygon can designate an anchorage area. A separate route can carry an intended path supplied by the responsible operator. These references remain readable across ship and shore tools without replacing the berth assignment, vessel identity, port procedures, or navigation data. Elongated operational strips are a planned specialization.

Scenarios and variations

• Berth footprints and quay-aligned handoff areas.
• Anchorage zones.
• Port approach and supplied harbor-transfer paths.

A caller on a moving boat may know the lake or bay but cannot name an actionable position for responders. Dispatch relies on landmark descriptions, coordinates read aloud, and repeated location updates.

The caller shares a full SRL or a shortened Emergency Code with the required reconstruction context. Dispatch can then provide a route reference for an externally chosen meeting point accessible to the shore-side response. A vector can describe the boat's reported movement. Each reference has a distinct role: current location, movement report, or intended path.

Scenarios and variations

• Emergency location relay from a boat.
• Direction and speed in a separate movement report.
• A supplied path toward a marina, dock, slipway, or shoreline pickup point.

Emergency Codes require spatial context. This scenario does not claim an implemented dispatch integration, certified response timing, or automatic marine routing.

A bay or harbor can contain safety regions and operating surfaces that cannot be described by one location pin. Participants rely on local labels, chart annotations, and specialist overlays.

A polygon or rectangle can designate the represented water surface, and a route can describe a supplied movement path. The same reference can accompany an operational message or a document shared between shore and waterborne participants. Planned circles and volumes can add suitable shape or vertical extent. The geometry does not itself establish a restriction, authorization, or safe navigation condition.

Scenarios and variations

• Marine safety zones in a bay.
• Seaplane operating surfaces.
• Harbor taxi and holding areas.
• Restricted or controlled water regions.

An offshore service team needs the specific transfer point and its height, not just the wind-farm name or turbine position. Instructions combine asset labels, coordinates, deck descriptions, and separate height information.

A service instruction can combine the asset identifier with a height-aware target reference and, where appropriate, a radius or footprint. That reference can move between a planner, offshore crew, and compatible aerial-service software. The exact target and vertical reference must come from suitable source information. A later elevated circle or volume can describe the handoff region more directly.

Scenarios and variations

• Wind-turbine hoist decks and transfer positions.
• A height-aware service target on an offshore platform.
• Drone or aerial-service handoff positions.
• A separately represented deck footprint or target radius.

The reference does not control a hoist or drone, and does not verify deck clearances or operating conditions.