Common Operating Picture

By: Sandi Cone Field Operations Guide

Organization: Laurel Police Department

Common Operating Picture (Situational Awareness)

Tandem Emergency Response Platform (TERP) Brief Explanation: A flex-based application for fusing and analyzing data from multiple sources to support police department and other public safety analytics and situational awareness. Department Background: Size: GIS Ability: Laurel PD is working with the City GIS Small None Dept and EOC to develop this capability X Medium X In House Large Separate Department Data Needed: Data is displayed in TERP in two ways: a live layer that runs continuously and can be toggled on and off; or as a discrete dataset which is only displayed when the RBE query is activated. From this last workflow, only the data that falls within the predefined buffer is returned from the full dataset. • CAD data o Open calls o Last 15 min of closed calls • Base Map Layers (Live Layer) o Municipal boundary o Street centerlines o Building footprint labeled w/ address o Snow emergency route o Fire hydrants (also in RBE) • Points of Interest (RBE) o Schools o Churches o Daycare Centers o Police Stations o Park and Ride Stations o Fire Stations • Incident and local department data. (RBE) o New releases from the Prince Georges County Jail. These are geocoded and appended to the new releases map service which is one of the point layers featured in the RBE query. o Probation and sex offender data feeds
Current workflow is downloading the data from a mapping site weekly (it comes down with X/Y coordinates so it is easy to plot and append)
The Department of Probation and Parole does publish a mapping service of the point layer but it currently requires authentication to access thus not formatted for version 3.1 Flex viewer. The City will test the functionality of the layer in Flex 4.0 as use of secure services have been addressed.
We currently obtain sex offender data from this DPP dataset but are working on getting access to the Department of Corrections’ feed. o Open Warrants
Prince Georges county publishes this feed that is updates 4 times a day. • Image service of 6 in ortho product • Live surveillance cameras maintained by the city • WeatherUnderground Service • Yahoo! Traffic data • BING maps • Twitter

Software Required: • ArcGIS 9.3.1 o ArcInfo (for geocoding and ability to save MXD as MSD to publish) o Server (for publishing services) • FlexBuilder • Sample Flex Viewer • Widgets o Either the RBE widget posted in the code gallery (for one jurisdiction data feed) or the newly developed Live Incident Monitor (consumes and consolidates multi-jurisdicitonal CAD feeds into one window and activates RBE functionality). The LIM can be obtained from the City of Laurel upon request. Skills to perform tasks (i.e. Network Analysis, GIS Data editing, etc.): • Consume and display spatial data as a map on the Adobe Flex platform and ESRI sample flex viewer. • Convert and query spatial data via modules (widget=menu, tool=interactive functionality) • Provide development framework for map interface, widgets and tools

Procedure: •

Workflows for publishing CAD data a. Current: i. At this point we are leveraging a data download from our CAD database every minute (using a scheduled task on the server) in a XML format. ii. Our CAD captures a X and Y coordinate, we can go directly to the geoRSS conversion functionality in the Live Incident Monitor. iii. Before being plotted on the map, the data points must be run through a geometry service as TERP is currently in web mercator and our data is in Maryland State Plane Feet. iv. While seemingly complicated, this action takes seconds. The only downside is that we aren’t capturing the closed call data. b. Future (in test) i. We are currently test in a new workflow that pushes new and updated CAD data directly from the CAD sql database to a GIS-SERVER sql database (sql.TERPc) via the use of triggers. ii. A table was set up on the GIS-SERVER database called sql.TERPc in the same schema as the CAD incident table. iii. A trigger was added to the CAD table to push an new calls to sql.TERPc upon initiation (new data row INSERT). Additionally, anytime an existing record is updated, this triggers an UPDATE function from the CAD incident table to sql.TERPc. iv. This UPDATE function also caputures when a call is closed. This leaves us with a sql table of all open and closed calls. v. We are testing the use of the OGR/GDAL toolkit (free Open Source GIS toolkit) which enables one to reproject spatial data in SQL Server 2008. This allows us to bypass the need to geoprocess the data points or use a geometry service. vi. We have written 3 views from this one table that will all separately be published as a service: 1. Open calls 2. Last 15 min of closed calls 3. All closed calls (for TERPanalytics only)

Additional Resources for creating situational awareness applications Guidelines for implementing the flex viewer common operating picture: Implementing the Flex Viewer Emergency Management Template Examples of other web mapping applications for public safety CARAT - Field Ops Guide