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 301 to 320.First1213141516171819Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3150007100210010 IRR- ODER ZELLERSEE LAITER Quick edit Valid - stable 2022-08-11 AT3150007100210010
euProtectedAreaCode.AT3150007100210020 IRR- ODER ZELLERSEE TIEFGRABEN Quick edit Valid - stable 2022-08-11 AT3150007100210020
euProtectedAreaCode.AT3150007100210030 IRR- ODER ZELLERSEE ZELL AM MOOS Quick edit Valid - stable 2022-08-11 AT3150007100210030
euProtectedAreaCode.AT3210001000170010 PREBERSEE TAMSWEG Quick edit Valid - stable 2022-08-11 AT3210001000170010
euProtectedAreaCode.AT3220000200020010 BADESEE GASTEIN BAD HOFGASTEIN Quick edit Valid - stable 2022-08-11 AT3220000200020010
euProtectedAreaCode.AT3220000800180010 REITECKSEE FLACHAU Quick edit Valid - stable 2022-08-11 AT3220000800180010
euProtectedAreaCode.AT3220000800230010 WINKLERSEE FLACHAU Quick edit Valid - stable 2022-08-11 AT3220000800230010
euProtectedAreaCode.AT3220001000070010 BONDLSEE GOLDEGG Quick edit Valid - stable 2022-08-11 AT3220001000070010
euProtectedAreaCode.AT3220001000110010 GOLDEGGER SEE Quick edit Valid - stable 2022-08-11 AT3220001000110010
euProtectedAreaCode.AT3220003000030010 BADESEE HOLLERSBACH Quick edit Valid - stable 2022-08-11 AT3220003000030010
euProtectedAreaCode.AT3220004000040010 BADESEE NIEDERNSILL Quick edit Valid - stable 2022-08-11 AT3220004000040010
euProtectedAreaCode.AT3220004400190010 RITZENSEE SAALFELDEN Quick edit Valid - stable 2022-08-11 AT3220004400190010
euProtectedAreaCode.AT3220004900060010 BADESEE UTTENDORF Quick edit Valid - stable 2022-08-11 AT3220004900060010
euProtectedAreaCode.AT3220005300250010 ZELLER SEE ERLBERG Quick edit Valid - stable 2022-08-11 AT3220005300250010
euProtectedAreaCode.AT3220005300250020 ZELLER SEE PRIELAU Quick edit Valid - stable 2022-08-11 AT3220005300250020
euProtectedAreaCode.AT3220005300250030 ZELLER SEE SCHUTTDORF Quick edit Valid - stable 2022-08-11 AT3220005300250030
euProtectedAreaCode.AT3220005300250040 ZELLER SEE THUMERSBACH Quick edit Valid - stable 2022-08-11 AT3220005300250040
euProtectedAreaCode.AT3220005300250050 ZELLER SEE ZELL AM SEE Quick edit Valid - stable 2022-08-11 AT3220005300250050
euProtectedAreaCode.AT3230000100140010 LIEFERINGER BADESEE SALZBURG Quick edit Valid - stable 2022-08-11 AT3230000100140010
euProtectedAreaCode.AT3230000800080010 BURGERAUSEE KUCHL Quick edit Valid - stable 2022-08-11 AT3230000800080010
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?