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,061 to 4,080.First200201202203204205206207Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBB_PR_0095 SCHERVENZSEE SCHERNSDORF BUNGALOWS Quick edit Valid - stable 2025-01-29 DEBB_PR_0095
euProtectedAreaCode.DEBB_PR_0096 SCHWIELOCHSEE CP TREBATSCH SAWAL Quick edit Valid - stable 2025-01-29 DEBB_PR_0096
euProtectedAreaCode.DEBB_PR_0097 SCHWIELOCHSEE NIEWISCH Quick edit Valid - stable 2025-01-29 DEBB_PR_0097
euProtectedAreaCode.DEBB_PR_0098 SPREE BERKENBRUECK Quick edit Valid - stable 2025-01-29 DEBB_PR_0098
euProtectedAreaCode.DEBB_PR_0099 SPREE BEESKOW SPREEPARK Quick edit Valid - stable 2025-01-29 DEBB_PR_0099
euProtectedAreaCode.DEBB_PR_0100 SPRINGSEE LIMSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0100
euProtectedAreaCode.DEBB_PR_0101 STOERITZSEE SPREEAU Quick edit Valid - stable 2025-01-29 DEBB_PR_0101
euProtectedAreaCode.DEBB_PR_0102 STORKOWER SEE DAHMSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0102
euProtectedAreaCode.DEBB_PR_0103 STORKOWER SEE STORKOW STRANDBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0103
euProtectedAreaCode.DEBB_PR_0104 STORKOWER SEE STORKOW WOLFSWINKEL Quick edit Valid - stable 2025-01-29 DEBB_PR_0104
euProtectedAreaCode.DEBB_PR_0105 TIEFER SEE RANZIG Quick edit Valid - stable 2025-01-29 DEBB_PR_0105
euProtectedAreaCode.DEBB_PR_0106 TIEFER SEE GRUBENSEE LIMSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0106
euProtectedAreaCode.DEBB_PR_0107 TREBUSER SEE FUERSTENWALDE TREBUS STRAND Quick edit Valid - stable 2025-01-29 DEBB_PR_0107
euProtectedAreaCode.DEBB_PR_0108 WERLSEE GRUENHEIDE SUEDSTRAND Quick edit Valid - stable 2025-01-29 DEBB_PR_0108
euProtectedAreaCode.DEBB_PR_0109 BAGGERSEE GUSOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0109
euProtectedAreaCode.DEBB_PR_0110 BOETZSEE EGGERSDORF STRANDBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0110
euProtectedAreaCode.DEBB_PR_0111 BOETZSEE EGGERSDORF FKK HOCHSPANNUNG POSTBRUCH Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0111
euProtectedAreaCode.DEBB_PR_0112 DIEKSEE FALKENHAGEN Quick edit Deprecated - retired 2025-11-04 DEBB_PR_0112
euProtectedAreaCode.DEBB_PR_0113 FREIBAD ZECHIN ZECHIN Quick edit Valid - stable 2025-01-29 DEBB_PR_0113
euProtectedAreaCode.DEBB_PR_0114 GABELSEE FALKENHAGEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0114
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?