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,381 to 5,400.First266267268269270271272273Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_2_0400 KLOSTERSEE DARGUN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0400
euProtectedAreaCode.DEMV_PR_2_0401 KUMMEROWER SEE SALEM Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0401
euProtectedAreaCode.DEMV_PR_2_0402 KUMMEROWER SEE KUMMEROW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0402
euProtectedAreaCode.DEMV_PR_2_0403 RUETZENFELDER SEE RUETZENFELDE Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0403
euProtectedAreaCode.DEMV_PR_2_0410 KUMMEROWER SEE SOMMERSDORF Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0410
euProtectedAreaCode.DEMV_PR_2_0411 KUMMEROWER SEE GRAVELOTTE Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0411
euProtectedAreaCode.DEMV_PR_2_0412 KUMMEROWER SEE VERCHEN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0412
euProtectedAreaCode.DEMV_PR_2_0413 KIESSEE ZARRENTHIN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0413
euProtectedAreaCode.DEMV_PR_2_0422 TUEZER SEE TUEZEN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0422
euProtectedAreaCode.DEMV_PR_2_0439 PLAUER SEE ALT SCHWERIN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0439
euProtectedAreaCode.DEMV_PR_2_0440 PLAUER SEE BAD STUER Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0440
euProtectedAreaCode.DEMV_PR_2_0441 PLAUER SEE ZISLOW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0441
euProtectedAreaCode.DEMV_PR_2_0442 PLAUER SEE LENZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0442
euProtectedAreaCode.DEMV_PR_2_0443 DREWITZER SEE SPAROW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0443
euProtectedAreaCode.DEMV_PR_2_0444 FLEESENSEE MALCHOW STRANDBAD Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0444
euProtectedAreaCode.DEMV_PR_2_0445 FLEESENSEE SILZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0445
euProtectedAreaCode.DEMV_PR_2_0446 JABELER SEE JABEL SPORTPLATZ Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0446
euProtectedAreaCode.DEMV_PR_2_0447 FLEESENSEE UNTERGOEHREN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0447
euProtectedAreaCode.DEMV_PR_2_0448 JABELER SEE JABEL BREUKKEN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0448
euProtectedAreaCode.DEMV_PR_2_0449 JABELER SEE DAMEROW Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0449
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?