The STAC best practices document mentions that data in datacube format should set the start_datetime and end_datetime fields to the start and end of the period the cube is covering. The datetime field should be set to a representative date, if possible.
Currently (as of 0d108ad):
start_datetime nor end_datetime are not setdatetime is set to the processing date
To set start/end_datetime we would need to implement some logic to extract this information from the cube, as it is only implicitly encoded in the asset file name metadata.
The datetime should likely be set to null. I don't see an obvious candidate for a representative date for FORCE datacubes. This is only possible, when start and end datetime are set.
The STAC best practices document mentions that data in datacube format should set the
start_datetimeandend_datetimefields to the start and end of the period the cube is covering. Thedatetimefield should be set to a representative date, if possible.Currently (as of 0d108ad):
start_datetimenorend_datetimeare not setdatetimeis set to the processing dateTo set
start/end_datetimewe would need to implement some logic to extract this information from the cube, as it is only implicitly encoded in the asset file name metadata.The
datetimeshould likely be set to null. I don't see an obvious candidate for a representative date for FORCE datacubes. This is only possible, when start and end datetime are set.