Actor Document

Purpose

Dynamic or interactive entity representations in the UI (e.g., moving platforms, simulated actors) possibly controlled by external services.

GeoJSON (DB metadata)

{
  "type": "Feature",
  "geometry": {"type": "Point", "coordinates": [30.153, 59.953]},
  "properties": {
    "type": "Actor",
    "title": "UAV Track",
    "created_at": "2025-09-20T10:00:00Z",
    "updated_at": "2025-09-20T10:05:00Z",
    "source": {
      "url": "wss://stream.example.com/actors/uav-42",
      "type": "websocket"
    },
    "style": {"icon": "uav", "color": "#33cc33"},
    "metadata": {"platform": "UAV", "callsign": "UAV-42"}
  }
}

Required properties

  • properties.type = Actor

  • Point geometry representing current or initial position

  • Link to a data stream or periodically refreshed dataset

Publishing workflow

  1. Expose an endpoint that provides actor state (stream or polling).

  2. Publish Feature with type Actor and relevant style.

Validation checklist

  • Endpoint responds and schema matches UI expectations.

  • Security/auth method documented if needed.

See Common properties for shared fields like legend, metadata, and classification. See also: GeoJSON Strategy and Upload Strategy.