I want to be able to run multiple scenarios in a typical ArcMap workflow. This will include making edits to feature classes, such as removing features, adding new features, or changing feature values in the attribute table.
Per scenario, I want to track these changes so that I can generate a report of what changes were made (what was added, removed, changed), as well as store those changes as a scenario (xml file?) that can be loaded in the future. This is where I think that definition queries can be used to some extent...
Is there a general setup for this type of workflow? The application that we have written in Python tests a single scenario and does not allow edits to the database. To test more than one scenario, a copy of the file geodatabase must be made before proceeding with further changes and re-testing the scenario outputs.
This is how I imagine the scenarios will be represented...
The user launches ArcMap and adds a feature from a prescribed file geodatabase.
|FID|NAME |TYPE | | 0|Metro|Commercial|
Here we have a feature with 1 object as the base scenario.
The user starts an editing session and adds an object.
|FID|NAME |TYPE | | 0|Metro |Commercial| | 1|NoFrills|Commercial|
Scenario: A has two objects. The delta change between the Base Scenario and A is one object.
What I would like to be able to do is keep track of what was added, removed or changed in a Scenario so that I can "load" a scenario and assess the delta change between them.
Also, because I know what is contained in the Base Scenario, I can store the FID values that will form the basis of my definition query. Scenario A will have a different set of FID values for its definition query.