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
A 0 is being added to the tenths place in station level endtime decimal seconds when converting from stationxml to dataless seed. This is a likely associated with keeping a correct Bytes count but need to be investigated.
StationXML Representation of Station LA03 EndTime:
2022-03-02T13:35:33.205000Z
Dataless Representation of Station LA03 EndTime:
LA03: 2019,181,01:47:40.0000~2022,061,13:35:33.0205
The text was updated successfully, but these errors were encountered:
Not sure if this needs a separate bug report, but to add:
When converting stationxml -> dataless, epoch times with fractional seconds with leading zeros sometimes results in the zero being removed such that XX.0919 will become XX.919
Thank you for reporting this. This does sound related. Just hazarding a guess, but the fractions of a second might be getting stored as a separate integer, wherein during the encoding the left-leading zeroes get truncated.
A 0 is being added to the tenths place in station level endtime decimal seconds when converting from stationxml to dataless seed. This is a likely associated with keeping a correct Bytes count but need to be investigated.
StationXML Representation of Station LA03 EndTime:
2022-03-02T13:35:33.205000Z
Dataless Representation of Station LA03 EndTime:
LA03: 2019,181,01:47:40.0000~2022,061,13:35:33.0205
The text was updated successfully, but these errors were encountered: