How the SunsetVue forecast works
This page describes what the model measures, where it looks, and how a sunset or sunrise ends up with a rating out of five. It also says what the model does not know — including the honest answer about terrain, which is near the bottom and worth reading before you trust a verdict in the mountains.
The forecast running in production is model 1.24.0. Every forecast you have ever run is stored with the version that produced it, and no release ever re-scores an old one.
The idea in one paragraph
The colour in a sunset does not come from the sky above you. It comes from sunlight that has travelled hundreds of kilometres nearly parallel to the ground, losing its blue on the way, before it hits the underside of the clouds over your head and turns them red. That gives a good sunset two separate requirements, and they are in different places: a clear path near the horizon for the light to arrive through, and cloud above you for it to land on. Either one alone gives you nothing. This is why an overcast sky at your house can still produce the best evening of the month, and why a perfectly clear sky usually produces a pale, forgettable one.
Almost everything below is the consequence of taking that one sentence seriously.
Where we look
For each forecast we work out exactly where the sun will set (or rise) for your location and date, then sample the weather at 10 points along that bearing — real coordinates on a great circle, not an approximation. They fall into two groups that do two different jobs.
The canvas — what the light lands on
4 points — 5 km behind you, your own location, 5 km and 20 km toward the sun — covering the cloud you will actually photograph. Here we read how much cloud sits in each layer, how high its base is, how humid and how clear the air is, and how likely rain is.
The point behind you is not a mistake. At sunset the clouds over your shoulder are lit head-on rather than from beneath, and are often the better picture.
The light corridor — what the light has to get through
Points from 50 km out to 350 km toward the sun. Out here we are not asking what the sky looks like; nobody is going to see it. We are asking one question: does the light get through?
Because the Earth curves away, a ray arriving at your horizon was higher up when it passed over each of those distant points. So at each one we only look at the cloud layer the ray actually passes through. Cloud below the ray is ignored — it is under the light, not in front of it.
Cloud above the ray is ignored too, and that half surprises people more. A sheet of high cirrus over a point 50 km away sits 8 km up or more, while the ray is only 0.2 km up there — the light passes underneath it. So the corridor can report an open path on an evening when the whole western sky looks covered, and it is describing the ray rather than the view. What that cirrus does to your own sky is judged separately, by the canvas points above.
| Distance | Height of the ray there | Layer we check |
|---|---|---|
| 50 km | 0.2 km up | low cloud |
| 100 km | 0.8 km up | low cloud |
| 150 km | 1.8 km up | low cloud |
| 200 km | 3.1 km up | mid-level cloud |
| 300 km | 7.1 km up | mid-level cloud |
| 350 km | 9.6 km up | high cloud |
This is why a low bank of cloud on the horizon 50 km away kills a sunset while the same bank 350 km away does not: by then the ray is well above it.
A further 4 points — 2.5 km behind you, 2.5 km, 10 km and 30 km — are sampled for the cross-section chart only. They make the drawing honest at short range and are deliberately excluded from every calculation, so the picture can be denser than the model without changing it.
In time, as well as in space
A sunset is a window, not an instant. We score the sky at the moment the sun crosses the horizon and again an hour either side of it, and we separately work out when the colour is most likely to peak — usually some minutes after the sun has gone, when the light is grazing the cloud base at its flattest angle. The headline number is the crossing itself; the peak moment and a second weather model are folded into the rating you see.
What data it uses
Commercial Open-Meteo forecast data, refreshed hourly. At every sample point we buy:
- Cloud cover in three layers — low (0–3 km), mid (3–8 km) and high (8–12 km), plus total cover.
- Cloud cover at 12 pressure levels, from near the ground to about 12 km up. This is what lets us find the base of a cloud deck rather than just knowing that cloud exists somewhere in a band, and it is what the cross-section draws.
- Where those levels actually are. Pressure is not height, and the textbook conversion is wrong by 60–480 m depending on the weather. We buy the real heights for the forecast hour instead of calculating them.
- Humidity, visibility and precipitation probability — how clean the air is and whether it is about to rain on you.
- Aerosol optical depth at your location: dust, smoke and haze. A moderate amount is what makes reds saturated; too much just makes everything grey.
- A second, independent weather model (ECMWF) over the same geometry. It never changes the engine’s own score — it is there so we can tell you when two forecasts disagree instead of projecting false confidence.
The primary source is Open-Meteo’s best available model for your coordinates, so in the Alps you are usually being served a 2.2 km high-resolution model and in the middle of an ocean a global one. We do not pick per country by hand.
How the rating is calculated
The score is a chain, not a checklist. Four factors multiply together:
score = cloud canvas × light reach × lit share × air quality
Multiplication is the point. If the light cannot arrive, it does not matter how beautiful the cloud overhead is — anything times zero is zero. An earlier version added and subtracted points, which meant a sky with no evidence of light reaching anything still started at “Fair” and only had to avoid penalties. Nothing starts at Fair now; a forecast begins at zero and has to earn its way up.
1. Is there a surface worth lighting? (cloud canvas)
What this sky would be worth if the light arrived. The best case is a broken mid- and high-level canvas — roughly a quarter to three-quarters cover. Too little and you get a clean but pale glow with nothing to catch colour; too much and you get a closed lid, where colour only reaches the edges. A thick low deck overhead is the worst case of all, because it hides the coloured undersides completely — unless you are standing above it, in which case the same deck becomes the subject and scores higher.
2. Can the light get here at all? (light reach)
This is the corridor, combined into a single figure for how much of the light path is blocked. Below about 30% the corridor counts as open; above about 55% it counts as shut, with a sliding scale between.
Two refinements matter. The corridor is weighted by the length of path each sample represents, so adding or moving a sample cannot quietly change the answer. And cover is not the same as opacity: a completely covered layer of thin, high cirrus does not stop a sunset the way a completely covered bank of low stratus does. So a fully covered layer is treated as blocking 100% of the light if it is low, 80% if mid-level and 50% if high.
Those last three figures are the least certain thing in the model. No weather model we can reach publishes cloud optical depth, so they began as estimates from published ranges. We have since checked them against the models’ own forecast of direct sunlight and they held up, but they remain the number most likely to move.
3. Are those clouds actually lit? (lit share)
Having cloud overhead and having a clear corridor is still not enough: the specific deck above you has to be able to see the sun. For each cloud in the scene we trace the ray back toward the horizon and ask whether something closer to the sun is in the way — including other cloud. A canvas whose undersides are all in shadow is not a canvas, it is grey cloud, and no amount of clean air rescues it.
This factor saturates at half: a sky with half its undersides lit is not half a sunset. The lit half is the subject and the shadowed half is usually the contrast that makes the photograph.
4. What is the air like? (air quality)
A modifier on light that has already arrived, deliberately kept close to 1. Moderate aerosol and good visibility saturate the reds and earn a small bonus; heavy haze or very humid air mutes them and costs a little. Clean air never creates a sunset and dirty air never entirely destroys one, so this scales the result — it does not decide it.
Softening rather than zeroing
Two situations used to wipe a forecast out completely and no longer do. A high chance of rain somewhere on the canvas now reduces the score hard instead of zeroing it, because a broken showery sky is exactly the weather that produces the best evenings — we had verified photographs of sunsets the model had called impossible on one rain probability reading. Only overcast at every single sample point still zeroes outright.
What the number means
The raw result is clamped to 0–5 and rounded. The wording you see — Skip, Likely Skip, Maybe, Probably Go, Go — comes from combining the sunset rating (80%) with the Golden Hour rating (20%), when both are available.
The sunset rating itself is the average of every scenario we have: the moment of the event, the predicted best-light moment, and the second weather model. If those disagree, the card says so rather than hiding it behind an average.
The other two ratings
Golden Hour asks a different question — whether warm, usable sunlight will actually reach you and the landscape in front of you while the sun is still low. It is a near-field judgement: it looks only at the cloud close enough to stand between you and the low sun, and ignores the far corridor entirely. Distant cloud can make a spectacular sunset without affecting the golden hour at all, and the reverse happens too.
Sky & clouds rates how visually interesting the weather around you is regardless of whether anything turns red — layering, texture, depth, an undercast below a summit viewpoint. It is shown separately and does not change the Go/Skip recommendation, on purpose: we want to check it against real photographs before letting it move a verdict.
Alongside those, five optical phenomena are evaluated in-app when the conditions and the landscape allow: rainbows, alpenglow, crepuscular rays, valley mist and exceptional clarity.
Terrain: what we use, and what we do not
This is the most important limitation on the page, and it has three parts, because “terrain” means three different things here.
Elevation for pressure and cloud levels
Every sample point carries the elevation of the ground beneath it, and the model uses it. It is how a cloud base measured in pressure becomes a height above your head; it is how we tell a cloud sea below a summit from you standing inside the fog that makes it; and it is why setting your viewpoint’s real altitude on a saved spot changes the result. A cloud layer at 4.2 km is a spectacular undercast from a 3.8 km summit and an ordinary overcast from the valley floor, and the model gets that right only because it knows where you are standing.
The shape of the land — to determine if you are in mountains or not
We also read an elevation profile along the sun bearing to work out whether the landscape can support certain phenomena at all: alpenglow needs mountain faces in the opposite direction, valley mist needs valleys. That profile decides which phenomena are even offered at your location. It does not touch the sunset, Golden Hour or Sky & clouds ratings.
Mountains blocking the light — no, and this is a real gap
The ratings do not check whether a mountain stands between you and the cloud the model says is lit. When the model traces a ray from a distant cloud back toward the setting sun, it asks whether other cloud is in the way. It never asks whether rock is.
We know what this costs, because we have photographed it. At an Alpine viewpoint the model has drawn a lit cloud deck whose underside sat several hundred metres below the ridges standing between the photographer and the sun — the light could not physically have arrived. The same applies to the horizon: when the forecast says the sun should be visible at the horizon, that is a statement about cloud, not about the ridge to your west.
We have built the fix and measured it against our archive of rated forecasts, twice. Both times it changed almost no verdicts while risking real ones, so it has not shipped. What it affects most is the underlight drawn on the cross-section chart, which is why the ground line on that chart carries its own note.
The practical version: in mountains, check your horizon yourself. The model is describing the sky, and it assumes you can see it.
The ground line on the chart
The terrain drawn under the cross-section is real elevation data, sampled along the sun bearing — finely close to you, where one ridge decides the view, and more coarsely far out. It is there so you can judge the geometry the model cannot. It is drawn, and nothing more: no rating reads it.
Other things the model does not know
- It cannot see thickness. The weather models we can reach report how much of the sky a layer covers, not how thick or how bright it is. 100% thin cirrus and 100% dense altostratus look identical to the inputs, and the per-layer figures above are our partial answer to that.
- Its resolution is kilometres, not metres. A grid cell is a few kilometres across. A valley-scale fog bank, a single convective cell, or a cloud that clears your ridge and nothing else is below what the input can describe.
- Cloud beside the line is only partly seen. We sample along the bearing to the sun. A cloud system just off that line, which may well be in your frame, is not directly measured.
- It cannot tell you a spot is safe. SunsetVue forecasts light. It says nothing about trail conditions, avalanche risk, road access or whether you can get back down in the dark. Check the official sources.
When we do not know, we say so
A weather provider sometimes returns nothing for a point. The single most dangerous thing a forecast can do is treat a missing measurement as a good one — an absent cloud reading silently counted as “clear” makes the sky look better, which is the direction that sends someone out to a dead sky.
So a point that did not report is excluded rather than replaced by a plausible number. If part of the light path could not be measured, the card tells you that instead of claiming the corridor is open, the chart draws a gap instead of a line, you are not charged for the forecast, and we do not send a notification on a verdict that rests on something nobody measured.
How we check ourselves
A sunset forecast is a probability, not a promise, and we would rather show our working than our confidence. Every forecast is stored with the exact model version that produced it and can be rated afterwards — the sunset, the golden hour and the sky, separately — and those ratings are what model changes are judged against. Several of the mechanisms described above were found by pointing a webcam archive at a forecast we had got wrong.
Two rules follow from that and are worth stating. Old forecasts are never re-scored: your rating answers “how was the forecast?”, and rewriting the forecast afterwards would destroy the only evidence we have. And the model version is currently frozen. Thirteen model versions, every one of them an improvement, left no single version with enough rated evenings to measure against. It is held at 1.24.0 so that one can reach that point.
Sources and credit
Weather data by Open-Meteo (CC BY 4.0). Elevation from Terrain Tiles on AWS Open Data, produced using Copernicus data funded by the European Union (EU-DEM) and SRTM data courtesy of the U.S. Geological Survey.
Questions about what a particular rating meant are best answered from the forecast itself — every rating on the card opens an explanation of how that specific number was reached. See also the Terms of Service, which set out what you are and are not being promised.