UV index and cloud cover fields can move in opposite directions at elevation. Here’s why, and how to build altitude-aware UV logic in your app.
WeatherAPI condition codes are numeric — but mapping them to user-facing text in multiple locales breaks in subtle ways. Here’s how to build around it.
SWE is missing from most weather API responses. Here’s why, and how to estimate it from totalsnow_cm, temp, and humidity fields you already have.
WBGT isn’t in your API response — but you can derive a useful estimate from temp, humidity, solar radiation, and wind. Here’s how to build it.
moon_phase strings tell you the phase name, not how bright the sky actually is. Here’s how to derive lunar illumination from WeatherAPI’s astronomy fields.
Visibility fields in weather APIs behave differently after dark. Here’s why vis_km breaks down at night and how to build fog detection that accounts for it.
humidity_pct alone tells you almost nothing about water demand. Here’s how to derive ET₀ estimates from WeatherAPI’s hourly fields — and where the math breaks down.
Combining WeatherAPI history and forecast responses by timestamp? Here’s where epoch fields break, how timezones trap you, and the right way to join them.
feelslike_c can mislead at high elevation. Here’s why wind chill and heat index break down above ~2000m, and how to flag it in your app.
Passing city names to WeatherAPI? Here’s what actually happens behind the scenes — and why lat/lon coordinates almost always give you better results.
