Inland Waterway Route Planning: Why Canals Need a Different Planner

Sea routing and inland routing look like the same problem - two points, find the way - and are engineered like different sports. At sea, the water is continuous and the router's job is picking a line across it. Inland, the water is a network: discrete channels connected at junctions, closed by locks, interrupted by bridges, one-way in places. This guide explains how inland routing actually works under the hood, why your sea planner sends you around the coast, and what an inland passage plan needs that a coastal one does not.

#The graph under the water

Every serious inland planner - from commercial barge software to the Dutch consumer apps - is a graph search. The waterway network is stored as nodes (junctions, where a boat can change channel) and edges (the stretches between them, with lengths). Your start point snaps to the nearest edge, the destination likewise, and a shortest-path algorithm walks the graph. The quality of the result is entirely the quality of the network data: which channels exist, which connect, which allow boats. Europe's inland network is thoroughly mapped in open data, which is why inland routing is possible without licensing anything - the Marine OS planner's new inland mode (Dutch network beta) is built as exactly this: an open-data waterway graph with the same shortest-path engine our sea router uses on shipping lanes.

#Why the schedule beats the distance

Coastal planning optimizes distance and weather. Inland planning optimizes appointments. Every opening bridge is a queue that moves on its keeper's schedule; every lock is a chamber cycle you share with whoever arrived first; many close for lunch, weekends, or wind. The practical math: a 40-mile inland day at 6 knots is under 7 hours of water time, but ten bridge waits at 15 minutes each adds 2.5 hours - a third of the day spent stationary and none of it visible on a distance-only plan. Good inland planning therefore lists the interruptions in order with ETAs, exactly the shape of a voyage timeline, so the day's rhythm is known before it starts.

#Clearances: the constraint that does not negotiate

At sea, your draft is the constraint; inland, add your air draft. A fixed bridge with 2.4 meters of clearance is simply a wall for a sailboat, and even bascule bridges have closed clearances that decide whether you wait for an opening or slide under now. National fairway datasets publish exactly this - the Dutch service lists thousands of bridge openings with closed heights and widths - which is why height data belongs inside the planner rather than on a paper chart from three seasons ago. Route planning inland means routing for YOUR boat: the network that exists for a sloep is smaller for a mast.

#What a good inland passage plan contains

1. 1The route through the network - computed over the waterway graph, then adjusted by hand for preference and local knowledge.
2. 2Every bridge and lock in order, with ETA - the day's appointment list.
3. 3Clearances vs your air draft, flagged before departure, not discovered at the bridge.
4. 4Moorings and fuel along the line - inland fuel stops are scarcer than harbors.
5. 5The honest time budget: moving time plus realistic waiting time, with the share link filed ashore like any other passage.

#Frequently asked questions

A graph, an appointment list, and your air draft - that is inland planning in three objects. For the Dutch specifics see the Netherlands canal route planner guide, and for the shared craft, the passage plan guide applies on any water that floats a boat.