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
errorType Fixed values
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 May 2023
skos:editorialNote Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:hiddenLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

612 concepts found, displaying 341 to 360.First1415161718192021Last
Id Label Status Status Modified Notation
G09 List unique namespaces used and count number of elements Quick edit Valid 2023-05-04 G09
G09.1 Check namespace is registered  Quick edit Valid 2023-05-04 G09.1
G10 The Attainment Pollutant  must be one of the following: SO2, O3, NO2, NOX, PM10, PM2.5, CO, Pb in PM10, Cd in PM10, Ni in PM10, As in PM10, BaP in PM10 Quick edit Valid 2023-05-04 G10
G100 INF and ALT thresholds - COUNT number zone-pollutant-target combination to match those in dataset B and dataset C for the same reporting Year Quick edit Valid 2023-05-19 G100
G11 Exceedance Description Base is only expected for the following pollutants: SO2, PM10, PM2.5, CO Quick edit Valid 2023-05-04 G11
G12 Exceedance Description Adjustment is only expected for the following pollutants: SO2, PM10, PM2.5, CO Quick edit Valid 2023-05-04 G12
G13 Attainment should link to a valid assessment regime with matching Pollutant and Objetive Type Quick edit Valid 2023-05-04 G13
G13b Attainment must link to a valid assessment regime with matching Pollutant and Protection Target Quick edit Valid 2023-05-04 G13b
G13c Attainment should link to a valid assessment regime with matching Pollutant/Objective Type/ReportingMetric/ProtectionTarget/ Quick edit Valid 2023-05-04 G13c
G14 COUNT number zone-pollutant-target combination to match those in dataset B and dataset C for the same reporting Year Quick edit Valid 2023-05-04 G14
G14b All the /aqd:AQD_AssessmentRegime reported under latest dataflow C must be xlinked once at one Attainment (with exception of /MO) Quick edit Valid 2023-05-04 G14b
G15 Must be a valid AQ Zone. Quick edit Valid 2023-05-04 G15
G16 The attainment(s) for PM2.5 AEI (both ECO & ERT) MUST not link to any specific zone. Quick edit Valid - experimental 2023-05-04 G16
G17 Linked zones must contain same pollutant as the Attainment Quick edit Valid 2023-05-04 G17
G18 Any attainment for LVmaxMOT should link to a zone with a time extension Quick edit Valid 2023-05-04 G18
G19 Objective Type must use one of the following: TV LV CL LVMOT LVmaxMOT INT ALT LTO ECO Quick edit Valid 2023-05-04 G19
G20 The Exceedence description must use an approved reporting metric, These are: Three consecutive hours in exceedance Annual mean / average , Winter Mean, Hours in exceedance in a calendar year, Days in exceedance in a calendar year, Days in exceedance averaged over 3 calendar years, Accumulated Ozone Exposure , Accumulated Ozone Exposure averaged over 5 years, Average Exposure Indicator Quick edit Valid 2023-05-04 G20
G21 The protection target must use the approved vocabulary Quick edit Valid 2023-05-04 G21
G22 Check and list any invalid combination of pollutant & environmental objective Quick edit Valid 2023-05-04 G22
G23 reserved Quick edit Deprecated 2023-05-04 G23
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?