Versions Compared

Old Version 36

changes.mady.by.user Shahram Najm

Saved on

compared with

New Version 37

changes.mady.by.user Shahram Najm

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

GRIB-API is entirely included in ecCodes without any major change to its Fortran 90, Python and C interfaces.   The functions with the "grib_" prefix are included in the ecCodes library.

However there are some minor changes and rationalisations described below.:

API Changes

Warning

The following functions have been removed:
grib_handle_new_from_template: This was already deprecated in GRIB-API and has been replaced by grib_handle_new_from_samples.
grib_context_new: This was experimental. One should use the default context


The following C function signatures have changed:
grib_get_data: no longer takes the final "size" argument. This was redundant and never used by the function.
grib_fieldset_new_from_files: The "where_string" and "order_by_string" arguments are now "const char*".
grib_handle_new_from_message: The "data" argument is now "const void*".
grib_handle_new_from_partial_message:  The "data" argument is now "const void*".

...

   section_length[3] section1Length ;

...


The names of the files in the definitions/mars directory have also changed. Previously they had the prefix "grib1" but this was misleading as they pertain to all editions. So the new files have the prefix "grib" e.g.
   definitions/mars/grib.oper.fc.def
...

The "include" statements now require the relative path from the top-level of the definitions directory so instead of
...
   include "grib2/template.4.statistical.def"
 

The migration from GRIB-API to ecCodes should not affect user software and will be managed in installation and linking phases. Nevertheless, very significant changes in the library have been performed to implement the encoding of different types of messages and in particular for BUFR.
...
Some more tests are needed to be fully confident that ecCodes can replace GRIB-API in an operational environment, but we don't have experience at the moment of problems with the GRIB decoding/encoding part of ecCodes. We strongly advise the users to do their own migration tests and send feedback to software.support@ecmwf.int.