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,321 to 5,340.First263264265266267268269270Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_2_0077 LANGHAGENSEE CP DIANA Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0077
euProtectedAreaCode.DEMV_PR_2_0080 TEMPZINER SEE BLANKENBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0080
euProtectedAreaCode.DEMV_PR_2_0082 ROTER SEE BRUEEL Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0082
euProtectedAreaCode.DEMV_PR_2_0084 HOLZENDORFER SEE DABEL Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0084
euProtectedAreaCode.DEMV_PR_2_0086 KLEIN PRITZER SEE KL PRITZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0086
euProtectedAreaCode.DEMV_PR_2_0087 KLEIN PRITZER SEE KUKUK Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0087
euProtectedAreaCode.DEMV_PR_2_0091 LUCKOWER SEE CP STERNBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0091
euProtectedAreaCode.DEMV_PR_2_0092 STERNBERGER SEE STRANDBAD Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0092
euProtectedAreaCode.DEMV_PR_2_0094 ORTMANNSEE WITZIN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0094
euProtectedAreaCode.DEMV_PR_2_0095 WOSERINER SEE WOSERIN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0095
euProtectedAreaCode.DEMV_PR_2_0098 OBERER SEE STERNBERG Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0098
euProtectedAreaCode.DEMV_PR_2_0100 BARNINER SEE BARNIN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0100
euProtectedAreaCode.DEMV_PR_2_0103 CAMBSER SEE LANGEN BRUETZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0103
euProtectedAreaCode.DEMV_PR_2_0104 SCHWERINER SEE CP FLESSENOW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0104
euProtectedAreaCode.DEMV_PR_2_0107 SCHWERINER SEE CP RETGENDORF Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0107
euProtectedAreaCode.DEMV_PR_2_0109 PINNOWER SEE GODERN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0109
euProtectedAreaCode.DEMV_PR_2_0114 TIEFER SEE DEMEN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0114
euProtectedAreaCode.DEMV_PR_2_0120 SCHWERINER SEE SEEHOF CAMPINGPLATZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0120
euProtectedAreaCode.DEMV_PR_2_0121 SCHWERINER SEE SEEHOF BADEANSTALT Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0121
euProtectedAreaCode.DEMV_PR_2_0125 SCHWERINER SEE HOHEN VIECHELN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0125
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?