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,581 to 4,600.First226227228229230231232233Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBW_PR_0294 LANDWASSER MOOSWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0294
euProtectedAreaCode.DEBW_PR_0295 WEINGARTEN DIETENBACHSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0295
euProtectedAreaCode.DEBW_PR_0296 FREIBURG BETZENHAUSEN FLUECKIGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0296
euProtectedAreaCode.DEBW_PR_0297 OPFINGEN GROSSER OPFINGER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0297
euProtectedAreaCode.DEBW_PR_0298 OPFINGEN BAGGERSEE OCHSENMOOS Quick edit Valid - stable 2025-01-29 DEBW_PR_0298
euProtectedAreaCode.DEBW_PR_0299 HOCHDORF SILBERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0299
euProtectedAreaCode.DEBW_PR_0300 HOCHDORF TUNISEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0300
euProtectedAreaCode.DEBW_PR_0301 MANNHEIM VOGELSTANG SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0301
euProtectedAreaCode.DEBW_PR_0302 MANNHEIM STOLLENWOERTHWEIHER 1 Quick edit Valid - stable 2025-01-29 DEBW_PR_0302
euProtectedAreaCode.DEBW_PR_0303 MANNHEIM STOLLENWOERTHWEIHER 2 Quick edit Valid - stable 2025-01-29 DEBW_PR_0303
euProtectedAreaCode.DEBW_PR_0304 MANNHEIM RHEINAUER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0304
euProtectedAreaCode.DEBW_PR_0305 FROMMERN SCHIEFERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0305
euProtectedAreaCode.DEBW_PR_0306 OBERDIGISHEIM STAUSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0306
euProtectedAreaCode.DEBW_PR_0307 RANGENDINGEN STAUSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0307
euProtectedAreaCode.DEBW_PR_0308 SCHOEMBERG STAUSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0308
euProtectedAreaCode.DEBW_PR_0309 WINTERLINGEN NATURBAD Quick edit Valid - stable 2025-01-29 DEBW_PR_0309
euProtectedAreaCode.DEBW_PR_0310 BIBERSFELD STARKHOLZBACHER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0310
euProtectedAreaCode.DEBW_PR_0311 NEULER GRIESWEIHER Quick edit Deprecated - retired 2025-01-29 DEBW_PR_0311
euProtectedAreaCode.DEBW_PR_0312 URLOFFEN MAX-JORDAN-SEE Quick edit Deprecated - retired 2025-01-29 DEBW_PR_0312
euProtectedAreaCode.DEBW_PR_0313 WUESTENROT FINSTERROTER SEE Quick edit Deprecated - superseded 2025-11-04 DEBW_PR_0313
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?