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 1,961 to 1,980.First9596979899100101102Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BG3FSWMA402R102 VARLISHNITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA402R102
euProtectedAreaCode.BG3FSWMA403R102 BELESHTNITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA403R102
euProtectedAreaCode.BG3FSWMA500R104 CHEPELARSKA RIVER CHAYA Quick edit Valid - stable 2025-01-29 BG3FSWMA500R104
euProtectedAreaCode.BG3FSWMA500R106 SUSHITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA500R106
euProtectedAreaCode.BG3FSWMA500R107 BELISHKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA500R107
euProtectedAreaCode.BG3FSWMA500R108 KRUSHOVSKA REKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA500R108
euProtectedAreaCode.BG3FSWMA500R114 CHUDNITE MOSTOVE RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA500R114
euProtectedAreaCode.BG3FSWMA500R116 CHEPELARSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA500R116
euProtectedAreaCode.BG3FSWMA500R127 TAMRASHKA RIVER AND ITS TRIBUTARIES FROM SPRING Quick edit Valid - stable 2025-01-29 BG3FSWMA500R127
euProtectedAreaCode.BG3FSWMA500R217 MARITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA500R217
euProtectedAreaCode.BG3FSWMA501R108 MANASTIRSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA501R108
euProtectedAreaCode.BG3FSWMA501R127 TAMRASHKA RIVER AND ITS TRIBUTARIES FROM HPP Quick edit Valid - stable 2025-01-29 BG3FSWMA501R127
euProtectedAreaCode.BG3FSWMA600L134 VACHA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA600L134
euProtectedAreaCode.BG3FSWMA600R131 VACHA-2 Quick edit Valid - stable 2025-01-29 BG3FSWMA600R131
euProtectedAreaCode.BG3FSWMA600R136 DEVINSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA600R136
euProtectedAreaCode.BG3FSWMA600R141 SHIROKOLASHKA RIVER AND ITS TRIBUTARIES Quick edit Valid - stable 2025-01-29 BG3FSWMA600R141
euProtectedAreaCode.BG3FSWMA600R142 BUINOOVSKA RIVER AND ITS TRIBUTARIES Quick edit Valid - stable 2025-01-29 BG3FSWMA600R142
euProtectedAreaCode.BG3FSWMA600R218 DEVINSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA600R218
euProtectedAreaCode.BG3FSWMA601R142 TRIGRADSKA RIVER AND ITS TRIBUTARIES Quick edit Valid - stable 2025-01-29 BG3FSWMA601R142
euProtectedAreaCode.BG3FSWMA602R142 CHEIRSKA RIVER AND ITS TRIBUTARIES Quick edit Valid - stable 2025-01-29 BG3FSWMA602R142
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?