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,461 to 4,480.First220221222223224225226227Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBW_PR_0174 HUEGELSHEIM ERLAENDERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0174
euProtectedAreaCode.DEBW_PR_0175 GRAUELSBAUM BAGGERSEE Quick edit Deprecated - retired 2025-01-29 DEBW_PR_0175
euProtectedAreaCode.DEBW_PR_0176 GRAUELSBAUM BAGGERSEE III Quick edit Valid - stable 2025-01-29 DEBW_PR_0176
euProtectedAreaCode.DEBW_PR_0177 MUGGENSTURM KALTENBACHSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0177
euProtectedAreaCode.DEBW_PR_0178 OTTERSDORF BAGGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0178
euProtectedAreaCode.DEBW_PR_0179 PLITTERSDORF DEGLERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0179
euProtectedAreaCode.DEBW_PR_0180 WINTERSDORF SAEMANNSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0180
euProtectedAreaCode.DEBW_PR_0181 WINTERSDORF SAUWEIDE Quick edit Valid - stable 2025-01-29 DEBW_PR_0181
euProtectedAreaCode.DEBW_PR_0182 STOLLHOFEN FREIZEITZENTRUM OBERRHEIN Quick edit Valid - stable 2025-01-29 DEBW_PR_0182
euProtectedAreaCode.DEBW_PR_0183 SOELLINGEN HANF SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0183
euProtectedAreaCode.DEBW_PR_0184 STOLLHOFEN FREIZEITZENTRUM INSELSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0184
euProtectedAreaCode.DEBW_PR_0185 ALTSHAUSEN ALTER WEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0185
euProtectedAreaCode.DEBW_PR_0186 WANGEN BAGGERSEE GRENIS Quick edit Valid - stable 2025-01-29 DEBW_PR_0186
euProtectedAreaCode.DEBW_PR_0187 AMTSZELL SINGENBERGER WEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0187
euProtectedAreaCode.DEBW_PR_0188 ARGENBUEHL MOORBAD BURG Quick edit Valid - stable 2025-01-29 DEBW_PR_0188
euProtectedAreaCode.DEBW_PR_0189 AULENDORF STEEGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0189
euProtectedAreaCode.DEBW_PR_0190 BAD WALDSEE STADTSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0190
euProtectedAreaCode.DEBW_PR_0191 BAD WURZACH LANGWEIHER BAIERZ Quick edit Valid - stable 2025-01-29 DEBW_PR_0191
euProtectedAreaCode.DEBW_PR_0192 BAD WURZACH METZISWEILERWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0192
euProtectedAreaCode.DEBW_PR_0193 BAINDT EGELSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0193
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?