-
Notifications
You must be signed in to change notification settings - Fork 13
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
raster.reconstruct does not work on global netcdfs in 0-360 longitude format #289
Comments
Thanks @nickywright for reporting this bug, GPlately should be enhanced to support the netcdf grids in 0-360 longitude format. And when GPlately saves the reconstructed data into a new grid file, the longitude format should be preserved. |
I will look into this issue after I have updated GWS for FK and made some progress with pyGMT. |
@nickywright |
Hi @michaelchin , notebook is here, and it uses the netcdf file downloadable from zenodo here. |
Thank you very much. I will find some time to look into it asap. I am a bit busy recently. It may take longer than usual. Sorry about that. |
@nickywright
|
@GPlates/gplately-dev This issue can be fixed by setting the "realign=True". It is False by default. Anyone knows what is the reason that it is False by default? Can I set to True by default? |
It does sound like internally GPlately/pyGPlates would like to use [-180,180] (instead of [0,360]). So one idea is to realign internally regardless of the Ah, but Nicky's example is writing with @brmather might have a better idea. |
Hi all, The most painless way forward is probably to realign to [-180,180] before reconstructing the raster then un-realign it to [0,360] after it has been reconstructed. |
This bug has been fixed in master branch. Use this notebook to verify the fix. Further improvement to the raster reconstruction function will be tracked with #310 Close this one now. |
Reconstructing my raster does not work if my netcdf is in 0-360 format, GPlately will import the raster OK, and say that it has reconstructed it OK, but half the world (the 180-360 portion) will be missing.
I'm guessing this is because static polygons don't align (i.e., are these in -180 to 180 format), because my data ends up with NaNs in it?
i.e.:
checking the longitudes before saving out...
The text was updated successfully, but these errors were encountered: