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,441 to 5,460.First269270271272273274275276Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_2_0532 DOMJUECH SEE NEUSTRELITZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0532
euProtectedAreaCode.DEMV_PR_2_0535 LANGER SEE NEUSTRELITZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0535
euProtectedAreaCode.DEMV_PR_2_0536 USERINER SEE USERIN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0536
euProtectedAreaCode.DEMV_PR_2_0538 GRANZOWER MOESCHEN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0538
euProtectedAreaCode.DEMV_PR_2_0539 MIROWER SEE Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0539
euProtectedAreaCode.DEMV_PR_2_0543 WEISSER SEE WESENBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0543
euProtectedAreaCode.DEMV_PR_2_0546 PLAETLINSEE WUSTROW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0546
euProtectedAreaCode.DEMV_PR_2_0549 GROSSER PRIEPERTSEE PRIEPERT Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0549
euProtectedAreaCode.DEMV_PR_2_0558 SCHMALER LUZIN CARWITZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0558
euProtectedAreaCode.DEMV_PR_2_0559 BREITER LUZIN LICHTENBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0559
euProtectedAreaCode.DEMV_PR_2_0560 FELDBERGER HAUSSEE Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0560
euProtectedAreaCode.DEMV_PR_2_0561 BREITER LUZIN FELDBERG HUETTENBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0561
euProtectedAreaCode.DEMV_PR_2_0573 WANZKAER SEE WANZKA Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0573
euProtectedAreaCode.DEMV_PR_2_0593 KAEBLICKSEE KRATZEBURG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0593
euProtectedAreaCode.DEMV_PR_2_0600 LUEBKOWSEE SCHWICHTENBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0600
euProtectedAreaCode.DEMV_PR_2_0610 STADTSEE STRASBURG Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0610
euProtectedAreaCode.DEMV_PR_2_0611 SCHMIEDEGRUNDSEE NEUENSUND Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0611
euProtectedAreaCode.DEMV_PR_2_0613 KIESSEE KRUGSDORF Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0613
euProtectedAreaCode.DEMV_PR_2_0615 LOECKNITZER SEE LOECKNITZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0615
euProtectedAreaCode.DEMV_PR_2_0721 PINNOWER SEE PINNOW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0721
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?