No latitudes/longitudes provided by ecCodes for gridType

cfgrib relies on the ECMWF ecCodes C-library for encoding and decoding the GRIB format, including everything related to the coordinate systems. GRIB files encoded in a gridType not supported by the installed ecCodes version will print the warning: No latitudes/longitudes provided by ecCodes for gridType.

The GRIB file will be opened but the geographic portion of the data will be represented by as single dimension without coordinate named values.

For example:

>>> cfgrib.open_dataset('../ST4.2018080204.01h')
No latitudes/longitudes provided by ecCodes for gridType = 'polar_stereographic'
<xarray.Dataset>
Dimensions:     (values: 987601)
Coordinates:
    time        datetime64[ns] ...
    step        timedelta64[ns] ...
    surface     int64 ...
    valid_time  datetime64[ns] ...
Dimensions without coordinates: values
Data variables:
    tp          (values) float32 ...
Attributes:
    GRIB_edition:            1
    GRIB_centre:             kwbc
    GRIB_centreDescription:  US National Weather Service - NCEP 
    GRIB_subCentre:          4
    history:                 GRIB to CDM+CF via cfgrib-0.9.../ecCodes-2.8...

The list of known supported gridTypes is:

• latitude and longitude as dimension coordinates
  • regular_ll
  • regular_gg
• xand y as dimensions and latitude and longitude as non-dimension coordinates
  • rotated_ll
  • rotated_gg
  • lambert
  • lambert_azimuthal_equal_area
  • albers
  • polar_stereographic (ecCodes > 2.9.0)
• values as dimension and latitude and longitude as non-dimension coordinates
  • reduced_ll
  • reduced_gg
  • unstructured_grid

see http://xarray.pydata.org/en/stable/data-structures.html#coordinates for details on xarray naming conventions.

Initially noted in #27.

[alexamici]

@marcowurth you can add backend_kwargs={'errors': 'ignore'} to your xr.open_dataset call to have all errore silenced, e.g.:

>>> xr.open_dataset('dwd.grib', engine='cfgrib', backend_kwargs={'errors': 'ignore'})

[shahramn]

@winash12 Apologies. I am using the ecCodes command line tools to decode these ICON files.

The sample file you mentioned (igfff00000000) doesn’t seem to have any lat/lon info. None of its parameters are using the parameter category 191 which gives you “Geographical latitude” and “Geographical longitude”. In the ICON files I had seen before, there were two GRIB messages providing those values.

So for this one I’m afraid you would have to contact the data provider