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
29 Oct 2015
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

106,312 concepts found, displaying 1,281 to 1,300.First6162636465666768Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BEVL_BGW_029_S KATTE-MEUTERBOS Quick edit Valid - stable 2022-08-11 BEVL_BGW_029_S
euProtectedAreaCode.BEVL_BGW_030_S KLEIN VORSEN Quick edit Valid - stable 2022-08-11 BEVL_BGW_030_S
euProtectedAreaCode.BEVL_BGW_031_S KLEMSKERKE Quick edit Valid - stable 2022-08-11 BEVL_BGW_031_S
euProtectedAreaCode.BEVL_BGW_032_S KLOOSTERWEG-BEUKENBOSSTRAAT Quick edit Valid - stable 2022-08-11 BEVL_BGW_032_S
euProtectedAreaCode.BEVL_BGW_033_S LEMBEKE-OOSTEEKLO Quick edit Valid - stable 2022-08-11 BEVL_BGW_033_S
euProtectedAreaCode.BEVL_BGW_034_S LONDERZEEL Quick edit Valid - stable 2022-08-11 BEVL_BGW_034_S
euProtectedAreaCode.BEVL_BGW_035_S MENEBEEK (KUMTICH) Quick edit Valid - stable 2022-08-11 BEVL_BGW_035_S
euProtectedAreaCode.BEVL_BGW_036_S MOERBEKE-WACHTEBEKE Quick edit Valid - stable 2022-08-11 BEVL_BGW_036_S
euProtectedAreaCode.BEVL_BGW_037_S MOL Quick edit Valid - stable 2022-08-11 BEVL_BGW_037_S
euProtectedAreaCode.BEVL_BGW_038_S NELLEBEEK-KOUTERSTRAAT (KRIJT) Quick edit Valid - stable 2022-08-11 BEVL_BGW_038_S
euProtectedAreaCode.BEVL_BGW_039_S NIEUWERKERKEN Quick edit Valid - stable 2022-08-11 BEVL_BGW_039_S
euProtectedAreaCode.BEVL_BGW_040_S OLEN Quick edit Valid - stable 2022-08-11 BEVL_BGW_040_S
euProtectedAreaCode.BEVL_BGW_041_S OLMEN-KANAAL Quick edit Valid - stable 2022-08-11 BEVL_BGW_041_S
euProtectedAreaCode.BEVL_BGW_042_S OLMEN-NETE Quick edit Valid - stable 2022-08-11 BEVL_BGW_042_S
euProtectedAreaCode.BEVL_BGW_043_S ORMENDAAL-NOORD-ZUID-HET BROEK Quick edit Valid - stable 2022-08-11 BEVL_BGW_043_S
euProtectedAreaCode.BEVL_BGW_044_S PAILLART Quick edit Valid - stable 2022-08-11 BEVL_BGW_044_S
euProtectedAreaCode.BEVL_BGW_045_S POEDERLEE Quick edit Valid - stable 2022-08-11 BEVL_BGW_045_S
euProtectedAreaCode.BEVL_BGW_0461_S PUT 1 (HEUSDEN-ZOLDER) Quick edit Valid - stable 2022-08-11 BEVL_BGW_0461_S
euProtectedAreaCode.BEVL_BGW_0462_S PUT 2 (HEUSDEN-ZOLDER) Quick edit Valid - stable 2022-08-11 BEVL_BGW_0462_S
euProtectedAreaCode.BEVL_BGW_0463_S PUT 3 (HEUSDEN-ZOLDER) Quick edit Valid - stable 2022-08-11 BEVL_BGW_0463_S
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?