geo reference of wrfout

6 posts / 0 new
Last post
clee
geo reference of wrfout

Hi,

I am trying to create a wrf-like netcdf file with merge wrfout_d02 and wrfout_d01 together. and then use wrf2vdf to convert it. To get accurate geo-information, i feed in the following global attributes:
/ global attributes:
:CEN_LAT = 26.50002f ;
:CEN_LON = -79.f ;
:TRUELAT1 = 17.25f ;
:TRUELAT2 = 27.75f ;
:MOAD_CEN_LAT = 26.50002f ;
:STAND_LON = -79.f ;
:DX = 4000.f ;
:DY = 4000.f ;
:POLE_LAT = 90.f ;
:POLE_LON = 0.f ;
:MAP_PROJ = 1 ;
:JULYR = 2012 ;
:JULDAY = 239 ;
:GMT = 12.f ;
:WEST-EAST_GRID_DIMENSION = 1196 ;
:SOUTH-NORTH_GRID_DIMENSION = 1076 ;
:BOTTOM-TOP_GRID_DIMENSION = 36 ;

Now, I try to cut my domain to zoom in on Gulf of Mexico, and I use the new CEN_LAT, CEN_LON, MODA_CEN_LAT, however, somehow geo-information is wrong in vapor. Can anyone tell me what information in wrfout is necessary for correct geo-information.

Thanks
-Chiaying

alan

I think your georeferencing is correct.  However you should not put both D01 and D02 into the same file, the georeferencing can only refer to one grid.  Vapor can not handle both D01 and D02 data in the same scene.

clee

because vapor can not handle both d01 and d02, I have to merge both file on my own wrf-like netcdf ( basically interpolate d01 onto d02's resolution) and I use the geo-information from d01. if I do "not" try to cut domain, it works perfect. I can convert it to vdf, and and overlay it with other geotiff files.
The problem comes from while I try to cut and save the data from sub-set region of d01 ( GOM).

So, the original d01 is about from 7N to 44N, from -103 to -55.
and the subset data is from 17 to 40N, from -100 to -76. Once I did it, the geo-reference is wrong. I load it in vapor, and the minimum lat is 0 N, although my XLAT field still correct.

alan

Chiaying,

In addition to the georeferencing and the XLAT/XLON variables, you must also change the value of the DX and DY attributes to reflect the corrected grid spacing.

-Alan

prepagosmedellin.co

I think your georeferencing is correct. However you should not put both D01 and D02 into the same file, the georeferencing can only refer to one grid. Vapor can not handle both D01 and D02 data in the same scene.

web-alliance

Does this work on mobile applications ?
We are going to test this in the field and we would like to adapt this on a larger scale.
Do you have the procedures ?
Thanks @ web alliance (www.web-alliance.com)