The quantity stored is currently the start time. So we should use datetime_start, but then also include a datetime_length to still allow calculation of datetime again (or just store a calculated datetime together with datetime_start).
The datetime length is given by the time_coverage_resolution global attribute (in ISO 8601 "PT%(interval_seconds)fS" format). For most products this is 1080 ms in nominal operation, except for "L2O3PR", which uses 3240 ms due to coaddition.
The quantity stored is currently the start time. So we should use
datetime_start
, but then also include adatetime_length
to still allow calculation ofdatetime
again (or just store a calculateddatetime
together withdatetime_start
).The datetime length is given by the
time_coverage_resolution
global attribute (in ISO 8601 "PT%(interval_seconds)fS" format). For most products this is 1080 ms in nominal operation, except for "L2O3PR", which uses 3240 ms due to coaddition.