Defining AI Layer and Scenarios

Go to PROJECT MANAGEMENT → AOI WIZARD.

To define an AI layer, select it in the Layer combo and the correspondent Aoi ID.

Note: Output layers cannot be defined as AI layer.

To locate specific geometries in the AI layer for scenario composition click on the icon and open the search interface.


Property: select the reference attribute.

Operator: select the operation type to execute in the filter.

Value: the user can choose to select by the attribute itself (property) or enter one specific category of the attribute (value).

Click on the icon to add the filter condition. To remove a specific filter condition from the list click on the icon beside of it.

To clean all the filter condition list click on the icon .


The AOI List shows the geometries in the layer selected in the AI list. When using the Search filter, this list shows only the geometries that satisfy the search condition.

Once the desired geometry is found, it is necessary to assign a date to it, composing the scenario. This date must identify when the data to be worked was observed. In the following example, the selected geometry was the boundary of the c_pret=AA row 12 and assigned date must be 03/03/2016, since this is the date of acquisition of this satellite image.

Select the located polygon by clicking on it in the table, type the date and click on the icon to assign the date to the geometry.

The assignment of a date to this geometry establishes the creation of a scenario. It is possible to create many scenarios for the same geometry by assigning different dates to it.

Note: Once a geometry has a View Date, it will not be possible to remove or edit this geometry.

Click on Next button. The wizard goes to the next step and shows in its upper part the list of all scenarios inserted in the database.


Find in this list the desired scenario and click on it in the list to select it. Is is possible to select more than one at a time. It is necessary to choose in this list the scenario to be worked in order to associate them with their respective projects in the next step.

This scenario list grows as the project is executed. When needed, use the Filter to locate the desired scenarios. It is possible to order the result by clicking on the title of the desired column.

If no filter is informed, then all scenarios will be shown.

Note: About this part of the interface: the column id is the scenario identification generated when a view_date is inserted; the column ai_geometry_id is the link column between attributes and geometries tables of the AI layer; the view_date is the date in which the satellite took the picture; the inclusion_date is the date in which the view_date was inserted in the database through the step before of this interface; the ai_layer is the name of the AI layer used in this scenario.

Select the scenarios to add to the project and click on the icon .

A scenario may be added to many projects.

Click on the Finish button to conclude the procedure and close the interface.

Refer to page 4 for instructions on the use of the Locked check box.

Locking a Scenario

Locking a scenario prevents it from being used in the vectorial edition. This is possible given that in order for Operator users to execute edition, they must create and activate a process for each scenario to be worked. It is not possible to create a new process with a locked scenario; also it is not possible to activate an already existing process for locked scenarios.

Scenario lock is effective only for the selected project. That way it is possible to have the same scenario enabled in a project and blocked in another one.

To lock a scenario, follow the interface until the last step, where the association between scenarios and projects is made, without executing any selection of the previous steps.

Select the desired project in the Project field.


Next, select the scenario to be locked in the bottom list and check in the Locked box.. In the example above, the single existing scenario of the LANDUSE project was locked.

Note: Locking scenarios prevents the current vectorial edition only after the users have closed their respective processes. If a user does not close his process, he can continue with the edition. Therefore, it is necessary that the Administrator asks users to end their processes.