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 481 to 500.First2122232425262728Last
Id Label Status Status Modified Notation
I27 Road Length attribute must be in kilometers (use http://dd.eionet.europa.eu/vocabulary/uom/length/km). Quick edit Valid 2023-05-04 I27
I29 A link to the exceeding SamplingPoint(s) and/or Model(s) must be provided [at least one]. Quick edit Valid 2023-05-04 I29
I3 Number of existing Plans compared to previous report. ERROR will be returned if XML is an update and ALL localId (100%) are different to previous delivery (for the same YEAR). Quick edit Valid 2023-05-04 I3
I30 If SamplingPoint(s) and/or Model(s) are provided these must be valid. Quick edit Valid 2023-05-04 I30
I31 The models referenced here must be found in the Attainment document (dataflow G). The following models do not appear in the Attainment documents deliver for this reporting year. Quick edit Valid 2023-05-04 I31
I32 The link to sampling points referenced here must be found in the Attainment document (dataflow G). The following sampling points do not appear in the linked Attainment. Hint: do not xlink to station eiocode/localId Quick edit Valid 2023-05-04 I32
I33 Spatial extent or administrative unit may be provided. Quick edit Valid 2023-05-04 I33
I34 Information on surface area or road length shall be provided. Quick edit Valid 2023-05-04 I34
I35 If exceedance is TRUE: information on population exposed must be provided. Quick edit Valid 2023-05-04 I35
I37 Reference year for the population/exposure data in yyyy format. Quick edit Valid 2023-05-04 I37
I38 Exceedance reason must match vocabulary. Quick edit Valid 2023-05-04 I38
I39 If the pollutant is SO2 / PM10 / PM2.5 or CO, deduction assessment methods may be populated. Quick edit Valid 2023-05-04 I39
I4 List of unique identifier information for all Source Apportionments records. ERROR will be returned if no SA(s) are provided. Quick edit Valid 2023-05-04 I4
I40 If the pollutant is SO2 / PM10 / PM2.5 or CO, the aqd:adjustmentType MUST be either (fullyCorrected noneApplicable noneApplied) under aqd:deductionAssessmentMethod Quick edit Valid 2023-05-04 I40
I41 If the pollutant is SO2 / PM10 / PM2.5 or CO, a description of the assessment type is expected. Quick edit Valid 2023-05-04 I41
I42 If the pollutant is SO2 / PM10 / PM2.5 or CO, a link to the assessment method in D or D1b is required via xlink:href attribute. Quick edit Valid 2023-05-04 I42
I43 If the pollutant is NOT SO2 / PM10 / PM2.5 or CO, the following elements are not expected: assessmentType link to adjusting sampling point/model, assessmentTypeDescription, assessmentType. Quick edit Valid 2023-05-04 I43
I44 If the pollutant is SO2 / PM10 / PM2.5 or CO and deductionAssessmentMethod is populated, adjustmentType must be "fullyCorrected" (else "noneApplicable"). Quick edit Valid 2023-05-04 I44
I45 If the pollutant is SO2 / PM10 / PM2.5 or CO and deductionAssessmentMethod is populated, adjustmentSource must conform with vocabulary (else "noneApplicable"). Quick edit Valid 2023-05-04 I45
I7 All gml ID attributes shall have unique code. Quick edit Valid 2023-05-04 I7
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?