You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HRRR : Failed to get CRS from crs variable LambertConfor mal_Projection #38
thanks for reporting! I'll have a closer look at it but already found one issue that at least should solve the update problem with map0.update(z=500, method='nearest') (see #39).
Is it an option that you update your xarray to 0.19? I see that you are still using 0.17. I get different error messages, that's why...
map0.update(t = '2021-10-02', method='nearest')
This one is a bit tricky and I am not sure, whether psyplot should really interfer... You have 8 time-stamps on 2021-10-02 and apparently xarray takes all if you do a ds["Geopotential_height_isobaric"].sel(time='2021-10-02', method='nearest')
I'll also have a look into the other files and keep you posted.
alright, seems the current implementation in psy-maps assumed the false_easting and false_northing attributes for the grid mapping are mandatory. They are now made optional in psyplot/psy-maps#41
thanks for reporting! I'll have a closer look at it but already found one issue that at least should solve the update problem with map0.update(z=500, method='nearest') (see #39).
Is it an option that you update your xarray to 0.19? I see that you are still using 0.17. I get different error messages, that's why...
map0.update(t = '2021-10-02', method='nearest')
This one is a bit tricky and I am not sure, whether psyplot should really interfer... You have 8 time-stamps on 2021-10-02 and apparently xarray takes all if you do a ds["Geopotential_height_isobaric"].sel(time='2021-10-02', method='nearest')
see here
So maybe you should use map0.update(t = '2021-10-02T00:00:00', method='nearest')
I used a datetime object and that seems to work better.
I installed xarray to 0.19, but got the same symptom. It seems to work fine w/ the nomads.ncep.noaa.gov data source. The thredds.ucar.edu data source has a lot of extra coordinates, eg : time1, time2, isobaric1, etc. That said, thredds.ucar.edu works with MetPy.
Also, mapvector works OK w/ the nomads sref data (takes about 10 seconds to plot), but it's slow w/ gfs (5 minues) & hrrr.
hey @captcha1! Apologies for the delay. I fixed everything (I suppose) and it would be great if you could quickly test it. Just use the fix/38 branch of psyplot and psy-maps.
To do this, update your local installation from github (pip install -U git+https://github.com/psyplot/psyplot.git@fix/38 git+https://github.com/psyplot/psy-maps.git@fix/38) and please rerun you script with all the datasets that you mentioned above
hmm, ok. Thanks for the feedback! The cartopy projection assumes coordinates to be in meter, whereas your coordinates are in units of km. That is why. I need to transform this
alright @captcha1! I added a fix with psyplot/psy-maps@37121cf and it seems to work. But it would be great if you could verify once more. Just update psy-maps via pip install -U git+https://github.com/psyplot/psy-maps.git@fix/38
but thinking about it, the solution there is not bulletproof. It does not take bounds into account and it cannot be used for unstructured grids, for instance. So it's probably better to generalize the conversion handling that I already implemented for radians
Activity
Chilipp commentedon Oct 15, 2021
hey @captcha1!
thanks for reporting! I'll have a closer look at it but already found one issue that at least should solve the update problem with
map0.update(z=500, method='nearest')(see #39).Is it an option that you update your xarray to 0.19? I see that you are still using 0.17. I get different error messages, that's why...
This one is a bit tricky and I am not sure, whether psyplot should really interfer... You have 8 time-stamps on
2021-10-02and apparently xarray takes all if you do ads["Geopotential_height_isobaric"].sel(time='2021-10-02', method='nearest')see here
So maybe you should use
map0.update(t = '2021-10-02T00:00:00', method='nearest')No idea about this one. It looks like it wants to download the entire netCDF file because I am getting the following message:
So something is going wrong here because the entire data should not be loaded, only what is needed for visualization. I'll need to have a look.
I'll also have a look into the other files and keep you posted.
captcha1 commentedon Oct 15, 2021
Great !
FYI, HRRR mapplot works OK direct from nomads (mapvector slow (ok w/ sref)) :
FYI, apparently thredds.ucar.edu gets it's data from nomads via NOAAPORT (satellite broadcast).
Chilipp commentedon Oct 15, 2021
alright, seems the current implementation in psy-maps assumed the
false_eastingandfalse_northingattributes for the grid mapping are mandatory. They are now made optional in psyplot/psy-maps#41captcha1 commentedon Oct 16, 2021
I used a datetime object and that seems to work better.
I installed xarray to 0.19, but got the same symptom. It seems to work fine w/ the nomads.ncep.noaa.gov data source. The thredds.ucar.edu data source has a lot of extra coordinates, eg : time1, time2, isobaric1, etc. That said, thredds.ucar.edu works with MetPy.
Also, mapvector works OK w/ the nomads sref data (takes about 10 seconds to plot), but it's slow w/ gfs (5 minues) & hrrr.
Chilipp commentedon Oct 16, 2021
Sure! I already found the cause but need a few minutes to fix it (it's weekend 😉).
Chilipp commentedon Oct 18, 2021
hey @captcha1! Apologies for the delay. I fixed everything (I suppose) and it would be great if you could quickly test it. Just use the
fix/38branch ofpsyplotandpsy-maps.To do this, update your local installation from github (
pip install -U git+https://github.com/psyplot/psyplot.git@fix/38 git+https://github.com/psyplot/psy-maps.git@fix/38) and please rerun you script with all the datasets that you mentioned abovecaptcha1 commentedon Oct 19, 2021
Thanks for your quick fix !
The "ucar hrrr" data (ei : https://thredds.ucar.edu/thredds/dodsC/grib/NCEP/HRRR/CONUS_2p5km/Best ) doesn't error out, but has the wrong plot : the latitude goes from 25.003 to 25.03 and longitude goes from 95.01 to 94.99.
Chilipp commentedon Oct 19, 2021
hmm, ok. Thanks for the feedback! The cartopy projection assumes coordinates to be in
meter, whereas your coordinates are in units ofkm. That is why. I need to transform thisChilipp commentedon Oct 19, 2021
alright @captcha1! I added a fix with psyplot/psy-maps@37121cf and it seems to work. But it would be great if you could verify once more. Just update psy-maps via
pip install -U git+https://github.com/psyplot/psy-maps.git@fix/38Thanks a lot for your patience =)
Chilipp commentedon Oct 20, 2021
but thinking about it, the solution there is not bulletproof. It does not take
boundsinto account and it cannot be used for unstructured grids, for instance. So it's probably better to generalize the conversion handling that I already implemented forradianshttps://github.com/psyplot/psy-simple/blob/ac305c052b6bc9da47465ee1f35a1c64e489aca6/psy_simple/plotters.py#L126-L143
I can take care of that tomorrow
Chilipp commentedon Oct 28, 2021
hey @captcha1! I did implement the fix now (apologies for the delay). Could you please verify that it works by running
and testing your script above? Then I'll merge the three PRs #39, psyplot/psy-simple#30 and psyplot/psy-maps#41 and close this issue