MPA OCEANS-X Vessel Positions
Provides vessel identity, type, speed, heading, latitude, longitude, and timestamp. The poller writes a latest layer for live display and an archive layer for history-dependent analysis.
ArcGIS value from live port data.
OCEANS-X feeds land in secured ArcGIS Online layers, maps, and dashboards for governed analysis.
Live Inputs
MPA OCEANS-X feeds used today.
Arrivals & Departures
Hourly arrivals and departures feed dwell time, arrival/departure rates, net accumulation, and freshness checks. Event history needs continuous polling before rolling metrics become stable.
Inbound ETAs
Vessels due to arrive feed arrival-surge windows. The API returns ETA and port codes, not inbound coordinates, so the dashboard does not map those vessels directly.
Declarations
Arrival purpose and departure next-port context are persisted in minimised form. Agent, crew, and passenger details are deliberately excluded from the analytical layers.
ArcGIS Ecosystem
Layers, maps, dashboards, and secure access.
| Item | Role | Dashboard Use |
|---|---|---|
| PortOperations_PortInfrastructure | Terminals, anchorage zones, wharf-edge references, berth candidates. | Terminal count, map context, and M8 geometry assumptions. |
| PortOperations_VesselPositions | Latest vessel snapshot plus rolling position archive. | Map vessels, vessel count, M1 anchorage pressure, and M8 occupancy. |
| PortOperations_ArrivalsDepartures | Append-only arrival/departure event history with minimised declaration context. | M3 dwell, M4/M5 rates, M6 net accumulation, M9 context. |
| PortOperations_ArrivalsForecast | Latest inbound ETA window. | M2 arrival surge and source freshness. |
| PortOperations_CongestionMetrics | Latest route rows plus route-neutral time-series archive. | KPI cards, route selector, route exposure, and trend charts. |
| PortOperations_WebMap_Congestion | Operational layer composition and symbology. | Main ArcGIS map inside the custom web dashboard. |
Reference & Candidate Sources
What supports the view, and what is gated.
OpenStreetMap Geometry
Anchorage polygons are useful for M1. Terminal polygons and wharf-edge references are seed geometry and should be replaced or reviewed where coverage is incomplete.
OCEANS-X Reference APIs
Port, location, country, and vessel-type dictionaries can decode operational fields. They are reference data, not route geometry, cargo value, or commercial exposure sources.
Dataminr
Available for future event context, but sampled Singapore/PSA records were noisy and broad. It remains separate from the current congestion score until filtered and licensed for display/cache.
Kpler/Spire Routing
Preferred future route-geometry candidate for distance, duration, ETA, and polyline context, pending current API access, licensing, display rights, and cache limits.