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,061 to 5,080.First250251252253254255256257Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEHE_PR_0010 TRAIS HORLOFFER SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0010
euProtectedAreaCode.DEHE_PR_0011 LICHER WALDSCHWIMMBAD Quick edit Valid - stable 2025-01-29 DEHE_PR_0011
euProtectedAreaCode.DEHE_PR_0012 LAUNSBACHER SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0012
euProtectedAreaCode.DEHE_PR_0013 WISSMARER SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0013
euProtectedAreaCode.DEHE_PR_0014 BADESEE GERNSHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0014
euProtectedAreaCode.DEHE_PR_0015 BADESTELLE WALLDORFER SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0015
euProtectedAreaCode.DEHE_PR_0016 WALDSEE RAUNHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0016
euProtectedAreaCode.DEHE_PR_0017 RIEDSEE LEEHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0017
euProtectedAreaCode.DEHE_PR_0018 WALDSCHWIMMBAD RUESSELSHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0018
euProtectedAreaCode.DEHE_PR_0019 SCHWIMMBAD VOGEL GEINSHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0019
euProtectedAreaCode.DEHE_PR_0020 FULDASEE BAD HERSFELD Quick edit Deprecated - retired 2025-01-29 DEHE_PR_0020
euProtectedAreaCode.DEHE_PR_0021 FULDASEE BEBRA BREITENBACH Quick edit Valid - stable 2025-01-29 DEHE_PR_0021
euProtectedAreaCode.DEHE_PR_0022 SEEPARK KIRCHHEIM Quick edit Valid - stable 2025-01-29 DEHE_PR_0022
euProtectedAreaCode.DEHE_PR_0023 BADESTELLE HATTSTEINWEIHER Quick edit Valid - stable 2025-01-29 DEHE_PR_0023
euProtectedAreaCode.DEHE_PR_0024 BUGA SEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0024
euProtectedAreaCode.DEHE_PR_0025 BADESEE KLEIN KROTZENBURG Quick edit Valid - stable 2025-01-29 DEHE_PR_0025
euProtectedAreaCode.DEHE_PR_0026 LANGENER WALDSEE Quick edit Valid - stable 2025-01-29 DEHE_PR_0026
euProtectedAreaCode.DEHE_PR_0027 BADESEE MAINFLINGEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0027
euProtectedAreaCode.DEHE_PR_0028 KOENIGSEE ZELLHAUSEN Quick edit Valid - stable 2025-01-29 DEHE_PR_0028
euProtectedAreaCode.DEHE_PR_0029 FKK-ORPLID Quick edit Deprecated - retired 2025-01-29 DEHE_PR_0029
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?