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,041 to 5,060.First249250251252253254255256Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEHB_PR_1000 WESER Quick edit Valid - stable 2025-01-29 DEHB_PR_1000
euProtectedAreaCode.DEHB_PR_9002 ACHTERDIEKSEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9002
euProtectedAreaCode.DEHB_PR_9003 BULTENSEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9003
euProtectedAreaCode.DEHB_PR_9006 GRAMBKER SEEBAD Quick edit Valid - stable 2025-01-29 DEHB_PR_9006
euProtectedAreaCode.DEHB_PR_9010 MAHNDORFER SEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9010
euProtectedAreaCode.DEHB_PR_9011 ROTTKUHLE ARBERGEN Quick edit Valid - stable 2025-01-29 DEHB_PR_9011
euProtectedAreaCode.DEHB_PR_9013 SODENMATTSEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9013
euProtectedAreaCode.DEHB_PR_9014 STADTWALDSEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9014
euProtectedAreaCode.DEHB_PR_9015 WALLER FELDMARKSEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9015
euProtectedAreaCode.DEHB_PR_9016 WERDERSEE Quick edit Valid - stable 2025-01-29 DEHB_PR_9016
euProtectedAreaCode.DEHB_PR_9044 SPORTPARKSEE GRAMBKE Quick edit Valid - stable 2025-01-29 DEHB_PR_9044
euProtectedAreaCode.DEHE_PR_0001 BADESEE BENSHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0001
euProtectedAreaCode.DEHE_PR_0002 BADESEE LAMPERTHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0002
euProtectedAreaCode.DEHE_PR_0003 ARHEILGER MUEHLCHEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0003
euProtectedAreaCode.DEHE_PR_0004 GRUBE PRINZ VON HESSEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0004
euProtectedAreaCode.DEHE_PR_0005 GROSSER WOOG Quick edit Valid - stable 2025-01-29 DEHE_PR_0005
euProtectedAreaCode.DEHE_PR_0006 ERLENSEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0006
euProtectedAreaCode.DEHE_PR_0007 BADESEE NIEDERNHAUSEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0007
euProtectedAreaCode.DEHE_PR_0008 GUCKAISEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0008
euProtectedAreaCode.DEHE_PR_0009 HEUCHELHEIMER SEE II Quick edit Valid - stable 2025-01-29 DEHE_PR_0009
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?