Laserfiche WebLink
MainLine <br /> ExlerbCoating <br /> JoinTYpe (2( <br /> Liningiype <br /> Pipecloss Abstract Roughness <br /> Cardinality <br /> t <br /> u PressunzedMain GrovifyMoin Grovitylvain <br /> Feature Shapes <br /> Depth BareCount <br /> Darrel Class CrossSectionShape <br /> GroundSurtaceType Upstreaminvert <br /> PressureRating Downstreaminverl <br /> Measurement (2) <br /> Domain <br /> Blowoff Interconnect <br /> Carner Coded value domain <br /> Bypass Pipearidge GravityMainShapes <br /> Description <br /> In Cine Storage <br /> Field type Srring <br /> AirRelease <br /> Soupolicy Default Value <br /> SampiingSfation Merge policy Duplicate <br /> Pipe <br /> r <br /> CheCircular Circular <br /> Cheri <br /> on Transmission Matn Horseshoe Horseshoe <br /> Oblong Oblong <br /> Unknown Unknown <br /> DistnbutionMaln Subtypes <br /> Figure 5-4: Example Section of a Logical Database Design Data Model Flow Chart <br /> KtPhysical Database Design <br /> A physical data model must be created after the logical data model is complete . The <br /> Physical Database Design consists of implementing the logical data model schema within <br /> the geodatabase . This entails physically creating all of the features designed in the Logical <br /> Data Model . <br /> n This is the final step before the migration of existing data to the geodatabase . Therefore , a <br /> decision must be made with regard to which data layers should be represented in the <br /> geodatabase once the initial geodatabase is created . The County currently has a <br /> substantial number of spatial data layers. Most of these data layers will be relatively easy to <br /> migrate , although some layers will require more effort , including conversion and <br /> consolidation . <br /> A Indian River County should consider the following criteria when it has identified layers to <br /> implement in the Physical Database Design during initial implementation : <br /> • The County may wish to restrict access to some data layers until an agreed-upon <br /> level of completeness or accuracy is achieved <br /> • Data layers may require a customized data model provided by a software vendor <br /> • Users may be more comfortable with the existing format of data layers, or users may <br /> not have received training on utilizing data stored in a geodatabase <br /> 58 <br /> GIS Needs Assessment and Implementation Plan Chapter 5 - Database Design and Setup <br />