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,561 to 4,580.First225226227228229230231232Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBW_PR_0274 SCHORNDORF ZIEGELEISEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0274
euProtectedAreaCode.DEBW_PR_0275 ALFDORF EISENBACHSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0275
euProtectedAreaCode.DEBW_PR_0276 KAISERSBACH EBNISEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0276
euProtectedAreaCode.DEBW_PR_0277 MURRHARDT WALDSEE FORNSBACH Quick edit Valid - stable 2025-01-29 DEBW_PR_0277
euProtectedAreaCode.DEBW_PR_0278 PLUEDERHAUSEN BADESEE PLUEDERHAUSEN Quick edit Valid - stable 2025-01-29 DEBW_PR_0278
euProtectedAreaCode.DEBW_PR_0279 WELZHEIM AICHSTRUTERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0279
euProtectedAreaCode.DEBW_PR_0280 ALTLUSSHEIM BLAUSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0280
euProtectedAreaCode.DEBW_PR_0281 BRUEHL BAGGERSEE KOLLERINSEL Quick edit Valid - stable 2025-01-29 DEBW_PR_0281
euProtectedAreaCode.DEBW_PR_0282 HEDDESHEIM BAGGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0282
euProtectedAreaCode.DEBW_PR_0283 HEMSBACH WIESENSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0283
euProtectedAreaCode.DEBW_PR_0284 KETSCH HOHWIESENSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0284
euProtectedAreaCode.DEBW_PR_0285 SANKT LEON BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0285
euProtectedAreaCode.DEBW_PR_0286 WALLDORF BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0286
euProtectedAreaCode.DEBW_PR_0287 WEINHEIM WAIDSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0287
euProtectedAreaCode.DEBW_PR_0288 WEINHEIM FKK SEE MIRAMAR Quick edit Valid - stable 2025-01-29 DEBW_PR_0288
euProtectedAreaCode.DEBW_PR_0289 BRAEUNLINGEN KIRNBERGSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0289
euProtectedAreaCode.DEBW_PR_0290 DONAUESCHINGEN RIEDSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0290
euProtectedAreaCode.DEBW_PR_0291 SANKT GEORGEN KLOSTERWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0291
euProtectedAreaCode.DEBW_PR_0292 SCHONACH NATURFREIBAD Quick edit Valid - stable 2025-01-29 DEBW_PR_0292
euProtectedAreaCode.DEBW_PR_0293 SANDWEIER KUEHLSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0293
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?