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
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
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
hasFeatureOfInterest Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

440,076 concepts found, displaying 161 to 180.First56789101112Last
Id Label Status Status Modified Notation
eionetMonitoringSiteCode.ALRV_607 SEMAN RIVER MUJALLI Quick edit Deprecated - superseded 2021-06-17 ALRV_607
eionetMonitoringSiteCode.ALRV_701 VJOSA RIVER MIFOL Quick edit Deprecated - retired 2021-06-17 ALRV_701
eionetMonitoringSiteCode.ALRV_703 DRINO RIVER URA E LEKLIT Quick edit Valid - experimental 2021-06-17 ALRV_703
eionetMonitoringSiteCode.ALRV_705 VJOSA RIVER MEMALIAJ Quick edit Valid - experimental 2021-06-17 ALRV_705
eionetMonitoringSiteCode.ALRV_8 TIRANA RIVER KAMEZ Quick edit Deprecated - retired 2021-06-17 ALRV_8
eionetMonitoringSiteCode.ALRV_9 TIRANA RIVER RINAS Quick edit Deprecated - retired 2021-06-17 ALRV_9
eionetMonitoringSiteCode.ALSHKODRA-LAKE SHKODRA LAKE Quick edit Deprecated - retired 2021-06-17 ALSHKODRA-LAKE
eionetMonitoringSiteCode.AT100 ACHENSEE Quick edit Deprecated - retired 2021-06-17 AT100
eionetMonitoringSiteCode.AT10000017 UNKNOWN Quick edit Deprecated - retired 2021-06-17 AT10000017
eionetMonitoringSiteCode.AT10000027 WGEV-STELLE SEEHOF Quick edit Deprecated - superseded 2021-06-17 AT10000027
eionetMonitoringSiteCode.AT10000037 HAMMER KASTELL Quick edit Deprecated - superseded 2021-06-17 AT10000037
eionetMonitoringSiteCode.AT10000047 UNKNOWN Quick edit Deprecated - retired 2021-06-17 AT10000047
eionetMonitoringSiteCode.AT10000057 UNKNOWN Quick edit Deprecated - retired 2021-06-17 AT10000057
eionetMonitoringSiteCode.AT10000067 UNKNOWN Quick edit Deprecated - retired 2021-06-17 AT10000067
eionetMonitoringSiteCode.AT10000077 NICKELSDORF Quick edit Deprecated - superseded 2021-06-17 AT10000077
eionetMonitoringSiteCode.AT10000087 NEUMARKT Quick edit Deprecated - superseded 2021-06-17 AT10000087
eionetMonitoringSiteCode.AT10000097 ELTENDORF Quick edit Deprecated - superseded 2021-06-17 AT10000097
eionetMonitoringSiteCode.AT10000107 HEILIGENBRUNN Quick edit Deprecated - superseded 2021-06-17 AT10000107
eionetMonitoringSiteCode.AT10000116 RIEDLINGSDORF Quick edit Deprecated - superseded 2021-06-17 AT10000116
eionetMonitoringSiteCode.AT10000126 SCHWENDGRABEN Quick edit Deprecated - superseded 2021-06-17 AT10000126
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?