Skip to content

Suggestion: move preliminary calculations to module initialization #41

@efvik

Description

@efvik

Initializing the TimeSeries module currently just sets the variables. I think it would be better to restructure and perform most of the preparations at initialization, rather than in import_data. For example:

  • get date range,
  • get nearest location to coordinates,
  • generate urls
  • test that we can access first and last file

This way we can also print (optional) feedback before downloading is initialized, for example:

  • how many files will be accessed,
  • the time range and number/frequency of timestamps,
  • which location was found and distance+direction from the requested coordinates,
  • approximate size of the dataset, or approximate time to download

This would make it easier to use the api for someone unfamiliar with a product, and make it possible to debug or adjust the request before starting a download.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions