2008 Geodatabase Re Design V2

19
H-GAC’s H-GAC’s 2008 Geodatabase Re-Design 2008 Geodatabase Re-Design and Implementation and Implementation Robert LaBarbera Robert LaBarbera and and Thomas (TJ) Schultz Thomas (TJ) Schultz Data Services Department Data Services Department

description

Centralized GIS repository implementation plan

Transcript of 2008 Geodatabase Re Design V2

Page 1: 2008 Geodatabase Re Design V2

H-GAC’sH-GAC’s2008 Geodatabase Re-Design2008 Geodatabase Re-Design

and Implementationand Implementation

Robert LaBarberaRobert LaBarberaandand

Thomas (TJ) SchultzThomas (TJ) Schultz

Data Services DepartmentData Services Department

Page 2: 2008 Geodatabase Re Design V2

Data Services - GIS MissionData Services - GIS Mission

Data Service’s internal GIS mission:Data Service’s internal GIS mission:• Maintain geographic databases, layers, Maintain geographic databases, layers,

historical & present-day raster imageryhistorical & present-day raster imagery• Support H-GAC’s internal GIS users Support H-GAC’s internal GIS users • Assist with the publication of on-line mapsAssist with the publication of on-line maps• Facilitate GIS trainingFacilitate GIS training

Page 3: 2008 Geodatabase Re Design V2

Data CentralizationData Centralization• GIS data should be centrally located within GIS data should be centrally located within

Data ServicesData Services• GIS data should reside within ArcSDE and GIS data should reside within ArcSDE and

not permanently on PCsnot permanently on PCs

Client Data Client Data

RequestsRequests

Data Delivery

Data Delivery

Data Services ArcSDE Data Services ArcSDE

SQL ServerSQL Server

(Data Stored)(Data Stored)

Page 4: 2008 Geodatabase Re Design V2

GIS ArcSDE Database BenefitsGIS ArcSDE Database Benefits

Centralization Benefits:Centralization Benefits:• Backup and restoration is simpler to manageBackup and restoration is simpler to manage• Easier data management – privileged users edit Easier data management – privileged users edit

layers that you version them to editlayers that you version them to edit• Easier data organization – no need to constantly Easier data organization – no need to constantly

maintain multiple file formats for GIS data (personal maintain multiple file formats for GIS data (personal geodatabases, shape files, or file geodatabases)geodatabases, shape files, or file geodatabases)

• Distribution of data is easier via ArcSDEDistribution of data is easier via ArcSDE

Page 5: 2008 Geodatabase Re Design V2

GIS Data Naming ConventionsGIS Data Naming Conventions

• GIS data should be named such that any user GIS data should be named such that any user can easily identify what the data set containscan easily identify what the data set contains

• Data Services has adopted the following naming Data Services has adopted the following naming convention for regional GIS data:convention for regional GIS data:

• ProposalProposal - Transportation and C&E should also - Transportation and C&E should also come up with a naming convention for their datacome up with a naming convention for their data

[entity]_[description]_[year][entity]_[description]_[year]

Page 6: 2008 Geodatabase Re Design V2

GIS Data SharingGIS Data Sharing

• ProposalProposal - GIS data created by departments - GIS data created by departments should be shared with Data Services for the should be shared with Data Services for the Global Geodatabase.Global Geodatabase.• For backup purposesFor backup purposes• For internal organizational sharing and viewing of For internal organizational sharing and viewing of

non-private datanon-private data• For ease of public data transfer and sharing to For ease of public data transfer and sharing to

external entitiesexternal entities

Page 7: 2008 Geodatabase Re Design V2

GIS Data UpdateGIS Data Update

• ProposalProposal - GIS data created by departments - GIS data created by departments should be updated in a periodic manner in should be updated in a periodic manner in ArcSDEArcSDE• Risks of not saving GIS data in ArcSDE:Risks of not saving GIS data in ArcSDE:

• can be destroyed or corruptedcan be destroyed or corrupted• can become inadvertently outdatedcan become inadvertently outdated• is not easily shared within the organizationis not easily shared within the organization

Page 8: 2008 Geodatabase Re Design V2

Database Migration from Oracle to Database Migration from Oracle to Microsoft SQL ServerMicrosoft SQL Server

• Data Services will be migrating from Oracle to Data Services will be migrating from Oracle to SQL Server in 2008SQL Server in 2008• SQL Server is:SQL Server is:

• less expensiveless expensive• easier to manage and maintaineasier to manage and maintain• licensing is more flexiblelicensing is more flexible

MicrosoftMicrosoft

SQL SQL ServerServer

OracleOracle

Page 9: 2008 Geodatabase Re Design V2

Database Migration from Oracle to Database Migration from Oracle to SQL Server SQL Server (cont’d)(cont’d)

• The SQL implementation will occur in parallel The SQL implementation will occur in parallel with the existing Oracle databasewith the existing Oracle database• Users will have the flexibility to:Users will have the flexibility to:

• utilize the Oracle database in conjunction with building the utilize the Oracle database in conjunction with building the SQL database(s)SQL database(s)

• share their regional GIS data with Data Services for loading share their regional GIS data with Data Services for loading into global geodatabaseinto global geodatabase

• C&E and Transportation can have their own SQL C&E and Transportation can have their own SQL databases to house private or work in progress databases to house private or work in progress project dataproject data

Page 10: 2008 Geodatabase Re Design V2

Tentative SQL Server Completion Tentative SQL Server Completion DateDate

• Data Services proposes to have the SQL Data Services proposes to have the SQL database in production by June of 2008database in production by June of 2008

• The tentative implementation time line is below:The tentative implementation time line is below:

JanuaryJanuary

MayMay

MarchMarch

JulyJuly

Build consensus on Build consensus on design, design,

organization, and organization, and workflowworkflow

Create SQL instances Create SQL instances and test database and test database

data loadingdata loading

Implement the Implement the production production databasedatabase

Load raster imagery Load raster imagery into production into production

database or database or utilize ArcGIS utilize ArcGIS Image ServerImage Server

Page 11: 2008 Geodatabase Re Design V2

Database AdministrationDatabase Administration• Data Services proposes that there be two or three Data Services proposes that there be two or three

ArcSDE databases:ArcSDE databases:• A global / regional databaseA global / regional database• Private / project databasesPrivate / project databases

• ArcSDE databases will reside on a separate server than ArcSDE databases will reside on a separate server than the ArcGIS Server (ArcIMS)the ArcGIS Server (ArcIMS)

Global CE/Transportation

Page 12: 2008 Geodatabase Re Design V2

Database Administration Database Administration (cont’d)(cont’d)

• The Global GeodatabaseThe Global Geodatabase• Administered and managed by the Data Services’ GIS Administered and managed by the Data Services’ GIS

AnalystAnalyst• Holds all regional data setsHolds all regional data sets

• ParksParks• RiversRivers• City LimitsCity Limits• Digital Elevation ModelsDigital Elevation Models• Aerial ImageryAerial Imagery

• Holds publicly accessible dataHolds publicly accessible data• Can be distributed to external agenciesCan be distributed to external agencies

Page 13: 2008 Geodatabase Re Design V2

Database Administration Database Administration (cont’d)(cont’d)

• The Private GeodatabaseThe Private Geodatabase• Administered by the Data Services’ GIS AnalystAdministered by the Data Services’ GIS Analyst• Managed by Transportation and C&E staffManaged by Transportation and C&E staff• Holds private data setsHolds private data sets

• Transportation projectsTransportation projects• Transportation model NetworksTransportation model Networks• C&E projectsC&E projects• Any private or sensitive GIS dataAny private or sensitive GIS data

• Not distributed to external agenciesNot distributed to external agencies

Page 14: 2008 Geodatabase Re Design V2

Database Administration Database Administration (cont’d)(cont’d)

• GlobalGlobal database snapshot: database snapshot:

Page 15: 2008 Geodatabase Re Design V2

GIS Data Repository FolderGIS Data Repository Folder

• The GIS_Data_Repository on Q:\DATASRV will The GIS_Data_Repository on Q:\DATASRV will be reorganized to hold the following & have a be reorganized to hold the following & have a logical naming convention:logical naming convention:• Historical GIS DataHistorical GIS Data• GIS related data such as:GIS related data such as:

• TrainingTraining• Personnel itemsPersonnel items• 911 Contacts and Information911 Contacts and Information

Page 16: 2008 Geodatabase Re Design V2

Existing GIS Data Repository FolderExisting GIS Data Repository Folder

Page 17: 2008 Geodatabase Re Design V2

GIS Database Repository File AgesGIS Database Repository File Ages

Page 18: 2008 Geodatabase Re Design V2

Feedback and Comments?Feedback and Comments?

Page 19: 2008 Geodatabase Re Design V2

Thanks!Thanks!