Regional outvars are not assigned proper names when imported

[dgustafsson]

Regional outvars are named with a leading RG in addition to the common 4-letter code (RGxxxx). Beut when imported by for instance ReadTimeOutput, the name is abbreviated to the first 4 letters (RGxx).

[rcapell]

Thanks!
I did not think of regional outputs when I first wrote the function (maybe they did not even exist then). Will look into it.

For the time being, you can specify the variable name manually in argument hype.var.

[dgustafsson]

thanks, its no urgency, I can use the workaround for now. I am trying to generalize netcdf export using the dataframe attributes. thats why I need it.

[dgustafsson]

There are also other cases such as class outputs, when the variable name is further extended in te file name, for example: timeSDEN_DD_s02
timeSDEN_DD_s02.txt

[rcapell]

Affects ReadTimeOutput, ReadMapOutput, ReadBasinOutput

ReadBasinOutput needs cleaning of HYPE variable names in table header, removal of "rg" prefix. Will get new argument "id" instead of "subid", function decides if ID is stored in attribute "subid" or new attribute "outregid".

ReadTimeOutput and ReadMapOutput need cleaning of "RG" prefix in filename. New internal look-up vector with HYPE variable names to decide if file contents are regional or not. New attribute "outregid" for regional contents.

[rcapell]

HYPEtools now handles regional and class output variable recognition in basin files and time files. Map files on hold because HYPE does not write regional outputs in map files atm (might be a bug, under investigation).

OUTREGIDs for regional outputs are saved in attribute 'outregid' ('subid' set to NA). Class outputs currently look like subbasin outputs after import.

Closing for now.

[rcapell]

Regional map files do now work in HYPE (from v5.10.2).
Reopening to sort out regional variable handling in map files as well.