Neptun·
IHO S-124 · Navigational Warnings · Edition 2.0.0

Navigational warnings in S-124. Today, not in 2030.

S-100 ECDIS are arriving, but most authorities will publish S-124 warnings only in a few years. Neptun already turns the official warnings of 106 sources into S-124 datasets: validated against the IHO schema, digitally signed, packed as S-100 exchange sets and served by API. For ECDIS and navigation software makers, VDES integrators and test beds.

2.0.0S-124 edition (build 20250729)
112official sources worldwide
Part 15every file signed
≤ 50 KBper dataset, as the spec requires

Why now

IMO's revised ECDIS performance standards (MSC.530(106)) bring S-100 onto the bridge, and S-124 is the product for navigational warnings in it. The specification is ready; the data is not. National coordinators still publish text: NAVTEX, web pages, PDFs. Neptun bridges that gap: you can build, test and demonstrate S-124 in your product today with real, current warnings instead of hand-made samples.

What you get

Each request returns a ZIP containing one S-100 exchange set. Unpacked, it looks like this:

S100_ROOT/ ├── CATALOG.XML exchange catalogue (S-100 Part 17), one signature per dataset ├── CATALOG.SIGN signature of CATALOG.XML (S-100 Part 15) └── S-124/DATASET_FILES/NPTN/ ├── 124NPTN1HDCBB9F.GML one navigational warning = one dataset (≤ 50 KB) ├── 124NPTN7DGH9DE6.GML └── …

Who sent it, and is it unchanged?

S-124 is not just a data format. A receiver has to know who issued a warning and that nobody altered it on the way. Neptun covers three layers:

1 · DataOrigin inside the dataset

Each dataset names the authority that issued the warning in agencyResponsibleForProduction, with its series, number and year. The file name carries our producer code NPTN.

2 · SignatureS-100 Part 15

Every dataset and the catalogue are signed (DSA, SHA-256). The certificates are in the catalogue, so a receiver can check the data without asking us.

3 · TransportHTTPS today, SECOM next

Today: HTTPS with an API key. Next: a SECOM service (IEC 63173-2) where both sides identify with Maritime Connectivity Platform certificates.

What we are, and what we are not

Neptun distributes official warnings; it does not issue them. We sign as Neptun, never in the name of an authority. The original source prevails. Our certificates come from Neptun's own test scheme administrator, not from the IHO scheme used for type-approved ECDIS, so an ECDIS in operation will not accept them. That is fine for development, testing and situational awareness. Every catalogue entry is marked notForNavigation. The data does not replace the official reception of navigational warnings via NAVTEX/GMDSS.

API

GET /v1/warnings/s124?bbox=minLat,minLon,maxLat,maxLon

Exchange set (ZIP) for an area; also lat/lon/radius, lang, source, since. Up to 1,000 datasets per package; page with the X-Neptun-Next-Offset header.

GET /v1/warnings/s124/{mid}

A single warning as an S-124 dataset (GML), by its Neptun ID.

curl -H "Authorization: Bearer mapi_…" -o navarea-x.zip \
  "https://neptun.marine-api.com/v1/warnings/s124?bbox=-60,90,0,170&lang=en"

How a warning becomes S-124

Neptun fieldS-124Note
nts “AUSCOAST 317/26”messageSeriesIdentifierseries AUSCOAST, number 317, year 2026
series namewarningTypeNAVAREA, coastal or local warning
source authorityagencyResponsibleForProductionthe issuing authority
category / kindnavwarnTypeGeneral, navwarnTypeDetailsIHO labels; details only where unambiguous
place, detailnavwarnTitle, informationin the requested language
valid_from / valid_untilfixedDateRange, cancellationDate
closedrestrictionEntry Prohibited
polygon, line, positionS100:Surface, Curve, Pointapproximate positions get no geometry

Check it yourself

Every release is tested against the official IHO schemas (S-124 2.0.0, S-100 5.0.0 exchange catalogue and Part 15), and every signature is verified. You can do the same with the sample and our public certificates:

unzip neptun-s124-sample-navarea-x.zip
xmllint --noout --schema 124_2.0.0.xsd S100_ROOT/S-124/DATASET_FILES/NPTN/*.GML
openssl verify -CAfile neptun-s100-test-root.pem neptun-data-server-nptn.pem

Certificates
Neptun S-100 test scheme administrator SHA-256 906ae33e97a555da640ff24f1620f3502b7d035aebfe1427cd53df1b67fd08cd
Neptun data server NPTN SHA-256 7aa127b7f35efd310f326f9851a3872843d9e91458a57739491b238e57fc4b2a

Next steps

For NAVAREA and national coordinators

Your warnings already exist as text. Neptun turns them into an S-124 draft; your staff check and release it, and it is signed with your own key in your environment. We never see your key. If you want to see your own warnings in S-124, write to us and we will send you a package.

Access and pricing

S-124 is offered on request: trial access for development and testing, and licences for use and redistribution in your product. Write to [email protected] with a sentence about your project.

Questions

Which edition?

S-124 Edition 2.0.0 (IHO schema build 20250729) on the S-100 5.0.0 GML profile.

Why are there no code values in the enumerations?

S-124 makes the numeric code optional. The labels are normative, so we deliver labels only. That way no wrong code can creep in.

Which languages?

The texts come in the language you ask for (lang), and the language code is set in every text element.

Where does the data come from?

From the official sources listed on the coverage page. Each dataset names its authority; the original always prevails.