TRACKING · Tracking record

WeatherNext 3 · Records and changes

Release and subsequent capability and access records for WeatherNext 3.

00
UNDERSTANDING · What we know

Uses, conditions and important changes.

WeatherNext 3 · Based on sources through 6 Sept 2026

WeatherNext 3 adds live satellite inputs and hourly forecasts, with selected surface variables on a 5 km grid. Google describes rollout into its weather services and developer data channels. Model capabilities, local forecast performance and your access to the data remain separate questions.

Conditions and open questions

The 5 km grid does not cover every variable; others use 10 or 25 km. A finer grid does not imply an equal improvement in accuracy. We checked the official description, not forecast performance, regional rollout or account access.

What to check next

Look for performance in specific regions and weather conditions, alongside access requirements for the variables you need.

Full reading and sources →

01
THE FULL RECORD · Full timeline

2 events retained by the site.

This object’s records stay together across live coverage, the watch pool and history. Every event links to its source record; corroboration and material changes have separate labels.

Dates use Beijing time. Open an event for its full record, original source and evidence. Corroboration adds support without counting as a material change.

02
COVERAGE · Record status

How these records are currently listed.

Coverage status describes how this site maintains its records, not whether a product is worth using. Existing records remain available after leaving the current list.

Registered follow-up scope

These are registered scopes, not complete product coverage or a receipt for the latest successful check.

  • WeatherNext 3

    Material follow-up changes on the original page: revisions, data updates, or an official response

    Open the tracked source ↗

03
THE LINEAGE · Lineage

Explore earlier and later versions.

These are the established earlier, later and same-series versions. A version relationship does not establish matching uses, conditions or capabilities.