Now you save an area on the map, click it, and get the aggregated forecast for the whole region: the median inside a min–max band, with direction and the peak location highlighted.
Whoever runs an operation rarely watches a single point. They watch an area: a bay, an access channel, an offshore field, a stretch of coastline. But the forecast has always been read point by point. You picked a coordinate, opened the meteogram, and hoped that point represented the whole surrounding region well.
Weather, though, isn't uniform across an area. On a 3 km grid, an entire bay is covered by dozens of computation cells, and they can disagree with one another: the wind coming through the inlet, the gust funneled by the terrain, the rain covering only half the field. A single point doesn't tell that whole story.
From now on, you read the forecast for the entire area at once.
On the Forecast screen, your saved areas now appear on the map as polygons. Clicking inside one opens a menu with three actions: "View forecast", "Create event", and "Remove area".
Under "View forecast", the panel opens with the area's meteogram. Instead of a single line, you see two readings at the same time, computed every hour over all the grid cells inside the polygon:
Just like the point meteogram, you choose which forecast to use (where more than one is available) and see the last update of the selected source. You pick one variable at a time, in the same sidebar you already know from points.
The band between the minimum and the maximum isn't there to clutter the chart. It answers a question a single point never could: how much conditions vary inside your area.
It's the same logic as always at i4sea: more spatial context, less blind reading of an isolated number. The variation inside the area isn't a flaw in the data. It's the data telling you your region isn't homogeneous.
Intensity without direction only gets you halfway to a decision. That's why, for wind variables, the area forecast carries direction arrows over the median line, computed for each hour over the same cells. Direction always rides with intensity; it never appears on its own.
And when you hover over an hour on the chart, the map marks the cell where the maximum value occurs at that instant. So beyond knowing how strong, you know where: which edge of the bay, which part of the field, which end of the channel holds the most severe condition. The marker follows the cursor and disappears when you leave the chart.
For an area's forecast to exist, the area itself has to exist first. The Locations screen was rebuilt from scratch for that.
It now lists, in a native table, the locations saved by you or your company, with Name, Coordinate Type (Point or Area), and the actions to edit and delete. A name search and a type filter help you find what you're after when the list grows.
Under "Create Locality", a side panel guides the setup. For an area, you have three paths:
Editing, renaming, and deleting all live in the same panel, with a confirmation before removal and a clear message when the area is in use by an operation rule.
With several locations saved, the Forecast map could get crowded. That's why it gained visibility controls.
The "Show/hide locations" panel lets you filter by type, turn each location on and off individually, and return to the full view with one click. And "Map clipping" lets you draw a region and keep on the map only what's inside it, handy when you want to focus on a specific sector of the operation. Your choices are kept between visits.
The operation happens over an area, and now the forecast does too. Instead of picking a point and hoping it represents the whole region, you click the saved area and read, all at once, the central condition, how much it varies in space, the direction, and where the peak is. Less guessing, more reading of the real scenario.
Questions or suggestions? Talk to our team. The area forecast was born from conversations with the people who monitor entire regions every day.