WeatherNext 3 gives you hourly forecasts with local detail, but a forecast is only useful if you ask it a specific question. This guide walks through the workflow step by step, then shows how to read the output so it actually changes a decision.
The whole process comes down to four moves: pick a place, pick variables, describe the decision, and read the progression.
Step 1: Choose a location that matches the decision
Start with the ground you care about, not the nearest big city. A wind farm, a distribution hub, a field, and a city centre can sit within 40 km of each other and still see different conditions at 5 km resolution.
Two practical tips:
- If the decision is tied to a fixed asset, use the asset coordinates.
- If the decision covers a route or a region, name the region and then check the forecast at two or three representative points rather than trusting a single centre value.
Step 2: Select variables deliberately
It is tempting to request everything. Resist it. Each variable should map to part of your decision, otherwise it is noise.
| Your decision | Variables that matter most |
|---|---|
| Can we run this outdoor work block? | Precipitation, wind, temperature |
| Is the solar site going to produce? | Radiation, cloud cover, temperature |
| Do we need frost protection tonight? | Temperature, humidity, wind |
| Should we delay a delivery route? | Precipitation, wind, visibility-relevant cloud cover |
| Is a heat response needed? | Temperature, humidity |
WeatherNext 3 resolves targeted temperature and humidity at 5 km and other surface variables at 10 km, so temperature and humidity are usually the sharpest tools available for a specific site.
Step 3: Describe the decision, not just the weather
"Tell me the weather in Berlin" produces a summary. "We have a crane lift scheduled between 09:00 and 13:00, is the wind window usable?" produces an answer.
Include three things:
- The action. What you are deciding to do or not do.
- The window. The hours that matter.
- The threshold. The wind speed, rain rate, temperature, or humidity level at which your plan changes.
When you supply a threshold, the forecast stops being a description and becomes a comparison against your operating limit.
Step 4: Read the progression, not the timestamp
This is where hourly generation pays off. Look at how conditions evolve across the window:
- Timing shifts. If the rain band arrives two hours later than the previous run, the window may still be usable. Compare runs before cancelling.
- Ramp shape. A gradual wind ramp is a different operational problem from a step change, even if both peak at the same speed.
- Persistence. Conditions that stay stable across several consecutive hourly runs are the ones worth planning around.
- Disagreement. When forecasts keep moving between runs, treat the outcome as genuinely uncertain and build in margin.
A worked example: scheduling an outdoor work block
Suppose you need a four-hour window for high-access work with a wind limit of 12 m/s and no active precipitation.
- Enter the site coordinates so the forecast resolves to the asset, not the nearest town.
- Select wind and precipitation, then add temperature if crew safety depends on it.
- State the window, the four-hour duration, and the 12 m/s threshold.
- Compare candidate windows across the next runs. Pick the one where both wind and precipitation stay inside your limits with margin, not the one that merely touches them.
The same structure applies to spraying windows in agriculture, turbine maintenance in energy, and outdoor events in cities. Only the variables and the thresholds change.
Common mistakes to avoid
- Using a city centre for a rural asset. The 5 km grid is fine enough that this matters.
- Reading one run as the final answer. Hourly refresh exists precisely because forecasts move.
- Ignoring humidity with temperature. Frost, fog, and crop stress depend on moisture as much as on heat.
- Forgetting wind direction. Speed tells you whether a window is workable; direction tells you whether it is safe.
- Skipping official warnings. For safety-critical operations, always check the national weather service alongside any forecast tool.
Frequently asked questions
How often should I refresh a forecast during an operation?
Check at least once per hour while the operation is live. Hourly generation means each new run can materially change the timing of a rain band or a wind ramp, and that is exactly the information you want before committing crews.
Which variables should I start with?
Start with precipitation and wind for most outdoor decisions, then add temperature and humidity when the decision is sensitive to cold, heat, frost, or moisture.
Do I need a paid plan to explore forecasts?
You can sign in and explore with the entry plan, and heavier exploration uses more forecast credits. The pricing page shows what each plan includes, and the documentation explains how credits renew.
