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 41 to 60.First12345678Last
Id Label Status Status Modified Notation
B30 Enviromental Domain must conform to http://inspire.ec.europa.eu/codelist/MediaValue/[code] Quick edit Valid 2023-05-04 B30
B31 Legislation citation name must be “2011/850/EC”  Quick edit Valid 2023-05-04 B31
B32 Legislation citation date must be “2011-12-12”  Quick edit Valid 2023-05-04 B32
B33 Legislation citation line must be “http://rod.eionet.europa.eu/instruments/650”  Quick edit Valid 2023-05-04 B33
B34 Base level must conform to http://inspire.ec.europa.eu/codelist/LegislationLevelValue/[code] Quick edit Valid 2023-05-04 B34
B35 Zone code must be unique. The value may e equal the LocalId Quick edit Valid 2023-05-04 B35
B36 Population must be a value higher than zero Quick edit Valid 2023-05-04 B36
B37 Year in which the resident population was estimated must have the format yyyy Quick edit Valid 2023-05-04 B37
B38 The Area value must be a decimal number, greater than zero. Quick edit Valid 2023-05-04 B38
B39a Check for correct Pollutant/ProtectionTarget combination Quick edit Valid 2023-05-04 B39a
B39b Check if at least one of the expected Pollutant/ProtectionTarget combination(s) is provided in the delivery Quick edit Valid 2023-05-04 B39b
B39c Check and list if any individual zone with any duplicated Pollutant/ProtectionTarget combination  Quick edit Valid 2023-05-04 B39c
B40 ExtensionExemption accepted prior to 2015 deliveries Quick edit Valid 2023-05-04 B40
B41 Where AQTimeExemption is either NO2-1h, or NO2-annual, then NO2 and Protection Target Health must be present Quick edit Valid 2023-05-04 B41
B42 Where AQTimeExemption is either PM10-24h, or PM10-annual, then PM10 and Protection Target Health must be present. Quick edit Valid 2023-05-04 B42
B43 Where AQTimeExemption is C6H6-annual, then C6H6 and Protection Target Health must be present. Quick edit Valid 2023-05-04 B43
B45 Geometry should not be a hyperlink. If provided via shapefile, element aqd:shapefileLink need to be used Quick edit Valid 2023-05-04 B45
B46 Where a link is provided, it should refer to an existing and valid shape file in the same folder in the CDR as the XML is uploaded Quick edit Valid 2023-05-04 B46
B47 Zone type must be either Agglomeration or Non-agglomeration  Quick edit Valid 2023-05-04 B47
B48 Designation Period DATE must be provided in extended ISO format Quick edit Valid 2023-05-04 B48
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?