GEOSS Banner

4.3.2 Publishing Legacy Data Sets Using an Import Tool

Table of contents
No headers

<<Prev T.O.C

This section describes how the import of sensor data archives available as comma-separated values (CSV) files can be achieved. The tool described in this section can be downloaded here:

A user guide for this tool is available on the web, as well:

The remainder of this section provides a step-by-step guide how the data import tool can be used.

Please note: At the moment this tool has only been tested with the 52°North SOS implementation. If you are aware of any other transactional SOS implementations please report your experiences to the devleopers of this tool so that compatibility with other implementations can be achieved as well.


Step 1:

In the first step, the user selects the CSV file which contains the observation data set that shall be published through a OGC Sensor Observation Service (SOS).



Step 2:

The general settings for parsing the file are set (column separator, comment indicator and text qualifier).



Step 3:

The content of the different columns needs to be defined. Depending on the type of data contained in a column further information needs to be set by the user. For example:

  • If a column contains data and time, the according format (e.g. dd/MM/yy HH:mm) needs to be described.
  • If a column contains observed values the data type (e.g. numeric, Boolean, category) need to be set and if applicable also thousands and decimal separators.

Specifying the content of a "Date & Time" column, in this example the tool assists the user by notifying about parsing problems of one date (the heading of the column which of course cannot be parsed):



Specifying the content of a "Measured Value" column:



Step 4:

If multiple columns with the same content type are present in a CSV file, according associations must be created, for example:

  • If there are multiple timestamp columns it must be defined which time stamp column belongs to which measured value column.
  • If there are multiple unit of measurement columns it must be defined which unit of measurement column belongs to which measured value column.

Creating associations between measured values and units of measurements:



Creating associations between measured values and time stamps:



Step 5:

If there is missing metadata for a time stamp column (e.g. time zone, provided as UTC offset) the user has to provide this information in this step.



Step 6:

In case certain metadata elements are missing within the positions of sensor observations, this step can be used for inserting the according information (e.g. height, EPSG code of the reference system).



Step 7:

If no time stamps at all are provided for the measured data, the following menu requests the according input from the user.



Step 8:

If the CSV file does not contain information about the observed property (the phenomenon which has been observed by the sensor, e.g. air temperature), this can be inserted by the user as shown below.



Step 9:

Also, if no sensor identifier is available in the CSV file then it can be described manually:



Step 10:

In case the CSV file doesn’t provide any spatial reference for the measured values, the menu below offers the possibility to enter the position manually (in a later version a map based selection of the sensor location will be included).



Step 11:

After all necessary data and metadata elements are entered, the SOS instance to which the sensor observations shall be published must be entered. Please refer to the requirements section for learning more which SOS implementations you can use for installing a SOS you can use for publishing your data.



Step 12:

Finally, the publication process is started and the user is informed about the progress.



Step 13:

After the data have been sent to the SOS the user is informed if there were any errors. A log file is accessible to investigate these problems.


<<Prev T.O.C


Files (0)

You must login to post a comment.