Leveraging GIS to Rejuvenate Fire & Police Response Mapping. Alex Sainz Monique Larragoitia Michael Neal

Transcription

1 Leveraging GIS to Rejuvenate Fire & Police Response Mapping Alex Sainz Monique Larragoitia Michael Neal

2 Chula Vista Fire/GIS Team Alex Sainz, GIS Specialist Monique Larragoitia, GIS Specialist Michael Neal, Fire Captain

3 Find unit C-3

4

5

6 One-Stop Shop Product Distribution Method CAD USB/Index QR Code/ Web Hard Copy Structure Pre-Plan X X X X Wildland Pre-Plan X X Critical Infrastructure & Key Resource Pre-plan X X X X B-cards X X Map Books Wall/District Maps Summary/ Tactical Report X X X X X X

7 Direct access via CAD

8 Demo Touch-enabled PrePlans

9 Also used by Law Enforcement

10 Chula Vista Best Practices & Value Added Features Challenge o Confusing field data collection o Multiple repetitive attribute fields o Editor input errors o Data tracking/accountability o Repetitive but predictable workflow o Preplan tracking o Non-CAD access o Secured and instant sharing of maps Adopted Solution / Best Practice o Standardized data collection form o Attribute Assistant add-on o Model Builder o MXD Templates o Data Driven Pages o Python scripting o Regional mapping database o PrePlan Index o QR codes

11 Chula Vista Best Practices & Value Added Features Challenge o Confusing field data collection Adopted Solution / Best Practice o Standardized data collection form

12

13

14 Chula Vista Best Practices & Value Added Features Challenge o Multiple repetitive attribute fields o Editor input errors o Data tracking/accountability Adopted Solution / Best Practice o Attribute Assistant add-on

15 Repetitive Data Entry 90% of features require own Primary Key to be calculated. Very repetitive, much potential for user error. Primary Key formula: ( * [AgencyID] [OBJECTID]) =

16 Primary Keys propagated to all other features based on spatial relationship. Repeat for multiple attributes in 80+ feature classes!

17 Attribute Assistant User-defined rules to automatically populate and validate attributes. Layer to modify. Field to modify. Rule to be applied. Calculations, parameters or values to apply. When to apply rule. * Editor tracking

18 Chula Vista Best Practices & Value Added Features Challenge o Repetitive but predictable workflow Adopted Solution / Best Practice o Model Builder o MXD Templates o Data Driven Pages o Python scripting

19 Model Builder: Create Replicas Create check-out replicas for local editing Standardized naming convention Clip to local area

20 Model Builder: Synchronize Changes Synchronize changes (check-in)

21 Model Builder: Maintenance Tasks Based on ESRI recommended version administration workflow Modified for disconnected editing environment.

22 Chula Vista Best Practices & Value Added Features Challenge o Repetitive but predictable workflow Adopted Solution / Best Practice o Model Builder o MXD Templates o Data Driven Pages o Python scripting

23 Template for Overview Page 1. No fussing with formatting. 2. Only layers relevant to page turned on. 3. Symbology different from other pages. 4. Data Driven Pages / Dynamic Text updates header info.

24 Manipulate MXDs and layers with Python

25 Previous Workflow ( ) Load MXD + + and locate site x4 + one for each type of map page Locate and package all PDF pages. Streamlined Workflow

26

27 Chula Vista Best Practices & Value Added Features Challenge o Preplan tracking o Non-CAD access Adopted Solution / Best Practice o Regional mapping database o PrePlan Index

28 PrePlan Tracking Database

29 PrePlan Index

30 Chula Vista Best Practices & Value Added Features Challenge o Secured and instant sharing of maps Adopted Solution / Best Practice o QR codes

31 Secured and Instant Sharing of Maps Scan QR code with smart phone or web-enabled tablet. Directed to preplan location* in webportal. Log in with shared password. Get instant access to critical site information. *

32 Wildland Urban Interface Maps Bradley Pickett, Chula Vista GIS Specialist

33 Future of the Project Currently grant funded. In process from project to a program. Lots of preplans still to be created.

34 How is this done? Highly invested fire and GIS team Well-defined project goals

35 Communication Collaborative work environment between fire personnel and GIS staff. Operation needs heard and met by GIS. Suggestions by GIS team evaluated by operations. End result: easy-to-use maps that comply with regionally adopted standards

36 Why do we do this? Because seconds count!

37 Questions? PRESENTATION CHULA VISTA FIRE GIS TEAM