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,081 to 5,100.First251252253254255256257258Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEHE_PR_0030 STRANDBAD NIEDER RODEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0030
euProtectedAreaCode.DEHE_PR_0031 AARTAL SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0031
euProtectedAreaCode.DEHE_PR_0032 STAUWEIHER EWERSBACH Quick edit Valid - stable 2025-01-29 DEHE_PR_0032
euProtectedAreaCode.DEHE_PR_0033 HEISTERBERGER WEIHER Quick edit Valid - stable 2025-01-29 DEHE_PR_0033
euProtectedAreaCode.DEHE_PR_0034 KROMBACHTALSPERRE Quick edit Valid - stable 2025-01-29 DEHE_PR_0034
euProtectedAreaCode.DEHE_PR_0035 ULMBACHTALSPERRE Quick edit Valid - stable 2025-01-29 DEHE_PR_0035
euProtectedAreaCode.DEHE_PR_0036 DUTENHOFENER BADESEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0036
euProtectedAreaCode.DEHE_PR_0037 SEEWEIHER MENGERSKIRCHEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0037
euProtectedAreaCode.DEHE_PR_0038 WALDSEE MENGERSKIRCHEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0038
euProtectedAreaCode.DEHE_PR_0039 STRANDBAD SPESSARTBLICK Quick edit Valid - stable 2025-01-29 DEHE_PR_0039
euProtectedAreaCode.DEHE_PR_0040 BAERENSEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0040
euProtectedAreaCode.DEHE_PR_0041 BIRKENSEE Quick edit Deprecated - retired 2025-01-29 DEHE_PR_0041
euProtectedAreaCode.DEHE_PR_0042 KINZIGSEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0042
euProtectedAreaCode.DEHE_PR_0043 STRANDBAD RODENBACH Quick edit Valid - stable 2025-01-29 DEHE_PR_0043
euProtectedAreaCode.DEHE_PR_0044 PERFSTAUSEE BREIDENSTEIN Quick edit Deprecated - retired 2025-01-29 DEHE_PR_0044
euProtectedAreaCode.DEHE_PR_0045 NIEDERWEIMARER SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0045
euProtectedAreaCode.DEHE_PR_0046 MARBACH STAUSEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0046
euProtectedAreaCode.DEHE_PR_0047 SCHULTHEIS WEIHER Quick edit Valid - stable 2025-01-29 DEHE_PR_0047
euProtectedAreaCode.DEHE_PR_0048 STOCKELACHE Quick edit Valid - stable 2025-01-29 DEHE_PR_0048
euProtectedAreaCode.DEHE_PR_0049 SILBERSEE FRIELENDORF Quick edit Valid - stable 2025-01-29 DEHE_PR_0049
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?