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

Configure attribute names that provide time coverage start and end #57

Open
forman opened this issue Jan 18, 2022 · 0 comments
Open

Configure attribute names that provide time coverage start and end #57

forman opened this issue Jan 18, 2022 · 0 comments

Comments

@forman
Copy link
Member

forman commented Jan 18, 2022

Users are currently forced to write a custom pre-processor if time coverage start and end is not given by CF attributes time_coverage_start and time_coverage_end. This can be avoided by simple configuration.

Proposal

input:
  # Names of global attributes that provide time coverage start and end.
  # Yields `time_bnds` coordinate pair and `time` timestamp (the pair's center value)
  time_bnds_attr_names = ['time_coverage_start', 'time_coverage_end']
  # The name of the global attribute that provides the data's timestamp.
  # If not given the `time_bnds` pair's center value is used.
  time_attr_name = null

Example:

input:
  time_attr_name = 'observation_date'
  time_bnds_attr_names = ['start_date', 'stop_date']
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant