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 141 to 160.First4567891011Last
Id Label Status Status Modified Notation
D16 List unique namespaces used and count number of Stations used. Blocker will be returned if namespace is not unique. Quick edit Valid 2023-05-04 D16
D16.1 Check namespace is registered  Quick edit Valid 2023-05-04 D16.1
D17 Station name must be provided Quick edit Valid 2023-05-04 D17
D18 Station must belong to a network Quick edit Valid 2023-05-04 D18
D19 Must conform to a recognised media value. These are: Air, Biota, Landscape, Sediment, Soil/Ground, Waste and Water. Quick edit Valid 2023-05-04 D19
D1bCrossCheck Cross checks with other data-flows Quick edit Valid 2023-05-04 D1bCrossCheck
D20 The coordinate reference system for the stations must be defined with a correct uniform resource name Quick edit Valid 2023-05-04 D20
D21 The location of the station must be correctly reported and within the countries' bounding box Quick edit Valid 2023-05-04 D21
D23 Check if the operational period for the station is within the network it belongs to. Quick edit Valid 2023-05-04 D23
D24 Total number of operational Stations Quick edit Valid 2023-05-04 D24
D25 Station altitude must be provided in meters according to vocabulary and between -10 to 5700 meters Quick edit Valid 2023-05-04 D25
D26 Station code must be unique, starting with ISO2-country code Quick edit Valid 2023-05-04 D26
D27 Station Meterological Parameters must conform to the standard "Climate and Forecast Standard"  Subset of GRIB or the Meteo parameter list eionet data dictionary Quick edit Valid 2023-05-04 D27
D28 Must conform to a recognised Station Classification from the eionet data dictionary. These are: Rural, Rural-Nearcity, Rural-Regional, Rural-Remote, Suburban, Urban Quick edit Valid 2023-05-04 D28
D29 Must use a recognised Local description from the eionet data dictionary. These are: Canyon, Detached, Elevated and Open. Quick edit Valid 2023-05-04 D29
D30 Must use a recognised Regional descriptor: Alpine, Base, Basin-Hilly, Coast-Mount,  Coast-Plane, Hilly, Mount, Mount-Slope, Plane, Valley-Hilly and Valley-Mount. Quick edit Valid 2023-05-04 D30
D31 Sampling Point local Id must be unique Quick edit Valid 2023-05-04 D31
D32 List unique namespaces used and count number of SamplingPoint used. Quick edit Valid 2023-05-04 D32
D32.1 Check namespace is registered  Quick edit Valid 2023-05-04 D32.1
D33 Must conform to the code 'air' in the Media codelist in the Inspire registry  Quick edit Valid 2023-05-04 D33
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?