Eliminate use of XML files in installed build

[edwardhartnett]

There is a quarterly release of XML and CSV files from the WMO, with all GRIB tables defined. And we use the XML one. The XML data file is included in the build.

Finding data files after install is non-trivial, and I'm worried about the way NOAA moves things from one machine to another. Will data files be lost or not found?

Instead, the code can be changed to read the XML and output a C program file which encodes the data as a struct. Then that C can be compiled into the library and will never get lost.

[edwardhartnett]

I welcome input on this issue, I'm not sure what the best way to proceed is.

Choices include: 1 - Keep libxml and move on. 2 - Change to using CSV input to eliminate libxml. 3 - Change to generate code (occasionally) which is checked in, not using libxml except for the special utility that creates code. 4 - Something else?

[edwardhartnett]

We will:

• Create a new file, g2ccsv.c, which will duplicate the functionality of g2cxml, but with a CSV file. (Just a new init function is needed).
• After that is done, as a separate step, we will remove the xml version.