Laserfiche WebLink
• Primary and secondary data custodians <br /> • Acquisition scale and accuracy <br /> • Spatial information ( projection , coordinate system , datum , units, etc .) <br /> • Status of the data ( complete , incomplete, etc . ) <br /> • Data update frequency <br /> Constraints on accessing and using the data <br /> • Point of contact for each layer <br /> KtLogical Database Design Products <br /> The logical database design process should result in two products : <br /> 1 . Printed documents <br /> 2 . Flow Chart drawings <br /> 1 . Printed document <br /> A printed and bound database design document should be developed . The <br /> database design document should individually document each data layer that will be <br /> included in the process . Important metadata about each layer should be <br /> documented at the top of each sheet, as well as a snapshot of what the layer looks <br /> like visually ( Figure 5-2) . Every attribute field should be listed , to include : <br /> • Field Name <br /> • Description ( of the field) <br /> • Data Type (string , date, integer, etc, J <br /> ., a Allows Nulls (whether null values are allowed or not) <br /> • Default Value (if appropriate ) <br /> • Domain (reference to domain that dictates allowed values for this field ) <br /> • Length ( number of characters allowed ) <br /> • Precision ( number of allowable significant digits) <br /> • Scale ( number of allowable decimal places) <br /> Index (whether a field is indexed ) <br /> 5-5 <br /> GIS Needs Assessment and Implementation Plan Chapter 5 - Database Design and Setup <br />