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 301 to 320.First1213141516171819Last
Id Label Status Status Modified Notation
Eb21 Check valid TextEncoding (decimalSeparator="." tokenSeparator=“”SEMICOLON”” blockSeparator="@@") Quick edit Valid 2023-05-04 Eb21
Eb22 The order of the fields within individual data blocks must correspond to the order described. Quick edit Valid 2023-05-04 Eb22
Eb23 The count of values provided for observation should match the count declared. Quick edit Valid 2023-05-04 Eb23
Eb24 Difference between endTime & startTime must correspond to the definition under <swe:field name="Value"><swe:Quantity definition=> Quick edit Valid 2023-05-04 Eb24
Eb25 The temporal envelopes of the swe:values (reported via starTime and EndTime) shall reconcile with ./om:phenomenonTime/gml:TimePeriod/gml:beginPosition Quick edit Valid 2023-05-04 Eb25
Eb26 The combination of Model, ModelProcess, ModelArea (optional) and Pollutant must be valid compared to Assessment Methods (D1b), yearly specific, reported Quick edit Valid 2023-05-04 Eb26
Eb27 Check that all values (between @@) include as many fields as declared under swe:DataRecord Quick edit Valid 2023-05-04 Eb27
Eb28 The data array should not end with "@@". Please note that @@ is a block separator. Quick edit Valid 2023-05-04 Eb28
Eb29 Check for unexpected spaces  around all values (between comma separator) under swe:values Quick edit Valid 2023-05-04 Eb29
Eb31 Check for date overlaps between consecutive data blocks within swe:values Quick edit Valid 2023-05-04 Eb31
Eb32 Check that all data submitted via CDR has been fully verified (flag 1) Quick edit Valid 2023-05-04 Eb32
Eb35 rangeParameters must be provided when reporting ascii grids - shape files or GeoTiff Quick edit Valid 2023-05-04 Eb35
Eb36 Aggregation process of the results must be provided and must match EEA vocabulary Quick edit Valid 2023-05-04 Eb36
Eb37 A user-friendly label should be provided Quick edit Valid 2023-05-04 Eb37
Eb38 A clear description of the results provided MUST be provided Quick edit Valid 2023-05-04 Eb38
Eb39 Unit of the results must be provided and must match EEA vocabulary Quick edit Valid 2023-05-04 Eb39
Eb40 Check if data is provided using the recommended unit according to vocabulary  Quick edit Valid 2023-05-04 Eb40
Eb41 When reporting results using ASCII grid shape file or GeoTiff a reference must be provided to the result file Quick edit Valid 2023-05-04 Eb41
Eb42 The result file (*.zip, *.shp ; *.tiff, *.asc) must follow this format: A valid cdr URL matching location of XML + File including extension + Variable using a # (e.g. #no2) Quick edit Valid 2023-05-04 Eb42
Eb43 When results are provided via an external file and the external file is ESRI shapefile, it must include the *.prj file Quick edit Valid 2023-05-04 Eb43
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?