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 4,001 to 4,020.First197198199200201202203204Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBB_PR_0035 HAVEL KETZINER HAVELSTRAND Quick edit Valid - stable 2025-01-29 DEBB_PR_0035
euProtectedAreaCode.DEBB_PR_0036 HOHENNAUENER SEE HOHENNAUEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0036
euProtectedAreaCode.DEBB_PR_0037 HOHENNAUENER SEE SEMLIN BAUERNDEICH Quick edit Valid - stable 2025-01-29 DEBB_PR_0037
euProtectedAreaCode.DEBB_PR_0038 HOHENNAUENER SEE FERCHESAR DRANSESCHLUCHT Quick edit Valid - stable 2025-01-29 DEBB_PR_0038
euProtectedAreaCode.DEBB_PR_0039 HOHENNAUENER SEE WASSERSUPPE Quick edit Valid - stable 2025-01-29 DEBB_PR_0039
euProtectedAreaCode.DEBB_PR_0040 HOHENNAUENER SEE FERCHESAR ZELTPLATZ Quick edit Valid - stable 2025-01-29 DEBB_PR_0040
euProtectedAreaCode.DEBB_PR_0041 KLESSENER SEE KLESSEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0041
euProtectedAreaCode.DEBB_PR_0042 NYMPHENSEE BRIESELANG Quick edit Valid - stable 2025-01-29 DEBB_PR_0042
euProtectedAreaCode.DEBB_PR_0043 BRIESENER SEE BRIESENSEE Quick edit Valid - stable 2025-01-29 DEBB_PR_0043
euProtectedAreaCode.DEBB_PR_0044 FRAUENSEE KIEZ FRAUENSEE GRAEBENDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0044
euProtectedAreaCode.DEBB_PR_0045 GEHRENER MUHLENFLIESS GEHREN Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0045
euProtectedAreaCode.DEBB_PR_0046 GROSS LEUTHENER SEE GROSS LEUTHEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0046
euProtectedAreaCode.DEBB_PR_0047 KOERBISKRUGER TONSEE BESTENSEE Quick edit Valid - stable 2025-01-29 DEBB_PR_0047
euProtectedAreaCode.DEBB_PR_0048 HOELZENER SEE KIEZ HOELZENER SEE GRAEBENDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0048
euProtectedAreaCode.DEBB_PR_0049 HORSTTEICH BORNSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0049
euProtectedAreaCode.DEBB_PR_0050 KIESSEE II BESTENSEE LIEGEWIESE Quick edit Valid - stable 2025-01-29 DEBB_PR_0050
euProtectedAreaCode.DEBB_PR_0051 KLEIN KOERISER SEE GROSS KOERIS OT KLEIN KOERIS JUGENDHERBERGE Quick edit Valid - stable 2025-01-29 DEBB_PR_0051
euProtectedAreaCode.DEBB_PR_0052 KOETHENER SEE KOETHEN JUGENDHERBERGE Quick edit Valid - stable 2025-01-29 DEBB_PR_0052
euProtectedAreaCode.DEBB_PR_0053 KRIMNICKSEE KOENIGS WUSTERHAUSEN OT NEUE MUEHLE Quick edit Valid - stable 2025-01-29 DEBB_PR_0053
euProtectedAreaCode.DEBB_PR_0054 KROSSINSEE WERNSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0054
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?