You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some OREX labels (collections) have <start_date_time> in "yyyy-MM-ddZ" format (e.g., 2016-09-08Z) which Harvest could not parse. For example, OREX/OCAMS/data_calibrated/collection_ocams_data_calibrated.xml collection.
It doesn't look like a valid date. A date without time, but with a timezone considered invalid, at least in Java. Timezone usually makes sense if there is both a date and a time.
Need confirmation that "2016-09-08Z" is valid or not in PDS labels.
The text was updated successfully, but these errors were encountered:
Resolves#29Resolves#30
* Handle yyyy-MM-ddZ format
* Handle yyyy-MM-ddZ format
* (1) Use a list instead of a set for multivalues fields. (2) Generate a list of fields in /out folder.
Co-authored-by: Eugene <karpenko@RAYL-AI846797.jpl.nasa.gov>
Some OREX labels (collections) have <start_date_time> in "yyyy-MM-ddZ" format (e.g., 2016-09-08Z) which Harvest could not parse. For example, OREX/OCAMS/data_calibrated/collection_ocams_data_calibrated.xml collection.
It doesn't look like a valid date. A date without time, but with a timezone considered invalid, at least in Java. Timezone usually makes sense if there is both a date and a time.
Need confirmation that "2016-09-08Z" is valid or not in PDS labels.
The text was updated successfully, but these errors were encountered: