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 5,621 to 5,640.First278279280281282283284285Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DENI_PR_TK25_2910_04 NATURBAD GESPRENGTE BRUECKE Quick edit Deprecated - retired 2025-01-29 DENI_PR_TK25_2910_04
euProtectedAreaCode.DENI_PR_TK25_2910_05 BADESEE CAMPINGPLATZ PRANGENWEG PAPENBURG Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2910_05
euProtectedAreaCode.DENI_PR_TK25_2912_01 HOLLENER SEE Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2912_01
euProtectedAreaCode.DENI_PR_TK25_2914_01 NATURBADEPLATZ WESTERHOLT Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2914_01
euProtectedAreaCode.DENI_PR_TK25_2916_01 BADESTELLE FALKENSTEINSEE FALKENBURG Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2916_01
euProtectedAreaCode.DENI_PR_TK25_2918_01 SILBERSEE STUHR Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2918_01
euProtectedAreaCode.DENI_PR_TK25_2918_02 STELLER SEE GROSSMACKENSTEDT Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2918_02
euProtectedAreaCode.DENI_PR_TK25_2919_01 ALTE WESER IN DREYE Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2919_01
euProtectedAreaCode.DENI_PR_TK25_2920_01 OYTER SEE Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2920_01
euProtectedAreaCode.DENI_PR_TK25_2922_01 BULLENSEE Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2922_01
euProtectedAreaCode.DENI_PR_TK25_2924_01 BADEANSTALT NEUENKIRCHEN Quick edit Deprecated - retired 2025-01-29 DENI_PR_TK25_2924_01
euProtectedAreaCode.DENI_PR_TK25_2925_01 MORAENE SEE DITTMERN Quick edit Deprecated - retired 2025-01-29 DENI_PR_TK25_2925_01
euProtectedAreaCode.DENI_PR_TK25_2925_02 BADESEE SKANDINAVIA - SOLTAU Quick edit Deprecated - retired 2025-01-29 DENI_PR_TK25_2925_02
euProtectedAreaCode.DENI_PR_TK25_2934_01 GARTOWER SEE BADESTRAND Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2934_01
euProtectedAreaCode.DENI_PR_TK25_2934_02 GARTOWER SEE SURFSTRAND Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2934_02
euProtectedAreaCode.DENI_PR_TK25_2934_03 LAASCHER SEE - BADESTELLE I Quick edit Deprecated - retired 2025-01-29 DENI_PR_TK25_2934_03
euProtectedAreaCode.DENI_PR_TK25_2934_04 LAASCHER SEE BADESTELLE II Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_2934_04
euProtectedAreaCode.DENI_PR_TK25_3009_01 BADESEE HEEDE DOERPEN Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_3009_01
euProtectedAreaCode.DENI_PR_TK25_3009_02 HERZOGSEE Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_3009_02
euProtectedAreaCode.DENI_PR_TK25_3009_03 SEEPARK EIKEN WALCHUM Quick edit Valid - stable 2025-01-29 DENI_PR_TK25_3009_03
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?