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 321 to 340.First1314151617181920Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3230001200200010 SEEWALDSEE ST KOLOMANN Quick edit Valid - stable 2022-08-11 AT3230001200200010
euProtectedAreaCode.AT3230001500210010 WALDBAD ANIF Quick edit Valid - stable 2022-08-11 AT3230001500210010
euProtectedAreaCode.AT3230001800120010 GRABENSEE PERWANG Quick edit Valid - stable 2022-08-11 AT3230001800120010
euProtectedAreaCode.AT3230001900090010 BURMOOSER SEE Quick edit Valid - stable 2022-08-11 AT3230001900090010
euProtectedAreaCode.AT3230002600100010 FUSCHLSEE FUSCHL Quick edit Valid - stable 2022-08-11 AT3230002600100010
euProtectedAreaCode.AT3230003100220010 WALLERSEE HENNDORF Quick edit Valid - stable 2022-08-11 AT3230003100220010
euProtectedAreaCode.AT3230003200130010 HINTERSEE Quick edit Valid - stable 2022-08-11 AT3230003200130010
euProtectedAreaCode.AT3230003300100020 FUSCHLSEE HOF Quick edit Valid - stable 2022-08-11 AT3230003300100020
euProtectedAreaCode.AT3230003700150010 MATTSEE LOCHEN GEBERTSHAM Quick edit Valid - stable 2022-08-11 AT3230003700150010
euProtectedAreaCode.AT3230003700150020 MATTSEE MATTSEE Quick edit Valid - stable 2022-08-11 AT3230003700150020
euProtectedAreaCode.AT3230003700160010 OBERTRUMER SEE SEEHAM Quick edit Valid - stable 2022-08-11 AT3230003700160010
euProtectedAreaCode.AT3230003700160020 OBERTRUMER SEE STAFFL Quick edit Valid - stable 2022-08-11 AT3230003700160020
euProtectedAreaCode.AT3230003800220020 WALLERSEE NEUMARKT Quick edit Valid - stable 2022-08-11 AT3230003800220020
euProtectedAreaCode.AT3230004300050010 BADESEE ST GEORGEN Quick edit Deprecated - retired 2022-08-11 AT3230004300050010
euProtectedAreaCode.AT3230004400240010 WOLFGANGSEE ST GILGEN-RIED Quick edit Valid - stable 2022-08-11 AT3230004400240010
euProtectedAreaCode.AT3230004400240030 WOLFGANGSEE ST GILGEN Quick edit Valid - stable 2022-08-11 AT3230004400240030
euProtectedAreaCode.AT3230004400240040 WOLFGANGSEE ST GILGEN - GAMSJAGA Quick edit Valid - stable 2022-08-11 AT3230004400240040
euProtectedAreaCode.AT3230004800240020 WOLFGANGSEE STROBL Quick edit Valid - stable 2022-08-11 AT3230004800240020
euProtectedAreaCode.AT3230005000010010 AUTOBAHNSEE VIEHHAUSEN Quick edit Deprecated - retired 2022-08-11 AT3230005000010010
euProtectedAreaCode.AT3230005021200010 HARRBERGSEE FREIZEITANLAGE Quick edit Valid - stable 2022-08-11 AT3230005021200010
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?