Marine Transportation Data for Developers & Data-Product Builders

The four relevance-3 records lead this ranking, seven relevance-2 workhorses follow and four relevance-1 sources trail — ordered by Datadory quality score inside each band.

11 of the 15 datasets ship JSON — against 675 of 1,744 (38.7%) catalog-wide — and 10 ship CSV, so both a streaming client and a DataFrame loader have native options. AISStream.io frames every message as JSON over WebSocket and publishes OpenAPI 3.0 model definitions for the payload. BarentsWatch returns JSON over HTTPS REST, accepts GeoJSON geometry input and exposes the whole surface as an OpenAPI 3.0 specification you can codegen against. Eurostat serves mar_go, mar_pa and mar_tf as JSON from its dissemination statistics API, with bulk SDMX TSV when you want one file instead of calls. On the reference side, NGA's World Port Index ships GeoJSON next to its shapefile and USACE's WCSC exposes an ArcGIS Feature Service speaking JSON. EMODnet's density maps are the exception worth planning for: GeoTIFF, WMS and WFS only.

AISHub issues access once you register with the data-sharing network. BarentsWatch uses self-registration against the Norwegian Coastal Administration portal. Two statistical sources skip auth by skipping APIs: the UK Department for Transport distributes ODS spreadsheets, and UNCTADstat hands over CSV, gzipped if you take the API route.

For history, invert the pattern: MarineCadastre's USCG Nationwide AIS lands annually as Zstd-compressed daily CSV and GeoParquet, and EMODnet rebuilds its EU vessel-density rasters yearly for WMS and WFS consumption.