Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keep delta_time instead of renaming to offset_time #1949

Closed
zxdawn opened this issue Dec 20, 2021 · 6 comments · Fixed by #1952
Closed

keep delta_time instead of renaming to offset_time #1949

zxdawn opened this issue Dec 20, 2021 · 6 comments · Fixed by #1952
Assignees

Comments

@zxdawn
Copy link
Member

zxdawn commented Dec 20, 2021

Describe the bug

In the official TROPOMI products, it's delta_time but renamed to offset_time.

offset_time:
name: 'offset_time'
file_type: tropomi_l2
file_key: 'PRODUCT/delta_time'
standard_name: offset_time

int delta_time(time=1, scanline=2906);
  :long_name = "offset of start time of measurement relative to time_reference";
  :units = "milliseconds since 2019-07-02 00:00:00";
  :_FillValue = -2147483647; // int
  :_ChunkSizes = 1U, 2906U; // uint

Is it better to keep it as the original name? I'm producing the data for some KNMI researchers. They usually use delta_time.

@djhoese
Copy link
Member

djhoese commented Dec 20, 2021

It looks like you (@zxdawn) and @tommyjasmin are the main people who use/used this reader. @tommyjasmin originally wrote it and my guess is that this name change was either arbitrary or was to match existing software related to McIDAS/ADDE as part of is work at the SSEC. @tommyjasmin any memory of this?

@tommyjasmin
Copy link
Contributor

Hi @zxdawn and @djhoese - I do not recall making any changes for this dataset, but I barely recall what I did a month ago :-)

I will look into it soon as I can (but today the meetings are thick). I would not have changed it for McIDAS, since McIDAS-V has it's own Java reader (I wrote that too), and while I see an ADDE server in our future, the Python ADDE servers are still in their relative infancy.

@djhoese
Copy link
Member

djhoese commented Dec 20, 2021

@tommyjasmin Thanks. The main question is why something called delta_time in the file was changed to be called offset_time in Satpy.

@zxdawn
Copy link
Member Author

zxdawn commented Dec 21, 2021

@tommyjasmin Thanks. And I'm not sure that the renaming of time is necessary:

ref_time:
name: 'ref_time'
file_type: tropomi_l2
file_key: 'PRODUCT/time'
standard_name: ref_time

@tommyjasmin
Copy link
Contributor

Attn: @djhoese and @zxdawn

Hello Xin - I am not sure why I renamed the delta_time variable in Satpy - the only reason I can think of is, possibly, because that's what the long_name attribute mentions (see below). I think you can go ahead and change the .yaml for both of these variables as suggested if you have permission. Otherwise I can do it.

group: PRODUCT {
variables:
float delta_time(line=358, ele=450);
:coordinates = "latitude longitude";
:_FillValue = -2147483647; // int
:long_name = "offset from reference start time of measurement";
:units = "milliseconds";
:_ChunkSizes = 1, 358, 450; // int

@zxdawn
Copy link
Member Author

zxdawn commented Dec 21, 2021

@tommyjasmin Got it! I will create a PR soon. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants