OpenNavData — open official data along your route · Help · What's new · Coverage by country · About

What changed in OpenNavData that you can see, newest first.

beta 3.0 — 2026-10-31

• The Northern Sea Route on request. A scenario can now go «via the Northern Sea Route»: the NSR opens for that scenario only, and the table says how many miles of the route lie in the NSR water area and which of the Rules' areas it crosses — or that the route found does not use it. The NSR water area is the one the Merchant Shipping Code of the Russian Federation (art. 5.1) describes, built from VLIZ's Maritime Boundaries (an approximation, no legal value). The Northwest Passage stays closed. Every run through the NSR says that navigation there requires a permit and that ice class, season, ice conditions and icebreaker escort are not modelled.
• Ice class. The Vessel section takes a Russian Register ice class; on an NSR route the Rules' admission criteria for that class are shown for the area groups crossed — shown, never applied.
• NSR / icebreaker fee. Entered per scenario; the tariff is not computed (Help 02, 13).

beta 2.9 — 2026-10-30

• Canada's ENC cells are in our catalogues. With CHS's permission, the Canadian cells of PRIMAR's catalogue are listed again, with Canada's own cell limits from the Canadian Hydrographic Service: a Canadian cell is selected when either PRIMAR's box or CHS's limit meets the corridor, the map draws CHS's limit, and a cell CHS lists that PRIMAR lacks is a row of its own. The line «Canada's cells are not in our catalogues» is gone. Wherever a Canadian cell is listed — the map's legend, the Cells tab, the CSV, the RTZ, Coverage by country — the source reads S57 Individual ENC Limits — Fisheries and Oceans Canada / Canadian Hydrographic Service. Only the limits with the cell's name, title, scale and last update date are used — no chart content (Help 02, 09).

beta 2.8.1 — 2026-10-29

• Arctic routes are no longer offered. Without a vessel profile, a route between East Asia and Northern Europe could take the Northern Sea Route when it was the shorter way, with nothing on the route saying so — Yokohama to Hamburg went north of 74° N. Until the Arctic has a task of its own (ice class, permit and season said, a choice you make), it is closed on every run: such routes now go by Suez or round a cape, and a route only the Arctic could give is refused in those words — routes to ports on the Northern Sea Route itself (Dudinka, Pevek, Sabetta) among them (Help 02).

beta 2.8 — 2026-10-29

• Scenarios: one voyage, several routes side by side. The new Scenarios tab («③ Compare scenarios») runs up to four variants of a voyage — continue to the destination, divert to another port, through a canal or round a cape — each with its route and its estimate, and shows their figures in one table with each figure's difference from a column you set. It ranks and colours nothing. The map draws every scenario's route, each with its own dash pattern and letter; one at a time with its corridor and cells (Help 13).
• Close a passage for one run. A scenario can close the Suez Canal, the Panama Canal, the Cape of Good Hope, or Cape Horn with the Strait of Magellan, so «round the Cape» is a route of its own; the table says which passages each route runs through. With passages closed, the Arctic is not offered (Help 13).
• From a position: the last port of call for EU ETS. A voyage that starts at sea can name its last port of call; EU ETS then counts the voyage from that port, as MRV does (Help 13).
• A route from a position to a port now starts at the position. With a position as Departure and a port as Destination, the route was built from the port to the position: the cells were the same, but the direction was reversed — in the estimate, the ETA, the times MARPOL areas are entered with a speed, and the RTZ. It now runs as typed.

beta 2.7.4 — 2026-10-28

• The corridor is closed round at every turn. Where a route turns at a waypoint, each leg's corridor used to end flat at the waypoint, so a wedge outside the turn — within 1.25 nm of the waypoint itself — belonged to no leg, and a cell lying only there was missed. Each such waypoint now carries a 1.25 nm disc, so everything within the half-width of the waypoint is in the corridor. On the routes we check this lists one cell that was missed and drops none (Help 03).

beta 2.7.3 — 2026-10-27

• Turku and Naantali reach the sea by the deep fairway. The Utö–Naantali fairway (VL1, published design draught 15.1 m) ended south of Utö with no link to the open-sea network, so with a draft of 10 m a route out of Turku or Naantali took two inner fairways with no published depth. Its sea end is now joined to the open-sea network 9.9 nm due south, in open water: at 10 m these routes keep to the 15.1 m fairway (about 6–7 nm longer). Without a draft the routes are as before.

beta 2.7.2 — 2026-10-27

• The corridor is one shaded area. On a long route the corridor is computed in parts; each part used to be drawn with its own outline, so the joins showed as double lines. Once the run is complete, the corridor is drawn once, as one shape, shaded with no outline: in harbours its outline drew a comb of strokes (Help 04).
• «Cells in view» on the map. The catalogue grid now has its own switch on the map, with the band chips and a line that says how many cells are in view, when to zoom in to see them one by one, and when the view holds more than the 4 000 one answer carries (Help 04).

beta 2.7.1 — 2026-10-27

• No cell missed on very long legs. A leg too wide for one map projection — the Cape of Good Hope to the Gulf of Guinea on the Cape route — was left without cells («cells not computed for this leg»); six cells were missing there. Such a leg is now worked in parts along its own line, and every cell it crosses is listed under the leg (Help 02).
• A stretch whose cells could not be computed is shown on the map, on the route line in the warning colour, dotted, with the reason (Help 04).

beta 2.7 — 2026-10-27

• Your draft now closes shallow fairways. With a draft entered, an official fairway whose published depth is below it is no longer used: the route goes round it, and says which stretch it avoided (Finland's design draught; the U.S. Army Corps channels, the lesser of the maintained and the authorized depth). Finnish small-boat fairways (classes VL5 and VL6, published as at most 2.5 m deep) close for a draft above 2.5 m. Where a fairway publishes no depth, the route prefers fairways that do, and each stretch without a depth is named (Help 02).
• When the only way into a port is too shallow, the run says so — «no route for draft 12 m: HOUSTON (maintained 11.3 m, authorized 11.3 m, USACE) is the only way out» — and offers Build without the draft limit: the route as without a draft, its cells, and the depth caution, for a port you enter on the tide.

beta 2.6.3 — 2026-10-27

• Edit: a click on a leg adds a waypoint again. On a route that enters or leaves an emission control area (ECA) the map's ECA marks took every click, so in Edit only dragging worked; a click or a tap on a leg now adds a waypoint there, with every layer on (Help 05).
• Day theme: every button's label is readable. Edit's label vanished (white on white) while Edit was on; the alerts' count and the estimate page's Estimate button are clearer too.

beta 2.6.2 — 2026-10-25

• Port Said: routes now use the traffic lane (TSS). Westbound Suez transits went round the north-west approaches to Port Said; they now enter the traffic lane (TSS) from the canal approach and leave it at its north-west end — about 12 nm shorter (Ras Laffan → Rotterdam). In the schemes taken from OpenStreetMap a route may now join the global network between two of its points, not only at them, so it reaches a traffic lane (TSS) by a short connector where the network is sparse (Help 04).

beta 2.6.1 — 2026-10-25

• Routes outside the United States are no longer refused where our catalogues have cells. Djibouti → Jeddah, Port Klang → Singapore, Algeciras → Genoa and similar routes were refused «region not covered yet»; they now get their cell list. Only a route with no cell of ours anywhere near it is refused (Help 01).
• No cell missed on long legs. A long leg's corridor now follows the line the leg declares (a rhumb line; a great circle where your RTZ says Orthodrome) as well as the straight line, and the largest catalogue cells keep their true outline. Cells that were missed are now listed — for example Norway's overview cell on every North Sea route and three cells on the Suez routes (Help 02).

beta 2.6 — 2026-10-24

• More traffic separation schemes. Routes now also follow the schemes off Ushant, off the Casquets and in the Corsica Channel (SHOM), and five schemes drawn by OpenStreetMap: Bab el-Mandeb, the north-west approaches to Port Said, the Strait of Gibraltar, the Malacca Strait at One Fathom Bank and the German Bight. About two hundred more OpenStreetMap schemes are drawn grey and dotted — shown, not used for routing. The Strait of Hormuz and the Dardanelles are listed as gaps on the coverage page (Help 04).

beta 2.5 — 2026-10-24

• Cells along routes outside U.S. waters. The catalogue is now our catalogues: NOAA's open data and PRIMAR's ENC catalogue together, by PRIMAR's permission — most of the world's ENC cells. Each cell names its source; where catalogues disagree on the edition, the newest stands and the row says so. Stretches no catalogue covers say «not in our catalogues». Your exchange set still adds your own catalogue and permits (Help 01, 02).

beta 2.4 — 2026-10-23

• Cleaner turns where traffic lane (TSS) parts meet. At the joins in the Dover Strait, off Porkkala, off Kalbådagrund and in the Kvarken the route now turns once, keeping within 20° of each part's direction of traffic, instead of running on to the end of one part and back (Help 04).
• Edit is no longer shown as pressed after a route is built. When legs are hatched on the map for review, the button shows how many: «Edit · 2» (Help 05).

beta 2.3 — 2026-10-23

• Straighter routes through traffic separation schemes. Inside the Dover Strait and the Finnish schemes the route no longer zigzags at the joins of traffic lane (TSS) parts: turn points are dropped where a straight leg stays clear of separation zones and lines and keeps the direction of traffic. Routes through these schemes are a little shorter; the RTZ, the CSV, the API and the estimate use the same line (Help 04).

beta 2.2 — 2026-10-23

• Voyage estimate: one reference fuel. Consumption is entered for one fuel; the others are converted by lower calorific value (MGO is 94 % of the VLSFO mass for the same energy, IMO MEPC.364(79)). Estimates with MGO inside ECAs come out lower than before.
• The route on the estimate: a line with its ports, miles and ECA miles, a small map, and «route changed — update» when the route page builds another.
• Prices as of (fuel and EUA), in the result and the CSV.
• Inputs to a file and two demo files. EU MRV consumption is now read for ships whose latest EU report is from before 2024 (Help 12).

beta 2.1 — 2026-10-23

• Routes follow the Finnish traffic separation schemes (Traficom) where they are complete in the data: off Porkkala with the Helsinki approach, off Kalbådagrund and in the Kvarken — in their traffic lanes (TSS) only in the direction of traffic, never through a separation zone. Helsinki to and from Rotterdam and Hamburg now run 0 nm against a traffic lane (TSS). Schemes that the data hold only in part (off Hanko, the Åland Sea, near Sommers and Gogland) are drawn grey and dotted: shown, not used for routing (Help 04).

beta 2.0 — 2026-10-22

• Two numbered buttons. «① Build route» and «② Estimate voyage», each with a line saying what it does; the next step is the filled one. «② Estimate voyage» builds the route first if there is none.
• The voyage estimate is a tab of the route page, «Voyage estimate», after Catalogue; it keeps its own address, /estimate. Its sources are one «Data:» line and a collapsed «Sources and licences» block.
• Traffic separation schemes in magenta, as on charts: the separation zones a translucent magenta fill; the direction arrows outlined and shown from zoom 9.
• The route's direction: one small arrow per leg long enough to carry one on the screen.

beta 1.9 — 2026-10-22

• Voyage estimate: help on every field. An (i) beside each label says what the field is and where the figure comes from. The consumption hint shows the typical range for the ship's type from EU MRV. The IMO lookup now gives the ship's name from Wikidata and the year built, and says why a field stayed empty. With no keel date, NOx Tier III is inferred from the year built and marked as inferred (Help 12).

beta 1.8 — 2026-10-22

• Voyage estimate. From a route: enter the IMO number, check the questionnaire prefilled from open sources (each value with its source and date), get sea and port days, fuel inside and outside each ECA, emissions, EU ETS, costs, result and TCE — an estimate for commercial planning, not a passage plan (Help 12). Opens from the run panel.

beta 1.7 — 2026-10-21

• Routes through the Dover Strait follow its traffic separation scheme (SHOM): inside a traffic lane (TSS) only in its direction of traffic, never through a separation zone, joining and leaving at its ends; the inshore traffic zones are closed to through traffic and the deep-water route is closed (Help 04). Routes elsewhere are unchanged.

beta 1.6 — 2026-10-21

• Warnings sources along the route. A new Warnings tab lists the sources to consult for navigational warnings: the NAVTEX stations in range, their NAVAREA coordinators and the national services, each with its official page and when we last checked it. No warning text is shown (Help 11).

beta 1.5 — 2026-10-21

• Vessel profile. Gross tonnage, passenger ship, keel date and Tier III engines now decide whether a MARPOL row's rule applies to your vessel — the 400 GT oil rule, the Baltic passenger-ship sewage rule, NOx Tier III in each NECA. Save the whole profile to a file and load it again, or keep it in this browser by choice; nothing is stored on our server (Help 10, Agreement §2).

beta 1.4 — 2026-10-18

• Traffic separation schemes on the map (2026-10-21). The Dover Strait scheme — lanes with their direction, separation zones and lines, the inshore traffic zones, the deep-water route — from SHOM (Licence Ouverte 2.0). Display only: routes do not follow it yet (Help 04).
• Korea's official fairway areas. KHOA's statutory port fairways, traffic routes and three traffic separation schemes are on the map (from zoom 8) and along your route: every area within 1.25 nm of a Korean route is listed and widens the corridor. There is no Korean network yet — the route keeps its own path. The source says parts may be missing; the Legend and the Log say so (Help 04).

beta 1.3 — 2026-10-16

• Korea's national sulphur areas. Five Korean port areas (Incheon and Pyeongtaek-Dangjin, Yeosu and Gwangyang, Busan, Busan west, Ulsan) where Korean law limits fuel sulphur to 0.1 % by weight show on the MARPOL tab as national rows — never «ECA», each line says «national rule, not MARPOL» — with their own RTZ points «NAT IN / OUT» (Help 10).

beta 1.2 — 2026-10-15

• Cancelled cells in your product list. A cell your product list carries with edition 0 (cancelled) no longer appears when its successor is selected — the journal names both. With no successor selected it stays, with the remark cancelled-in-catalogue and its own reason, and it is not counted in the permits (Help 06).
• Inland waters under the North American and US Caribbean ECAs. US internal waters and Canadian waters south of 60° N, the St. Lawrence and the Great Lakes included, now count inside the ECA, as US and Canadian law has it: a route up the Columbia or the St. Lawrence no longer shows «ECA OUT» on the river. The map still draws the sea area only; the row and the Log say so (Help 10).

beta 1.1 — 2026-10-09

• The Layers panel is one row per theme. Three rows before a run — Official fairways (zones, then centrelines from zoom 6, then the fairway areas from zoom 8), ENC cells (the chosen catalogue's grid; the Catalogue tab's band filter is what the map draws, bands 4–6 until you touch it) and MARPOL areas (the ECAs; the special areas by a switch on the MARPOL tab) — and after a run the group Route with Cells and Corridor. The route and the basemap are always drawn and have no row. A run never resets a switch. Traffic density and calibration left the panel; they are read on Coverage by country. Help 04 and the Legend follow.

beta 1.0 — 2026-10-08

• MARPOL zones along the route. Emission control areas (MARPOL ECA) and the special areas of Annexes I, II, IV and V as a map layer; the crossings table — entry and exit, miles and hours inside, the requirement in one sentence with its source — on the MARPOL tab and as a CSV of its own; a one-page report for print. A Voyage group in Input (departure date, speed) says which date the zones are judged by; the Run checkboxes choose what is computed along the route. The RTZ export can add «ECA IN / OUT» waypoints at the boundaries. Not compliance advice.

beta 0.9 — 2026-10-05

• The switch keeps the view. Switching day and night no longer moves the map — centre and zoom stay exactly where they were. The overview band is a shade brighter at night.

beta 0.8 — 2026-10-05

• Day and night. A second palette for a lit bridge: the button beside the bell switches; the first visit follows your system's setting, a press is remembered. Every colour keeps its meaning in both.

beta 0.7 — 2026-10-05

• Small things. Zoomed out, a click on the catalogue grid says «zoom in to pick cells»; the page's scripts and styles load with a version in their address, so a new release never runs with old files.

beta 0.6 — 2026-10-04

• Catalogue, after use with a 27 000-cell set. The producer filter is a searchable list instead of a wall of chips; a click on the map's grid adds a cell again whatever was switched on first; producers without a country in the S-62 register read by code and name; the list no longer runs under the footer on a short screen.

beta 0.5 — 2026-10-04

• Japan's notice where you read the result. When a run used the Japan Coast Guard's data, the required notice (Japanese and English) and its source line sit under the result line — no need to open the Log — and in the CSV header.
• One note per stretch. The vessel-draft note on official channels and the Maritime Traffic Safety Act note now come one per stretch of the fairway, each with its marker, instead of one per leg.

beta 0.4 — 2026-10-04

• U.S. channel depths. On U.S. Army Corps channels the vessel-draft note now fires on the lesser of the maintained and the authorized depth and names both, with the channel reach.
• Clearer refusal. When your vessel's closed passages leave no route, the line reads «no route without passages closed for this vessel: …».

beta 0.3 — 2026-10-04

• Catalogue. A third tab lists the whole catalogue — open data or your exchange set — with filters by producer and band and a search; add any cell to your list or remove one, in the list or by clicking it on the map («show grid on map»). Added cells go into the cost, the CSV and the RTZ.

beta 0.2 — 2026-10-03

• Optimise the list. Untick whole groups at once — by producer country or by band — beside «exclude overlaps»; the warning names any stretch left without its scale, and an optimised list says so, with what you applied, on the result line, in the CSV and in the RTZ.

beta 0.1 — 2026-10-02

Everything that arrived since the first public version (2026-09-26):

• Your own product list. Attach your ENC exchange set and permits: the cell list then says which cells you already own and which you would buy.
• Vessel profile. Give a vessel class or your ship's dimensions, and routes avoid canals and straits whose published limits the ship exceeds.
• On the phone. The map comes first; the cell list is a list of cards you can scroll with one thumb.
• Choose the catalogue. Open data (U.S. waters) or your own exchange set — the run says which one it used.
• Download CSV from the map. The Run panel has the same «Download CSV» as the cell table.
• Country and title of every cell. Each cell shows the country of its producer and, where the catalogue gives it, its full title.
• Choose the cells. Untick the cells you do not want, or «exclude overlaps» in one click; a warning names every stretch of the route left without a cell of its scale.
• Japan. Routes in Japanese waters follow the Japan Coast Guard's traffic routes and port passages; inside the Maritime Traffic Safety Act fairways a note reminds you their rules apply.
• Notes you can see. The result line counts the run's warnings and notes, and the bell shows the notes as a second, muted number.
• Coverage by country. A page (footer link) lists what is known for each country — fairway network, cell coverage, traffic calibration, density — with the source, its licence and when it was downloaded.

Indicative corridor for data-procurement planning. Not a passage plan. Not for navigation.