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
( e .g . , nightly) . The " distributed access " model will require robust network connectivity and a <br /> means for various users to access the data (e .g . , Intranet GIS data browser) . The centralized <br /> access model can be used by any application that has network access to the enterprise <br /> database; the distributed access model requires applications network access to several <br /> databases as well as functionality that allows access to various data sources at once . <br /> " Distributed Access " Model "Centralized Access" Model <br /> Dab nom Deserlmenpl DaaGrea <br /> Is E,&acW and copped m <br /> cenYall al Enterprises DaUWse <br /> countyGIS usersAaaene "EntersOae. <br /> Deparna lGIs Dam drectly <br /> , . _mk ...v 4 y,•, v SrJ <br /> j Mpo ental <br /> oaaea..a <br /> U.c.. noP«y <br /> Ppalwra OMce) <br /> D,wnme,ml Eue ,aged <br /> iDam m cm.anuanee as <br /> _j connry as oxen cmadlaabE Pan m Centralized <br /> En <br /> l £a Man deal GIs <br /> Enterprise DaUDasse <br /> Dam through ODatabase cwn* GIs Users ACCel All <br /> C,madficsn GIs Dam wg One Database <br /> F ,Dasa, Connector, <br /> GIS Usevs 4 infigh s eea a <br /> Data Lom External Databases Is <br /> PonWlvllr ImryRd In <br /> Centralized! Entities, <br /> �mbase <br /> cwnly GIs Users Mar Aocess External GIs <br /> t <br /> Dam Deeeer nnlaaal t <br /> • - -- -- - F#xnal <br /> "a DaFabmea <br /> o "a Ann... 11 waaae tea 'lol� saterr—.....:' <br /> Figure 5- l : Database Access Options for Indian River County <br /> Based on the County ' s existing network infrastructure and configuration , it is recommended <br /> that in the short term a centralized data access model should be implemented—however, <br /> as the County ' s GIS implementation progresses , it is recommended that the County develop <br /> the proper and necessary network infrastructure and configuration to establish a distributed <br /> data access model . <br /> Regardless of which model the County implements, a logical database design effort will be <br /> needed in order to properly implement a centralized enterprise GIS database . Subsequent <br /> logical database revisions may be needed as GIS data needs evolve and /or as the County <br /> modifies its GIS database model . <br /> ItLogical Database Design <br /> Why conduct a logical database design2 <br /> The logical database design process can be time consuming and produces no end -use <br /> applications . Therefore , the logical design process often receives limited attention , if any. <br /> However, there may be risks associated with not conducting a logical database design . By <br /> not going through the logical design process , Indian River County risks having a poorly <br /> y constructed database that does not meet present or future requirements . Poor database <br /> design can result in duplicate , missing, or unnecessary data ; inappropriate representation of <br /> data ; or lack of proper data management techniques . <br /> v 5-2 <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.