Maritime transport - emergency ports WFS

Open data API in a single place

Provided by Kystverket / Geodatatjenesten

Get early access to Maritime transport - emergency ports WFS API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2017.10.18 00:00
Created
2017.10.18
Available languages
English
Keywords
Oljevern, Nødhavn, Oljevernberedskap, Kystverket, Strandsetting, port of refuge, Norwegian Coastal Administration, beaching, oilspill preparedness
Quality scoring

Dataset description

The service includes a description of the Norwegian Coastal Administration's pre-evaluated emergency port locations included in the Norwegian Coastal Administration's emergency response plans. These locations are deemed to be the most relevant locations in which to place ships in distress in order to avoid or limit acute contamination. The data constitutes part of the Norwegian Coastal Administration's decision support tool for use in situations where there is a risk of acute contamination or such contamination has already occurred. In individual situations, any location is a possible emergency port. Emergency port categories: The emergency port locations are divided into three categories. Category 1: Emergency ports that are particularly well-suited to the biggest ships (tankers and large bulk carriers). Category 1 emergency ports will primarily be needed in connection with outer fairways used by tankers, as well as fairways into oil terminals and other ports used by tankers and product tankers. Can also be used by other traffic in the area. Design sizes (metres); Length: 330, Width: 60, Draught: 18 Category 2: Emergency ports for the anticipated traffic in the area. Primarily ships over 5000 BT. Design sizes (metres); Length: 200, Width: 25, Draught: 10.5 Category 3: A third category has been introduced in some Norwegian Coastal Administration regions, with a maximum ship length of 120 metres and a maximum width of 15 metres. The maximum depth is then assessed in each individual case, depending on local conditions, to see whether the ship can approach safely. Design sizes (metres); Length: 120, Width: 15
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks