Exploit imagery and geospatial collections at operational tempo.
GEOINT and ISR teams need to test how their own collection formats, metadata and processing loads behave on the hardware available to the analyst.
Describe the collection load
Provide approved raster, vector, terrain and sensor examples with coordinate systems, resolutions and acquisition metadata. Include a representative large collection and a problematic input. Confirm individual format support rather than assuming a named sensor family is sufficient.
Inspect the exploitation chain
GTK 2.0 combines ingest, normalisation, cataloguing, indexing and caching with analyst-controlled exploitation. Check that metadata and source context survive each stage. Review assisted outputs and rejected detections with the analyst who will use them.
Evaluate local availability
A disconnected test needs installed data, models, caches and dependencies. Establish which workflows remain available when the enterprise network is removed. Confirm storage capacity, update arrangements and output handling for the selected workstation or team profile.
Questions for an evaluation
Which formats are accepted without conversion? What is lost during normalisation? Can an analyst identify the source behind an output? How are results exported to the receiving system? Measure the agreed workload and document limits without inventing throughput or accuracy targets.