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,181 to 4,200.First206207208209210211212213Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBB_PR_0215 DREETZSEE THOMSDORF CAMPINGPLATZ Quick edit Valid - stable 2025-01-29 DEBB_PR_0215
euProtectedAreaCode.DEBB_PR_0216 FAEHRSEE TEMPLIN CAMPINGPLATZ Quick edit Valid - stable 2025-01-29 DEBB_PR_0216
euProtectedAreaCode.DEBB_PR_0217 GLEUENSEE KLOSTERWALDE ZELTPLATZ Quick edit Valid - stable 2025-01-29 DEBB_PR_0217
euProtectedAreaCode.DEBB_PR_0218 GOLLINSEE GOLLIN Quick edit Valid - stable 2025-01-29 DEBB_PR_0218
euProtectedAreaCode.DEBB_PR_0219 GROSSER KRONSEE RUTENBERG Quick edit Valid - stable 2025-01-29 DEBB_PR_0219
euProtectedAreaCode.DEBB_PR_0220 KUHSEE GRAMZOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0220
euProtectedAreaCode.DEBB_PR_0221 GROSSER LYCHENSEE LYCHEN STRANDBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0221
euProtectedAreaCode.DEBB_PR_0222 GROSSER SEE HOHENGUESTOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0222
euProtectedAreaCode.DEBB_PR_0223 GROSSER SEE FUERSTENWERDER Quick edit Valid - stable 2025-01-29 DEBB_PR_0223
euProtectedAreaCode.DEBB_PR_0224 GROSSER VAETERSEE GROSS VAETER Quick edit Valid - stable 2025-01-29 DEBB_PR_0224
euProtectedAreaCode.DEBB_PR_0225 WARTHESEE WARTHE Quick edit Valid - stable 2025-01-29 DEBB_PR_0225
euProtectedAreaCode.DEBB_PR_0226 HAUSSEE HARDENBECK Quick edit Valid - stable 2025-01-29 DEBB_PR_0226
euProtectedAreaCode.DEBB_PR_0227 KASTAVENSEE RETZOW KASTAVEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0227
euProtectedAreaCode.DEBB_PR_0228 KLEINOWSEE FALKENWALDE OT NEU KLEINOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0228
euProtectedAreaCode.DEBB_PR_0229 LUEBBESEE MILMERSDORF OT PETERSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0229
euProtectedAreaCode.DEBB_PR_0230 LUEBBESEE TEMPLIN SEEHOTEL Quick edit Valid - stable 2025-01-29 DEBB_PR_0230
euProtectedAreaCode.DEBB_PR_0231 LUETZLOWER SEE LUETZLOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0231
euProtectedAreaCode.DEBB_PR_0232 NAUGARTENER SEE NAUGARTEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0232
euProtectedAreaCode.DEBB_PR_0233 OBERUCKERSEE FERGITZ Quick edit Valid - stable 2025-01-29 DEBB_PR_0233
euProtectedAreaCode.DEBB_PR_0234 OBERUCKERSEE SEEHAUSEN QUAST Quick edit Valid - stable 2025-01-29 DEBB_PR_0234
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?