Four times in the last week, the National Weather Service has displayed a current temperature for my town higher than the expected high for the day. Surely if the current temperature is 68° F, the expected high cannot be 62°, it must be at least 68°. Is there any programming language in which that cannot be fixed with a single line of code?
Today the expected high was 49°, while the reported temperature around noon was 63°, which is what it felt like. A fourteen degree discrepancy is impressive, even for government bureaucrats.
Regional phenomenon, I suggest: out here, the expected high has been too high three days running and was scaled back on the fly. (Yesterday, the forecast called for 48; by noon, with the predicted clearing not happening, they dropped it to 43; only briefly did it touch 40.)
I cannot, however, fully explain this:
Tomorrow’s expected high (or “hi”) is 34°, while tomorrow night’s expected low (or “lo”) is 35°. Is that mathematically possible? Surely a nightly low cannot be higher than the high in a directly adjacent day, either before or after? I don’t know when the official switchover from day to night is (sunset?), but if the temperature in the last minute of day is 34° or less, can it really be 35° or more in the first minute of night? If anything, we would expect a relatively sudden drop in temperature at sunset, but today’s forecast implies a sudden jump.
In my neck of the woods, anyway, we tend to expect the lowest temperature of the day right around sunrise, and forecasts for “tonight” often include the qualifier “after midnight” if significant events are anticipated at such hours. But we’ve had rising temperatures overnight many times; all it takes is a wind shift at the right moment. And it’s warmer now, half an hour before the sun, than it was at 8 pm last night.
(With apologies to Victor Borge.)