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,541 to 4,560.First224225226227228229230231Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBW_PR_0254 ALTENHEIM BAGGERSEE WACHOLDERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0254
euProtectedAreaCode.DEBW_PR_0255 DUNDENHEIM BAGGERSEE STOCKFELDSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0255
euProtectedAreaCode.DEBW_PR_0256 OFFENBURG STRANDBAD GIFIZ Quick edit Valid - stable 2025-01-29 DEBW_PR_0256
euProtectedAreaCode.DEBW_PR_0257 FREISTETT BADESEE FREISTETT Quick edit Valid - stable 2025-01-29 DEBW_PR_0257
euProtectedAreaCode.DEBW_PR_0258 HONAU BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0258
euProtectedAreaCode.DEBW_PR_0259 RUST BAGGERSEE ALLMENDSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0259
euProtectedAreaCode.DEBW_PR_0260 SCHUTTERWALD BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0260
euProtectedAreaCode.DEBW_PR_0261 NONNENWEIER BAGGERSEE ANGLERHEIM Quick edit Valid - stable 2025-01-29 DEBW_PR_0261
euProtectedAreaCode.DEBW_PR_0262 HESSELHURST WALDSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0262
euProtectedAreaCode.DEBW_PR_0263 LEGELSHURST BAGGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0263
euProtectedAreaCode.DEBW_PR_0264 ELLENBERG HAESLESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0264
euProtectedAreaCode.DEBW_PR_0265 ELLENBERG HASELBACHSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0265
euProtectedAreaCode.DEBW_PR_0266 ELLWANGEN KRESSBACHSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0266
euProtectedAreaCode.DEBW_PR_0267 ELLWANGEN SONNENBACHSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0267
euProtectedAreaCode.DEBW_PR_0268 GSCHWEND NATURBADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0268
euProtectedAreaCode.DEBW_PR_0269 ELLWANGEN FISCHBACHSEE Quick edit Deprecated - retired 2025-01-29 DEBW_PR_0269
euProtectedAreaCode.DEBW_PR_0270 WALDHAUSEN BAGGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0270
euProtectedAreaCode.DEBW_PR_0271 RAINAU BADESEE BUCH Quick edit Valid - stable 2025-01-29 DEBW_PR_0271
euProtectedAreaCode.DEBW_PR_0272 ROSENBERG ORROTSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0272
euProtectedAreaCode.DEBW_PR_0273 UNTERSCHNEIDHEIM FREIZEITSEE WESTERE Quick edit Valid - stable 2025-01-29 DEBW_PR_0273
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?