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,161 to 1,180.First5556575859606162Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BEVL_BGW_10706_M VLAKENHOF PUT6 Quick edit Valid - stable 2025-01-29 BEVL_BGW_10706_M
euProtectedAreaCode.BEVL_BGW_10707_M VLAKENHOF PUT7 Quick edit Valid - stable 2025-01-29 BEVL_BGW_10707_M
euProtectedAreaCode.BEVL_BGW_108_M DIETS-HEUR Quick edit Valid - stable 2025-01-29 BEVL_BGW_108_M
euProtectedAreaCode.BEVL_BGW_109_M LAUW-TONGEREN Quick edit Valid - stable 2025-01-29 BEVL_BGW_109_M
euProtectedAreaCode.BEVL_BGW_111_M MEERLE Quick edit Valid - stable 2025-01-29 BEVL_BGW_111_M
euProtectedAreaCode.BEVL_BGW_112_M BOLKSE HEIDE Quick edit Valid - stable 2025-01-29 BEVL_BGW_112_M
euProtectedAreaCode.BEVL_BGW_113_M HOOGSTRATEN Quick edit Valid - stable 2025-01-29 BEVL_BGW_113_M
euProtectedAreaCode.BEVL_BGW_114_M RAVELS Quick edit Valid - stable 2025-01-29 BEVL_BGW_114_M
euProtectedAreaCode.BEVL_BGW_115_M WUUSTWEZEL Quick edit Valid - stable 2025-01-29 BEVL_BGW_115_M
euProtectedAreaCode.BEVL_BGW_116_M ESSEN Quick edit Valid - stable 2025-01-29 BEVL_BGW_116_M
euProtectedAreaCode.BEVL_BW_ANT01 ANTWERPEN GALGENWEEL Quick edit Valid - stable 2025-01-29 BEVL_BW_ANT01
euProtectedAreaCode.BEVL_BW_BLA02 BLANKENBERGE WESTSTRAAT Quick edit Valid - stable 2025-01-29 BEVL_BW_BLA02
euProtectedAreaCode.BEVL_BW_BLA04 BLANKENBERGE KERKSTRAAT Quick edit Valid - stable 2025-01-29 BEVL_BW_BLA04
euProtectedAreaCode.BEVL_BW_BLA06 BLANKENBERGE ARTANHELLING Quick edit Valid - stable 2025-01-29 BEVL_BW_BLA06
euProtectedAreaCode.BEVL_BW_BLE01 BERLARE NIEUWDONK Quick edit Valid - stable 2025-01-29 BEVL_BW_BLE01
euProtectedAreaCode.BEVL_BW_BRE01 BREDENE TURKEYEN Quick edit Valid - stable 2025-01-29 BEVL_BW_BRE01
euProtectedAreaCode.BEVL_BW_BRE02 BREDENE DUINGAT Quick edit Valid - stable 2025-01-29 BEVL_BW_BRE02
euProtectedAreaCode.BEVL_BW_BRE03 BREDENE ASTRID Quick edit Valid - stable 2025-01-29 BEVL_BW_BRE03
euProtectedAreaCode.BEVL_BW_BRE04 BREDENE DROGE OPGANG Quick edit Valid - stable 2025-01-29 BEVL_BW_BRE04
euProtectedAreaCode.BEVL_BW_BRE05 BREDENE DE DUINPAN Quick edit Valid - stable 2025-01-29 BEVL_BW_BRE05
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?