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 121 to 140.First345678910Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT1110002000120010 SONNENSEE RITZING Quick edit Valid - stable 2022-08-11 AT1110002000120010
euProtectedAreaCode.AT1120000200060010 NEUSIEDLERSEE RUST Quick edit Valid - stable 2022-08-11 AT1120000200060010
euProtectedAreaCode.AT1120000300060010 NEUSIEDLERSEE BREITENBRUNN Quick edit Valid - stable 2022-08-11 AT1120000300060010
euProtectedAreaCode.AT1120000900060010 NEUSIEDLERSEE MORBISCH Quick edit Valid - stable 2022-08-11 AT1120000900060010
euProtectedAreaCode.AT1120001100040010 NEUFELDER SEE Quick edit Valid - stable 2022-08-11 AT1120001100040010
euProtectedAreaCode.AT1120001800130010 STEINBRUNNER SEE Quick edit Valid - stable 2022-08-11 AT1120001800130010
euProtectedAreaCode.AT1120002700070010 STAUSEE FORCHTENSTEIN Quick edit Valid - stable 2022-08-11 AT1120002700070010
euProtectedAreaCode.AT1120003200030010 BADESEE NEUDORFL Quick edit Valid - stable 2022-08-11 AT1120003200030010
euProtectedAreaCode.AT1120004000050010 ROMERSEE WIESEN Quick edit Valid - stable 2022-08-11 AT1120004000050010
euProtectedAreaCode.AT1120004400010010 BADESEE ANDAU Quick edit Valid - stable 2022-08-11 AT1120004400010010
euProtectedAreaCode.AT1120004500020010 BADESEE APETLON Quick edit Valid - stable 2022-08-11 AT1120004500020010
euProtectedAreaCode.AT1120005200060010 NEUSIEDLERSEE ILLMITZ Quick edit Valid - stable 2022-08-11 AT1120005200060010
euProtectedAreaCode.AT1120005600060010 NEUSIEDLERSEE NEUSIEDL Quick edit Valid - stable 2022-08-11 AT1120005600060010
euProtectedAreaCode.AT1120006100060010 NEUSIEDLERSEE PODERSDORF Quick edit Valid - stable 2022-08-11 AT1120006100060010
euProtectedAreaCode.AT1120006200140010 ZICKSEE ST ANDRA Quick edit Deprecated - retired 2022-08-11 AT1120006200140010
euProtectedAreaCode.AT1120006500060010 NEUSIEDLERSEE WEIDEN Quick edit Valid - stable 2022-08-11 AT1120006500060010
euProtectedAreaCode.AT1130002700100010 STAUSEE RAUCHWART Quick edit Valid - stable 2022-08-11 AT1130002700100010
euProtectedAreaCode.AT1130004500080010 STAUSEE BURG HANNERSDORF Quick edit Valid - stable 2022-08-11 AT1130004500080010
euProtectedAreaCode.AT1130005800110010 STAUSEE RECHNITZ Quick edit Valid - stable 2022-08-11 AT1130005800110010
euProtectedAreaCode.AT1130006800090010 STAUSEE NEUSTIFT LAFNITZ Quick edit Valid - stable 2022-08-11 AT1130006800090010
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?