-
Notifications
You must be signed in to change notification settings - Fork 10
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
Change longitude range from -180--180 to 0--360 #371
Comments
I have not noticed this suspicious behavior. Maybe there is something wrong or missing in the metadata of your longitude axis. You would probably get what you describe if your longitude was not recognized as a longitude axis (therefore cdms2 would not know about the 360 degrees periodicity) Could you give the output of |
Thanks for replying. Here is the output from
Output from
This is an intermediate output file I wrote using cdat-lite so not so many metadata. The code I used to reproduce my issue:
In cdat-lite, var2 has 0--359.25 longitude range. |
Your longitude axis has indeed a circular topology with modulo: 360.0, so it should work, unless maybe there is a problem with your actual longitude values? I have just tried rewrapping on a test file in CDAT 8.1, and it works fine. You can try to do the same and see if it works on the test file
|
@jypeter Thanks for the info. I also tried re-creating the longitude axis in cdat8, using the original values, and re-assigning the axis, then it worked. Really weird. I've uploaded my nc file to a repo (https://github.com/Xunius/dummy_repo), would you like to have a look? |
Hi,
I noticed a change in behaviour from the old cdat (I was using cdat-lite) to the newer cdat8 in this line of code:
The old version changes my data in -180 -- 180 longitude range to 0 -- 360, and also does the zonal shift, so the size remains the same.
The newer version clips the 0 -- 180 hemisphere out for me.
I wonder what's the new recommended way of zonal shifting and range change?
Thanks.
The text was updated successfully, but these errors were encountered: