Data can be exported from Outpost Central or Wildeye through several available export options:
The FTP, email and Dropbox exports are sometimes referred to as "Push" exports where Outpost Central/Wildeye server pushes the data out on a subscribed time or schedule. The REST interface is sometimes referred to as a "Pull" interface where customer server requests and receives data from the Outpost Central database through the REST interface.
Any inputs of a Site in the Outpost Central / Wildeye system can be exported including hardware System inputs such as battery and signal data (see Setting Inputs for more details on logger inputs). Exports can be grouped by sub-clients or by groups.
Push exports files in CSV (Comma-separated Values) format; REST interface exports files in XML format.
- See Setting up Data Exports for more details on Push exports
- See REST Interface for more details on Pull exports
There a number of issues for developers to consider when using the REST interface to request data from the Outpost Central / Wildeye platform. Here is a list of important considerations:
- Number of Data Points per request
- Time Alignment
- Export Back Period
Number of Data Points in the Export
The number of data points contained in an export period for the site input data can vary according to several factors. It is therefore important to build tolerance into the data processing to allow for this.
- Change of Outpost/Wildeye logging frequency. An Outpost/Wildeye logger comes with a typical 15 min logging frequency which may be updated. For example, when a logger input logging frequency is increased from 96 reads (15 min logging) to 288 reads in a 24-hour period (5 min logging), the change will only occur the next time the logger connects with Outpost Central / Wildeye server at it's prescribed dial schedule. This may result in an increase of the data points part-way through an export period.
- Magnet activation. An Outpost / Wildeye can be activated via a magnet or TEST button which will force an immediate sample of all input channels. This may result in extra data-point per input for each instance of a magnet activation.
- Online or Offline. An Outpost / Wildeye is powered up or down. This may result in reading changes through an export period on the day of the power transition.
Raw data points logged by Outpost hardware are normally time aligned to the nearest logical time boundary. For example 15-minute logging should have raw data logged at hh:mm:ss
Exact time alignment cannot be guaranteed and may drift. Time drifts can be caused by:
- Inaccurate onboard real-time clock (RTC) on the Outpost logger which causes slight drifts daily. RTC is automatically synchronized during the logger connection with Outpost Central server. This synchronization can result in time offset affecting the data points nearest to the time of synchronization.
- Cellular Network Time Synchronization (NITZ) time correction can result in a few seconds of time offset to a data point.
- Hardware processing limitations of some logger hardware may take several seconds per input to sample. If 2 or more inputs are configured to log at the same time, the inputs will be offset according to when the reads occur on the hardware.
Export period of 24-hours is typically set for Push exports. This can be changed using the Days in Export field in the Site Data Export if required to increase export period beyond 24-hours.
Export period via REST interface can be dynamic by checking the date-time of the last successfully imported data point and requesting for data to that date-time point. However, it is more effective to request data points for a fixed, overlapping period.