Integration of third party Remote Sensing systems with Intterra's Airborne Intel Tool provide near-real-time information to operations and partner agency personnel on wildfire and public safety events. The Airborne Intel Tool and the Remote Sensing systems have been designed to allow a user to monitor and receive intelligence from a Remote Sensing mission as well as to access data from previous missions.  A variety of video, imagery and vector 'tactical' products can be integrated.   

Here is an article describing the products, capability and use of the a Airborne Intel Tool.

A secure Amazon S3 file sharing system is used by Remote Sensing and Intterra to exchange data. The Amazon S3 system requires an authorization credential issued by Intterra for data exchange.  Credentials will be sent to the Remote Sensing provider by the Intterra account manager/Integrations specialist during their onboarding period.

Here is a detailed Remote Sensing Interface Control Document describing the Intterra/Remote Sensing Interface. RemoteSensing_ICD_26AUG2021.pdf
This version of the ICD includes July 2020 enhancements for - 
  • 'GSTOP' file naming convention - An Option B file naming convention that closely aligns with the GSTOP (GIS Standard Operating Procedures).  The file name passes through to products downloaded from Intterra's Airborne Intel Tool. 
  • Supports additional Vector product types - isolated heat, scatter heated, structure, Infrastructure, water source, and route. 
Here are sample products to provide examples. ICD_SampleProducts_27Aug2020.zip

NOTE:  The naming convention 'closely aligns' with GSTOP, but isn't identical since 1) we have options for  products that are not in GSTOP (structure, Infrastructure, water source, and route), 2) some GSTOP naming (not all) includes the agency/unit code - which is typically not known by the mission operators when they send it to us, and 3) GSTOP uses local time with no time zone designator, which is not suited for an aircraft that could be in multiple time zones in a single mission (so we used UTC and the file name timestamp includes a Z).  The goal was to get something close enough so that if it is placed on an ftp site, people will have some understanding of what it is.