Skip to content

Open datasets

Monthly datasets derived by Voydar, free to download and reuse under Creative Commons Attribution 4.0. Each one is built only from inputs whose licences allow derived and bulk redistribution; the sources behind every file are listed with it.

Licence: CC BY 4.0. Credit "Voydar (seadar.io)" and the upstream sources listed with each file. Licence text · Terms for embeds, feeds and datasets

Port calls by port and month

How many ships called at each port each month, detected from AIS positions.

Files with data

No files with data are available for this dataset yet.

Empty files · 3 months

These published files contain no data rows. Download them if you need the file structure.

Method

The Voydar port-call detector (v1+detector.v2) run again, for this dataset only, over AIS positions from the permitted feeds alone: a call starts when a ship stays under 2 knots inside a port's geofence for 15 minutes, and ends when it leaves 1.5 times the fence radius. Harbour-service and leisure craft are not counted, and fences without harbour evidence count only ships with an IMO number. A call is counted in the month it began. Coverage is limited to the waters the permitted feeds cover, so counts are lower bounds. seadar.open_port_calls v1+detector.v2

Data dictionary

ColumnTypeDescription
monthdateFirst day of the month (UTC), ISO date.
unlocodetextUN/LOCODE of the port.
port_nametextPort name as shown on Voydar.
country_iso2textISO 3166-1 alpha-2 country of the port.
callsintegerPort calls that began in the month.
vesselsintegerDistinct ships (by MMSI) in the row.
calls_closedintegerCalls whose departure was also observed in the permitted data.
median_dwell_hoursdoubleMedian time in port of the closed calls, in hours (empty when none).
methodtextMethod identifier.
method_versiontextMethod version.
input_sourcestextRegistry ids of the sources whose positions fed this row, separated by "|".

Chokepoint transits by month

Ships that passed through major canals and straits each month, by direction.

Files with data

No files with data are available for this dataset yet.

Empty files · 3 months

These published files contain no data rows. Download them if you need the file structure.

Method

Voydar's gate-line method (v1+transits.v1) over AIS positions from the permitted feeds alone: a ship seen at least a buffer distance on one side of a waterway's gate line and then on the other within the waterway's time limit is one transit. Only ships with a checksum-valid IMO number that are not harbour-service or leisure craft are counted. Counts are lower bounds where coverage is thin. seadar.open_waterway_transits v1+transits.v1

Data dictionary

ColumnTypeDescription
monthdateFirst day of the month (UTC), ISO date.
waterwaytextWaterway slug, as in seadar.io/waterway URLs.
waterway_nametextWaterway name.
from_sidetextSide of the gate line the ship came from: "left" or "right" of the line as drawn (see from_label).
to_sidetextSide of the gate line the ship crossed to.
from_labeltextPlain-language name of the from side (for example "north (Port Said, Mediterranean)").
to_labeltextPlain-language name of the to side.
transitsintegerTransits completed in the month (crossing time in the month).
vesselsintegerDistinct ships (by MMSI) in the row.
methodtextMethod identifier.
method_versiontextMethod version.
input_sourcestextRegistry ids of the sources whose positions fed this row, separated by "|".

Which sources may feed a dataset

A source feeds these datasets only when the Voydar source registry records its derived, bulk and commercial rights as "yes", it is active and not legally uncertain, and its licence has no share-alike term. The check runs at generation time, so a source whose rights change is added or dropped at the next run. AIS feeds whose redistribution terms are unknown (among them AISstream and BarentsWatch) are excluded, which is why coverage is regional for now.

Sources that pass todayDigitraffic marine AIS, Kystverket raw AIS (open tier), Voydar-operated receivers

Stable URLs

Every file has a permanent address. Monthly files never change once published except to fix an error, which the changelog records. "latest" always points at the newest complete month.

https://www.seadar.io/datasets/port-calls-by-port/latest.csv
https://www.seadar.io/datasets/chokepoint-transits/latest.csv
https://www.seadar.io/datasets/index.json

Changelog