| Description | Scottish Flood Defence Asset Database Final Report |
|---|
| ISBN | (Web Only) |
|---|
| Official Print Publication Date | |
|---|
| Website Publication Date | August 20, 2007 |
|---|
Contents |
Listen
APPENDIX D: DATABASE STRUCTURE
Data collated throughout this project for example from the paper files, on-site with GISmo a (handheld PC based GIS application for asset identification, assessments and data collection) and from the hydraulic modelling has been incorporated into a final Asset Database.
The final Asset Database has been developed as a relational database. Relational databases are the most widely developed databases today due to their robustness and flexibility. A relational database is a database built of tables with relationships between the tables within the database. For example, in the Asset database a wall table is linked by a relationship to the Flood Prevention Scheme table because a wall defence is part of a Flood Prevention Scheme.
Relations between the tables in a relational database help the developer and database administrator ensure that the data entered into the database is correct. For example the integrity of the database is maintained when a defence such as a wall is entered into a database and the administrator must identify the scheme that the wall belongs to. If the wall is entered without being linked to a scheme, the database will bring up an error message.
The relations between the tables in the database are maintained using primary and foreign keys. A primary key is a field in the database with an ID which identifies the piece of data in that row as unique. A foreign key is a primary key of one table placed in another table. The relations between the tables in the database are maintained between the primary and foreign keys in the tables. For example, a wall table will have a primary key identifying that wall and in this case it will have a foreign key of the Flood Prevention Scheme ID which identifies which scheme the wall belongs to.
Section D.2 Appendix D details the table and field definitions of the tables in the final Asset Database.
Table 12-1: Information stored in the Asset Database
Table | Description |
Flood Prevention Scheme | Flood Prevention Scheme in Scotland Promoted under the Flood Prevention (Scotland) Act 1961 |
Flood Defence Assets | Flood Defence Assets that make up a Flood Prevention Scheme for example walls and embankments |
local authority Boundary | The Boundaries of the 32 local authorities in Scotland |
Faults | Faults associated with a Flood Prevention Scheme or a Flood Defence Asset recorded during the condition assessment. |
Photographs | Photographs of a Flood Prevention Scheme recorded during the condition assessment. |
Historic Flood Outlines | Historic Flood Outlines digitised from the original paper copy |
Modelled Flood Outlines | Modelled Flood Outline created during the Hydraulic Modelling |
Drawings | The location of drawings related to the Flood Prevention Schemes |
Hydrology | Hydrology of a Flood Prevention Scheme |
Condition Assessment Notes | Administration notes following the condition assessment |
Condition Assessment Findings | Findings noted during the condition assessment |
Condition Assessment Variations and Additions | Variations and additions from the original Flood Prevention Order noted during the condition assessment |
Surveyed Cross Sections | Cross sections surveyed prior to the hydraulic modelling. |
Note:
In the Asset database, both the location and associated information (attribute data) is stored for all the types of tables detailed above, apart from the Drawings and the Condition Assessment Notes tables for which only the attribute data, and not a geographic location, is stored.
Contents |