Skip to content

Documentation for input dataset requirements / conventions #267

@darothen

Description

@darothen

At the moment, we don't provide any clear documentation on what the structure of input datasets should look like in order to play nicely with EWB:

  • What temporal dimensions do we need? For both the forecast lead time and the epoch/init time?
  • What should the latitude coordinate be named and should it be ascending or descending?
  • What should the longitude coordinate be named and should it run from [0,360) or [-180, 180)?
  • What are the standard naming conventions and units expected for fields?

There are probably more details needed, but this information is critical to explicitly lay out so that users can connect EWB to their own datasets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions