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 741 to 760.First3435363738394041Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BERW_AC_LEGLISE03_AIVE DRAIN CHIERPAY Quick edit Valid - stable 2025-01-29 BERW_AC_LEGLISE03_AIVE
euProtectedAreaCode.BERW_AC_LEGLISE04_AIVE MAZURCHAMPS Quick edit Valid - stable 2025-01-29 BERW_AC_LEGLISE04_AIVE
euProtectedAreaCode.BERW_AC_LEGLISE07_AIVE BASSEILLE Quick edit Valid - stable 2025-01-29 BERW_AC_LEGLISE07_AIVE
euProtectedAreaCode.BERW_AC_LEGLISE10_AIVE BLANC CAILLOUX Quick edit Valid - stable 2025-01-29 BERW_AC_LEGLISE10_AIVE
euProtectedAreaCode.BERW_AC_LIBIN04_AIVE ROLIBUCHY SOURCE A Quick edit Valid - stable 2025-01-29 BERW_AC_LIBIN04_AIVE
euProtectedAreaCode.BERW_AC_LIBIN05_AIVE NOUVEAU PUITS GERBEFE Quick edit Valid - stable 2025-01-29 BERW_AC_LIBIN05_AIVE
euProtectedAreaCode.BERW_AC_LIBIN09_AIVE HAIE DE DEVANT LA FANGE Quick edit Valid - stable 2025-01-29 BERW_AC_LIBIN09_AIVE
euProtectedAreaCode.BERW_AC_LIBIN10_AIVE HALVOYMONT Quick edit Valid - stable 2025-01-29 BERW_AC_LIBIN10_AIVE
euProtectedAreaCode.BERW_AC_LIBIN12_AIVE LA RESPE SOURCE B Quick edit Valid - stable 2025-01-29 BERW_AC_LIBIN12_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT03_AIVE FOULON Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT03_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT04_AIVE BRAS-HAUT BOIS VOLTAIRE Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT04_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT05 SEVISCOURT-LE GORET-SO-DR Quick edit Deprecated 2025-01-29 BERW_AC_LIBRAMONT05
euProtectedAreaCode.BERW_AC_LIBRAMONT05_AIVE SEVISCOURT - LE GORET SO DR Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT05_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT07 BONNERUE-WINACHAMPS SO-DR OLD Quick edit Deprecated 2025-01-29 BERW_AC_LIBRAMONT07
euProtectedAreaCode.BERW_AC_LIBRAMONT07_AIVE BONNERUE-WINACHAMPS SO- DR Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT07_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT09_AIVE PETITE ROCHETTE-PUITS 1 - LE SERPONT Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT09_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT10 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT10
euProtectedAreaCode.BERW_AC_LIBRAMONT10_AIVE REMAGNE SASSOUET Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT10_AIVE
euProtectedAreaCode.BERW_AC_LIBRAMONT11_AIVE SAINTE-MARIE-CHEVIGNY LANEUVILLE SO -DR Quick edit Valid - stable 2025-01-29 BERW_AC_LIBRAMONT11_AIVE
euProtectedAreaCode.BERW_AC_LIMBOURG02 RULL TAK - GALERIE - PUITS DE LA LOUVETERIE Quick edit Valid - stable 2025-01-29 BERW_AC_LIMBOURG02
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?