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,701 to 4,720.First232233234235236237238239Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBY_PR_GAP_0192 LAUTERSEE MITTENWALD Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0192
euProtectedAreaCode.DEBY_PR_GAP_0193 BARMSEE KRUEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0193
euProtectedAreaCode.DEBY_PR_GAP_0194 BAYERSOIENER SEE BAD BAYERSOIEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0194
euProtectedAreaCode.DEBY_PR_GAP_0195 EIBSEE GRAINAU NORDUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0195
euProtectedAreaCode.DEBY_PR_GAP_0196 EIBSEE GRAINAU SUEDUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0196
euProtectedAreaCode.DEBY_PR_GAP_0197 EICHSEE GROSSWEIL Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0197
euProtectedAreaCode.DEBY_PR_GAP_0198 FERCHENSEE MITTENWALD Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0198
euProtectedAreaCode.DEBY_PR_GAP_0199 FROSCHHAUSER SEE MURNAU Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0199
euProtectedAreaCode.DEBY_PR_GAP_0200 GEROLDSEE KRUEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0200
euProtectedAreaCode.DEBY_PR_GAP_0201 GRUBSEE KRUEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0201
euProtectedAreaCode.DEBY_PR_GAP_0202 PFLEGERSEE GARMISCH PARTENKIRCHEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0202
euProtectedAreaCode.DEBY_PR_GAP_0203 RIEGSEE RIEGSEE CAMPING BRUGGER Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0203
euProtectedAreaCode.DEBY_PR_GAP_0204 RIEGSEE RIEGSEE CAMPING RIEGSEE Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0204
euProtectedAreaCode.DEBY_PR_GAP_0205 RIESSERSEE GARMISCH PARTENKIRCHEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0205
euProtectedAreaCode.DEBY_PR_GAP_0206 STAFFELSEE MURNAU MURNAU Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0206
euProtectedAreaCode.DEBY_PR_GAP_0207 STAFFELSEE SEEHAUSEN SEEHAUSEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0207
euProtectedAreaCode.DEBY_PR_GAP_0208 STAFFELSEE UFFING ALPENBLICK Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0208
euProtectedAreaCode.DEBY_PR_GAP_0209 STAFFELSEE UFFING UFFING Quick edit Valid - stable 2025-01-29 DEBY_PR_GAP_0209
euProtectedAreaCode.DEBY_PR_GZ_0102 SILBERSEE RETTENBACH Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0102
euProtectedAreaCode.DEBY_PR_GZ_0103 OBERRIEDER WEIHER BREITENTHAL Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0103
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?