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

Parse temporal information from collection metadata #139

Open
juliacollins opened this issue Feb 11, 2025 · 0 comments
Open

Parse temporal information from collection metadata #139

juliacollins opened this issue Feb 11, 2025 · 0 comments

Comments

@juliacollins
Copy link
Contributor

juliacollins commented Feb 11, 2025

issue-15 implemented the step to communicate with CMR and retrieve collection metadata if it exists. The entire TemporalExtents element is currently saved in a Collection class object. An example of the TemporalExtents element for SNEX23_SSADUCk is shown below. Representations for collections with a single date and time, or periodic dates/times, are slightly different.

Based on a quick comparison of the UMM-G schema and the UMM-C schema, the main difference between the two is that collections can have an array of TemporalExtent elements, whereas a granule can only have a single range of date/time values (begin and end) or a single date/time value. If a collection only has one TemporalExtent element then it's straightforward to apply that one RangeDateTime or SingleDateTime to each granule. If the collection has multiple temporal extent entries (i.e. an array of RangeDateTime objects), then we may not want to mess with using the collection metadata at all to populate UMM-G temporal information. My guess is that we'd need to merge the multiple collection TemporalExtent elements into a range that covers all of the collection objects and apply that big range to the granule, which seems like it might be a fairly inaccurate representation.

Outcome of this story: MetGenC can extract a single collection temporal information RangeDateTime or SingleDateTime object (if there is only one) and use it to populate the temporal information in UMM-G output.

Story points: 2, assuming we would only apply this feature to collections with a single temporal extent.

References:

"TemporalExtents": [
      {
        "EndsAtPresentFlag": false,
        "RangeDateTimes": [
          {
            "BeginningDateTime": "2023-03-06T00:00:00.000Z",
            "EndingDateTime": "2023-03-16T23:59:59.999Z"
          }
        ]
      }
 ],
@lisakaser lisakaser added this to the Dec-Jan-Feb milestone Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants