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 281 to 300.First1112131415161718Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3150000200160020 HALLSTATTERSEE UNTERSEE Quick edit Valid - stable 2022-08-11 AT3150000200160020
euProtectedAreaCode.AT3150000400240010 OFFENSEE EBENSEE Quick edit Valid - stable 2022-08-11 AT3150000400240010
euProtectedAreaCode.AT3150000400270010 TRAUNSEE RINDBACH Quick edit Valid - stable 2022-08-11 AT3150000400270010
euProtectedAreaCode.AT3150000500270040 TRAUNSEE GMUNDEN Quick edit Valid - stable 2022-08-11 AT3150000500270040
euProtectedAreaCode.AT3150000900160008 HALLSTATTERSEE KESSELGRABEN Quick edit Valid - stable 2022-08-11 AT3150000900160008
euProtectedAreaCode.AT3150000900160010 HALLSTATTERSEE HALLSTATT Quick edit Valid - stable 2022-08-11 AT3150000900160010
euProtectedAreaCode.AT3150001200160004 HALLSTATTERSEE OBERTRAUN Quick edit Valid - stable 2022-08-11 AT3150001200160004
euProtectedAreaCode.AT3150001700290010 WOLFGANGSEE APPESBACH Quick edit Valid - stable 2022-08-11 AT3150001700290010
euProtectedAreaCode.AT3150001800270020 TRAUNSEE TRAUNKIRCHEN Quick edit Valid - stable 2022-08-11 AT3150001800270020
euProtectedAreaCode.AT3150002200010040 ATTERSEE ATTERSEE Quick edit Valid - stable 2022-08-11 AT3150002200010040
euProtectedAreaCode.AT3150003200220020 MONDSEE LOIBICHL Quick edit Valid - stable 2022-08-11 AT3150003200220020
euProtectedAreaCode.AT3150003500220010 MONDSEE MONDSEE Quick edit Valid - stable 2022-08-11 AT3150003500220010
euProtectedAreaCode.AT3150005100090010 REGAU BADESEE Quick edit Valid - stable 2022-08-11 AT3150005100090010
euProtectedAreaCode.AT3150005500220030 MONDSEE ST LORENZ Quick edit Valid - stable 2022-08-11 AT3150005500220030
euProtectedAreaCode.AT3150005900010030 ATTERSEE LITZLBERG Quick edit Valid - stable 2022-08-11 AT3150005900010030
euProtectedAreaCode.AT3150005900010050 ATTERSEE SEEWALCHEN Quick edit Valid - stable 2022-08-11 AT3150005900010050
euProtectedAreaCode.AT3150006000010010 ATTERSEE WEISSENBACH Quick edit Valid - stable 2022-08-11 AT3150006000010010
euProtectedAreaCode.AT3150006000010020 ATTERSEE STEINBACH Quick edit Valid - stable 2022-08-11 AT3150006000010020
euProtectedAreaCode.AT3150006500010060 ATTERSEE UNTERACH Quick edit Valid - stable 2022-08-11 AT3150006500010060
euProtectedAreaCode.AT3150006900010070 ATTERSEE WEYREGG Quick edit Valid - stable 2022-08-11 AT3150006900010070
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?