My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2006-193B.
CBCC
>
Official Documents
>
2000's
>
2006
>
2006-193B.
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/27/2017 2:14:33 PM
Creation date
10/1/2015 12:14:07 AM
Metadata
Fields
Template:
Official Documents
Official Document Type
Plan
Approved Date
06/06/2006
Control Number
2006-193B.
Agenda Item Number
10.A.
Entity Name
Geographic Technologies Group
Subject
Three year implementation plan and assessment
Geographic Information Systems GIS
Supplemental fields
SmeadsoftID
7365
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
48
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
eLogical Database Design Methodology <br /> The Logical Database Design should consist of four parts : <br /> 1 . Kickoff Meeting <br /> 2. Existing data acquisition and review <br /> 3. Interviews <br /> 4. Logical Database Design <br /> Kickoff Meeting <br /> Kickoff meeting attendees should include all Indian River County personnel that currently or <br /> will in the future: <br /> • Create spatial data <br /> • Provide input on the creation , updating or use of spatial data <br /> • Use spatial data on a regular basis . <br /> The kickoff meeting should introduce the goals and objectives of this project, outline how the <br /> project will be conducted , and inform attendees of what will be required of each them . <br /> Existing Data Acquisition and Review <br /> Before the Logical Database Design process can move forward , Indian River County will <br /> need to ensure that if has a copy of all existing County data layers and source data from <br /> each department that will be included in the database design . <br /> Interviews <br /> All pertinent staff members from each County department/division should be interviewed . <br /> Interviews can be conducted separately for each department, or in logical groupings . The <br /> goal of each interview is to discuss in detail each data layer for which attendees are the <br /> Subject Matter Expert . <br /> Issues that should be discussed include : <br /> Deletion of existing attribute fields <br /> w0 Addition of new attribute fields <br /> • Allowable values for important attribute fields <br /> • Relationship of layer to other layers <br /> • Associated tables and cardinality <br /> • Description or alias of each field (when not obvious) <br /> • Subtypes <br /> • Default values <br /> • Whether null values are allowed or not <br /> • Indexes <br /> Several important metadata aspects ( not documented or available from the earlier existing <br /> data acquisition ) to include ( but not limited to) should be documented , including : <br /> • Feature Class Name <br /> • Feature Class Type ( point, line , polygon or raster) <br /> Feature Dataset <br /> • Description <br /> • Purpose <br /> • Data source <br /> 54 <br /> GIS Needs Assessment and Implementation Plan Chapter 5 - Database Design and Setup <br />
The URL can be used to link to this page
Your browser does not support the video tag.