Skip to content
New issue

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

Use Forecast Extension instead of package-specific fields #8

Open
m-mohr opened this issue May 14, 2024 · 1 comment
Open

Use Forecast Extension instead of package-specific fields #8

m-mohr opened this issue May 14, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@m-mohr
Copy link

m-mohr commented May 14, 2024

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.

@m-mohr m-mohr added the enhancement New feature or request label May 14, 2024
@TomAugspurger
Copy link
Member

Agreed. We'll probably want the forecast: fields in addition to these, to avoid breaking users relying on the current names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants