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,301 to 5,320.First262263264265266267268269Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_2_0005 SCHWERINER SEE KALKWERDER Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0005
euProtectedAreaCode.DEMV_PR_2_0008 LANKOWER SEE SUEDUFER Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0008
euProtectedAreaCode.DEMV_PR_2_0009 LANKOWER SEE NORDUFER Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0009
euProtectedAreaCode.DEMV_PR_2_0011 OSTORFER SEE KASPELWERDER Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0011
euProtectedAreaCode.DEMV_PR_2_0012 OSTORFER SEE NEUMUHLE Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0012
euProtectedAreaCode.DEMV_PR_2_0015 ZIEGELAUSSENSEE C -F -FLEMMING- KLINIK Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0015
euProtectedAreaCode.DEMV_PR_2_0055 PLAUER SEE FERIENDORF HEIDENHOLZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0055
euProtectedAreaCode.DEMV_PR_2_0056 PLAUER SEE QUETZIN RICHTBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0056
euProtectedAreaCode.DEMV_PR_2_0057 PLAUER SEE SEELUSTER BUCHT Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0057
euProtectedAreaCode.DEMV_PR_2_0058 PLAUER SEE CP ZURUF Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0058
euProtectedAreaCode.DEMV_PR_2_0060 PLAUER SEE PLOETZENHOEHE BAD Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0060
euProtectedAreaCode.DEMV_PR_2_0062 DOBBERTINER SEE CP DOBBERTIN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0062
euProtectedAreaCode.DEMV_PR_2_0063 DOBBERTINER SEE HELMSRADE Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0063
euProtectedAreaCode.DEMV_PR_2_0065 GOLDBERGER SEE BADESTRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0065
euProtectedAreaCode.DEMV_PR_2_0068 WOCKERSEE PARCHIM Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0068
euProtectedAreaCode.DEMV_PR_2_0070 TREPTOWSEE GR PANKOW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0070
euProtectedAreaCode.DEMV_PR_2_0071 KREIENER SEE KREIEN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0071
euProtectedAreaCode.DEMV_PR_2_0073 KRITZOWER SEE BROOCK Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0073
euProtectedAreaCode.DEMV_PR_2_0074 KRITZOWER SEE SCHLEMMIN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_2_0074
euProtectedAreaCode.DEMV_PR_2_0075 PASSOWER SEE PASSOW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0075
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?