this is what I did with grib_api. We have a central repository (database) which
is visible on the web
for GRIB edition 1
and GRIB edition 2
This database is used to build the decoding rules inside grib_api. In this way
we keep coherence between specifications/documentation/decoder.
I am working at the moment on a similar database/decoder for BUFR.
We would be able to provide xml format out of the database for general exchange
I would be happy to share our experience and collaborate to build a common
Jeff Ator wrote:
This is more of a general survey question. Here at NCEP, we currently
have our BUFR and GRIB2 master table information scattered across a
bunch of ASCII tables, web pages and system files. We're thinking about
designing and implementing a relational database to store all of this
information in one place, and then developing methods to allow the
information to be easily exported from the database into the specific
formats we need for all of our APIs and other operational tasks. We
believe the BUFR and GRIB2 tables lend themselves well to relational
database design (especially when multiple versions of tables including
local entries need to be stored), and having one master repository would
alleviate problems we're currently having keeping information
synchronized across multiple system files and documents.
My question is, has anyone out there ever done or thought about doing
this type of thing? If so, we'd be interested to correspond with you
about your experiences, issues encountered, best practices, etc. and
explore any possible avenues for collaboration. It's hard for us to
believe that nobody else has ever thought of this before, so if at all
possible we'd like to benefit from any existing experience in the
community and avoid re-inventing the proverbial wheel.
Please let me know if you have any thoughts or experience in this area
that you'd be willing to share. Either way, thanks for your time and
With best regards,