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 261 to 280.First1011121314151617Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3110000600170010 HERATINGERSEE IBM Quick edit Valid - stable 2022-08-11 AT3110000600170010
euProtectedAreaCode.AT3110000800200010 HOLZOSTERSEE FRANKING Quick edit Valid - stable 2022-08-11 AT3110000800200010
euProtectedAreaCode.AT3110002300040010 MINING BADESEE Quick edit Valid - stable 2022-08-11 AT3110002300040010
euProtectedAreaCode.AT3110003700190010 HOLLERERSEE ST PANTALEON Quick edit Valid - stable 2022-08-11 AT3110003700190010
euProtectedAreaCode.AT3110009700060010 MUHLHEIM BADESEE Quick edit Valid - stable 2022-08-11 AT3110009700060010
euProtectedAreaCode.AT3110010300070010 PRAMET BADESEE Quick edit Valid - stable 2022-08-11 AT3110010300070010
euProtectedAreaCode.AT3120000100250010 PICHLINGERSEE LINZ Quick edit Valid - stable 2022-08-11 AT3120000100250010
euProtectedAreaCode.AT3120000100280010 WEIKERLSEE LINZ Quick edit Valid - stable 2022-08-11 AT3120000100280010
euProtectedAreaCode.AT3120001100230010 GREITERSEE-N PUPPING Quick edit Deprecated - retired 2022-08-11 AT3120001100230010
euProtectedAreaCode.AT3120003500110010 TRAUN-OEDT BADESEE Quick edit Valid - stable 2022-08-11 AT3120003500110010
euProtectedAreaCode.AT3120004100140010 FELDKIRCHEN-BADESEE N-O Quick edit Valid - stable 2022-08-11 AT3120004100140010
euProtectedAreaCode.AT3120005300260010 PLESCHINGERSEE STEYREGG Quick edit Valid - stable 2022-08-11 AT3120005300260010
euProtectedAreaCode.AT3120005300260020 BADESEE STEYREGG Quick edit Valid - stable 2022-08-11 AT3120005300260020
euProtectedAreaCode.AT3130003700180010 AUSEE HOHENLOHE LUFTENBERG Quick edit Valid - stable 2022-08-11 AT3130003700180010
euProtectedAreaCode.AT3130003900050010 MITTERKIRCHEN BADESEE Quick edit Valid - stable 2022-08-11 AT3130003900050010
euProtectedAreaCode.AT3130005200120010 WALDHAUSEN BADESEE Quick edit Valid - stable 2022-08-11 AT3130005200120010
euProtectedAreaCode.AT3130006800030010 KLAFFER BADESEE Quick edit Valid - stable 2022-08-11 AT3130006800030010
euProtectedAreaCode.AT3140000700130010 ELISABETHSEE KLAUS Quick edit Valid - stable 2022-08-11 AT3140000700130010
euProtectedAreaCode.AT3140001900150010 GLEINKERSEE SPITAL A P Quick edit Valid - stable 2022-08-11 AT3140001900150010
euProtectedAreaCode.AT3150000100270030 TRAUNSSEE ALTMUNSTER Quick edit Valid - stable 2022-08-11 AT3150000100270030
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?