| Process 4 Saving upgraded spatial data back to GIS / IT Environment |
| This is the second Process that needs to be written by the client. This
process is site specific and would normally display, edit and check the
data back into the corporate GIS environment. This may mean: • The upgraded data is held as an additional version of the original features • The upgraded data is held as an additional theme • The GIS may need some development to show the upgraded themes with a predefined legend • Additional drivers may be needed All the local business rules for data integrity and connectivity come into play at this point. This may mean: One can expect any legacy data issues to be detected against more recent business rules. This may mean: Occasionally some features (less than 0.5%) can be expected to have an adjustment error that needs to be fixed manually. This may mean: This may be an iterative process due to local data integrity rules and
spatial data connectivity rules. Some of these rules may only be available
during the check-in process, and if any rules are broken an error message
is returned and the data rolled back out of the database. Hence errors
can only be fixed as reported, making the process iterative in nature. |