[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #GJF-200148]: TDS 4.3 GRIB names different from TDS 4.2



Fan,

I did a little more digging, and I don't think the file name extension will 
matter - that was my misinterpretation of how the table was getting picked up.  
However, you will probably have the best result directly embedding the table 
information in your featureCollection element using the xml notation.  It looks 
like you tried this already, so I am not sure why it did not work for you.  It 
is possible that it broke because you did not follow udunits standard -- for 
instance, square meters is notated as m^2, rather than m(superscript)2.  The 
code you are asking about is just the number that identifies the grib parameter.

Inside your <featureCollection> element:

<gribConfig>
   <parameterMap>
    <parameter code="2">  <<-- This will override the standard table values for 
parameter 2 (code < 128 are standard, > 128 are local) 
      <description>Pressure reduced to MSL</description>
      <units>Pa</units>
      <name>PRMSL</name>
    </parameter>
    <parameter code="131">
      <description>Snowfall rate</description>
      <units>kg/m^2.s</units> <<--Compound units are notated with a dot, so 
/m^2/s is just /m^2.s
      <name>Snof</name>
    </parameter>
    ...

  </parameterMap>

 </gribConfig>
-Lansing Madry
  Unidata
  Boulder, Colorado

Ticket Details
===================
Ticket ID: GJF-200148
Department: Support THREDDS
Priority: Low
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.