matcher to recognize same value but different codes (grib2)

[lidiabressan]

ciao !

I noticed a query failed because the level (same value) was written differently :

• diff <( grib_dump -O d0_icon_2I_fcast_all5km.soim.grb ) <( grib_dump -O ../20240424_bordofalso/d0_icon_2I_fcast_all5km.soim.grb )

67c67
< 18        indicatorOfUnitOfTimeRange = 1 [Hour (grib2/tables/15/4.4.table) ]
---
> 18        indicatorOfUnitOfTimeRange = 0 [Minute (grib2/tables/15/4.4.table) ]
70c70
< 24        scaleFactorOfFirstFixedSurface = 3
---
> 24        scaleFactorOfFirstFixedSurface = 0
73,74c73,74
< 30        scaleFactorOfSecondFixedSurface = 3
< 31-34     scaledValueOfSecondFixedSurface = 10
---
> 30        scaleFactorOfSecondFixedSurface = 2
> 31-34     scaledValueOfSecondFixedSurface = 1

diff of arki-scan --dump --annotate grib:

4c4
< Level: GRIB2D(106, 003, 0000000000, 106, 003, 0000000010)     # sfc Depth below land surface (m) 3 0 sfc Depth below land surface (m) 3 10
---
> Level: GRIB2D(106, 000, 0000000000, 106, 002, 0000000001)     # sfc Depth below land surface (m) 0 0 sfc Depth below land surface (m) 2 1

instead of listing all the possible options ( (3,0 or 0,0) or (3,10 or 1,2) ), could it be possible for arkimet to recognize that it is the same value ?

thanks ciao

Lidia

[lidiabressan]

The same happens with time and timeranges in grib2, with different units. a simpler solution could be adding all units combinations to the alias?