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,181 to 1,200.First5657585960616263Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BEVL_BW_BRG01 BERINGEN PAALSE PLAS Quick edit Valid - stable 2025-01-29 BEVL_BW_BRG01
euProtectedAreaCode.BEVL_BW_BRG02 BERINGEN T FONTEINTJE Quick edit Valid - stable 2025-01-29 BEVL_BW_BRG02
euProtectedAreaCode.BEVL_BW_BRN01 BEERNEM GEVAERTS ZUID Quick edit Valid - stable 2025-01-29 BEVL_BW_BRN01
euProtectedAreaCode.BEVL_BW_BRU01 BRUGGE COUPURE Quick edit Valid - stable 2025-01-29 BEVL_BW_BRU01
euProtectedAreaCode.BEVL_BW_BRU02 BRUGGE SINT PIETERSPLAS Quick edit Valid - stable 2025-01-29 BEVL_BW_BRU02
euProtectedAreaCode.BEVL_BW_BRU03 BRUGGE DAMSEVAART Quick edit Valid - stable 2025-01-29 BEVL_BW_BRU03
euProtectedAreaCode.BEVL_BW_BRU04 BRUGGE WESTKANT - ZEEBRUGGE Quick edit Valid - stable 2025-01-29 BEVL_BW_BRU04
euProtectedAreaCode.BEVL_BW_BRU06 BRUGGE KOUDE KEUKEN Quick edit Valid - stable 2025-01-29 BEVL_BW_BRU06
euProtectedAreaCode.BEVL_BW_DEI01 DEINZE VOSSELARE PUT Quick edit Valid - stable 2025-01-29 BEVL_BW_DEI01
euProtectedAreaCode.BEVL_BW_DES01 DESSEL - CAMPINASTRAND Quick edit Valid - stable 2025-01-29 BEVL_BW_DES01
euProtectedAreaCode.BEVL_BW_DHN01 DE HAAN VOSSESLAG Quick edit Valid - stable 2025-01-29 BEVL_BW_DHN01
euProtectedAreaCode.BEVL_BW_DHN02 DE HAAN CENTRUM Quick edit Valid - stable 2025-01-29 BEVL_BW_DHN02
euProtectedAreaCode.BEVL_BW_DHN04 DE HAAN WENDUINE Quick edit Valid - stable 2025-01-29 BEVL_BW_DHN04
euProtectedAreaCode.BEVL_BW_DHN05 DE HAAN HARENDIJKE - WENDUINE Quick edit Valid - stable 2025-01-29 BEVL_BW_DHN05
euProtectedAreaCode.BEVL_BW_DPN01 DE PANNE LEOPOLD Quick edit Valid - stable 2025-01-29 BEVL_BW_DPN01
euProtectedAreaCode.BEVL_BW_DPN03 DE PANNE CANADEZENPLEIN Quick edit Valid - stable 2025-01-29 BEVL_BW_DPN03
euProtectedAreaCode.BEVL_BW_DST01 DILSEN-STOKKEM TERHILLS RESORT Quick edit Valid - stable 2025-01-29 BEVL_BW_DST01
euProtectedAreaCode.BEVL_BW_GER01 GERAARDSBERGEN DE GAVERS Quick edit Valid - stable 2025-01-29 BEVL_BW_GER01
euProtectedAreaCode.BEVL_BW_GNT01 GENT BLAARMEERSEN ZWEMSPORTZONE Quick edit Valid - stable 2025-01-29 BEVL_BW_GNT01
euProtectedAreaCode.BEVL_BW_GNT02 GENT BLAARMEERSEN STRAND-BADZONE Quick edit Valid - stable 2025-01-29 BEVL_BW_GNT02
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?