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 341 to 360.First1415161718192021Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3230005100220030 WALLERSEE SEEKIRCHEN Quick edit Valid - stable 2022-08-11 AT3230005100220030
euProtectedAreaCode.AT3230005100220040 WALLERSEE ZELL Quick edit Valid - stable 2022-08-11 AT3230005100220040
euProtectedAreaCode.AT3310001100100010 HALDENSEE STRANDBAD Quick edit Valid - stable 2022-08-11 AT3310001100100010
euProtectedAreaCode.AT3310001400120010 HEITERWANGER SEE CAMPINGPLATZ Quick edit Valid - stable 2022-08-11 AT3310001400120010
euProtectedAreaCode.AT3310002800190010 PLANSEE CAMPINGPLATZ Quick edit Valid - stable 2022-08-11 AT3310002800190010
euProtectedAreaCode.AT3310002800190020 PLANSEE HOTEL SEESPITZ Quick edit Valid - stable 2022-08-11 AT3310002800190020
euProtectedAreaCode.AT3310002800270010 URISEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3310002800270010
euProtectedAreaCode.AT3320000100070010 BADESEE ROSSAU OST Quick edit Valid - stable 2022-08-11 AT3320000100070010
euProtectedAreaCode.AT3320000100070020 BADESEE ROSSAU WEST Quick edit Valid - stable 2022-08-11 AT3320000100070020
euProtectedAreaCode.AT3320002300140010 LANSER SEE NORD Quick edit Valid - stable 2022-08-11 AT3320002300140010
euProtectedAreaCode.AT3320003000170010 NATTERER SEE NORD Quick edit Valid - stable 2022-08-11 AT3320003000170010
euProtectedAreaCode.AT3320004900240010 SEEFELDER SEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3320004900240010
euProtectedAreaCode.AT3330003000260010 TRISTACHER SEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3330003000260010
euProtectedAreaCode.AT3340000900160010 MIEMINGER BADESEE NORD-WEST Quick edit Valid - stable 2022-08-11 AT3340000900160010
euProtectedAreaCode.AT3340001400180010 PIBURGER SEE STRANDBAD Quick edit Valid - stable 2022-08-11 AT3340001400180010
euProtectedAreaCode.AT3340003700020010 BADESEE UBERWASSER IN LADIS Quick edit Deprecated - retired 2022-08-11 AT3340003700020010
euProtectedAreaCode.AT3340004400220010 RIEDER BADESEE NORD-OST Quick edit Valid - stable 2022-08-11 AT3340004400220010
euProtectedAreaCode.AT3350000300150010 LAUCHSEE STRANDBAD Quick edit Valid - stable 2022-08-11 AT3350000300150010
euProtectedAreaCode.AT3350000400040010 BADESEE GOING NORDBUCHT Quick edit Valid - stable 2022-08-11 AT3350000400040010
euProtectedAreaCode.AT3350000900050010 BADESEE KIRCHBERG SUD-WEST Quick edit Valid - stable 2022-08-11 AT3350000900050010
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?