The Data page: all that a route rests on
Is the forecast fresh, does it reach your arrival, is your passage in a fine model's area? The Data page answers before you trust a route.
Before trusting a route, a careful skipper wants to know what it rests on. Is the forecast this morning's or yesterday's? Does it reach far enough to cover the arrival, or will the route stop halfway? Is the passage within a fine regional model, or only seen by the global ones?
The Data page answers all three. For every wind and current model, it shows the run on hand and how far ahead it still forecasts, counted from now, with a warning when a model falls behind; a timeline lays the forecasts along the days, so you see at a glance which ones reach the day you plan to arrive.
Beside the models, it lists what the routes keep off, the coastline from OpenStreetMap and the depths of EMODnet and GEBCO, with how fine each one is, and every name opens a page of its own: who makes it, what it does well, where it errs at sea. And it shows where each one reaches: a map draws the areas of the regional models, which only give a route when both ends of the passage lie inside them; the global ones cover the whole planet.
Say you plan to cross the Bay of Biscay tomorrow, from Brest to A Coruña, two and a half days at sea. The page shows that AROME France, the finest model along the French coast, sees only about two days ahead: its route will stop short of Spain, while the global models reach the arrival. You know before computing which routes will cover the whole crossing, and that on the morning you leave, AROME France's latest run will see much further into it.
The page tells what the routes rest on, not whether the forecast is right: this morning's run can still be wrong, and only the routes compared side by side show where the models disagree. The coastline and the depths are fixed editions, which nothing renews: a sandbank that has shifted since its survey is not on them.