A citizen observatory campaign is defined as one particular usage of a citizen observatory to assess a concern by measuring a phenomenon or phenomena in a semi-structured way. A campaign is defined by a stakeholder by choosing the type of data that needs to be collected, defining the contextual constraints for gathering that data (time, area, number of participants, event typology, . . . ), and specifying the expected reporting outcomes (maps, graphs, written reports . . . ).

A campaign is used to assess a concern of citizens by measuring a certain phenomenon, for example: “Measure air pollution around Zaventem airport and express whether you are annoyed or unaffected by it”.

An example would be “Measure air pollution within 5km of Zaventem airport and express your appreciation of the situation (annoying or ok). We are only interested in measurements of participants who uploaded at least 10 measurements. A map showing where at least 5 citizens within 500m of each other had annoying experiences during the night should be produced.”.

A campaign consists of 5 steps: it is 1) defined and 2) deployed by stakeholders, 3) enacted by citizens, 4) terminates successfully, and finally results in 5) analysed data.

After defining a campaign, the campaign is deployed, where the citizen observatory generates the necessary web services and apps to allow potential participants to obtain the required mobile software and instructions. As soon as the campaign is deployed it can be enacted, i.e., the citizen observatory orchestrates data collection so that the campaign terminates successfully, by guaranteeing that campaign constraints are upheld, appropriate data is collected in time, and guiding campaign designers and participants in carrying out remedial actions if this is not the case. After the campaign terminates, it needs to be analysed, where reports are produced, interactively or not, and raw data is turned into knowledge by post-processing and policy-supporting tools.