WeatherNext 3 License: Code, Data and Commercial Use

WeatherNext 3 does not have one blanket license. Google separates the terms for published code and research materials, real-time forecast data and historical data. This guide maps those paths and the questions to resolve before shipping a public product. It is an independent research summary, not legal advice. Verify the current official terms and review your exact use case. Published October 20, 2026.

Research summary, not legal advice · check the current Google terms before production use · compare access paths

A weather globe wrapped in transparent layered access boundaries

What are you licensing?

The asset matters more than the WeatherNext 3 brand name. Code, diagrams, historical fields and future forecasts follow different rules.

Code and notebooks

Google states that WeatherNext open-model notebooks and associated code use Apache License 2.0. Keep the license notice and comply with its conditions.

Other research materials

Google states that other materials on the open-model page use CC BY 4.0. Attribution and modification records matter.

Real-time or future data

Forecast data relating to a time less than one hour ago or in the future uses the separate GDM Real-Time Weather Forecasting Experimental Data Terms of Use.

Historical data

Data relating to a time at least one hour ago is documented as CC BY 4.0. The same field changes classification as it ages past that threshold.

A practical licensing matrix

These are the first questions to answer before a team publishes, redistributes or builds on WeatherNext 3.

Is the data real-time?

If the meteorological valid time is less than one hour ago or still in the future, the real-time experimental terms apply according to Google's access documentation.

Is the data historical?

If the valid time is one hour or more in the past, Google documents CC BY 4.0 licensing. Attribute the source and identify modifications.

Is the cost separate?

A data license does not make the underlying Google Cloud infrastructure free. Storage, query, egress and compute charges can still apply.

Will users recover the forecast?

A public product may display a derived answer while still allowing users to recover the underlying forecast. Review whether the intended interface crosses the real-time data restrictions.

Before you build

Run these four checks

The legal and operational review should happen before the data pipeline becomes production infrastructure.

1

Inventory the assets

List code, notebooks, maps, model outputs, real-time fields, historical archives and third-party datasets separately.

2

Match the current terms

Open the official terms for each asset class. Save the version or access date used for the review instead of relying on a search snippet.

3

Review the product surface

Describe what users see, download and can recover. A value-added answer, a raw data browser and a public API create different compliance questions.

4

Record attribution and changes

Keep the required notices, source attribution and a record of transformations. Ask counsel before a commercial public launch.

WeatherNext 3 licensing questions

Short answers to common commercial-use and redistribution questions.







Official starting points: model and data licensing, forecast access FAQ, open models and the real-time experimental terms.

Choose the access path before the build

Compare the independent forecast experience, the managed subscription and the raw Google Cloud channels. Seven-day free trial, cancel anytime. Background: data access and API pricing.

WeatherNext 3 License: Code, Data & Commercial Use