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,247 concepts found, displaying 3,941 to 3,960.First194195196197198199200201Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBB_PR_0005 GRIMNITZSEE JOACHIMSTHAL LIEGEWIESE Quick edit Valid - stable 2026-04-28 DEBB_PR_0005
euProtectedAreaCode.DEBB_PR_0006 GROSSER WUKENSEE BIESENTHAL STRANDBAD Quick edit Valid - stable 2026-04-28 DEBB_PR_0006
euProtectedAreaCode.DEBB_PR_0007 LIEPNITZSEE LANKE WALDBAD Quick edit Valid - stable 2026-04-28 DEBB_PR_0007
euProtectedAreaCode.DEBB_PR_0008 OBERSEE LANKE BADEWIESE Quick edit Valid - stable 2026-04-28 DEBB_PR_0008
euProtectedAreaCode.DEBB_PR_0009 PARSTEINER SEE BRODOWIN PEHLITZ CP Quick edit Valid - stable 2026-04-28 DEBB_PR_0009
euProtectedAreaCode.DEBB_PR_0010 PARSTEINER SEE PARSTEIN CP Quick edit Valid - stable 2026-04-28 DEBB_PR_0010
euProtectedAreaCode.DEBB_PR_0011 STOLZENHAGENER SEE STOLZENHAGEN STRANDBAD Quick edit Valid - stable 2026-04-28 DEBB_PR_0011
euProtectedAreaCode.DEBB_PR_0012 UEDERSEE FINOWFURT FERIENPARK Quick edit Valid - stable 2026-04-28 DEBB_PR_0012
euProtectedAreaCode.DEBB_PR_0013 WANDLITZSEE WANDLITZ STRANDBAD Quick edit Valid - stable 2026-04-28 DEBB_PR_0013
euProtectedAreaCode.DEBB_PR_0014 WERBELLINSEE EICHHORST BEROLINA CAMPINGPARADIES Quick edit Valid - stable 2026-04-28 DEBB_PR_0014
euProtectedAreaCode.DEBB_PR_0015 WERBELLINSEE JOACHIMSTHAL CP Quick edit Valid - stable 2026-04-28 DEBB_PR_0015
euProtectedAreaCode.DEBB_PR_0016 WERBELLINSEE JOACHIMSTHAL LIEGEWIESE AM STEIN Quick edit Valid - stable 2026-04-28 DEBB_PR_0016
euProtectedAreaCode.DEBB_PR_0017 WERBELLINSEE JOACHIMSTHAL EJB Quick edit Valid - stable 2026-04-28 DEBB_PR_0017
euProtectedAreaCode.DEBB_PR_0018 WERBELLINSEE JOACHIMSTHAL HOLZABLAGE MICHEN Quick edit Valid - stable 2026-04-28 DEBB_PR_0018
euProtectedAreaCode.DEBB_PR_0019 BEETZSEE MASSOWBURG Quick edit Valid - stable 2026-04-28 DEBB_PR_0019
euProtectedAreaCode.DEBB_PR_0020 BREITLINGSEE MALGE Quick edit Valid - stable 2026-04-28 DEBB_PR_0020
euProtectedAreaCode.DEBB_PR_0021 GROSSER WENDSEE WENDSEEUFER Quick edit Valid - stable 2026-04-28 DEBB_PR_0021
euProtectedAreaCode.DEBB_PR_0022 MOESERSCHER SEE BRANDENBURG OT KIRCHMOESER ARKE Quick edit Valid - stable 2026-04-28 DEBB_PR_0022
euProtectedAreaCode.DEBB_PR_0023 PLAUER SEE CAMPING UND FERIENPARK AM PLAUER SEE Quick edit Valid - stable 2026-04-28 DEBB_PR_0023
euProtectedAreaCode.DEBB_PR_0024 BADESEE BAD ERNA SCHOENBORN OT LINDENA HAUPTTEICH Quick edit Valid - stable 2026-04-28 DEBB_PR_0024
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?