qiceradar / radar_wrangler

BSD 3-Clause "New" or "Revised" License
2 stars 0 forks source link

Data Question: Time for traces in BAS data #12

Open lauralindzey opened 10 months ago

lauralindzey commented 10 months ago

I'm looking for a way to get the time of each trace. I

I thought that the UTC_time_layerData field might contain this data, and expected it to give the time in seconds since some epoch for each trace.

However, for POLARGAP P03a, it ranges from 736313.75 to 736313.94, with many repeats.

I've pinged Alice/Julien to ask about this; for now, I'm just turning off the axes labels that depend on time.

lauralindzey commented 10 months ago

They're aware of the issue:

'Please note that an issue with the floats in the NetCDF variable “UTC_time_layerData” has resulted in this variable having rounded up decimal numbers. In order to fix this issue, we advise users who need this variable to download the separately published bed pick data for the POLARGAP survey (doi: https://doi.org/10.5285/d55e87dd-a74d-4182-be99-93ab805103ab) and use the ‘DateTime_YYYY-MM-DD_HH:MM:SS.S’ column which is the same as the one used to produce the NetCDF.’

So, the radargram display will just need to be robust to bad timestamps (maybe load_bas_radargram() will flag POLARGAP ones as bad.)

lauralindzey commented 2 weeks ago

I spoke with @julbod a few days ago, and he indicated that the radargrams have been reprocessed, but possibly not yet pushed up to the servers.

I should ping Alice when we're both back from travels...