Requirement: Eliminate time correction field as a required, always-present field and retain as an optional field present when needed

[krischer]

Simplification of MiniSEED2: Eliminate time correction field as a required, always-present field and retain as an optional field present when needed.

[chad-earthscope]

miniSEED 2.x contains an always-present field, even though it was rarely used, in the fixed header for time corrections along with a flag indicating whether it had been applied to the record start time. This scenario requires readers to always check the flag and apply the time adjustment if needed to determine the correct start time. This is a no-brainer.

[krischer]

How does this mesh with #21? In my interpretation #21 would make the time correction field obsolete and any tool converting from MiniSEED2 to the new format would have to make the calculation if necessary and directly incorporate it into the record start time.

[chad-earthscope]

In my interpretation #21 would make the time correction field obsolete and any tool converting from MiniSEED2 to the new format would have to make the calculation if necessary and directly incorporate it into the record start time.

This is exactly what I would expect as well. Unapplied time corrections are fixed when moving forward to NGF.

[krischer]

Summary

(Please let me know if I missed a point or misunderstood something)

Please vote on:

1. (Assuming Requirment: Simplify and improve record start time #21 gets a no) Should the time-correction field be optional? (Yes/No)
2. (Assuming Requirment: Simplify and improve record start time #21 gets a yes) Should there be an optional flag "time-correction applied"?

[crotwell]

1 yes
2 no - this is a properly a provenance issue, but a datacenter could increment #13 data/publication version if/when time corrections are applied.

[chad-earthscope]

1. Yes. Assuming we have optional extra headers.
2. No.

[kaestli]

2. No (Assuming we avoid optional extra headers :)
3. No

[ozym]

1. No
2. No

[ketchum-usgs]

yes, use optional header if time is not right
no

[claudiodsf]

1. (Assuming Requirment: Simplify and improve record start time #21 gets a no) Should the time-correction field be optional? (Yes/No)

Yes

2. (Assuming Requirment: Simplify and improve record start time #21 gets a yes) Should there be an optional flag "time-correction applied"?

No. Agree with @crotwell on that this is a provenance issue

[ihenson-bsl]

1. Yes
2. No

[ValleeMartin]

1. Yes
2. No

[JoseAntonioJara]

1. Yes
2. No