Overwatch now includes a full year of structured board meeting data across all five supported port authorities — Oakland, Long Beach, Los Angeles, JAXPORT, and the Port Authority of New York and New Jersey. Over 90 meetings and 1,400+ agenda claims have been backfilled and normalized, so you can run cross-port queries against a meaningful historical window from day one. Oakland meetings also include extracted vote outcomes and resolution facts via Legistar. See the data catalog for the full list of port authority tables.
You can now configure how far around a monitored port Overwatch tracks vessels. The new AIS coverage settings let you choose between the default expanded radius (~220 km) and a maximum global range, depending on your coverage needs. This gives you control over the tradeoff between broader vessel visibility and data volume.
AIS position data now follows a structured lifecycle with tiered downsampling. Positions older than 7 days are thinned to one per vessel per minute, and data beyond 30 days is archived to cold storage at full resolution. Retention windows for port events, dark events, STS events, and loitering events have also been tightened. These changes keep the live database performant as data volume grows, with no loss of historical data — archived records can be rehydrated on request.
Access controls have been tightened on civic intelligence and flood exposure datasets. These tables are now subject to the same row-level security policies as the rest of the platform, ensuring that data access is properly scoped to your account. No action is required on your part.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
