We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The fields
"ecmwf:reference_datetime": "2022-02-01T00:00:00Z", "ecmwf:forecast_datetime": "2022-02-01T00:00:00Z", "ecmwf:step": "0h",
are also defined in the forecast extension. The fields should be preferred over the fields used here.
The text was updated successfully, but these errors were encountered:
Agreed. We'll probably want the forecast: fields in addition to these, to avoid breaking users relying on the current names.
forecast:
Sorry, something went wrong.
No branches or pull requests
The fields
are also defined in the forecast extension. The fields should be preferred over the fields used here.
The text was updated successfully, but these errors were encountered: