Geospatial Technical Support Module 2 California Department of Water Resources Geospatial Technical Support Module 2 Architecture overview and Data Promotion

Geospatial Technical Support Module 2

California Department of Water ResourcesGeospatial Technical Support Module 2

Architecture overview and Data PromotionFebruary 20, 2013


Meeting Agenda

Topic Time

1. Introductions

2. Project Overview & Goals

3. Tasks Completed

4. 10.1 Architecture

5. Data Promotion

6. Questions and Comments

7. Adjourn


Project Overview

As part of the Geospatial Technical Support contract, the VESTRA Team was asked to:

Recommend an implementation strategy for DWR’s EGIS solution. Implement the recommendations focusing on:

Esri ArcGIS version 10.1 software.

Best practices used by other large agencies that have successfully implemented robust Enterprise GIS programs.

Provide guidance to DWR regarding GIS application development environment & approach.

Enterprise GIS Applications

ESBSecurity and

AuthenticationData Services

Map Geocode Others...

Data Promotion Process (from Staging to Production)

Model control applications (Sample

Services)

Map Geocode

Other Web Services

ArcGIS Desktop

How to connect to data?

ServicesOthers...


Upgrade to ArcGIS 10.1

Publish ArcGIS Server Services

Promote Data/Services to Production Tier

Evaluate/Refine EGIS Architecture

Model Applications

Service Widgets

Code Samples

ArcGIS Desktop Connections

Web Mapping Connections

Users

EGIS Architecture ArcGIS 10.1 File

geodatabases DataSpace

Control Applications Silverlight JavaScript

Project GoalsKnowledge Transfer

Establish Connectivity

Develop GIS Application Samples


• To support control applications

Sample spatial data into the Staging tier• Viewer and Editor role

• Data Owner account at database level• Database Authentication

(Pending Oracle IDM)

Assign user permissions/privileges

• Map Service• Feature Service• Geoprocessing service• Geocoding service• PrintingTool service

Sample ArcGIS services

• JavaScript & Silverlight• Using ArcGIS services• In Staging Tier

Model Applications

• Automated promotion (Python)

• Includes re-projection

Promote to the Production tier• GeoSystems Monitor• Informs HP OVO• Needs additional configuration

Monitoring

Tasks Completed: Data, Services, Applications, Promotion, Monitoring


Tasks Completed: Enterprise GIS Architecture – Initial ArcGIS 10.1 Architecture


Tasks Completed: Enterprise GIS Architecture – Scalable Architecture Options


Looking Forward: Sample Workflows


• Multiple users• Shared by several staff in

different office locations• VDI Desktop• ArcGIS for Desktop• File Geodatabase• Custom User Interface• Calls Python scripts• Utilizes CASGEM data

Looking Forward: Sample Workflows - Groundwater Change in Storage GIS


Promote Spatial Data to Production Tool• Promote feature classes to Production Tier• Auto re-project to Web Mercator• User determines which feature classes to promote• Log level selection• Should be monitored

Current Status: Sample Python Automation – Promote Spatial Data to Production


Promote Spatial Data to Production - Exclusions Tool• Select feature classes to exclude from promotion to the production tier• Define a Working Directory

Current Status: Sample Python Automation – Promote Spatial Data to Production


EGIS Architecture: Hands on ArcGIS 10.1 installation and configuration. Detailed documentation of install and configuration process specific to DWR ArcGIS 10.1

environment. Sample Workflow Technical Memorandum

o Leveraging file geodatabase in EGIS. With VDI With non-VDI remote offices

o Extending use of DataSpace. Incorporating Enterprise and Program data sources (including remote offices) into the EGIS workflow.

o Strategy for Spatially Enabled Application Integration into EGIS Architecture.

Current Status: Transfer knowledge to DWR development staff


EGIS Standard

EGIS

Program1

Program 3

Program2

Program4

Program ArcSDEArcGIS

Server

A X X

B X X

C X X

D X X

Looking Forward: DWR Programs and DTS responsibilities – Currently one size fits all


Program Requirements

IT Infrastructure

Data Model Development

Program data stored in EGIS (ArcSDE or FGDB)

DTS staff maintains the IT Infrastructure (Oracle/AGS & NAS/SAN)

Program staff create and manage data

Program staff create MXDs for Services

Program staff Publish AGS Services

Program and DTS staff develop Web Applications

Overlap of Program and DTS Responsibilities

Services Published

Web Applications Developed

Tool Development

EGIS

A

D

B C

Looking Forward: DWR Programs and DTS responsibilities Overlap


EGIS Standard Options

EGIS

A

GW GIS

CB

ProgramDesktopAccess

Web Apps

Analysis FGDB ArcSDEArcGIS Server

A X X X X

B X X X X X X

C X X X X X

GW GIS X X

Looking Forward: DWR Programs and DTS responsibilities – Options


Looking Forward: Recommendations

DWR needs a shared vision for GIS and in-house geospatial expertise• GIS Coordinator to provide vision and direction• Set clear targets and assign responsibility• Definition of staff roles

• Geodatabase Administrator – Oracle/ArcGIS• GIS Applications Manager – Coordinates Program needs with ArcGIS resources• Enterprise and Program Data Stewards – Manage and share GIS datasets

• Required staff skills• Enterprise geodatabase (ArcSDE on Oracle/SQL Server)• Programing (Visual Studio, ArcObjects, Python, JavaScript/HTML5, Silverlight, Flex)• Expertise to develop a GIS platform strategy

• Recruit skilled GIS professionals, or • Invest in current staff

• Cultivate a GIS-friendly culture by promoting conference and training attendance• Transition GIS from a volunteer activity to a core job responsibility• Identify staff with a passion for the technology (i.e. water engineers) and invest in

additional training/development• GIS development staff should attend the Esri Developers Conference


Looking Forward: Recommendations

• Program and DTS staff need to understand each others requirements and limitations• Communication and collaboration is critical between Program and DTS

• Identify cases when a geodatabase should be used as the central databases

• Continually assess current needs, and work to meet them

• Implement technology with defaults now, expand and customize as you go• Let Program use cases drive the technology• Keep technology as simple as you can, so staff can gain confidence with it, add complexity

as needed• Plan for 3 to 5 years, by then the technology will have changed• ArcGIS 10.1 is scalable – can expand as needed • Consider skipping an ArcGIS for Server release to allow more time for Programs to use

current technology• Balance technological efficiency with productivity


Questions and Comments

Documents

Geospatial Technical Support Module 2 California Department of Water Resources Geospatial Technical Support Module 2 Architecture overview and Data Promotion