Onboarding - Remote Sensing
      Back to home
      1. Knowledge Base
      2. Onboarding
      3. Onboarding - Remote Sensing

      Remote Sensing Troubleshooting

      Guide to finding and correcting common problems that occur when loaded air intel products into S3 for viewing in Intterra's Airborne Intel Tool

      References: 

      Airborne/Satellite Intel Tool

      Airborne Intel Mission Editing

      Remote Sensing Onboarding/ICD document

      Identifying the Problem 

      When products loaded into S3 don't display as expected in Intterra's Airborne Intel Tool, it is due to missing files, incorrect file naming, and/or invalid file formats. Below is a description of common problems, things to check, and potential solutions. 

      Missing products 

      Determine if the issue is most likely file naming or file format.  

      • If the product is not listed in the mission's product list in the air intel tool, the issue is likely file naming.  Use view access to S3 to diagnose further.
        • Did the file successfully load to S3?  Confirm that the file is present in S3.
        • Is there a problem with the file name? See the ICD doc references above. Here are the most common issues: 
          • Check for illegal characters in the mission name.  Only letters and '-' are permitted.  
          • Is there a Product Description included the end of the name? This is not currently supported for some video and image files. 
          • Any other issues with illegal characters, incorrect naming? 
      • If the product displays in the mission's product list but not on the map, the problem is most likely a file format issue. Use view access to S3 to diagnose further.
        • Determine if the file failed to process in Intterra?  Files that processes successfully will have additional 'Intterra-processed' files in S3 with the same mission name and date/time.  If there are no additional files, then there is likely a problem with the video, imagery or tactically format that caused processing to fail.  Confirm that is meets the format requirements in the ICD. 
      • If the product displays in the mission's product list but not on the map, the problem is most likely a file format issue. Use view access to S3 to diagnose further. Confirm that files meet the format requirements in the ICD. 
          • Tactical .kml's are the most common problem we see.   Files exported from ERSI or even Google Earth can contain code that causes the file to not show in the map in Intterra.  To confirm, use a conversion process like https://mygeodata.cloud/converter/kml-to-shp and choose kml as the output format.  This usually clean up issues that prevent processing. Reloading the file (into S3/airbornetesting for Intterra) will confirm if that was the issue.
          • Video
            • If a .ts file was provided, confirm that there is there an Intterra-generated .kml file with the same mission name/date in S3?  If not, the process failed before being able to determine a location.
            • If an .mp4 was provided, confirm the that required .kml was provided as well.
          • Imagery  
            • If a .png file was provide, confirm the that required .png.aux.xml with the same mission name/date was provided S3 as well AND that the timestamp shows that the .png.aux.xml arrived first. 
            • If a .tif file was provide, confirm the that the Intterra generated .kmz file with the same mission name/date is in S3? If not, the process failed before being able to determine a location.

        Zoom to mission or product not working in the tool

        This problem is a direct of no location data for a file.  See above.

        Multiple Missions incorrectly listed in mission list

        One mission is intended, but the mission name shows multiple times in the mission list.
        • There is a problem with the file name(s).  When using Naming Convention Option A, the date/time stamp represents the mission date and time, not the product.  Every unique combination of mission name and data/time will generate a new mission in the tool.    See the ICD doc referenced above.

        Mission Date and Time are incorrect

        The mission date is showing for the previous day or much earlier than the flight.  

        • When using Naming Convention B, a mission designator file determines mission's date and time.  The file is REQUIRED if using Naming Convention Option B and subsequent missions with the same mission name with be conducted within 24 hours.  If no file is provided, Intterra uses 00:00Z as a failsafe.  I quick way to check to see if this is the issue is to mouseover the mission name in the list and see if the time is 00:00UTC.  

        Correcting the Problem

        Once the problem is identified, reloading the files into S3 with the correct name and/or format should make the products available for the users.   

        NOTE: New files will not over-write the old ones with the same name.  If the files have the same mission and date/time stamp, you will need to provide a new name.  For Naming Convention Option A, this can be a slight change to the 9-digit series number.  This is required even if the file is removed form S3, since files are processed in a different location. occurs. 

        To clean up missions and products as seen in the air intel tool, users with edit access to the tool can follow this steps in this Airborne Intel Mission Editing doc.  

        The only way to correct the product count for a mission is to create a new mission, load all the updated files, and then delete the old mission per the above step.

        Contact Support

        If you are unable to identify or correct the problem, contact support@intterragroup.com. Its very helpful to clearly identify the file that is not processing.