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 241 to 260.First910111213141516Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT2220003200270010 ODENSEE KAINISCH Quick edit Valid - stable 2022-08-11 AT2220003200270010
euProtectedAreaCode.AT2230000200170010 FREIZEITSEE AU BEI TURNAU Quick edit Valid - stable 2022-08-11 AT2230000200170010
euProtectedAreaCode.AT2230001800140010 ERLAUFSEE ST SEBASTIAN Quick edit Valid - stable 2022-08-11 AT2230001800140010
euProtectedAreaCode.AT2230002000370010 ZENZSEE TRAGOSS Quick edit Valid - stable 2022-08-11 AT2230002000370010
euProtectedAreaCode.AT2230002200240010 LEOPOLDSTEINER SEE EISENERZ Quick edit Valid - stable 2022-08-11 AT2230002200240010
euProtectedAreaCode.AT2230002800080010 BADESEE STEINER KRAUBATH MUR Quick edit Valid - stable 2022-08-11 AT2230002800080010
euProtectedAreaCode.AT2230004000180010 FREIZEITSEE WALD SCHOBERPASS Quick edit Valid - stable 2022-08-11 AT2230004000180010
euProtectedAreaCode.AT2240006000030010 BADESEE GROSSSTEINBACH Quick edit Valid - stable 2022-08-11 AT2240006000030010
euProtectedAreaCode.AT2240008800060010 BADESEE MONICHWALD Quick edit Valid - stable 2022-08-11 AT2240008800060010
euProtectedAreaCode.AT2240011200340010 STUBENBERGSEE Quick edit Valid - stable 2022-08-11 AT2240011200340010
euProtectedAreaCode.AT2240012400290010 ROCKSEE GOSDORF Quick edit Valid - stable 2022-08-11 AT2240012400290010
euProtectedAreaCode.AT2250003000330010 STAUSEE SOBOTH Quick edit Valid - stable 2022-08-11 AT2250003000330010
euProtectedAreaCode.AT2250006200310010 SILBERSEE Quick edit Valid - stable 2022-08-11 AT2250006200310010
euProtectedAreaCode.AT2250006200350010 SULMSEE Quick edit Valid - stable 2022-08-11 AT2250006200350010
euProtectedAreaCode.AT2250008700110010 BADESEE WILDON WILDON Quick edit Valid - stable 2022-08-11 AT2250008700110010
euProtectedAreaCode.AT2250010100200010 FREIZEITZENTRUM PIBERSTEIN Quick edit Valid - stable 2022-08-11 AT2250010100200010
euProtectedAreaCode.AT2260004700210010 FURTNERTEICH MARIAHOF Quick edit Valid - stable 2022-08-11 AT2260004700210010
euProtectedAreaCode.AT2260004800070010 BADESEE MUHLEN Quick edit Valid - stable 2022-08-11 AT2260004800070010
euProtectedAreaCode.AT2260007300220010 GRASLUPPTEICH ZEUTSCHACH Quick edit Valid - stable 2022-08-11 AT2260007300220010
euProtectedAreaCode.AT3110000200020010 WILDENAU BADESEE Quick edit Valid - stable 2022-08-11 AT3110000200020010
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?