I'm working on a station/platform registry in the ecosystem domain (www.deims.org). I've discovered your codes registry and I would like to use it for some of our data as well, especially the facility type is interesting to me (https://codes.wmo.int/wmdr/_FacilityType).
However, the facility type doesn't distinguish between lakes and rivers and instead uses an aggregated category, e.g. http://codes.wmo.int/wmdr/FacilityType/lakeRiverFixed
Distinguishing between lakes and rivers is essential in the ecosystem domain.
Is it possible that you split it up into two distinct categories (river - lake)?
If you could do that, I would propose in my working groups to use your code registry instead of setting up our own.
This would greatly improve data interoperability.
EDIT: Maybe this issue goes unseen, so I'm tagging the github user that comitted the term on codes.wmo.int @kurt-hectic
I'm working on a station/platform registry in the ecosystem domain (www.deims.org). I've discovered your codes registry and I would like to use it for some of our data as well, especially the facility type is interesting to me (https://codes.wmo.int/wmdr/_FacilityType).
However, the facility type doesn't distinguish between lakes and rivers and instead uses an aggregated category, e.g. http://codes.wmo.int/wmdr/FacilityType/lakeRiverFixed
Distinguishing between lakes and rivers is essential in the ecosystem domain.
Is it possible that you split it up into two distinct categories (river - lake)?
If you could do that, I would propose in my working groups to use your code registry instead of setting up our own.
This would greatly improve data interoperability.
EDIT: Maybe this issue goes unseen, so I'm tagging the github user that comitted the term on codes.wmo.int @kurt-hectic