Linux workstation

Upstream software project

eccodes

Contains ecCodes development files

About eccodes

Contains ecCodes development files

This project links 8 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 4 package records; Fedora 44: 4 package records. Catalog coverage diagram, not an application screenshot.eccodes: recorded package coverageFedora 434 recordsFedora 444 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
eccodes
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
fedora-43, fedora-44
License expression
Apache-2.0
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

ecCodes is a package developed by ECMWF which provides an application programming interface and a set of tools for decoding and encoding messages in the following formats: * WMO FM-92 GRIB edition 1 and edition 2 * WMO FM-94 BUFR edition 3 and edition 4 * WMO GTS abbreviated header (only decoding). A useful set of command line tools provide quick access to the messages. C, and Fortran 90 interfaces provide access to the main ecCodes functionality. ecCodes is an evolution of GRIB-API. It is designed to provide the user with a simple set of functions to access data from several formats with a key/value approach. For GRIB encoding and decoding, the GRIB-API functionality is provided fully in ecCodes with only minor interface and behaviour changes. Interfaces for C, and Fortran 90 are all maintained as in GRIB-API. However, the GRIB-API Fortran 77 interface is no longer available. In addition, a new set of functions with the prefix "codes_" is provided to operate on all the supported message formats. These functions have the same interface and behaviour as the "grib_" functions. A selection of GRIB-API tools has been included in ecCodes (ecCodes GRIB tools), while new tools are available for the BUFR (ecCodes BUFR tools) and GTS formats. The new tools have been developed to be as similar as possible to the existing GRIB-API tools maintaining, where possible, the same options and behaviour. A significant difference compared with GRIB-API tools is that bufr_dump produces output in JSON format suitable for many web based applications.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. eccodes

    Fedora 43 / Unspecified / source eccodes

    2.48.0-1.fc43

    WMO data format decoding and encoding

    aarch64x86_6443
  2. eccodes-data

    Fedora 43 / Unspecified / source eccodes

    2.48.0-1.fc43

    Data needed by the eccodes library and tools

    noarch43
  3. eccodes-devel

    Fedora 43 / Unspecified / source eccodes

    2.48.0-1.fc43

    Contains ecCodes development files

    aarch64x86_6443
  4. eccodes-doc

    Fedora 43 / Unspecified / source eccodes

    2.48.0-1.fc43

    Documentation and example code

    noarch43

Fedora 44

  1. eccodes

    Fedora 44 / Unspecified / source eccodes

    2.48.0-1.fc44

    WMO data format decoding and encoding

    aarch64x86_6444
  2. eccodes-data

    Fedora 44 / Unspecified / source eccodes

    2.48.0-1.fc44

    Data needed by the eccodes library and tools

    noarch44
  3. eccodes-devel

    Fedora 44 / Unspecified / source eccodes

    2.48.0-1.fc44

    Contains ecCodes development files

    aarch64x86_6444
  4. eccodes-doc

    Fedora 44 / Unspecified / source eccodes

    2.48.0-1.fc44

    Documentation and example code

    noarch44

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.