RDBES: New codetype FreshWaterName and codes

[HenrikK-N]

Hi Adriana Can you create the following new codetype FreshWaterName and codes:

Codetype Description FreshWaterName Name of the fresh water. E.g. river name or lake name

The following is just to show some potential codes and descriptions. I have suggested that the code is using English letters and the description have the local letters.

Code Description Agluona Agluona Raane Aelv Råne älv Serksne Šerkšnė

And up to 450 more river names.

Contact WGBAST persons for the river name list (Martin is the chair): Martin Kesler martin.kesler@ut.ee; Tapani Pakarinen tapani.pakarinen@luke.fi; Susanne Tärnlund susanne.tarnlund@slu.se; Anders Kagervall Anders.Kagervall@slu.se.

Cheers Kjems

[neil-ices-dk]

These already exist under f.ex the WFD

also Eurostat. We should refer to subsets defined in these lists and not come with a new vocab.

[HenrikK-N]

Hi Neil and Adriana. I have asked around for such a list, of course we should use such list. Please send the list to the chair as soon as possible, so the chair and data users can agree that all codes they need are there. I will let the chair know. Cheers Kjems

[odontaster]

Contacted eionet help desk for clarification on the duplicated records but had no answer yet.

[odontaster]

@odontaster will create the CodeType WaterBody. Will populate it later on when we solved issues with duplicate Labels etc

[HenrikK-N]

Hi Adriana. We need to move on with this WaterBody (or WaterBodies) code list, the list should be ready when we open the RDBES the 22 Aug. I will attache the river list I received from WGBAST, have you had any contact with them? I suggest that we take a pragmatic approache, meaning that you take each of the rivers in the attached list and identify it in the EIONET Water bodies (I guess status stable, I suggest you forget EIONET issue with duplicate Labels), you create a code with the EIONET Lable, and the local spelling in the description to the extent possible, you can always at a later point update the description to a more correct local spelling. Then we are in-line with the EIONET, and we can have the code list ready for the 22 Aug.

Cheers Kjems

[HenrikK-N]

WGBAST_Rivers.xlsx

[odontaster]

I agree @HenrikK-N. I was in contact with WGBAST but had not much answer, probably due to holidays. Will work on this and try to have something usable for next thursday, will ask RMG or you for help if needed.

[odontaster]

There are several relevant sources of information for rivers, for example: https://data.apps.fao.org/aquamaps/ https://land.copernicus.eu/imagery-in-situ/eu-hydro/eu-hydro-river-network-database?tab=mapview In these cases, the data refer mostly to basins and subbasins. These are consistent at the european level, but they are defined for different scopes, based on geological and hydrological properties, so the scale is not fit for purpose for the WGBAST submissions, is too large scale, mostly in Baltic countries.

We also have WISE dataset in EIONET: https://dd.eionet.europa.eu/vocabulary/wise/WaterBody/view In this case, most rivers can be found, but there can be many records refering to different parts of the river. WGBAST requires a single code per river, as the reported data would refer to catches for the whole river, usually done in the lower part of it. WGBAST suggested to ask national experts to go through this vocabulary and hand pick the codes for each river that could fit better their scope, but it would always be an approximation, and at this moment it could take quite some time.

A third possibility arised from the conversation with WGBAST, as all countries have an authority defining codes for water catchments in the country, please see for instance https://www.smhi.se/polopoly_fs/1.26703!/Sveriges_huvudavrinningsomr%C3%A5den_SVAR_2016_6.pdf These are the codes WGBAST and submitters are commonly using in their national reporting (also included in the WISE codes). We could create a Code Type "National Rivers and Catchment Areas" (Description: Codes for fresh water bodies as defined by national authorities). The codes would require a country prefix, as some national codes are just numbers, underscore and the code as is in the national relevant authority site. The description would be the country and the Name of the river as is in the national authority site. WGBAST suggested that its members can provide all required information, but it might take them some time.

We solve a few issues with this suggestion: the list can grow with time, so we can start straightaway with the few rivers required for the data call (15 tops, Tapsa already working on it) and add more rivers as we receive the information from WGBAST members. This list can be used in other data calls, the codes are concise but quite informative and well known for each country nationals, it has relevant source of information and this list does not exist elsewhere, as far as we could research.

The list for next weeks opening would start with these codes:

Code | Description

SE_09 | Sweden Luleälven SE_20 | Sweden Skellefteälven SE_38 | Sweden Ångermanälven SE_40 | Sweden Indalsälven SE_48 | Sweden Ljusnan FI_61 | Finland Iijoki FI_65 | Finland Kemijoki LV41 | Latvia Daugava PL?? | Poland Vistula

[odontaster]

RMG accepts the proposal for a new Code Type. Some attention will be needed when receiving the national codes as to keep the aggregation level similar, rivers, basins or subbasins, accross countries.

[odontaster]

Preliminary list has been created, pending to improve with WGBAST input.

[HenrikK-N]

Hi @odontaster, can you as we talked about add the code 'NA' 'Not applicable', for all the catches not in rivers. Cheers Kjems

[odontaster]

29/09/2022: Asked WGBAST chairs for a short list of members per country to ask for their input to build up this list.

[odontaster]

Will attend WGBAST in March to move this a bit forward.

[odontaster]

Communicated to the group, asked for a table with national codes, descriptions an dlinks to national authorities. They seem to be able to fulfil the request during the week.

[odontaster]

Communicated in WGBAST, only received feedback from Estonia RiversAndCatchments_vocabulary_ICESDCrequest Estonian salmon rivers.xlsx

[odontaster]

NEW_RECO_Rivers&Catchments.xlsx

[odontaster]

Deprecate old ones and make them invisible. Create new ones without "-".

[HenrikK-N]

Hi Adriana If the same river change code and/or description, so it is possible to update the code and/or description, then that is best. Because then the data records are linked to current valid river codes, and the number of depricated codes is kept to a minimum. Cheers Kjems

[odontaster]

When asking WGBAST, most submitters proposed different codes to the ones created last year, in order to be able to be more specific and closer to their national databases. For these, all 8 codes were deprecated and made invisible to avoid confusion. New list is already available.