WEATHER DATA METHODOLOGY

A weather number needs context.

This page defines how climate context, live forecasts and planner recommendations should be kept separate.

Three layers of weather information

01 / CLIMATE

Historical averages

Our city pages show rounded monthly planning ranges from China Meteorological Data Service Centre climate datasets. The representative area is stated because a city-center reading is not a mountain or river forecast.

02 / FORECAST

Short-term conditions

No live forecast is currently presented. When one is added, it must use a commercially permitted provider, a visible timestamp, bounded caching and a readable fallback when the provider fails.

03 / OPERATIONS

Local notices

景区开放、铁路变化和临时通知 must come from the responsible official operator, not from a weather API.

What every number means

  • Monthly high and low are rounded typical temperature ranges in °C; the page can switch them to °F.
  • Rain is rounded monthly precipitation in millimetres, not a promise of rainy-day count.
  • Climate normals use a stated 1981–2010 reference period and review date.
  • Mountain, valley, city-center and nearby scenic conditions can differ materially.
  • Data source and methodology links remain visible beside the planning table.

Failure and update policy

The current climate layer is a bundled fallback, so it remains readable if an external source is unavailable. Live forecasts, when introduced, must be lazy-loaded and must never block the page’s main answer. Historical climate should be reviewed annually; travel recommendations should be reviewed quarterly and after major weather events.