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 136,421 to 136,440.First6,8186,8196,8206,8216,8226,8236,8246,825Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SKPZV100195 OSTROVNE LUCKY ST C 10 Quick edit Valid - stable 2025-01-29 SKPZV100195
euProtectedAreaCode.SKPZV100196 OSTROVNE LUCKY ST C 11 Quick edit Valid - stable 2025-01-29 SKPZV100196
euProtectedAreaCode.SKPZV100197 OSTROVNE LUCKY ST C 12 Quick edit Valid - stable 2025-01-29 SKPZV100197
euProtectedAreaCode.SKPZV100198 OSTROVNE LUCKY ST C 13 Quick edit Valid - stable 2025-01-29 SKPZV100198
euProtectedAreaCode.SKPZV100203 OSTROVNE LUCKY ST C 19 Quick edit Valid - stable 2025-01-29 SKPZV100203
euProtectedAreaCode.SKPZV100204 OSTROVNE LUCKY ST C 20 Quick edit Valid - stable 2025-01-29 SKPZV100204
euProtectedAreaCode.SKPZV100205 OSTROVNE LUCKY ST C 21 Quick edit Valid - stable 2025-01-29 SKPZV100205
euProtectedAreaCode.SKPZV100206 OSTROVNE LUCKY ST C 22 Quick edit Valid - stable 2025-01-29 SKPZV100206
euProtectedAreaCode.SKPZV100207 OSTROVNE LUCKY ST C 23 Quick edit Valid - stable 2025-01-29 SKPZV100207
euProtectedAreaCode.SKPZV100208 KARLOVA VES SIHOT STUDNA R Quick edit Valid - stable 2025-01-29 SKPZV100208
euProtectedAreaCode.SKPZV100219 PECNIANSKY LES STUDNA C 5A Quick edit Valid - stable 2025-01-29 SKPZV100219
euProtectedAreaCode.SKPZV100220 PECNIANSKY LES STUDNA C 31 Quick edit Valid - stable 2025-01-29 SKPZV100220
euProtectedAreaCode.SKPZV100223 PECNIANSKY LES STUDNA C 34 Quick edit Valid - stable 2025-01-29 SKPZV100223
euProtectedAreaCode.SKPZV100410 KALINKOVO S 10 Quick edit Valid - stable 2025-01-29 SKPZV100410
euProtectedAreaCode.SKPZV100411 SAMORIN S 1 Quick edit Valid - stable 2025-01-29 SKPZV100411
euProtectedAreaCode.SKPZV100412 SAMORIN S 2 Quick edit Valid - stable 2025-01-29 SKPZV100412
euProtectedAreaCode.SKPZV100413 SAMORIN S 5 Quick edit Valid - stable 2025-01-29 SKPZV100413
euProtectedAreaCode.SKPZV100414 SAMORIN S 6 Quick edit Valid - stable 2025-01-29 SKPZV100414
euProtectedAreaCode.SKPZV100415 SAMORIN S 7 Quick edit Valid - stable 2025-01-29 SKPZV100415
euProtectedAreaCode.SKPZV100416 SAMORIN S 8 Quick edit Valid - stable 2025-01-29 SKPZV100416
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?