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 6,281 to 6,300.First311312313314315316317318Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DESH_PR_0115 OSTS FEHMARN GAMMENDORF Quick edit Valid - stable 2025-01-29 DESH_PR_0115
euProtectedAreaCode.DESH_PR_0116 OSTS FEHMARN BANNESDORF Quick edit Valid - stable 2025-01-29 DESH_PR_0116
euProtectedAreaCode.DESH_PR_0117 OSTS FEHMARN FEHMARNSUND Quick edit Valid - stable 2025-01-29 DESH_PR_0117
euProtectedAreaCode.DESH_PR_0118 OSTS FEHMARN SUEDSTRAND Quick edit Valid - stable 2025-01-29 DESH_PR_0118
euProtectedAreaCode.DESH_PR_0119 SUESELER SEE SUESEL TANNENHOEHE Quick edit Deprecated - retired 2025-11-04 DESH_PR_0119
euProtectedAreaCode.DESH_PR_0120 MUEHLENTEICH BOKEL Quick edit Deprecated - retired 2025-01-29 DESH_PR_0120
euProtectedAreaCode.DESH_PR_0121 RANTZAUER SEE BARMSTEDT FREIBAD Quick edit Valid - stable 2025-01-29 DESH_PR_0121
euProtectedAreaCode.DESH_PR_0122 BADESEE OBERGLINDE FREIBAD Quick edit Valid - stable 2025-01-29 DESH_PR_0122
euProtectedAreaCode.DESH_PR_0123 NORDS HELGOLAND DUENE NORD Quick edit Valid - stable 2025-01-29 DESH_PR_0123
euProtectedAreaCode.DESH_PR_0124 NORDS HELGOLAND DUENE SUED Quick edit Valid - stable 2025-01-29 DESH_PR_0124
euProtectedAreaCode.DESH_PR_0125 BAGGERSEE APPEN Quick edit Valid - stable 2025-01-29 DESH_PR_0125
euProtectedAreaCode.DESH_PR_0126 OSTS MOENKEBERG Quick edit Valid - stable 2025-01-29 DESH_PR_0126
euProtectedAreaCode.DESH_PR_0127 OSTS KITZEBERG Quick edit Valid - stable 2025-01-29 DESH_PR_0127
euProtectedAreaCode.DESH_PR_0128 OSTS HEIKENDORF SEEBADEANSTALT Quick edit Valid - stable 2025-01-29 DESH_PR_0128
euProtectedAreaCode.DESH_PR_0129 OSTS MOELTENORT KURSTRAND Quick edit Valid - stable 2025-01-29 DESH_PR_0129
euProtectedAreaCode.DESH_PR_0130 OSTS LABOE KURSTRAND Quick edit Valid - stable 2025-01-29 DESH_PR_0130
euProtectedAreaCode.DESH_PR_0131 OSTS LABOE FREISTRAND Quick edit Valid - stable 2025-01-29 DESH_PR_0131
euProtectedAreaCode.DESH_PR_0132 OSTS STEIN NEUSTEIN Quick edit Valid - stable 2025-01-29 DESH_PR_0132
euProtectedAreaCode.DESH_PR_0133 OSTS STEIN STEINER MOLE Quick edit Valid - stable 2025-01-29 DESH_PR_0133
euProtectedAreaCode.DESH_PR_0134 OSTS BOTTSAND Quick edit Valid - stable 2025-01-29 DESH_PR_0134
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?