ncrcat function with COSMO-CLM 5 – in #13: Postprocessing

in #13: Postprocessing

<p> Dear colleagues, <br/> I have a problem with postprocessing my lffd…nc output files. I make, for example, as usually, <br/> <pre> ncrcat -h -O -v T_2M lffd??????????.nc T_2M.nc </pre> <br/> It results in: <br/> <pre> ncrcat: WARNING Record coordinate time has a "units" attribute but NCO was built without UDUnits. NCO is therefore unable to detect and correct for inter-file unit re-basing issues. See http://nco.sf.net/nco.html#rbs for more information. ncrcat: HINT Re-build or re-install NCO enabled with UDUnits. </pre> <br/> The file T_2M.nc was created, but it doesn’t contain lat and lon variables (geographical latitude and longitude), rlat and rlon only (rotated latitude and longitude). I have proofed this command with my output files from <span class="caps"> COSMO </span> - <span class="caps"> CLM </span> previous version, and there is the same <span class="caps"> WARNING </span> , cited above, but there are no problems with lat and lon variables. My <span class="caps"> NCO </span> version is 4.3.7, maybe it should be updated? Could you suggest, where the problem may be yet? <br/> Thank you! </p>

  @vladimirplatonov in #9eb9517

<p> Dear colleagues, <br/> I have a problem with postprocessing my lffd…nc output files. I make, for example, as usually, <br/> <pre> ncrcat -h -O -v T_2M lffd??????????.nc T_2M.nc </pre> <br/> It results in: <br/> <pre> ncrcat: WARNING Record coordinate time has a "units" attribute but NCO was built without UDUnits. NCO is therefore unable to detect and correct for inter-file unit re-basing issues. See http://nco.sf.net/nco.html#rbs for more information. ncrcat: HINT Re-build or re-install NCO enabled with UDUnits. </pre> <br/> The file T_2M.nc was created, but it doesn’t contain lat and lon variables (geographical latitude and longitude), rlat and rlon only (rotated latitude and longitude). I have proofed this command with my output files from <span class="caps"> COSMO </span> - <span class="caps"> CLM </span> previous version, and there is the same <span class="caps"> WARNING </span> , cited above, but there are no problems with lat and lon variables. My <span class="caps"> NCO </span> version is 4.3.7, maybe it should be updated? Could you suggest, where the problem may be yet? <br/> Thank you! </p>

ncrcat function with COSMO-CLM 5

VP wrote

Dear colleagues,
I have a problem with postprocessing my lffd…nc output files. I make, for example, as usually, 

ncrcat -h -O -v T_2M lffd??????????.nc T_2M.nc

It results in: 
ncrcat: WARNING Record coordinate time has a "units" attribute but NCO was built without UDUnits. NCO is therefore unable to detect and correct for inter-file unit re-basing issues. See http://nco.sf.net/nco.html#rbs for more information.
ncrcat: HINT Re-build or re-install NCO enabled with UDUnits.

The file T_2M.nc was created, but it doesn’t contain lat and lon variables (geographical latitude and longitude), rlat and rlon only (rotated latitude and longitude). I have proofed this command with my output files from COSMO - CLM previous version, and there is the same WARNING , cited above, but there are no problems with lat and lon variables. My NCO version is 4.3.7, maybe it should be updated? Could you suggest, where the problem may be yet?
Thank you!

View in channel
<p> In case your time coordinate is fine, the warning regarding <span class="caps"> UDU </span> nits does not matter. <br/> Regarding lon,lat it may be that your <span class="caps"> NCO </span> version does not check the coordinates attribute. If you want the lon,lat to be in the output file you may force to include them by modifying your ncrcat (version 4.3.7) command as follows: <br/> <pre> ncrcat -h -O -v T_2M,lon,lat lffd??????????.nc T_2M.nc </pre> </p> <p> I made a test at <span class="caps"> DKRZ </span> , <span class="caps"> NCO </span> version 4.4.2 should check the coordinate attribute. </p> <p> <pre> float T_2M(time, height_2m, rlat, rlon) ; T_2M:standard_name = “air_temperature” ; T_2M:long_name = “2m temperature” ; T_2M:units = “K” ; T_2M:grid_mapping = “rotated_pole” ; T_2M:coordinates = “lon lat” ;</pre> </p> <p> </p>

  @burkhardtrockel in #ff8cf73

<p> In case your time coordinate is fine, the warning regarding <span class="caps"> UDU </span> nits does not matter. <br/> Regarding lon,lat it may be that your <span class="caps"> NCO </span> version does not check the coordinates attribute. If you want the lon,lat to be in the output file you may force to include them by modifying your ncrcat (version 4.3.7) command as follows: <br/> <pre> ncrcat -h -O -v T_2M,lon,lat lffd??????????.nc T_2M.nc </pre> </p> <p> I made a test at <span class="caps"> DKRZ </span> , <span class="caps"> NCO </span> version 4.4.2 should check the coordinate attribute. </p> <p> <pre> float T_2M(time, height_2m, rlat, rlon) ; T_2M:standard_name = “air_temperature” ; T_2M:long_name = “2m temperature” ; T_2M:units = “K” ; T_2M:grid_mapping = “rotated_pole” ; T_2M:coordinates = “lon lat” ;</pre> </p> <p> </p>
BR replied

In case your time coordinate is fine, the warning regarding UDU nits does not matter.
Regarding lon,lat it may be that your NCO version does not check the coordinates attribute. If you want the lon,lat to be in the output file you may force to include them by modifying your ncrcat (version 4.3.7) command as follows: 

ncrcat -h -O -v T_2M,lon,lat lffd??????????.nc T_2M.nc

I made a test at DKRZ , NCO version 4.4.2 should check the coordinate attribute. 

	float T_2M(time, height_2m, rlat, rlon) ;
		T_2M:standard_name = “air_temperature” ;
		T_2M:long_name = “2m temperature” ;
		T_2M:units = “K” ;
		T_2M:grid_mapping = “rotated_pole” ;
		T_2M:coordinates = “lon lat” ;

View in channel