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,081 to 6,100.First301302303304305306307308Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEPE_NWF061 WESER Quick edit Valid - stable 2025-01-29 DEPE_NWF061
euProtectedAreaCode.DEPE_NWF062 HAMMBACH Quick edit Valid - stable 2025-01-29 DEPE_NWF062
euProtectedAreaCode.DEPE_NWF063 WUPPERTALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF063
euProtectedAreaCode.DEPE_NWF064 WUPPER Quick edit Valid - stable 2025-01-29 DEPE_NWF064
euProtectedAreaCode.DEPE_NWF065 WURM Quick edit Valid - stable 2025-01-29 DEPE_NWF065
euProtectedAreaCode.DER1C40G000771207101 PINNOW Quick edit Deprecated - retired 2025-01-29 DER1C40G000771207101
euProtectedAreaCode.DERP_PR_0001 LAACHER SEE Quick edit Valid - stable 2025-01-29 DERP_PR_0001
euProtectedAreaCode.DERP_PR_0002 FREIBAD THALHAUSERMUEHLE Quick edit Valid - stable 2025-01-29 DERP_PR_0002
euProtectedAreaCode.DERP_PR_0003 FREIBAD SCHINDERWEIHER Quick edit Valid - stable 2025-01-29 DERP_PR_0003
euProtectedAreaCode.DERP_PR_0004 STADTWEIHER BAUMHOLDER Quick edit Valid - stable 2025-01-29 DERP_PR_0004
euProtectedAreaCode.DERP_PR_0005 WALDSEE RIEDEN Quick edit Valid - stable 2025-01-29 DERP_PR_0005
euProtectedAreaCode.DERP_PR_0006 WALDSEE KRUFT Quick edit Valid - stable 2025-01-29 DERP_PR_0006
euProtectedAreaCode.DERP_PR_0008 BLAUER SEE Quick edit Valid - stable 2025-01-29 DERP_PR_0008
euProtectedAreaCode.DERP_PR_0009 WALDSEE ARGENTHAL Quick edit Valid - stable 2025-01-29 DERP_PR_0009
euProtectedAreaCode.DERP_PR_0010 FREIBAD SIMMERN Quick edit Valid - stable 2025-01-29 DERP_PR_0010
euProtectedAreaCode.DERP_PR_0011 BAGGERSEE DIEZ Quick edit Valid - stable 2025-01-29 DERP_PR_0011
euProtectedAreaCode.DERP_PR_0012 HERTHASEE Quick edit Valid - stable 2025-01-29 DERP_PR_0012
euProtectedAreaCode.DERP_PR_0013 POSTWEIHER Quick edit Valid - stable 2025-01-29 DERP_PR_0013
euProtectedAreaCode.DERP_PR_0014 KLINGELWIESE Quick edit Valid - stable 2025-01-29 DERP_PR_0014
euProtectedAreaCode.DERP_PR_0015 MAROTHER WEIHER Quick edit Valid - stable 2025-01-29 DERP_PR_0015
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?