Gateway-to-gateway daily transit counting for sparse vessel positions. The first production profile is Suez Canal: wide north/south gateway polygons, UTC event day, deduplicated transitions, and chart-ready daily aggregates.
This screen is for operations and QA as much as analytics: chart first, gateway geometry second, event list third. When counts look wrong, you can inspect the exact day and review what was counted.
This page tracks daily transit counts, directional split, and inferred speed trends for major global waterways using sparse AIS gateway detection. It is optimized for human operators and machine agents: filters are explicit, chart state is deterministic, and source links are stable.
What does Suez transit count mean? It is the number of vessels that crossed between north and south gateway polygons within the selected UTC day and filter.
Why can Suez counts change? Sparse AIS updates, delayed second-gateway hits, and detector backfill can shift day-level totals.
How to read Panama A→B and B→A totals? The directional totals show Pacific-to-Atlantic versus Atlantic-to-Pacific flow balance over the selected window.
What is peak day? Peak day is the single UTC day with maximum detected transits in the current filter state.
Are short straits noisier? Yes. Short transit windows are more sensitive to sparse AIS sampling and edge timing near gateways.
How to validate suspect days? Switch range, click the chart point, and compare directional split against nearby days.
Why monitor these waterways? They are high-impact chokepoints where directional imbalance and speed changes can signal regional trade stress.
What does average speed chart show? It is inferred from transit duration and nominal corridor distance, useful as a trend signal rather than exact SOG.
Can I compare waterways directly? Yes, but compare shape and directionality first; absolute counts vary strongly by corridor geometry and traffic mix.
Where to drill down? Use the detailed TOPOS link and map centering link for each selected waterway.
Stable machine-readable sources: /topos/api/transits/waterways, /topos/api/transits/daily_counts, /topos/api/transits/gateways, /topos/api/transits/qa_review, /topos/api/dashboard/news.
