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 5,821 to 5,840.First288289290291292293294295Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DENW_PR_0041 GROSSENBAUMER SEE FREIZEITANLAGE Quick edit Valid - stable 2025-01-29 DENW_PR_0041
euProtectedAreaCode.DENW_PR_0042 DUERENER BADESEE IN DUEREN GUERZENICH Quick edit Valid - stable 2025-01-29 DENW_PR_0042
euProtectedAreaCode.DENW_PR_0043 HEIDERBERGSEE BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0043
euProtectedAreaCode.DENW_PR_0044 HENNETALSPERRE BADEBUCHT MIELINGHAUSEN Quick edit Valid - stable 2025-01-29 DENW_PR_0044
euProtectedAreaCode.DENW_PR_0045 HENNETALSPERRE BERGHAUSER BUCHT Quick edit Valid - stable 2025-01-29 DENW_PR_0045
euProtectedAreaCode.DENW_PR_0046 HILLEBACHSEE NIEDERSFELD Quick edit Valid - stable 2025-01-29 DENW_PR_0046
euProtectedAreaCode.DENW_PR_0047 HORSTMARER SEE MITTE BADEZONE Quick edit Valid - stable 2025-01-29 DENW_PR_0047
euProtectedAreaCode.DENW_PR_0048 KLEINER KAARSTER SEE NOERDLBADESTR Quick edit Valid - stable 2025-01-29 DENW_PR_0048
euProtectedAreaCode.DENW_PR_0049 KRONENBURGER SEE BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0049
euProtectedAreaCode.DENW_PR_0050 KRUPPSEE FREIBAD Quick edit Valid - stable 2025-01-29 DENW_PR_0050
euProtectedAreaCode.DENW_PR_0051 LIBLARER SEE BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0051
euProtectedAreaCode.DENW_PR_0052 LIPPE SEE Quick edit Valid - stable 2025-01-29 DENW_PR_0052
euProtectedAreaCode.DENW_PR_0053 LISTERTALSPERRE CAMPING WINDEBRUCH Quick edit Valid - stable 2025-01-29 DENW_PR_0053
euProtectedAreaCode.DENW_PR_0054 LISTERTALSPERRE DLRG Quick edit Valid - stable 2025-01-29 DENW_PR_0054
euProtectedAreaCode.DENW_PR_0055 LISTERTALSPERRE KALBERSCHNACKE Quick edit Valid - stable 2025-01-29 DENW_PR_0055
euProtectedAreaCode.DENW_PR_0056 LISTERTALSPERRE RENGERBERG Quick edit Valid - stable 2025-01-29 DENW_PR_0056
euProtectedAreaCode.DENW_PR_0057 MILLINGER MEER BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0057
euProtectedAreaCode.DENW_PR_0058 MOEHNESEE STRANDBAD DELECKE Quick edit Valid - stable 2025-01-29 DENW_PR_0058
euProtectedAreaCode.DENW_PR_0059 MOEHNESEE STRANDBAD KOERBECKE NORD Quick edit Valid - stable 2025-01-29 DENW_PR_0059
euProtectedAreaCode.DENW_PR_0060 MOEHNESEE STRANDBAD KOERBECKE SUED Quick edit Valid - stable 2025-01-29 DENW_PR_0060
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?