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 381 to 400.First1617181920212223Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AT3420000300030080 BODENSEE WOCHERHAFEN BREGENZ Quick edit Valid - stable 2022-08-11 AT3420000300030080
euProtectedAreaCode.AT3420000300030090 BODENSEE SPORTHAFEN BREGENZ Quick edit Valid - stable 2022-08-11 AT3420000300030090
euProtectedAreaCode.AT3420000300040010 RHEINTAL-BODENSEEGEB Quick edit Deprecated - retired 2022-08-11 AT3420000300040010
euProtectedAreaCode.AT3420000700030010 BODENSEE HORNLEDAMM FUSSACH Quick edit Valid - stable 2022-08-11 AT3420000700030010
euProtectedAreaCode.AT3420000700030030 BODENSEE ROHRSPITZ FUSSACH Quick edit Valid - stable 2022-08-11 AT3420000700030030
euProtectedAreaCode.AT3420000900030060 BODENSEE STRANDBAD HARD Quick edit Valid - stable 2022-08-11 AT3420000900030060
euProtectedAreaCode.AT3420001000050010 BRUGGERLOCH HOCHST Quick edit Valid - stable 2022-08-11 AT3420001000050010
euProtectedAreaCode.AT3420001500070010 RIEDSEE LAUTERACH Quick edit Valid - stable 2022-08-11 AT3420001500070010
euProtectedAreaCode.AT3420001600030020 BODENSEE MILITARBAD LOCHAU Quick edit Valid - stable 2022-08-11 AT3420001600030020
euProtectedAreaCode.AT3420001600030070 BODENSEE STRANDBAD LOCHAU Quick edit Valid - stable 2022-08-11 AT3420001600030070
euProtectedAreaCode.AT3420002300060010 RHEINAUEN HOHENEMS Quick edit Valid - stable 2022-08-11 AT3420002300060010
euProtectedAreaCode.AT3420002400010010 ALTER RHEIN LUSTENAU Quick edit Valid - stable 2022-08-11 AT3420002400010010
euProtectedAreaCode.AT3420002900080010 UNTERE AU FRASTANZ Quick edit Valid - stable 2022-08-11 AT3420002900080010
euProtectedAreaCode.AT3420003800020010 BAGGERSEE PASPELS RANKWEIL Quick edit Valid - stable 2022-08-11 AT3420003800020010
euProtectedAreaCode.AT3428021500030100 BODENSEE FKK HARD Quick edit Valid - stable 2022-08-11 AT3428021500030100
euProtectedAreaCode.ATNVZ NITRATES VULNERABLE ZONE Quick edit Valid - experimental 2022-08-11 ATNVZ
euProtectedAreaCode.ATPA1 HEILIGENKREUZ-WALLENDORF Quick edit Valid - stable 2022-08-11 ATPA1
euProtectedAreaCode.ATPA10 SCHONGEBIET GOLLING - ERLAUF - BERGLAND Quick edit Valid - stable 2022-08-11 ATPA10
euProtectedAreaCode.ATPA100 SICHELDORF-RADKERSBURG Quick edit Valid - stable 2022-08-11 ATPA100
euProtectedAreaCode.ATPA101 FRIESACH BEI GRAZ Quick edit Valid - stable 2022-08-11 ATPA101
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?