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,721 to 4,740.First233234235236237238239240Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBY_PR_GZ_0104 MOOSWALDSEEN GUENZBURG Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0104
euProtectedAreaCode.DEBY_PR_GZ_0105 ERDBEERSEE GUENZBURG Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0105
euProtectedAreaCode.DEBY_PR_GZ_0380 HEILIGMANNSEE JETTINGEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0380
euProtectedAreaCode.DEBY_PR_GZ_0381 LUTZENBERGER SEE GUENZBURG Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0381
euProtectedAreaCode.DEBY_PR_GZ_0394 WAKEBOARD THANNHAUSEN Quick edit Valid - stable 2025-01-29 DEBY_PR_GZ_0394
euProtectedAreaCode.DEBY_PR_HAS_0008 BADESEE GOSSMANNSDORF HOFHEIM GOSSMANNSDORF GOSSMANNSDORF STEG Quick edit Deprecated - retired 2025-01-29 DEBY_PR_HAS_0008
euProtectedAreaCode.DEBY_PR_HAS_0009 HORHAEUSER SEE THERES HORHAUSEN HORHAUSEN SURFERSTRAND Quick edit Valid - stable 2025-01-29 DEBY_PR_HAS_0009
euProtectedAreaCode.DEBY_PR_HAS_0010 KLEIDERSEE HASSFURT AUGSFELD AUGSFELD SURFERUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_HAS_0010
euProtectedAreaCode.DEBY_PR_HAS_0011 KREBSSEE KNETZGAU WESTHEIM WESTHEIM LIEGEWIESE Quick edit Valid - stable 2025-01-29 DEBY_PR_HAS_0011
euProtectedAreaCode.DEBY_PR_HAS_0012 MOENUS-SEE STETTFELD SANDSTRAND Quick edit Deprecated - retired 2025-01-29 DEBY_PR_HAS_0012
euProtectedAreaCode.DEBY_PR_HAS_0013 PFISTER-FREIZEITLAND ELTMANN-ROSSSTADT ROSSSTADT SANDSTRAND Quick edit Deprecated - retired 2025-01-29 DEBY_PR_HAS_0013
euProtectedAreaCode.DEBY_PR_HAS_0014 SANDER SEE SAND AM MAIN SANDSTRAND Quick edit Valid - stable 2025-01-29 DEBY_PR_HAS_0014
euProtectedAreaCode.DEBY_PR_HAS_0408 SEIDENHAEUSER SEE ALTERSHAUSEN Quick edit Valid - stable 2025-01-29 DEBY_PR_HAS_0408
euProtectedAreaCode.DEBY_PR_HO_0033 AUENSEE JODITZ KOEDITZ JODITZ Quick edit Valid - stable 2025-01-29 DEBY_PR_HO_0033
euProtectedAreaCode.DEBY_PR_HO_0034 FRANKENWALDSEE LICHTENBERG Quick edit Deprecated - retired 2025-01-29 DEBY_PR_HO_0034
euProtectedAreaCode.DEBY_PR_HO_0035 SCHIEDATEICH SCHWARZENBACH ADSAALE SCHIEDA Quick edit Valid - stable 2025-01-29 DEBY_PR_HO_0035
euProtectedAreaCode.DEBY_PR_HO_0036 FOERMITZSPEICHER SCHWARZENBACH ADSAALE FOERMITZ Quick edit Valid - stable 2025-01-29 DEBY_PR_HO_0036
euProtectedAreaCode.DEBY_PR_HO_0037 UNTREUSEE HOF MOSCHENDORF Quick edit Valid - stable 2025-01-29 DEBY_PR_HO_0037
euProtectedAreaCode.DEBY_PR_IN_0210 INGOLSTADT AUWALDSEE BADEBEREICH BEI CAMPINGPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_IN_0210
euProtectedAreaCode.DEBY_PR_IN_0211 BAGGERSEE INGOLSTADT BADEBEREICH NAHE FISCHERHEIM Quick edit Valid - stable 2025-01-29 DEBY_PR_IN_0211
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?