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,341 to 4,360.First214215216217218219220221Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBW_PR_0054 HERMUTHAUSEN BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0054
euProtectedAreaCode.DEBW_PR_0055 WELDINGSFELDEN BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0055
euProtectedAreaCode.DEBW_PR_0056 OBERGINSBACH BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0056
euProtectedAreaCode.DEBW_PR_0057 UNTERGINSBACH BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0057
euProtectedAreaCode.DEBW_PR_0058 KUENZELSAU GARNBERG SEE ZIEGELEI Quick edit Valid - stable 2025-01-29 DEBW_PR_0058
euProtectedAreaCode.DEBW_PR_0059 KUENZELSAU KOCHERBADEBUCHT Quick edit Deprecated - retired 2025-01-29 DEBW_PR_0059
euProtectedAreaCode.DEBW_PR_0060 MULFINGEN STAUSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0060
euProtectedAreaCode.DEBW_PR_0061 JAGSTBERG BADESEE UNTERER RAILHOF Quick edit Valid - stable 2025-01-29 DEBW_PR_0061
euProtectedAreaCode.DEBW_PR_0062 HOLLENBACH BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0062
euProtectedAreaCode.DEBW_PR_0063 PFEDELBACH BUCHHORNER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0063
euProtectedAreaCode.DEBW_PR_0064 WALDENBURG NEUMUEHLSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0064
euProtectedAreaCode.DEBW_PR_0065 BAD SCHUSSENRIED ZELLER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0065
euProtectedAreaCode.DEBW_PR_0066 BAD SCHUSSENRIED OLZREUTHER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0066
euProtectedAreaCode.DEBW_PR_0067 ZUBEN BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0067
euProtectedAreaCode.DEBW_PR_0068 ELLMANNSWEILER BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0068
euProtectedAreaCode.DEBW_PR_0069 ERTINGEN SCHWARZACHTALER SEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0069
euProtectedAreaCode.DEBW_PR_0070 SINNINGEN BADESEE SINNINGEN Quick edit Valid - stable 2025-01-29 DEBW_PR_0070
euProtectedAreaCode.DEBW_PR_0071 LAUPHEIM PARKBAD Quick edit Valid - stable 2025-01-29 DEBW_PR_0071
euProtectedAreaCode.DEBW_PR_0072 OBERSULMETINGEN SURFSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0072
euProtectedAreaCode.DEBW_PR_0073 OCHSENHAUSEN ZIEGELWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0073
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?