[THREDDS #FIZ-452444]: Can NcML tackle this?

> John,
> 
> Just to make sure Sachin & I understand:
> 
> If we use CoordSysBuilder to fix this problem, we can then present u
> and v as separate variables via OpenDAP in a CF-compliant way by using
> the TDS, right?

correct

> 
> And do you have examples of AWIPS files in their original form, and as
> served by the TDS?

have a look at

ucar.nc2.dataset.conv.AWIPSConvention

for example a typical variable has 35 levels:

  float gh(record=5, levels_35=35, y=56, x=75);
     :long_name = "Geopotential height";
     :units = "geopotential meters";
     :valid_range = 0.0f, 10000.0f; // float
     :_FillValue = -99999.0f; // float
     :_n3D = 19; // int
     :levels = "MB 1000-100 by 50  K 280-350 by 5  FRZ";


which need to be broken out into seperate variables:

  float gh-PressureLevels19(record=5, PressureLevels19=19, y=56, x=75);
     :long_name = "Geopotential height-PressureLevels19";
     :units = "geopotential meters";
     :valid_range = 0.0f, 10000.0f; // float
     :_FillValue = -99999.0f; // float
     :_n3D = 19; // int
     :levels = "MB 1000-100 by 50  K 280-350 by 5  FRZ";

   float gh-PotTempLevels15(record=5, PotTempLevels15=15, y=56, x=75);
     :long_name = "Geopotential height-PotTempLevels15";
     :units = "geopotential meters";
     :valid_range = 0.0f, 10000.0f; // float
     :_FillValue = -99999.0f; // float
     :_n3D = 19; // int
     :levels = "MB 1000-100 by 50  K 280-350 by 5  FRZ";

   float gh-FreezingLevel0(record=5, FreezingLevel0=1, y=56, x=75);
     :long_name = "Geopotential height-FreezingLevel0";
     :units = "geopotential meters";
     :valid_range = 0.0f, 10000.0f; // float
     :_FillValue = -99999.0f; // float
     :_n3D = 19; // int
     :levels = "MB 1000-100 by 50  K 280-350 by 5  FRZ";


Ticket Details
===================
Ticket ID: FIZ-452444
Department: Support THREDDS
Priority: Normal
Status: Open