General

This import is available since 2023.02. Only scalars are supported.

The GOES (Geostationary Operational Environmental Satellite) server import type allows you to retrieve data from the Local Readout Ground Stations (LRGS).

See more about the data format on the page dedicated to the related import type GOES. 

The import uses the lrgs library to connect to the specified server and collect the data. The specified view period is passed as argument to the server which interprets it as the period in which data has been received from the stations (which happens once per hour), and not as the period in which data has been measured. For example: if data is received every hour at 51 past the hour, with measurement at 00, 15, 30 and 45, and the configured start and end times are 10:30 to 11:30 on the same day, the data imported will be only the one received at 10:51, i.e. the data measured between 10:45 and 08:00.


Configuration example

To import GOES data directly from the server, use the following import configuration.
Import.xml

<import>
     <general>
         <importType>GOES_server</importType>
         <serverUrl>https://cdadata.wcda.noaa.gov/</serverUrl>
         <user>username</user>
         <password>dummy_password</password>
         <relativeViewPeriod unit="day" start="-1" end="0" startOverrulable="true"/>
         <idMapId>import_mapping</idMapId>
     </general>
     <timeSeriesSet>
         <moduleInstanceId>my_module_Id</moduleInstanceId>
         <valueType>scalar</valueType>
         <parameterId>H.m</parameterId>
         <locationId>Delft</locationId>
         <timeSeriesType>external historical</timeSeriesType>
         <timeStep unit="minute" multiplier="15"/>
         <readWriteMode>add originals</readWriteMode>
     </timeSeriesSet>
</import>

The imported messages always contain slots for 8 parameters, which are provided in a fixed order.

The import_mapping configuration for these 8 parameters is as follow. Note that the external names of the parameters should not be changed as they actually refer to the hardcoded parameter names. Data is requested based on the external IDs. 

<idMap>
    <location external="518FF43C" internal="Delft"/>    

    <parameter internal="H.m" external="Main Stage"/>
    <parameter internal="SecStage" external="Secondary Stage"/>
    <parameter internal="Precipitation" external="Rainfall"/>
    <parameter internal="Temperature" external="AirTemp"/>
    <parameter internal="Humidity" external="RH"/>
    <parameter internal="InternalHumidity" external="Internal RH"/>
    <parameter internal="RepeaterBattery" external="Repeater Battery"/>
    <parameter internal="MainBattery" external="Main Battery"/>
</idMap>

External ID mapping is needed if the 

  • No labels

Disclaimer