Skip to content

Restrict scripts to only work with specific extents #52

@atteggiani

Description

@atteggiani

The high-resolution data doesn't cover all the globe, but has specific spatial extents that cover a region around Australia.
For example, for the BARRA2R dataset, the extents are the following:

  • time: 1979-01, 2024-09
  • lat: -57.97, 12.98
  • lon: 88.48, 207.39

This restriction should be captured within the script, to:

  • allow proper unit-testing
  • make it clearer what the inputs of the function(s) can be

Also, it might be good to point out these extents also within the suite, so the users know that they shouldn't set dates or lat/lon nest beyond these limitations, otherwise the suite would fail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    New Issues

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions