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,241 to 5,260.First259260261262263264265266Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_1_0744 GREIFSWALDER BODDEN LUDWIGSBURG Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0744
euProtectedAreaCode.DEMV_PR_1_0746 GREIFSWALDER BODDEN LOISSIN CAMPINGPLATZ Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0746
euProtectedAreaCode.DEMV_PR_1_0747 GREIFSWALDER BODDEN GAHLKOW Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0747
euProtectedAreaCode.DEMV_PR_1_0750 GREIFSWALDER BODDEN LUBMIN SEEBRUECKE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0750
euProtectedAreaCode.DEMV_PR_1_0752 GREIFSWALDER BODDEN LUBMIN WALDHEIDE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0752
euProtectedAreaCode.DEMV_PR_1_0763 OSTSEE NEUENDORF GELLEN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0763
euProtectedAreaCode.DEMV_PR_1_0764 OSTSEE VITTE DUENENHEIDE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0764
euProtectedAreaCode.DEMV_PR_1_0765 OSTSEE KLOSTER Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0765
euProtectedAreaCode.DEMV_PR_1_0767 OSTSEE DRANSKE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0767
euProtectedAreaCode.DEMV_PR_1_0768 OSTSEE BAKENBERG Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0768
euProtectedAreaCode.DEMV_PR_1_0769 OSTSEE NONNEVITZ Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0769
euProtectedAreaCode.DEMV_PR_1_0770 OSTSEE PUTGARTEN NORDSTRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0770
euProtectedAreaCode.DEMV_PR_1_0771 OSTSEE VITT Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0771
euProtectedAreaCode.DEMV_PR_1_0772 OSTSEE ZITTCHOW DREWOLDKE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0772
euProtectedAreaCode.DEMV_PR_1_0773 OSTSEE JULIUSRUH Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0773
euProtectedAreaCode.DEMV_PR_1_0774 OSTSEE SCHAABE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0774
euProtectedAreaCode.DEMV_PR_1_0775 OSTSEE SCHAABE-SUD Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0775
euProtectedAreaCode.DEMV_PR_1_0776 OSTSEE PRORA MUKRAN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0776
euProtectedAreaCode.DEMV_PR_1_0777 OSTSEE PRORA-SUD Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0777
euProtectedAreaCode.DEMV_PR_1_0778 OSTSEE BINZ PRORA Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0778
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?