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 321 to 340.First1314151617181920Last
Id Label Status Status Modified Notation
Eb44 When results are provided via an external file, the XML must include an om:parameter with the modelprojection via EEA vocabulary, using SRID number directly or one of the following references: http://dd.eionet.europa.eu/vocabulary/common/epsg/, https://spatialreference.org/ref/epsg/ or https://epsg.io/ Quick edit Valid 2023-05-04 Eb44
Eb45 When results are provided via an external file, the XML must include an om:parameter including the modelresolution via EEA vocabulary Quick edit Valid 2023-05-04 Eb45
Eb46 When results are provided via an external file (compressed in a zip file), the compressed file can only contain one external result (i.e only one shape file for each zip file) Quick edit Valid 2023-05-04 Eb46
Eb47 When results are provided via an external file, all reported files (*.zip, *.shp ; *.tiff, *.tif, *.asc) must be referenced via gml:fileReference Quick edit Valid 2023-05-04 Eb47
Eb48 When results are provided via an external file, definition of quantity must be provided and must match EEA vocabulary of aggregation processes. Quick edit Valid 2023-05-04 Eb48
Eb49 When results are provided via an external file, the combinations of file#variable declared in XML must be unique, and the variables declared in XML after a # should be unique. QC should return WARNING if the variables are not unique. QC should return BLOCKER if the combinations of file#variable are not unique. Quick edit Valid 2023-05-04 Eb49
Eb50a Each E1b observation must point to unique combination of formed by model + procedure + observedProperty + featureOfInterest + definition. Quick edit Valid 2023-05-04 Eb50a
Eb51 Attribute names specified in XML with url of external file must correspond univocally with the attribute names which can be found in dbf file of ESRI shapefile. Quick edit Valid 2023-05-04 Eb51
Eb52 Declaration of aggregation process in E1b must match with reporting metric in C. Quick edit Valid 2023-05-04 Eb52
Eb53 Values provided within the data array must be interpretable and logically possible. Quick edit Valid 2023-05-04 Eb53
Eb54 Combination of pollutant and aggregation process must match the one allowed in https://dd.eionet.europa.eu/vocabulary/aq/aggregationprocess Quick edit Valid 2023-05-04 Eb54
G0 Checks if this delivery is new or an update (on same reporting year) Quick edit Valid 2023-05-04 G0
G01 Number of Attainments reported Quick edit Valid 2023-05-04 G01
G02 Number of new Attainments compared to previous report. ERROR will be returned if XML is a new delivery and localId are not new compared to previous deliveries Quick edit Valid 2023-05-04 G02
G03 Number of existing Attainment 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 G03
G04 List of unique identifier information for all attainment records. Blocker if no attainments Quick edit Valid 2023-05-04 G04
G05 List number of final exceedances (TRUE) Quick edit Valid 2023-05-04 G05
G06 Check and provide a list of those attainment records with a time extension Quick edit Valid 2023-05-04 G06
G07 All gml ID attributes shall have unique code Quick edit Valid 2023-05-04 G07
G08 Local Id must be unique for the attainment records Quick edit Valid 2023-05-04 G08
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?