GOBI WebUI Configuration
Last updated
Last updated
GOBI WebUI software for GOBI gives users the ability to fully configure GOBI sensors for optimal data collection needs.
GOBI WebUI landing page gives users the ability to manage mission names, see capture status, altitude estimate from GNSS, notify if the capture trigger is ready, and start the mission.
Users should check the following:
Name the mission accordingly. By default, mission name will have the UTC date and time.
Check that paylod status is in Standby mode until the mission has started.
Check that altitude estimates and standard deviation are updating properly.
Capture trigger should turn green when altitude estimate standard deviation is less than ± 1m
Disk Settings show users the used and available space on disk, allow users to clear all sensor data (GNSS, LiDAR and VNIR), download logs, and clear logs.
Managing individual mission data will be coming in a firmware update soon. In the meantime, Clear Sensor Data will clear all GNSS, LiDAR, and VNIR data. Be careful and ensure data is backed up prior to clearing.
The VNIR setup page allows users to setup the necessary parameters for VNIR collection.
Polygon - Upload the HSI capture polygon (KML or TXT file)
Gain - Set the gain mode; low, normal, or high, depending on the available solar energy and saturation requirements for the collection
Exposure Time - Set the exposure time, dependent on solar energy and saturation requirements for the collection
Frame Period - Set the frame period, a function of altitude and flight speed
Flight Calculator - Depicted in the next section, allows frame period calculation for given flight parameters
Collect Dark Reference - Collects dark reference to determine internal sensor noise; Used for accurate raw -> radiance conversion
The flight calculator allows users to input their Flying Height and Flight Speed to calculate the necessary Frame Period for optimal collection.
Flight Calculator also introduces a parameter for inducing oversampling, determined as a percentage of Frame Period. In general, 10-20% oversampling is sufficient for minimizing VNIR data gaps in the forward direction in the event of general aircraft instability or excess wind.
