You are here:
Eionet
Data Dictionary
Edit vocabulary

Edit vocabulary

Folder Mandatory
Identifier Mandatory
Label Mandatory
Base URI Optional
Registration status Mandatory
Type Mandatory Common
Numeric concept identifiers Mandatory
Optional
Definition Optional
Version Optional
Source Optional
License Optional
 

Bound elements for concepts

Element Type Status
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

138,256 concepts found, displaying 2,261 to 2,280.First110111112113114115116117Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BGSARI03 DUNAV RIVER Quick edit Valid - stable 2025-01-29 BGSARI03
euProtectedAreaCode.BGSARI04 ISKAR RIVER Quick edit Valid - stable 2025-01-29 BGSARI04
euProtectedAreaCode.BGSARI05 KAMTCHIA RIVER Quick edit Valid - stable 2025-01-29 BGSARI05
euProtectedAreaCode.BGSARI06 MARITZA RIVER Quick edit Valid - stable 2025-01-29 BGSARI06
euProtectedAreaCode.BGSARI07 OGOSTA RIVER Quick edit Valid - stable 2025-01-29 BGSARI07
euProtectedAreaCode.BGSARI08 OSAM RIVER Quick edit Valid - stable 2025-01-29 BGSARI08
euProtectedAreaCode.BGSARI09 PROVADIJSKA I DEVNENSKA RIVER Quick edit Valid - stable 2025-01-29 BGSARI09
euProtectedAreaCode.BGSARI10 RUSENSKI LOM RIVER Quick edit Valid - stable 2025-01-29 BGSARI10
euProtectedAreaCode.BGSARI11 STRUMA RIVER Quick edit Valid - stable 2025-01-29 BGSARI11
euProtectedAreaCode.BGSARI12 TUNDJA RIVER Quick edit Valid - stable 2025-01-29 BGSARI12
euProtectedAreaCode.BGSARI14 YANTRA RIVER Quick edit Valid - stable 2025-01-29 BGSARI14
euProtectedAreaCode.CH01013 STRANDBAD MAUR Quick edit Valid - stable 2025-11-04 CH01013
euProtectedAreaCode.CH01016 STRANDBAD USTER Quick edit Valid - stable 2025-11-04 CH01016
euProtectedAreaCode.CH01029 STRANDBAD BAUMEN Quick edit Valid - stable 2025-11-04 CH01029
euProtectedAreaCode.CH01050 STRANDBAD KUESNACHT Quick edit Valid - stable 2025-11-04 CH01050
euProtectedAreaCode.CH01058 SEEBAD LATTENBERG Quick edit Valid - stable 2025-11-04 CH01058
euProtectedAreaCode.CH01061 STRANDBAD BUERGER Quick edit Valid - stable 2025-11-04 CH01061
euProtectedAreaCode.CH01065 STRANDBAD REITLIAU Quick edit Valid - stable 2025-11-04 CH01065
euProtectedAreaCode.CH02031 PLAGE DES JEUNES-RIVES Quick edit Valid - stable 2025-11-04 CH02031
euProtectedAreaCode.CH02032 PLAGE DES ENFANTS Quick edit Valid - stable 2025-11-04 CH02032
CSV Import

The CSV file should contain a header row for element names and data rows for concepts.
It is strongly recommended to use an exported CSV file as a template for bulk editing. Columns and rows can be added to or deleted from the template file.
A concept can be ignored by prepending a double-slash '//' to the concept row in the CSV
    Notes:
  • If the header row contains unknown elements the import will aborted and data will be rolled back
  • Erroneous concept rows are ignored, valid data rows are still imported
  • Successful import cannot be undone (unless "undo checkout" is performed)
  • If a concept with the same identifier already exists in the vocabulary it will be overwritten
  • "Purge Vocabulary" option deletes all the vocabulary concepts before import
Note
  • With this operation, contents of RDF file will be imported into vocabulary folder.
  • Only a working copy can be updated with a RDF file upload.
  • If user select "Purge Per Predicate" option. All seen predicates will be removed from vocabulary.
  • If user select "Purge All Vocabulary Data" option. All data will be removed from vocabulary.
  • Once import is successful, operation cannot be undone. If an error occurs during import, then all data will be rolled back.
In this case, existing vocabulary information will be updated with information from imported concepts.
In this case, predicates of existing concepts will be replaced with the imported predicates.
In this case, all existing concepts will be removed and the imported concepts will be added.
In this case, all imported concepts will be removed from the vocabulary.
How to handle missing concepts?