-
Notifications
You must be signed in to change notification settings - Fork 44
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
HAR/TU WRF-Mercator #242
HAR/TU WRF-Mercator #242
Conversation
Thanks! Could you make a clean PR without the previous commit? Also this might need some form of testing - but we can think about this later |
b62718f
to
048c423
Compare
salem/sio.py
Outdated
pargs['lon_0'] = ds.PROJ_CENTRAL_LON | ||
pargs['center_lon'] = ds.PROJ_CENTRAL_LON | ||
dx = ds.GRID_DX or ds.DX | ||
dy = ds.GRID_DY or ds.DY |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesnt look like a good idea because if GRID_DX is not available it will raise an error, not go to ds.DX
Did you rebase to latest master? I'm surprised the tests are still failing. |
251d982
to
70ca4c9
Compare
Did the rebase now. Adding a fix for your remark next |
Check if GRID_DX/GRID_DY are present in the attributes of files that have proj_envi_string. GRID_DX/GRID_DY should be preferred over DX/DY in this case as they are specifically defined in product generation at least for files generated at TUB. Fixes an issue where the test errors if GRID_DX/GRID_DY are not present.
As for testing, i can upload a small test file to the sample data repository |
Nah thanks, it's ok like this - I'm still puzzled as to why the tests fail, let's check on master |
Add support for WRF-Mercator projection in TU style products