[Bug] r3.support doesnt set vertical unit but hardcodes it as "unit"

[mazingaro]

When using r3.support to set metadata, It doesnt store it.

Example
r3.support map=enmap vunit="nanometers"

r3.info -g map=enmap

north=5142105
south=5106495
east=542955
west=498435
bottom=418.416
top=2445.3
nsres=30
ewres=30
tbres=12.2101
rows=1187
cols=1484
depths=166
datatype="DCELL"
timestamp="none"
units="none"
vertical_units="units"
tilenumx=60
tilenumy=60
tilenumz=21
tiledimx=25
tiledimy=20
tiledimz=8

Of course, it can be also a r3.info issue.

[nilason]

Units allowed currently are defined here:

grass/lib/gis/units.c

Line 406 in f16cd65

int G_units(const char *units_name)

nanometers is accordingly: U_UNKNOWN

[mazingaro]

Units allowed currently are defined here:

grass/lib/gis/units.c

Line 406 in f16cd65
int G_units(const char *units_name)

nanometers is accordingly: U_UNKNOWN

Are this also vertical units - should they be also set here or what? I am right now trying to set wavelength center for the hyperspectral datacubes and it is cool to have that well stored in the metadata, as some datasets are in nanometers, some in micrometers. I suppose other datasets can have preesure differences and many other units, that spatial data can have.

[petrasovaa]

How about adding new set of units then? Spectral units? In the past temporal units were added, so it probably wouldn't be that hard to add new ones.

[mazingaro]

How about adding new set of units then? Spectral units? In the past temporal units were added, so it probably wouldn't be that hard to add new ones.

That would be cool. Also it would be probably good to update the documentation ofr3.supportand r.support by explaining what units are available? Without @nilason 's comment I would never understand what was wrong 😄