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
Potable Water Valves - --- -- - <br /> Feama Clas Name: PotebkWaterVebes - <br /> Featus DaAret PotaUleWaterDisvbNiorS�;rstem <br /> Feat• a Clan Type: Poutl <br /> Data Soytrve: 2072 GPS Data Cotlecvon <br /> Primaq Cwbdim Michelle Wang - SIS Techres an - FIS rG15 <br /> Accuracy: +(- t merely <br /> Projection: NO Stale Plane, NAD83, feet - - -. <br /> SIalm: Cocgilete as cfEtecim, 20.03 <br /> Daft Update Frequeney: As charges are made in the fie:d _ <br /> Conanabrv: Data marr NOTbe released to the public - <br /> PointofContact: Katieeine O'Breen-FJSIGIS (919) 123"4567, KOBrkr�fac am Pica <br /> Description: Feud Layer of water Saba hications. <br /> Purpose: Inventory of ell campus pe[ebk vretervahres <br /> Attributer: <br /> reld Name Daft Allaxr fait Do idan 7< Dereriptian <br /> typeN•LL Value <br /> BypasVaM hall Yes 0 Bocleas 0 p 2 "n ULZs if ihe :alve has a wypassvaive for <br /> Integer <br /> memte ame <br /> CbckwiseToClore Small <br /> :rote r Yes 1 Boolean 0 U 2 Doesthe valve close in a nbckwise diedione <br /> teal <br /> " CwrenL`yOpen Integer Yrs L Boolean 0 0 2 Is the vahm. cuvenBy epenP <br /> Motorcycled Indo Yes 0 Boolean ] 0 Is the valve mctorriedP <br /> Nommlly-0pec oral Yes I Bookan 0 1 2 s the valve designed to be aper under novm: <br /> Into r mtwark clmummaer <br /> "> Percent n Into ,r as 100 0 Fane Nom Cuven[ oerent en <br /> Pressvresatt <br /> Sinns SinnYes Vote Nona 20 f-urentp,ressvre self <br /> Pegulat»nType Stung Yes WHSyetamVaUaReq�uaz Type Hong i Nom 20 aY9he�k) S1QP regulation performed (d <br /> TvrzsTrCbse fire Yes 0 Nom Ham Number tUturmre coredt idose tie vabe <br /> Diameter lntee[ Yes 10 Ma es illi. 'iarrzlei 0 Nom Nam Diameter of[hr Babe <br /> Bkvation Double Yes 1 0 None7ktmnofthevalve <br /> WaterT e Str = Yes potable Waterh e Nom Noce 20 T eofweterflowt. item the systera <br /> AdmniistMiveAree St Yes N AdmutislratrseArea Nona None 200 ' The vlrvnmtmGre area thet m:eems the object <br /> Fecilitym 51- Yes Nom Nom I 20 IAumque facility number for4m object <br /> :mtallDate Date Yes UJ <br /> S Date object <br /> was wlalkdmtie ori <br /> Lo:atlomDescrt on Stc Nom 9cm 200 Tei3desca ion. off�e locatmn <br /> OparetiomL4r_a String Yes Dl OpemimgArea None INam 200 Fx�gneermg or operational Cvtrict for [he <br /> Rotation Double Yes 0 U None Rotation angle ( may svmbolo� <br /> Likc lestates It Yes Active IGfeC ,kStetvs Nom Nom A St of the fazilit lifec k <br /> sibT e tine r Vas 1 IG Nom Nom T. of feature <br /> WorkOtdedD st Yes Nom Nom 2U <br /> Am Rule Inte r Yzs 0 Nom Nom <br /> Enabled °tTBII Yes 1 Fn,hkd 0 ] - ✓✓ark Order dot imtelled the ab act <br /> Integer j <br /> Figure 5-2: Example Printed Logical Database Design Sheet <br /> 2. Flow Chart Drawings <br /> Data model flow charts for the organization of each data layer within the <br /> geodatabase should be developed . Developed products should include individual <br /> printed drawings , digital drawings in MS Visio format , as well as digital images of each <br /> drawing . <br /> Data should be logically organized into the following categories : <br /> • Geodatabase <br /> • Feature Datasets <br /> • Feature Classes <br /> Geodatabases should be utilized to organize similar datasets. Feature Datasets should <br /> be established to logically group Feature Classes of similar type or business process . <br /> The data model flow charts should document all Feature Datasets, and the Feature <br /> Classes within each Feature Dataset ( Figure 5-3) . Feature Classes should be displayed <br /> according to type: point, line , or polygon . Additionally, the organization of other types <br /> ry of data that will be stored within the geodatabase, including ( but not limited to) rasters <br /> (such as aerial photography) , and CAD data , should be documented . <br /> 5-6 <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.