The proposals must address the organisation of a technological challenge on multi-source satellite image analysis based on the preliminary evaluation plan provided as part of the call document (see Annex 4b). This includes the collection, annotation and distribution of data, and the writing of the evaluation plans. The proposals must also address the possibility to involve representative defence users testing the demonstrators produced by the participating teams and providing feedback.

The following use cases should be considered when elaborating the evaluation plans:

Target analysis: vehicle functional status recognition, target identification and early target detection, classification and recognition.
Monitoring and tracking: change in detection, camps, oil tank volume estimation, non-linear tracking of targets, routes.
Searching: disturbed terrain detection, vehicle trails or moving targets detection, camouflage and material detection, minefield detection.
Mapping: terrain modelling (ground, water, roads, constructions), trafficability analysis and obstacle detection, coastal bathymetry for shallow waters.
Damage assessment: battle damage assessment, detection of climate/environment disaster-affected areas impacting defence operations.
Both optical and radar images must be considered. They may include the following:

Optical

• Standard (i.e., in the visible part of the EM spectrum) panchromatic and/or multispectral images with various spatial resolutions below or above 1 metre depending on the selected use-cases, based on commercial, dual-use or defence systems.
• Hyperspectral images with various spatial resolutions below 50m, based on scientific, commercial, dual-use or defence systems.
• Infrared images.
• This may include multi-view stereo or video modes where available.

Radar

• X-band SAR images (amplitude and phase, different polarisation) with various resolutions below or above 1 metre depending on the selected use-cases, based on commercial, dual-use or defence systems.
• C or S-band SAR images.
• P or L-band SAR images.
• The use of optical and radar aerial imagery may also be considered, in particular to test systems on high-resolution images for certain types of images (e.g. hyperspectral or infrared, simulation of higher resolution images).

Metadata that would normally be used in operational scenarios should be provided.

The actual types of images and metadata to be used for the challenge should be described in the proposals.

Accordingly, the proposals must cover at least the following tasks as part of mandatory activities:

Integrating knowledge:

• Setting up of the infrastructures for testing satellite image analysis systems in the framework of the technological challenge.
• Production of data annotation guidelines, collection and annotation of data, quality assessment, distribution and curation of databases.

Organisation of the evaluation campaigns, and in particular:

• Coordination of the exchanges with other stakeholders on the data annotation guidelines and evaluation plans, and elaboration of these documents;
• Management of the experimental test campaigns, including the objective measurements of the performances of the technological modules submitted to the tests by the participating teams according to the protocols and metrics described in the evaluation plans;
• Organisation of the debriefing workshops.

The proposals should include clear descriptions of the proposed criteria to assess work package completion. Criteria should include the production of detailed evaluation plans agreed upon by all stakeholders, the production of the annotated databases needed for the evaluations, the production of measurements for all systems submitted to the tests by the participating teams following these plans, and the organisation of the needed events.

Functional requirements

The proposed solutions should enable the measurement of the performances of satellite image analysis systems according to detailed evaluation plans based on the preliminary evaluation plan provided as part of this call document (see Annex 4b). Key aspects of the foreseen detailed evaluation plans and associated data management should be described in the proposals.

Proposals should in particular describe:

• the detailed use cases to be addressed and the nature and size of image data to collect;
• the nature and volume of data annotation to be produced, the order of magnitude of the number of different semantic classes, object types and characteristics considered for annotations, and the granularity of these classes with examples;
• a framework for trusted sharing of data during the challenge and beyond;
• a detailed plan of the test campaigns and an overall timeline/Gantt chart of the challenge;
• the evaluation procedures (rules and tools to implement the metrics) and significance tests to be performed on measurements.

A user board consisting of representative defence users should be set up and involved in the preparation of the evaluation plans and of the data. Data should be representative of use cases of interest for defence. Proposals should describe the foreseen efforts from users to test demonstrators and provide feedback.

Data may be annotated in a semi-automatic way. Agreements may be sought with participants to use automatic tools developed by them. All annotations should be manually checked. To assess the relevance and accuracy of the data annotations, at least part of the data should be annotated by two independent annotators. The two sets of annotations should be compared to each other using the same metrics as for the evaluation of system outputs. An analysis of this inter-annotator agreement should be presented during the evaluation campaign workshops.

During the challenge, a detailed evaluation plan should be prepared for each evaluation campaign. Drafts of these detailed evaluation plans should be submitted for discussion to the participating teams, early enough to take into account feedback and leave time for system development before the actual test campaigns. Any evolution of the evaluation plans should take into account several factors: technical possibilities and cost, scientific relevance of the measurement, and representativeness of the metrics and protocols with respect to military needs. The justification of any change that is not subject to a consensus should be documented.

The user board and the participating teams should be involved in the steering of the challenge. Proposals should include a clear description of the foreseen governance and decision-making processes.