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,201 to 5,220.First257258259260261262263264Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_1_0283 OSTSEE BOLTENHAGEN SEEBRUECKE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0283
euProtectedAreaCode.DEMV_PR_1_0284 OSTSEE BOLTENHAGEN REDEWISCHER STRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0284
euProtectedAreaCode.DEMV_PR_1_0285 OSTSEE BOLTENHAGEN REDEWISCHER BACH Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0285
euProtectedAreaCode.DEMV_PR_1_0286 OSTSEE STEINBECK Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0286
euProtectedAreaCode.DEMV_PR_1_0288 OSTSEE BOLTENHAGEN WEISSE WIEK Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0288
euProtectedAreaCode.DEMV_PR_1_0289 OSTSEE BROOK Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0289
euProtectedAreaCode.DEMV_PR_1_0290 OSTSEE GROSS SCHWANSEE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0290
euProtectedAreaCode.DEMV_PR_1_0291 OSTSEE BARENDORF Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0291
euProtectedAreaCode.DEMV_PR_1_0292 OSTSEE HOF BARENDORF Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0292
euProtectedAreaCode.DEMV_PR_1_0293 OSTSEE ROSENHAGEN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0293
euProtectedAreaCode.DEMV_PR_1_0623 STETTINER HAFF BELLIN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0623
euProtectedAreaCode.DEMV_PR_1_0624 STETTINER HAFF UECKERMUENDE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0624
euProtectedAreaCode.DEMV_PR_1_0625 STETTINER HAFF GRAMBIN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0625
euProtectedAreaCode.DEMV_PR_1_0626 STETTINER HAFF MOENKEBUDE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0626
euProtectedAreaCode.DEMV_PR_1_0701 OSTSEE TRASSENHEIDE HAUPTSTRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0701
euProtectedAreaCode.DEMV_PR_1_0702 OSTSEE KARLSHAGEN CAMPINGPLATZ Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0702
euProtectedAreaCode.DEMV_PR_1_0703 OSTSEE KARLSHAGEN HAUPTSTRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0703
euProtectedAreaCode.DEMV_PR_1_0707 PEENESTROM USEDOM Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0707
euProtectedAreaCode.DEMV_PR_1_0709 PEENESTROM KRIENKE Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0709
euProtectedAreaCode.DEMV_PR_1_0711 ACHTERWASSER BALM Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0711
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?