Compare Airport Temperature History by Date

Tell the assistant the airport, country and dates you want to review. It confirms the airport and its local clock before finding available temperature readings, so you can compare how the temperature changed.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use Toolmu to compare airport temperature history with https://toolmu.com/tools/get-temperature-series-weather-underground for [airport name] in [country], from [start date] to [end date]. Confirm the exact airport and its local clock from a reliable airport source before preparing the request; do not infer the airport clock from an associated city. If the airport or clock is unclear, ask me a simple airport/location question or request [airport weather page link], then pause if it remains unconfirmed. Act within my existing authorization and budget. Show available temperatures in time order with units, airport local times and the other time labels supplied. Include the daily highs calculated in Celsius from returned readings, with any reported times, counts and gaps. Keep source warnings and explain that missing readings can hide a warmer temperature; do not present calculated highs as official published highs or promise complete coverage.

Task:
Show airport temperature history for [airport name] in [country], from [start date] to [end date], using the airport local dates. Put readings in time order with their units, show daily highs calculated from returned readings, and explain gaps and source warnings.

Paste into your connected AI's conversation.

Connection guide

Up to 0.012 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Weather Underground

Compare Airport Temperature History by Date

You receive

Read the available temperatures in time order with their units and airport local times, keeping the other time labels supplied by the source. Daily summaries can add calculated Celsius highs, the time of each high, and counts and gaps that help you judge the available coverage.

Start with your task

Show airport temperature history for [airport name] in [country], from [start date] to [end date], using the airport local dates. Put readings in time order with their units, show daily highs calculated from returned readings, and explain gaps and source warnings.

What to know

Missing observations can hide a warmer reading. Counts and gaps do not prove that a whole day was observed, and a high calculated from returned readings is not an official published daily high. Keep the source warnings with the results.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
queryParams`queryParams`	`object`	Required	Required fields `country_code, end_date, start_date, station_id, timezone_name`
Last included local date`queryParams.end_date`	`string`	Required	The inclusive final local calendar date, written as YYYYMMDD and interpreted in timezone_name. Use the same start and end value to request one local day.
First local date`queryParams.start_date`	`string`	Required	The first local calendar date to request, written as YYYYMMDD. It is interpreted using timezone_name; 20260930 means September 30, 2026.
Airport ICAO station code`queryParams.station_id`	`string`	Required	The airport weather station's ICAO code, such as KJFK or EFHK. Use icaoCode from a station search result; this request does not use a personal weather station ID.
Station country code`queryParams.country_code`	`string`	Required	The required two-letter ISO country code for the airport station, such as US or FI.
Timezone for local dates`queryParams.timezone_name`	`string`	Required	The required IANA timezone name, such as America/New_York or Europe/Helsinki. It controls local dates and grouping, with daylight-saving transitions handled automatically.

View raw JSON

{
  "type": "object",
  "required": [
    "queryParams"
  ],
  "properties": {
    "queryParams": {
      "type": "object",
      "required": [
        "country_code",
        "end_date",
        "start_date",
        "station_id",
        "timezone_name"
      ],
      "properties": {
        "end_date": {
          "type": "string",
          "description": "End date in YYYYMMDD format, inclusive local calendar date."
        },
        "start_date": {
          "type": "string",
          "description": "Start date in YYYYMMDD format, interpreted as a local calendar date."
        },
        "station_id": {
          "type": "string",
          "description": "Airport station ICAO code (e.g. EFHK, KJFK). Obtain from search endpoint's icaoCode field."
        },
        "country_code": {
          "type": "string",
          "description": "Two-letter ISO country code for the station (e.g. FI, US)."
        },
        "timezone_name": {
          "type": "string",
          "description": "IANA timezone name for local date grouping (e.g. Europe/Helsinki, America/New_York). DST transitions are handled automatically."
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.

Result schema
Field / Path	Type	Meaning
Temperature observation time in UTC`result.data.observations[].observed_at_utc`	`string`	The observation timestamp in UTC. It can have a different calendar date from observed_at_local while referring to the same observation.
Local temperature observation time`result.data.observations[].observed_at_local`	`string`	The observation timestamp in the requested timezone, including its UTC offset. Use it when reading conditions within the selected local dates.
Observation's local date`result.data.observations[].local_date`	`string`	The local calendar date assigned to the observation using the requested timezone.
Observed temperature`result.data.observations[].temp`	`number`	The temperature recorded for this observation. Read the value with temp_unit; an unavailable value is not zero.
Observation temperature unit`result.data.observations[].temp_unit`	`string`	The unit accompanying the observation temperature. C means degrees Celsius; retain the unit with the value.
Local daily-summary date`result.data.daily_maxima[].date`	`string`	The local date represented by the daily maximum, grouped using the requested IANA timezone.
Highest returned temperature in Celsius`result.data.daily_maxima[].max_temp_c`	`number`	The highest temperature calculated from the returned observations for that local date, in degrees Celsius. Gaps can conceal a higher temperature outside the available records.
Local time of the maximum observation`result.data.daily_maxima[].max_observed_at_local`	`string`	The local timestamp supplied for the observation associated with the calculated daily maximum.
UTC time of the maximum observation`result.data.daily_maxima[].max_observed_at_utc`	`string`	The UTC timestamp for the observation associated with the calculated daily maximum; it is separate from the report's retrieval time.
Daily observation count`result.data.daily_maxima[].observation_count`	`number`	The reported number of observation rows for the local date. It does not guarantee one reading per hour or full-day coverage.
Longest observation gap in minutes`result.data.daily_maxima[].largest_gap_minutes`	`number`	The longest reported interval between available observations, in minutes. It does not prove coverage before the first or after the last observation.
Daily maximum's calculation basis`result.data.daily_maxima[].provenance`	`string`	DERIVED_FROM_RETURNED_ROWS identifies a maximum calculated from the returned observations. Keep this calculation label; it is not an official published daily-high value.
Data source note`result.data.data_source_note`	`string`	The response's source warning. UNVERIFIED_TWC_AIRPORT_HISTORY_PROXY identifies unverified TWC airport-history proxy data. Retain this warning with the temperature series.
Timezone used for the series`result.data.request_metadata.timezone_name`	`string`	The timezone recorded for the request. Keep it alongside local dates and times when comparing or sharing the series.

Additional notes

Dates and source context

Keep the selected IANA timezone with the dates when sharing the series. Daylight-saving transitions are handled using that timezone, and a UTC calendar date alone does not define the requested local day.

Source background: Weather Underground data information.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

Use the same date for [start date] and [end date]. The end date is included, using the confirmed airport local clock. If that clock cannot be confirmed from an airport source, the assistant asks a simple clarification or requests [airport weather page link] and pauses if it remains unclear.

Compare Airport Temperature History by Date

Compare Airport Temperature History by Date

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Dates and source context

Fill in the airport and dates

Send the task and confirm

Compare temperatures with gaps

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Dates and source context

Fill in the airport and dates

Send the task and confirm

Compare temperatures with gaps

Questions about this tool.

Can I check just one day?

Does the calculated daily high prove the day's highest temperature?