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 361 to 380.First1516171819202122Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3350001100230010 SCHWARZSEE STRANDBAD Quick edit Valid - stable 2022-08-11 AT3350001100230010
euProtectedAreaCode.AT3350002500090010 BERGLSTEINER SEE WEST Quick edit Valid - stable 2022-08-11 AT3350002500090010
euProtectedAreaCode.AT3350003000060010 BADESEE KIRCHBICHL HAUPTBADEBUCHT Quick edit Valid - stable 2022-08-11 AT3350003000060010
euProtectedAreaCode.AT3350003100130010 BADESEE KRUMMSEE SUD Quick edit Valid - stable 2022-08-11 AT3350003100130010
euProtectedAreaCode.AT3350003100200010 REINTALER SEE NORD-OST Quick edit Valid - stable 2022-08-11 AT3350003100200010
euProtectedAreaCode.AT3350003100200020 REINTALER SEE CAMPINGPLATZ Quick edit Valid - stable 2022-08-11 AT3350003100200020
euProtectedAreaCode.AT3350003200110010 HECHTSEE STRANDBAD Quick edit Valid - stable 2022-08-11 AT3350003200110010
euProtectedAreaCode.AT3350003400245010 STIMMERSEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3350003400245010
euProtectedAreaCode.AT3350004100210010 REITHER SEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3350004100210010
euProtectedAreaCode.AT3350004300125010 HINTERSTEINER SEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3350004300125010
euProtectedAreaCode.AT3350004600250010 THIERSEE BADEANSTALT Quick edit Valid - stable 2022-08-11 AT3350004600250010
euProtectedAreaCode.AT3350004600250020 THIERSEE CAMPINGPLATZ Quick edit Valid - stable 2022-08-11 AT3350004600250020
euProtectedAreaCode.AT3350004800280020 WALCHSEE CAMPING Quick edit Valid - stable 2022-08-11 AT3350004800280020
euProtectedAreaCode.AT3350004800280030 WALCHSEE UFERPROMENADE Quick edit Valid - stable 2022-08-11 AT3350004800280030
euProtectedAreaCode.AT3350005100010010 ACHENSEE NORD Quick edit Valid - stable 2022-08-11 AT3350005100010010
euProtectedAreaCode.AT3350005600010020 ACHENSEE STRANDBAD BUCHAU Quick edit Valid - stable 2022-08-11 AT3350005600010020
euProtectedAreaCode.AT3350005600010030 ACHENSEE SUD Quick edit Valid - stable 2022-08-11 AT3350005600010030
euProtectedAreaCode.AT3350008100290010 WEISSLAHN OST Quick edit Valid - stable 2022-08-11 AT3350008100290010
euProtectedAreaCode.AT3420000300030040 BODENSEE SEECAMPING BREGENZ Quick edit Valid - stable 2022-08-11 AT3420000300030040
euProtectedAreaCode.AT3420000300030050 BODENSEE STRANDBAD BREGENZ Quick edit Valid - stable 2022-08-11 AT3420000300030050
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?