CONUS404: Incorrect CRS derived from netCDF file attributes #406
Replies: 3 comments 2 replies
-
|
Hi @ercas - where are you accessing the CONUS404 files from? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I think I was able to fix the scale issue and now have the following:
I'm unsure how to translate it to the correct false latitude and longitude though. |
Beta Was this translation helpful? Give feedback.
-
|
I haven't really worked with the RDA data - but we use the python package In our example, we output |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have been having some issues trying to assign a CRS to the CONUS404 data. I have been following the approach from here to generate a PROJ4 string from the metadata embedded in the netCDF file: https://fabienmaussion.info/2018/01/06/wrf-projection/ which has resulted in the following PROJ4 string:
+proj=lcc +units=m +a=6370000.0 +b=6370000.0 +lat_1=30.0 +lat_2=50.0 +lat_0=39.100006103515625 +lon_0=-97.9000015258789 [+nadgrids=@null](mailto:+nadgrids=@null)This yields the following result, with the grid appearing very small and constrained to a small area near Minneapolis (Kansas):
How could I go about generating / finding the correct CRS for CONUS404? Any guidance would be appreciated. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions