Choose IJsselmeer or Markermeer first, then combine KNMI lake sectors, managed levels and the actual lock or bridge connection.
Choose the water side of the departure
Enkhuizen is a useful start for an IJsselmeer passage, a Markermeer itinerary or a journey using a lock connection. Record which lake the yacht will enter and the exact departure basin. A town weather result cannot tell you whether the route crosses a lake, waits at a lock or continues into the Wadden Sea.
Keep any onward Wadden passage as another planning stage: lake levels and open-sea tidal streams are different quantities. Do not reuse a North Sea tide table to explain a managed lake level, or a lake forecast to validate a coastal inlet.
Use the named KNMI lake sector
The KNMI coastal-waters text includes IJsselmeer and Marken alongside coastal districts. Select the relevant lake entry and its issue/valid period rather than borrowing the warning for Texel or an offshore continental-shelf area. Check mean wind, changes, visibility and any gust or thunderstorm information in the current product.
Assess short lake waves and fetch
Match wind direction to the available fetch across the planned lake crossing. Inland water is not automatically flat water: a short, steep sea may affect comfort and the ability to hold the intended arrival time. A sheltered berth reading must be compared with route-relevant observations, not promoted to a lake-wide measurement.
Treat locks and bridges as weather constraints
Use Rijkswaterstaat's shipping-information gateway for the current operating times, closures and any wind-related restrictions at the actual structure. Enkhuizen and Lelystad are different connections. Historical inspection or renovation news is not today's operating status; verify the current notice before committing to a long crossing.
Check managed level and arrival access
Waterinfo observations need a station, timestamp and datum. Keep observed lake level separate from a modelled level or a harbour's depth statement. If a delay at the lock would move the arrival into stronger wind or darkness, compare a shorter itinerary and a later start for the whole journey, not just the first lake leg.
Build a repeatable departure brief
Save the lake sector, warning status at its issue time, expected crossing duration and the source for the lock connection. Set a recheck before the last practical return option. This desk is a source-led preparation guide, not live confirmation that a lock is open or a recommended track through shallow water.
Official products by task
- KNMI: coastal waters, IJsselmeer and Marken — Named marine/lake sectors with issue and validity times. Use the lake sector, not the North Sea district; do not turn a warning threshold into a personal departure limit.
- Rijkswaterstaat Waterinfo — Water levels and available water observations; check station, units and datum before comparison.
- Rijkswaterstaat: shipping notices and waterway information — Official gateway to current bridge/lock operating times and closures through Vaarweginformatie. An old project or inspection announcement is not the current operating status.
Waters and onward passages
- IJsselmeer and Markermeer
An inland-water sailing plan needs lake sectors, actual levels and lock information.
- Netherlands coast and Wadden Sea
Use named KNMI coastal sectors and a separate water-level/approach check.
Countries and local sources
- Netherlands
Distinguish North Sea/Wadden, inland lakes and Zeeland waterways before choosing data.
Map orientation
The approximate area centre is not an approach waypoint, a track, a depth survey or a forecast-zone boundary. The third-party map loads only after your click.
Prepare a passage brief
Bring route timings, vessel and crew profile together with checked sources and reassessment triggers. Personal AI analysis and expert review are in invitation-only closed testing. An editorial geographic page does not extend the calculation service’s actual coverage.