Future Enhancements

Phases beyond the current model should consider integrating more feature classes and conversion from personal to mulitiuser Geodatabase in ArcSDE. This is possible and would be relatively easy .

Many-to-many relationships should be link parcels in the cadastral layer to other feature layers and attribute tables that were not included in the current project. A many-to-many relationship must be modeled using an intermediary relationship class that holds data values necessary to link the data tables together. Populating the relationship class data tables will require the use of a Visual Basic script. The Soils, Capability, and OCP_Urban intermediate tables could be added in this manner. Soils and Capability could be linked to the cadastral feature layer by populating a relationship class with values, determined by using the ARC/INFO INTERSECT command. OCP_Rural could be updated so it contained all parcels in the rural area. Also, OCP land use definitions need to be updated in order to match the zoning code.

Attribute data for the Water Utility, Storm, and Sanitary sewer require geocoding. The District's engineering department may have attributes for this data, but we understand the only way to add these attributes into the GIS file is to do it manually. The original zoning feature class layer needs to be updated (adding plus only for rural areas) and arbitrary (miscellaneous) lines running through parcels need to be removed. The Roads layer could be linked to the Cadastral layer after missing addresses or house numbers are added, and the street names between the two layers has been standardized. After the above problems have been corrected, the Roads and Cadastral layers, can easily create an intermediate table to link these two layers, using the ARC/INFO ADDRESSMATCH command.

Newly collected attribute data for the Storm, Sanitary and Water Utility feature classes should be ICI compliant (with GPS). This would improve on the poor matching of ICI and Pitt Meadows attributes. In addition, more metadata should be collected and wherever possible. It is thought that linkage to Vadim Finance Database would be beneficial to the business function of the District. Finally, the data model should be updated to include "date stamping" capabilities, and refined in order to minimize effort on the part of maintenance.

Policy Implications

The District's GIS department is encouraged to continue with its forward thinking GIS initiatives, and encouraged to partner again with SFU students in order to implement the various suggested future upgrades in a timely manner. In order to enable easy integration into the Geodatabase model, OD suggests that the District develop standards for data collection and AutoCad related files, and wherever possible to comply with ICI standards.