In this document is presented a review of the need for GIS at MDPD followed by an analysis on how well current software support the accurate and timely collection of intelligence and the follow-up and assessment of crime prevention and suppression methods.

1. Miami-Dade Police Department
Geographic Information System Applications Review and
Recommendations for Implementation
Prepared for:
Miami-Dade Police Department
Systems Development Bureau
Ira S. Feuer, Bureau Commander
Prepared by:
Miami-Dade Information Technology Department
Application Consulting Services Division
Orlando Suarez, Director
29 August 2012
Juan Tobar
Senior Systems Analyst/Programmer

2. 1. Introduction
The Miami-Dade Police Department GIS Application Review and
Recommendations for Implementation have been completed. In this document is
presented a review of the need for GIS at MDPD followed by an analysis on how
well current software support the accurate and timely collection of intelligence
and the follow-up and assessment of crime prevention and suppression methods.
Throughout this document a series of 14 recommendations are provided to
improve the current system. Appendix A contains a recommendation sign-off
sheet, Appendix B contains the results of an interview questionnaire that was
essential in crafting this document, Appendix C has three sample isopleth maps
and Appendix D has a possible implementation timeline.
The MDPD’s need for GIS Mapping is driven by the three tasks that Police Crime
Analyst Specialists (PCAS) perform: maps in support of COMPSTAT, special
map projects and map analysis. Of these tasks the one that is best supported by
the current GIS Mapping Application is COMPSTAT and this is because the
application simplifies the creation of standardized maps for these weekly events.
Special map projects and to a greater degree map analysis are not supported
because they require more functionality than the application currently offers. In all
three cases the need for maps is driven by two principles, which have proven to
be essential ingredients of an effective crime-fighting strategy1:
Accurate and Timely Intelligence - Effective operational and deployment
strategies require accurate and timely intelligence. Officers at all levels of
the police department must understand when (time of day, day of week,
week of year) various targeted types of crimes have been committed as
well as how, where, and by whom they have been committed.
Relentless Follow-up and Assessment - All action must be relentlessly
followed-up and assessed to ensure that the desired results have been
achieved. This is the only way of ensuring that recurring or similar
problems are dealt with effectively in the future.
1
NYPD Web Site at http://www.ci.nyc.ny.us/html/nypd/html/chfdept/reduction.html
2

3. 2. Accurate and Timely Intelligence and Current Procedures
The current data entry methods do not adequately support the collection of
accurate and timely intelligence for use with MDPD’s GIS System.
The lack of accurate intelligence is due to un-geocoded records. This accuracy
problem manifests itself as missing records that lead to the production of
inaccurate reports and maps when using the GIS System. The timely intelligence
problem affects only the display of crime incidents on the GIS system and not
general reporting functions of other applications such as CAS. The problem is
due to two geocoding procedures: initial batch geocoding which can require up to
24 hours before incident points are available for mapping and subsequent reject
geocoding which can require up to 48 hours before incident points are available
for mapping.
2.1 CAS – ORACLE Accuracy and Timeliness Problems
These problems result in CAS – ORACLE from the following procedures:
Complaint Desk Data Entry Process
Incidents are recorded in CAD Event Files
Incidents are displayed on Positron’s Complaint Desk Software
Incidents are transferred to Police CAD dispatchers
Bureau or District Data Entry Process
Records are added or updated into ORACLE from CAS at bureau or
district offices.
Initial 24-Hour Processes (This is a timeliness problem.)
Records are inserted into ORACLE from CAD event files.
All records from the past 13 months with a geocoding flag set to A for
added or Y for updated are pulled out of ORACLE for geocoding.
o First, zip codes are assigned using Finalist.
o Second, the records are geocoded against the property layer with
zip codes.
o Third, the rejects of this process are geocoded against the property
layer without zip codes.
o Fourth, the rejects of this process are geocoded against the road
centerline file with zip codes.
o Fifth, the rejects of this process are geocoded against the road
centerline file without zip codes.
o The rejects of this process remain un-geocoded and their
geocoding flag will be set to the value of “R” for reject.
Records are updated in ORACLE with X and Y coordinate information and
a geocoding flag for each record set to either: G for good or R for rejected.
3

4. All records from the past 13 months are pulled out of ORACLE and are
used to generate an ArcView shape file that contains the subset of
correctly geocoded records from ORACLE’s complete set. On average
about 2000 records are entered each day of which 95% - 100% come
from CAD and anywhere from 0% - 5% come from records added at
district or bureau offices. Of these 2000 records on average 20% - 30%
are rejects. This is an accuracy problem.
Subsequent 48-Hour Processes (This is a timeliness problem.)
o The reject results from the above batch process can now be
modified and then must wait to be reprocessed through same
procedure described above.
2.2 UCR – IDMS Accuracy and Timeliness Problems
These problems result in UCR – IDMS from the following procedures:
Data Entry Process
Incidents are recorded through UCR into IDMS
Initial 24-Hour Processes (This is a timeliness problem.)
Records are inserted from UCR-IDMS into ICDW-ORCALE.
All records from that day are pulled out of UCR-IDMS for geocoding.
o First, zip codes are assigned using Finalist.
o Second, the records are geocoded against the property layer with
zip codes.
o Third, the rejects of this process are geocoded against the property
layer without zip codes.
o Fourth, the rejects of this process are geocoded against the road
centerline file with zip codes.
o Fifth, the rejects of this process are geocoded against the road
centerline file without zip codes.
o The rejects of this process remain un-geocoded and will be
assigned a GEO field value of “R” for reject.
On average between 1000 and 1500 records are entered each day and of
these on average 10% - 15% are rejects. This is an accuracy problem.
Records are updated in the ICDW with X and Y coordinate information
and a geocoding flag for each record set to either: G for good or R for
rejected.
2.3 UCR – Arrests Accuracy and Timeliness Problems
Data Entry Process
Incidents are recorded through Arrests into IDMS.
Initial 24-Hour Processes (This is a timeliness problem.)
4

5. Records are inserted from Arrests-IDMS into the ORACLE-ICDW.
There are currently no geocoding procedures in place for this database. (This is
an accuracy problem.)
1
VAX
1 1
CAD
CAS Event UCR Arrests
ORACLE Files IDMS IDMS
2 3
ARC/INFO 2 2
ARC/INFO ARC/INFO REJECT
BATCH
BATCH BATCH
CAS 3
REJECT 3
REJECT
REJECT
3
PRESENT
CI
PROPOSED
Data
Warehouse
2.4. The Accuracy Problem and Possible Solutions
It is imperative to understand that the success of MDPD’s GIS system is directly
related to the resolution of the accuracy problem. GIS as a tool for Accurate
Intelligence and the Relentless Follow-up and Assessment of Tactics will not
work effectively until the GIS System has at its disposal all of the previous days
records.
This being said lets examine the results of three hypothetical and improved
geocoding processes in which 95%, 99%, 99.9% of all records are matched. The
question we then wish to answer is:
What is the probability that a map that needs to display 600 points will
have at least one error of omission because of rejects?
5

6. This type of question is often examined statistically with a binomial distribution
function a simplified form of which can be expressed as:
n
P 1 p
where P = the probability of an error on a map
p = the probability of any single point being correct in our case .95,
.99 and .999
n = the number of points that need to be displayed on our map
(1,2,3,…n)
Table 1 below presents the probability of errors using our current reject rate of
.30 and that of the hypothetical and improved geocoding processes at .05, .01
and .001.
Table 1: Probability of an Errors on a Map
P P P P
where p =0.70 where p = 0.95 where p =0.99 where p = .999
n current hypothetical hypothetical hypothetical
1 30% 5% 1% 0%
10 97% 40% 10% 1%
50 100% 92% 39% 5%
100 100% 99% 63% 10%
200 100% 100% 87% 18%
300 100% 100% 95% 26%
400 100% 100% 98% 33%
500 100% 100% 99% 39%
600 100% 100% 100% 45%
One of the most common types of map produced by PCAS is that of a crime type
specific map displaying all incidents for a single month. A summary of the
burglaries for October of 1998 by district shows that the total number of points
per district involves anywhere from 300 to 600 points2 (Table 2) in which case all
the improved hypothetical maps at 95%, 99% or 99.9% will likely contain an error
of omission.
Table 2: Burglaries by District for October of 1998
District Burglaries
Cutler Ridge 326
Hammocks 420
Kendall 370
2
This does not include rejects.
6

7. Doral 606
Northside 286
These statistics are sobering and indicate that anything short of correcting all
rejects will result in GIS reports and maps that more likely than not contain errors
of omission. This document is written under the assumption that the effort will be
made to correct this accuracy problem by attempting to geocode all records.
Should this not be the case and system development continues it will lead to GIS
applications that are perceived as “inaccurate”, “erroneous” and “incorrect”
because of the errors of omission found in the data used by the GIS.
2.1.1 Visual Basic/MapObjects Geocoder
One attempt to solve this accuracy problem involved the incorporation of a Visual
Basic (VB)/MapObjects (MO) geocoding application within CAS. This application
geocodes rejects or newly entered records against the road centerline file for the
purpose of confirming the validity of a given address. These records would then
be subjected to batch geocoding in order to create the updated shape files. This
pre-geocoding would have resolved many record discrepancies but its
implementation would have been flawed because it did not take into
consideration bureau and district policy on geocoding. This varies from office to
office in some locations there is a consistent attempt to correct as many records
as possible, unfortunately, what is more common is a total disregard for reject
processing. Thus, incorporation of this geocoder into CAS should involve training
sessions in which the importance of reject processing can be conveyed to PCAS.
ITD has created a number of these geocoders including the one for MDPD and
one for OEM. Since most of this geocoding will be for reject processing the
geocoder should maximize the ability of users to geocode incidents by simply
pointing and clicking. In this way incidents that occur in isolated areas or in those
areas where the road network infrastructure does not exist can be geocoded.
Needless to say it is imperative that this geocoder perform as quickly as possible
and that a certain objective acceptance criteria be set to judge its success. There
are a number of sources that indicate that the maximum time a user will patiently
wait for a web page to load in a browser is between 4 and 30 seconds 3. We can
define Geocoding in two manners: first, it may be defined as data entry,
generation of a candidate list, selection of a candidate and the assignment of
coordinates. Second it could be defined simply as pointing and clicking on a map
with a mouse and the assignment of coordinates. In either case if we assume
that each reject will require one minute to geocode then should PCAS need to
3
http://www.photosinc.net/labs/bamartposted.htm, http://www.dur.ac.uk/integra/intro.htm
7

8. geocode 60 to 70 rejects then they will spend 60 minutes in geocoding activities. 4
This should not be considered excessive considering the importance of the
procedure for the future of GIS at MDPD.
Programming modifications to this Geocoder will also involve its incorporation
into CAS and eventually a reprogramming or replacement to work with SDE.
Recommendation 1: Provide PCAS with an Enhanced VB/MO Geocoding
Engine.
2.1.2 Year-to-Date Reports
One common report at MDPD is that of the Year-to-Date Report which compares
crimes between the last two years to display the percent of change from one year
to the next. These reports require at least 24 months worth of data instead of the
13 months currently being provided to the GIS Mapping Application. MDPD may
take two course on this issue:
First, establish an aggressive program to geocode rejects over this 24-month
period. An estimate of the number of hours it would take to geocode 24 months
of data is about 10,000 hours.5
Second, take no active role in these historic records and wait two years after a
100% geocoding solution is implemented when all 24 months of data will be
geocoded.
Recommendation 2: Develop an aggressive program to geocode all rejects
as far back as 24 months.
2.1.3 Live Complaint Desk Geocoding
In this solution geocoding occurs at the Call Center. When a call comes into the
Complaint Desk System its address is extracted through Automatic Number
Identification (ANI) and in the future cellular calls will have an attached X and Y
coordinate. Either the address or x and y coordinates are immediately geocoded
and inserted into the CAD Event Files. The advantage of this solution is that the
information is geocoded at the source through ANI addresses. The negative
4
The average number of records entered into ORACLE per day is 2000 and this number is
multiplied by the percentage of records that remain un-geocoded after batch 30% this gives 600
rejects. These 600 rejects are divided by the number of districts nine and results in 67 records per
station. These 67 records are multiplied by 1 minute to total 67 minutes of geocoding.
5
This number was derived by assuming that on average 2000 records are entered per day, over
the last 24 months this would produce 1,460,000 records of which 30% or 438,000 are rejected.
Then if it is assumed that each record will necessitate 1 minute to geocode then this results in
438,000 minutes or 7300 hours which was increased to 10,000 hours in case of unforeseen
events.
8

9. aspects of this solution include the costs associated with acquiring the system
and training personnel.
2.1.3 Pre-requisite Reject Geocoding in CAS
Another option is to require a pre-requisite GEO field value of G for good, A for
added and Y for update of all the previous day’s records before PCAS are able to
use CAS for daily reporting or data entry. PCAS users would use a geocoding
application to correct rejects to one of the three codes mentioned. The benefits of
this solution include that it would guarantee that rejects would be geocoded. The
negative aspect includes that geocoding would be come a bottleneck preventing
PCAS from using CAS.
2.1.4 Pre-requisite Reject Geocoding in GIS
Another method would involve the same GEO field values as above but the lock
out would occur at the GIS application or GIS function level. That is the GIS
applications could be coded to verify that there are no rejects before becoming
available. Similarly the GIS applications could become available but reporting
and mapping functions would be unavailable until the rejects are processed. In
this later case the GIS application would essentially only be functioning in
browser mode. The benefits of this implementation include that the user will have
access to CAS reporting functions and limited GIS functions. The negative
aspects include that because CAS will be available an office may elect to forgo
reject processing and GIS use. An additional complication is that each
application deployed will have to be coded to examine the previous days data to
verify that all records have been geocoded before becoming available or making
available reporting and mapping functions.
Recommendation 3: Purchase Positron’s PowerMap application train staff
to process rejects and implement any of other solutions as necessary to
ensure that rejects are reduced to a minimum.
2.2 The Timeliness Problems
It is also important to understand that the success of MDPD’s GIS system is also
contingent on the resolution of the timeliness problems. GIS as a tool for Timely
Intelligence and the Relentless Follow-up and Assessment of Tactics will not
function efficiently until the turn around time for accessing rejected records is
reduced from today’s 48 hour waiting period.
Although we have documented two timeliness problems occurring in the initial
and subsequent geocoding processes we can expect only efficiency
improvements in the initial process related to the elimination of shape files. The
24-hour timeliness problem cannot be easily improved due to the loading of CAD
Event Files into ORACLE. As it stands now this event occurs once every 24
9

10. hours and unless there is live insertion of these records from CAD Dispatch
directly into ORACLE this 24-hour delay will remain. This section is primarily
concerned with the simplification data generation and the reduction of the time
needed to update rejected records.
In the section entitled 4. The Accuracy Problem and Possible Solutions the
methods described do not solve the timeliness problem because they all continue
to rely on shape files for the update of coordinate information in ORACLE and
GIS mapping functions. A more elegant solution to these two issues would take
an event address, conduct live reject geocoding, immediately store the feature
and it’s X and Y coordinates directly in a database and also allow for the direct
database access and display of these features through a GIS system. This
solution is available for all major databases through vendor specific spatial
enabling extensions or through ESRI’s Spatial Database Engine (SDE).
These extension solutions store and organize the spatial components of a
database by adding a spatial data type to relational databases. These extensions
do not change an existing database or affect current applications they simply add
a shape column to existing tables and provide software to manage and access
the shape data referenced by that column. These extensions store geometric
data and spatial indexes in separate tables, using a key in the shape column to
perform a joins.
In regard to MDPD crime data held within the data warehouse some possible
solutions are as follows:
2.2.1 ITD SDE Server
First, MDPD could use the SDE server currently operating at ITD. The benefits
here include: cost savings in hardware, software, training and maintenance; and
the leveraging of ORACLE and SDE knowledge at ITD for a faster
implementation. One of ESRI’s recommendations for the County’s SDE server is
that this server be centrally managed as apposed to having MDPD retain their
own system. The negative aspect of this configuration is that MDPD will not
maintain security and this in and of itself may bring into question the
confidentiality of these records.
It should be noted that the current SDE system is accessed by a number of
applications including the Property Appraiser’s Property Search Applications and
Team Metro’s Case Management System (VOCARTA). This server is also the
LIBRARIAN server that is used to maintain the County’s property layer. One
other note on this configuration is that since attribute information will be held at
MDPD and feature information will be held at ITD the maximum throughput to
district offices will be based on ITD to district connections rather than MDPD to
district connections.
10

11. 2.2.2 MDPD SDE Server at ITD
Another option is for MDPD to purchase its own SDE server and SDE software
and migrate the data from the above implementation to this server. The benefits
include a leveraging of the ORACLE and SDE knowledge at ITD, possibly higher
reliability and possibly faster performance. The negative aspects include
software, hardware, maintenance and training costs and the security concerns
expressed above.
2.2.3 MDPD SDE Server at MDPD
Third, MDPD could transfer the SDE server to MDPD and assume responsibility
for maintenance and update. The benefits to this configuration may possibly
include higher reliability and speed. The negative aspects include the same
software and hardware costs mentioned above plus training costs and the time
needed for staff to become proficient and productive in system design and
maintenance.
2.2.4 Data Warehouse SDE Server
Fourth, MDPD could purchase its own SDE software and install it on the Data
Warehouse Server. Pertinent ORACLE tables could then be SDE enabled or
separate SDE layers could be created to reference the records in these tables.
The benefits to this configuration include that there would be no additional cost
for an SDE server and District stations would communicate to MDPD
Headquarters rather than using the slower connections to ITD. The negative
aspects of this implementation include software, training costs and the time
needed for staff to become proficient and productive in system design and
maintenance, and higher performance requirements of the Data Warehouse
Server.
The following is presented to give the reader an example of the hardware and
software used in an ArcSDE Server System implementation and is not to be
construed as a system architecture recommendation for MDPD.
“Data General AViiON 3
Dual 700 MHz Pentium III Xeon processors (1 MB L2 cache)
1 GB RAM
Dual 18 GB 10K RPM SCSI drives (RAID 1)
Windows 2000 Advanced Server, SP1
CLARiiON 4500 fiber channel disk array with ten 18 GB 10K RPM SCSI
drives
Five disk RAID-5 LUN for database
Two, dual-disk RAID-1 LUNs for logs, etc.
Single disk "hot spare"
SQL Server 7.0, Enterprise Edition, SP2
11

12. ArcSDE 8.0.2, Patch 1” 6
It is important to note that if these recommendations are implemented in
sequence at this stage records would begin to be inserted directly into SDE and
that this procedure would be running in parallel with the batch processes
currently supporting the GIS Mapping Application.
Recommendation 4: MDPD should begin by using the SDE at ITD.
3. Relentless Follow-up and Assessment
6
ESRI’s Technology Demo Portal at http://eslims.esri.com/default.htm
12

13. The current MDPD GIS mapping and analysis system consists of the GIS
Mapping Application and this application does not adequately support Relentless
Follow-up and Assessment. This is because by its very nature it is a simplified
GIS mapping tool and not the robust mapping and analytical system needed for
special map projects or map analysis functions. It should be noted the application
could support COMPSTAT mapping functions adequately if the accuracy and
timeliness issues where resolved.
There are a number of problems inherent in continued support of this application
including that Avenue, the programming language in which the application is
written will not be supported in the next version of ArcView v8.0.
Additionally, the needs analysis revealed a number of enhancements that PCAS
wished for the GIS Mapping Application. These additions and enhancements
included: more cartographic manipulation options including more control of map
extents, icons, colors and layouts and the ability to add more data layers; more
data editing options including the ability to move point, lines, and polygons; and
more database manipulation options including the ability of executing tabular and
spatial joins. If all these enhancements where introduced into the application in
effect it would require the enabling of most of the underlying ArcView GIS
functionality.
Lastly, at some point the application will have to be re-written in Visual Basic the
programming language of ArcView v8.0+. This being said it is imperative that the
application be maintained until suitable replacement software is implemented and
found to be successful.
Recommendation 5: Maintain the GIS Mapping application until suitable
replacement software is implemented and found to be successful.
3.1 ArcView GIS
As has already been noted there are approximately 100 PCAS at MDPD and a
comparable number of ArcView GIS Systems each valued at about $800 with
associated annual upgrades of about $150 each. Yet, most of the functionality
found within ArcView remains unused and hidden underneath the GIS Mapping
Application. It is imperative that in order to secure a successful GIS program at
MDPD that ArcView software use be maximized. Although ArcView GIS is a
powerful Desktop GIS System it is not a crime analysis system, however,
ArcView can expanded through third party extensions such as CrimeView to
provide a richer set of crime analysis functions. It is the opinion of the author that
this software combination should be the basis for the replacement of the GIS
Mapping Application
3.2 ArcView Spatial Analyst
13

14. One of the primary reasons for COMPSTAT maps is the identification of hot-spot
locations. Currently hot-spot information is analyzed and compared via dot
density but not chloropleth (grid) maps or isopleth (continuous surface) maps.
Grid maps and continuous surface maps allow a depiction of crime per unit area
that in many cases is the best visual representation of these discrete events.
These maps also allow for the subtraction of one map from another in order to
produce maps depicting the net increase or decrease of crime per unit area.
(Appendix D). These maps can be created using ESRI’s Spatial Analyst
extension for ArcView that costs approximately $2,000. Another solution is the
implementation of a server processing technology. (See section 4.1.3.1 Server
Based Processing Solution)
3.3 CrimeView
ArcView is a powerful Desktop GIS however it lacks specific business tools
relevant to crime mapping. Much like other ArcView extensions fulfill nitch
markets: Network Analyst for Traffic Engineers, Spatial Analyst for Environmental
Scientist, AVSewer for Infrastructure Managers/Engineers, CrimeView provides
the tools for the most commonly requested Crime Analysis functions including:
Visualize incident patterns
Map repeat calls
Create density maps
Identify trouble spots
Prepare officer and citizen patrols
Improve officer safety
Maximize limited resources
Adjust beat boundaries
Locate parolees and other registrants (Megan's Law)
Map drug arrests by proximity to schools
Identify accident prone intersections
Analyze crime trends over time
Predict the expected range of crime activity
Compare crime data to demographic data
Analyze the probability and location of future crimes
This extension could be implemented using a server processing technology or
installed individually on PCAS PCs. A primary license for this software is $5,000
with additional copies priced at $1,295. It should be noted that this software
requires that ArcView Spatial Analyst also be installed.
ESR and the Omega Group have created a demonstration site where CrimeView
may be evaluated as it runs from a Windows Terminal Server at the following
URL:
http://eslims.esri.com
14

15. The procedure for enabling the Citrix client is as follows:
1. Click on the WTS Demos link.
2. Go down the page and click on the Citrix Icon (red & white) to download
and install a small plug-in. You only need to do this the first time - once
per machine.
3. Once that is done click on the WTS Login link.
4. Then use the following user name and password:
Username: psafety
Password: esri_wts
3.4 Pros and Cons on the ArcView/CrimeView Solution
There are a number of benefits to this solution and they include:
The solution maximizes the use of software already purchased and being
maintained by MDPD.
It provides PCAS users with a robust mapping and analytical system.
It will require of PCAS users to be knowledgeable in the GIS functions
they perform by requiring them:
o be trained in basic GIS concepts and in the use of ArcView GIS.
o be given a basic understanding of the current and future processes
that are used to create the crime data they use. In particular they
will be informed on why all records may not be available for
mapping and the importance of reject processing.
The solution greatly reduces application development costs that are better
spent on user support.
The solution reaps the benefits of vendor developed enhancements both
in general GIS functions and in specific crime analysis functions.
The solution requires the standardization of the County’s GIS data to
facilitate its use by PCAS.
The negative aspects of this solution include:
A steeper learning curve than would be the case with a simple Mapping
Application.
Costs associated with hardware upgrades.
Costs associated with training.
Costs associated with user support. This should be mitigated to some
extent by the reduced need for application development.
3.1 The Need for Data Standards
At present, the County has data stored as shape files, covers, Librarian layers,
SDE layers and geodatabase layers. Each of these GIS data types follow
15

16. different naming conventions making it incumbent upon the user to be
knowledgeable in five different storage schemas. In particular for MDPD, one of
the most commonly used data types that of ArcView Shape Files has a storage
schema that is not intuitive and requires a large bandwidth connection to be used
effectively. In order to simplify and thus promote the use of GIS at MDPD PCAS
should only need to be trained in the use of one storage schema regardless of
the GIS data type (Shape Files or SDE Layers) and this schema should be
intuitive, perform well in a network environment and be expandable. The reason
why PCAS need access to all of the County GIS data is because one of the main
analytical functions of these users is the identification of spatial, temporal
spatial/temporal patterns. Since these patterns can occur just about anywhere on
sea, air or land and be potentially related to any geographic feature actual or
virtual a pattern could possibly exist between crime and any one of the County’s
150 GIS layers. In addition, users need access to the County’s demographic data
for the analysis of crimes through the use of demographic profiling.
3.1.1 Spatial Data Standards
The most advanced GIS standard and the one most supported by Federal, State,
and Local Governments is the Spatial Data Standards (SDS) from the CAD/GIS
Technology Center. The SDS have focused on the development of graphic and
non-graphic standards for GIS implementations at Air Force, Army, Navy, and
Marine Corps installations, and U.S. Army Corps of Engineers Civil Works
activities.
“The SDS provide a standardized grouping of geographically referenced (i.e.,
geospatial) features (i.e., real-world features or objects depicted graphically on a
map at their real-world location (i.e., coordinates). Each geospatial feature has
an "attached" attribute table containing pertinent data about the geospatial
feature.
The SDS is the only "non-proprietary" GIS standard designed for use with the
predominant commercially available off-the-shelf GIS and CADD (e.g., ESRI
ArcInfo and ArcView; Intergraph MGE and GeoMedia; AutoDesk AutoCAD, Map
and World; and Bentley MicroStation and GeoGraphics), and relational database
software (e.g., Oracle and Microsoft Access). This nonproprietary design, in
conjunction with its universal coverage, has propelled the SDS into the standard
for GIS implementations throughout the Department of Defense (DoD), as well as
the de facto standard for GIS implementations in other Federal, State, and local
government organizations; public utilities; and private industry throughout the
United States and the World.
The SDS (along with the Facility Management Standards for facilities,
infrastructure, and environment (FMS) is distributed via CD-ROM and the
Internet (http://tsc.wes.army.mil). A user-friendly interactive Microsoft Windows-
based software application installs the SDS/FMS "Browser" and "Generator"
16

17. applications on desktop computers and networks. The "Browser" application
provides viewing and printing capability. The "Generator" application generates
Structured Query Language (SQL) code for construction of the GIS database.” 7
3.1.2 A Hierarchical Directory Structure based on the SDS for the Storage of
Shape Files
We previously stated that the maximum time a user will patiently wait for a web
page to load in a browser is between 4 and 30 seconds.8 If we apply the same
reasoning to the County’s listing of spatial data in shape file format we find that at
present it is not possible for PCAS to have timely access to GIS data held on
County servers. There are a number of contributing factors to this including: the
number of files to be browsed, the method by which ArcView browses directories
and files, the size of the files, and network connectivity. The simplest of these for
the County to manipulate is the number of files that need to be browsed.
Currently many of the County’s GIS layers are stored in a single directory (Figure
1).
Figure 1: A Small Portion of the Files in S0140158Pubshp
The directory S0140158Pubshp contains some 413 files at last count that when
accessed with ArcView GIS from a local machine running at 700 MHz takes 12
seconds to load. This same directory accessed from a remote district such as the
Carol City District Station loads in 1 minute 35 seconds. In the course of an
ArcView GIS mapping session this directory will be accessed multiple times each
time requiring this delay and thus rendering ArcView GIS practically unusable. In
addition, it is currently incumbent upon the GIS user to be knowledgeable of
7
CAD GIS Technology Center Web Site at http://tsc.wes.army.mil/
8
Photosync Web Site at http://www.photosinc.net/labs/bamartposted.htm
University of Durham Center for Applied Social Studies Web Site at
http://www.dur.ac.uk/integra/intro.htm
17

18. County naming conventions and in some instances to simply memorize the name
and content of different spatial data sets.
One solution to both of these issues is the creation of a verbose hierarchical
directory structure based on the SDS that can be drilled into to find the desired
information. Verbose directory names convey the greatest meaning possible
while the hierarchical form transfers the minimum amount of information
necessary to navigate and access data.
In the current system PMDPDGRD is the police grid area shape file and is stored
in the S0140158Pubshp directory among about 150 other shape files (Figure
2). In a hierarchical directory structure this same file would be stored in a
directory labeled Police_Grid_Area (Figure 3 and 4) as is recommended by the
SDS already discussed.
The creation of this directory structure is not difficult and a reasonable estimate
for creating it and the supporting programs is no more than 240 hours. Most of
the spatial data found within S0140158Pubshp would not necessitate daily
generation as most of this data does not change a more appropriate
maintenance schedule could be once per week for most of the data. Although
created for MDPD other departments could use this directory structure as a user-
friendlier library of spatial data.
Figure 2: PMDPDGRD or the Police Grid Area Shape File
18

19. FIGURE 3: Hierarchical Directory Structure Viewed through Windows Explorer
FIGURE 4: Hierarchical Directory Structure Viewed through ArcView GIS
3.1.3 Shape File Nomenclature using SDS
The SDS nomenclature for a coverage designates that the first two characters of
a cover’s name represent an Entity Set which is a broad grouping of similar
geographic features in the example above “boundary” would be abbreviated “bd”.
The following three characters represent an Entity Class a more confined
grouping of similar geographic features in the example above
“boundary_public_safety” is abbreviated “pub”. Lastly, the remaining three
characters represent the actual Entity or the object which will appear on the map
in the example above “police_grid_area” is abbreviated “grd”. Thus the name of
this cover using the SDS standard is “bdpubgrd”.
This has to be modified slightly in order to accommodate shape files by dropping
the first two characters “bd” and appending an underscore “_” followed by an “l”
for line, “p” for polygon and “x” for point. Thus, the police grid area shape files will
19

20. be named pubgrd_p.shp and pubgrd_l.shp Again, users do not need to know this
detailed nomenclature because of the verbose hierarchical directory structure
expands each of these abbreviations.
3.1.4 SDS Implementation Using SDE
This same nomenclature and hierarchical directory structure can be and should
be implemented with SDE in this way conforming the data PCAS see to a
common data standard.
Recommendation 6: Implement Spatial Data Standards in a production
hierarchical data directory structure for the storage of shape files, on the
shape files stored in this directory and the data layers within SDE.
3.1.5 Hierarchical User Directories
In order to simplify the use of MDPD’s GIS system it will also be necessary to
create a centralized user directory for saving user created projects and data.
Although MDPD maintains user workspaces these personal folders are not
specifically for the storage of GIS projects and data. The creation of a centralized
user directory will permit: projects to be saved on the server for efficient backups,
the sharing of project files, and simple and fast navigation of user directories.
Security can be easily managed through Windows NT/UNIX operating systems.
Again this should be a verbose directory structure that facilitates the location of
user directories (Figure 6). One possible configuration of this directory is as
follows:
Bureau and/or District Subdirectories
o Department Subdirectories
 User Directories
Project Directories
FIGURE 6: MDPD GIS User Directory
20

21. Once these issues have been resolved the new hierarchical directory structure
must be mapped to the same drive letter for all users. This is necessary because
ArcView saves links to spatial data in its project files. If a user maps this server to
a different path ArcView will be unable to locate the file and begin a series of
queries in which the user identifies the location of the pertinent data set. This
redirection is not difficult but very time consuming with the more complicated
projects requiring several minutes to redirect. It is for this same reason that GIS
user directories are needed since this encourages users to store additional data
files on the server in their own personal GIS directories which is preferable to
storage in a local drive.
Recommendation 7: We recommend that MDPD create and maintain a
hierarchical user directory structure for future GIS users.
3.2 Data Load Time
Although this directory structure will increase the efficiency of data navigation it
does not address the actual loading of the data into ArcView. In most cases, load
time will not be an issue, however, at remote locations or for PCAS with slow
machines further enhancements will need to implemented. Load time testing
results from the Carol City District Station known to have slow network
connectivity showed that most data load times at this station are unacceptable
21

22. (Table 3). Although we have already recommended that the crime data sets be
stored in SDE the data sets are presented here to show the relative load time
required for files of different sizes. Unfortunately, at remote locations most of the
County’s other shape files will suffer from this same delay.
Table 3: Carol City District Load Time Testing Results Using an Average Transfer Rate of
9
232,991 bytes/sec
Shape File File Size (Bytes) Load Time (sec) Load Time (min)
acrimes.shp 185,531,101 831 14
au.shp 12,377,004 55 1
aut.shp 12,377,004 55 1
auto.shp 11,914,222 53 1
burglary.shp 22,774,864 102 2
cpt.shp 2,876 <1 <1
ntar.shp 135,207,571 605 10
robbery.shp 2,485,350 11 <1
subject.shp 12,308,504 55 1
targeted.shp 39,979,080 179 3
vehicle.shp 36,921449 165 3
Dade_av.shp 36,390,843 163 3
Lot.shp 216,770,638 970 16
3.2.1 Server Based Processing Solution
One solution is to use MDPD’s Citrix server processing technology. On the
server, this technology has the unique ability to separate application logic from
the user interface. On the client users see and work with the application's
interface, but 100% of the application executes on the server (see Appendix C for
literature). A demonstration of this technology using Citrix and ArcView can be
found at the following URL:
http://eslims.esri.com
The procedure for enabling the Citrix client is as follows:
1. Click on the WTS Demos link.
9
A transfer rate of 232,991 bytes/sec was derived by timing the download of the Robberies
shape file 2,485,350 bytes which necessitated a 15 seconds to load and the road centerline file
36,390,840 bytes and necessitated a 150 seconds to load. These transfer rates of 223,377 and
242,605 where averaged to produce the transfer rate used in the table of 232,991 bytes/sec.
22

23. 2. Go down the page and click on the Citrix Icon (red & white) to download
and install a small plug-in. You only need to do this the first time -- once
per machine.
3. Once that is done click on the WTS Login link.
4. Then use the following user name and password:
Username: demo
Password: esri_wts
The advantages of this technology is that the data would be local to the server so
data load times would be significantly reduced and significant cost savings may
be realized in future distribution of GIS technology. As an example it may be
possible to move those ArcView licenses at the Inter-coastal and Coral City
District Stations to a local server running this technology these licenses would
then be available not just to these stations but to all MDPD. Some
disadvantages to this technology include the cost of a server to host this
technology. Additionally, although 100% of the processing is done on the server
PCAS workstations would still need to be top of the line in processing power in
order for this technology to function as smoothly as possible. Tests using the
above demo site have shown that even on a 750MHZ machine there is
considerable window “skipping” and “jumping” using this technology. One
possible disadvantage of this technology is that in order to print out maps the
server would have to transfer print or plot files to the client workstation.
The following is presented to give the reader an example of the hardware and
software used in a Windows Terminal Server implementation and is not to be
construed as a system architecture recommendation for MDPD.
“Data General AViiON 3800
Quad 700 MHz Pentium III Xeon processors (1 MB L2 cache)
2 GB RAM
Dual 18 GB 10K RPM SCSI drives (RAID 1)
Windows 2000 Advanced Server, SP1
Citrix MetaFrame 1.8, SP2
Citrix Feature Release 1
Citrix NFuse 1.5 MetaFrame Server Components
ArcInfo 8.0.2, Patch 1
ArcView GIS 3.2a” 10
3.2.2 Advanced Data Storage Solution
A parallel solution is the enabling of technology to serve the data to users in a
piecemeal fashion. Currently the County stores its property layer inside of SDE
and other large datasets could also be implemented in this format. The
10
ESRI’s Technology Demo Portal at http://eslims.esri.com/default.htm
23

24. advantage of this solution is that the technology and expertise already exists in
house. One possible disadvantage involves performance hits on the SDE server
if more data sets are incorporated which may affect the performance of SDE in
serving data to MDPD staff.
3.2.3 Data Subset Solution
One of the most common requests made by PCAS during the needs analysis
was the creation of subset data sets containing features just for their districts.
This solution would involve the creation of subset district data sets for those
shape files requiring longer load times than one minute. If districts continue to
experience delayed load times these subset district directories could be copied
by district PCAS to their local computer drives at the beginning of each business
day. The disadvantages of this option include that it would require several batch
processing jobs and the inevitable problems related to their execution. In the
worst-case scenario not all data sets may be available for PCAS the following
day because of patch processing issues.
Recommendation 8a: Use server processing technology to provide GIS
capabilities to district stations with slow bandwidth connections
Recommendation 8b: Enable access from ArcView to the property layer
currently stored in SDE.
4.0 Implementation
In order to measure the success of a full ArcView GIS and CrimeView Extension
implementation a pilot study in one district should be conducted. The selected
district should be the district in which most of the problem should be
encountered. The optimal district should have outdated equipment, slow
bandwidth connections, possess no general GIS or specific ArcView GIS training.
Recommendation 9: Conduct a pilot study using one district on the
feasibility of making ArcView GIS and CrimeVIew the default GIS
Mapping/Analysis application for PCAS.
4.1 Train ArcView Users
Either ITD or MDPD should develop an ArcView training program for PCAS
users. Assuming a class size of about 15 and one class per week 100 crime
analysts could be trained in about 2 months. One of the benefits of the current
PCAS structure is that most bureaus and district stations have on the order of
five PCAS which should result in more successful ArcView training do to
knowledge pooling at these locations. It is certainly true that should all PCAS be
24

25. trained in the use of ArcView not all of them will be successful users of the
software, however, it is likely that in most bureau/district offices one or two users
will become highly proficient in its use and it is these users which will make this
endeavor successful. However, in order to ensure successful training the
infrastructure changes mentioned above should be implemented in order to
facilitate access to the County’s spatial data. In addition, users should be
provided with either an ArcView skeleton project or supplied with map templates
for creating COMPSTAT maps.
Recommendation 9: Provide ArcView users with a crime analyst extension
in the form of CrimeView.
Recommendation 10: Train PCAS users in basic GIS principles, the
importance of reject processing, ArcView GIS and CrimeView.
3.2 GIS Users at MDPD
GIS Users at MDPD can be grouped into:
Public – These users would appreciate the ability to browse and produce
maps of crimes. Currently there is no delivery system to provide these
users with spatial information.
General Staff – These users include regular police officers, secretaries
and others not included below. These users could benefit from the ability
to browse and produce maps of crimes. Currently there is no delivery
system to provide these users with spatial information.
Command – These users include captains, chiefs, lieutenants, sergeants
and others involved in the distribution of resources. These users would
benefit from the ability to browse and produce maps of crimes. Currently
there is no system for these users to browse spatial data and mapping
needs are satisfied through requests to PCAS.
PCAS – These users include about 100 Crime Analyst distributed
throughout the County at Bureaus and District Offices. On average there
are about five PCAS assigned to each Bureau and District Office.
Currently these users are unable to browse GIS data and use the GIS
Mapping Application for the creation of COMPSTAT maps. These users
have a need for more robust data creation, manipulation and analysis
tools than are provided through the GIS Mapping Application.
Professional GIS – Currently there are no professional GIS users at
MDPD, however, in developing a GIS System for MDPD these users will
need to exist. The role of these users should be to advance and promote
the use of GIS within MDPD. In order to advance the use of GIS these
25

26. users should have as their primary roles: 1) to serve as MDPS’s spatial
data repository experts and 2) serve as GIS liaisons to bureaus or district
lacking their own expertise. In order to promote the use of GIS these users
should advance the position of a GIS on every desktop and at least one
highly trained PCAS at each bureau and district.
The current needs and delivery systems are provided in Table 4 below.
Table 4: GIS Users, Needs and Current Delivery Systems
Users GIS Needs Current Delivery System
Public Data Browsing None
Mapping None
General Staff Data Browsing None
Mapping None
Command Data Browsing None
Mapping PCAS
PCAS Data Browsing None
Mapping GIS Mapping Application
Data Creation None
Data Manipulation None
Data Analysis GIS Mapping Application
Professional GIS Data Browsing None
Mapping None
Data Creation None
26

27. Data Manipulation None
Data Analysis None
Data Management None
3.2.1 ArcExplorer
ArcExplorer is ESRI’s free data browser that all users should be able to use to
browse spatial data and geocode. This software could function as a secondary
system for fulfilling the needs for the General Staff and Command audiences as
well as providing a secondary method of implementing a “GIS on every desktop”
technology policy. MDPD should consider making ArcExplorer software standard
on all MDPD computers just as MS Word and Excel software is currently
distributed.
3.2.2 CrimeViewIMS
MDPD has requested that an Intranet/Internet GIS Analysis/Mapping platform be
evaluated as a delivery system for MDPD audiences. Internet/Intranet based GIS
mapping is still a new medium with all software existing as early releases (ESRI’s
ArcIMS 3, AutoDesk MapGuide 5, and MapInfo’s MapExtreme 3). This is even
more true of Internet/Intranet based GIS Crime Mapping with only The Omega
Group’s CrimeView IMS software currently at version 2 being available.
One of the benefits of this technology is the reduced cost of distribution. These
systems are usually priced per server processor, that is, a fixed price is paid
regardless of the number of users that hit a licensed processor. This medium is
also ideal for the implementation of a “GIS on every desktop” technology policy.
This technology could server as the primary GIS delivery system for the Public
and General Staff, and as a secondary delivery system for Command. There
exist some problems in the use of this technology to replace ArcView generated
COMPSTAT maps in that it may be difficult to implement continuous surface
maps from an Intranet/Internet application. According to the Omega Group
CrimeVIewIMS will have 80% - 85% of the standard CrimeView query
functionality. This may be sufficient to move some analysis functions from
ArcView to an Intranet platform. An ideal solution may be to implement
CrimeView IMS as is and then modify portions of its Arc Extensible Markup
Language (AXL) which is mostly JavaScript Extensible code to enhance its
interface for COMPSTAT mapping. Implementation of this technology for sites
already possessing ARC/IMS is around $10,000 while full installations requiring
ArcIMS, CrimeView IMS and onsite customer support runs from $18,000 to
$20,000. The ESRI Demo ArcIMS server system description is as follows:
The Omega Group has established a demonstration site for CrimeViewIMS
where the software maybe evaluated a the following URL:
27

28. http://www.microps.com/website/CVIMS_HTML/default.htm
The following is presented to give the reader an example of the hardware and
software used in an ArcIMS Server implementation and is not to be construed as
a system architecture recommendation for MDPD.
“Data General AViiON 3800
Dual 700 MHz Pentium III Xeon processors (1 MB L2 cache)
1 GB RAM
Dual 18 GB 10K RPM SCSI drives (RAID 1)
Windows 2000 Advanced Server, SP1
ArcIMS 3.0 (Application Server and Spatial Server)” 11
Recommendation 8: Implement CrimeView IMS and install ArcExplorer on
all MDPD computers.
Recommendation 9: Modify CrimeView IMS to better support MDPD
COMPSTAT Mapping.
3.2.7 ARC/INFO
ARC/INFO is ESRI’s Professional GIS platform and serves the professional GIS
group by performing higher end GIS tasks involved in the creation, manipulation,
modeling and storage of spatial data. Appropriation options here are to purchase
a primary license for ARC/INFO at a cost of $20,000 that entitles MDPD to
receive Tech Support and also send one representative to the yearly ESRI
Conference. Alternatively, it may be possible to purchased a secondary license
through ITD at a cost of $10,000 without support or conference attendance
rights.
Recommendation 14: MDPD should purchase a primary ARC/INFO license.
3.2.8 SDE
Please view section 3.2 Spatial Database Engine Solution to the Timeliness
Problem for more information.
4. Conclusion
This document began by examining the three primary functions of PCAS users,
namely, Computer Statistics (COMPSTAT), special map projects and map
11
ESRI’s Technology Demo Portal at http://eslims.esri.com/default.htm
28

29. analysis and how the MDPD’s Crime Analysis System and ITD’s GIS Mapping
Application in conjunction support these functions. Our needs analysis revealed
that these functions are not well supported by the applications because of
accuracy and timeliness problems. Our needs analysis also revealed that in
addition to these problems there is a far greater need for GIS functionality than
the GIS Mapping Application can support.
Our most important recommendations include the implementation of Live
Complaint Desk Geocoding and our recommendation on implementing SDE in
order to simplify data generation and halt the reliance on our 48-Hour
Subsequent Reject Process.
Our recommendations to solve the unmet needs of MDPD staff included the
adoption of the technology policy of “a GIS on every desktop”. It was also
recommended that this policy be implemented through ArcExplorer,
CrimeViewIMS and server processing technologies. It was also recommended
that MDPD commit to making ARCView GIS the primary GIS Analysis/Mapping
tool and to provide PCAS users with additional functionality through ArcView
Spatial Analyst, CrimeView and CrimeViewIMS. We also recommended that a
simpler and more intuitive data directory structure be develop to facilitate access
to GIS data by PCAS users.
The implementation of these recommendations will solve the accuracy and
timeliness problems, maximize the use of MDPD’s current GIS components,
introduce new components, provide coverage for every need of every audience
at MDPD (Table 5), and promote the accurate and timely reporting of intelligence
and the relentless follow-up and assessment of crime.
29

30. Table 5: GIS Users, Needs and Proposed Delivery Systems
Users GIS Needs Proposed Delivery Systems
Primary Secondary, Tertiary and
Quaternary
Public Data Browsing CrimeView IMS
Mapping CrimeView IMS
General Data Browsing CrimeView IMS ArcExplorer
Staff Mapping CrimeView IMS ArcExplorer
Command Data Browsing CrimeView IMS ArcExplorer
Mapping PCAS CrimeView IMS, ArcExplorer
PCAS Data Browsing ArcView GIS CrimeView, CrimeView IMS
Mapping ArcView GIS CrimeView, CrimeView IMS
Isopleth Citrix/Spatial Analyst CrimeView
Data Creation ArcView GIS CrimeView
Data Manipulation ArcView GIS CrimeView, CrimeView IMS
Data Analysis ArcView GIS CrimeView
Professional Data Browsing ARC/INFO ArcView, CrimeView,
GIS CrimeViewIMS
Mapping ARC/INFO ArcView, CrimeVIew,
CrimeViewIMS
Data Creation ARC/INFO
Data Manipulation ARC/INFO
Data Analysis ARC/INFO ArcView, CrimeVIew,
CrimeViewIMS
Data Management ORACLE-SDE
30

31. Appendix A: Recommendation Sign-Off Sheet
PHASE 1 Recommendations: Solutions to Accuracy Problem
Recommendation Priority Resources Time Sign-off
1: Provide PCAS with an ½ SGAP
Enhanced VB/MO 1 OSP
Geocoding Engine. MDPD
H
Ira S. Feuer
MDPD Bureau Commander
2: Develop an aggressive MDPD
program to geocode all
rejects as far back as 24
months. H
Ira S. Feuer
MDPD Bureau Commander
3: Purchase Positron’s ½ SGAP
PowerMap application
train staff to process
rejects and implement
any of other solutions as H Ira S. Feuer
necessary to ensure that MDPD Bureau Commander
rejects are reduced to a
minimum.
31

32. PHASE 2 Recommendations: Solutions to Timeliness Problem
Recommendation Priority Resources Time Sign-off
4: MDPD should begin by ½SGAP
using the SDE at ITD.
H
Ira S. Feuer
MDPD Bureau Commander
PHASE 3 Recommendations: Solutions to Improve Mapping and Reporting
32

33. Recommendation Priority Resources Sign-off
5: Maintain the GIS ½ SGAP
Mapping application until
suitable replacement
software is implemented H
and found to be Ira S. Feuer
successful. MDPD Bureau Commander
6: Implement Spatial Data ½ SGAP
Standards in a production 1 OSP 240 h
hierarchical data directory
structure for the storage H
of shape files, on the Ira S. Feuer
shape files stored in this MDPD Bureau Commander
directory and the data
layers within SDE.
7: We recommend that ½SGAP
ITD or MDPD create and
maintain a hierarchical
user directory structure H
for future GIS users.
Ira S. Feuer
MDPD Bureau Commander
8: Implement CrimeView ½ SGAP
IMS and install
ArcExplorer on all MDPD
computers. M
Ira S. Feuer
MDPD Bureau Commander
11: Establish ArcView ½ SGAP
GIS as the default GIS
interface for PCAS users
and by train PCAS in its M
use. Ira S. Feuer
MDPD Bureau Commander
8a: Use server ½ SGAP
processing technology to
provide GIS capabilities
to district stations with
slow bandwidth Ira S. Feuer
connections. M MDPD Bureau Commander
8b: Enable access from
ArcView to the property
layer currently stored in M
SDE. Ira S. Feuer
MDPD Bureau Commander
PHASE 3 Recommendations: Solutions to Improve Mapping and Reporting
Recommendation Priority Resources Sign-off
12: In support of isopleth ½ SGAP
33

34. mapping implement
ArcView Spatial Analyst
through Citrix’s L
WinFrame technology.
Ira S. Feuer
MDPD Bureau Commander
13: Provide ArcView ½ SGAP
users with a crime analyst
extension in the form of
CrimeView. L
Ira S. Feuer
MDPD Bureau Commander
9: Modify CrimeView IMS ½ SGAP
to better support MDPD
COMPSTAT Mapping.
L
Ira S. Feuer
MDPD Bureau Commander
14: MDPD should ½ SGAP
purchase a primary
ARC/INFO license.
H
Ira S. Feuer
MDPD Bureau Commander
34

35. Appendix B: Interview Questionnaire
As part of the Phase I – Needs Assessment an interview questionnaire
(Appendix A) was conducted from 19 October 2000 to 9 November 2000. This
questionnaire was targeted at the Police Crime Analyst Specialists (PCAS) at
both MDPD headquarters and district offices and inquired into the present GIS
Mapping System in order to identify those limiting factors that should be
corrected in the new GIS Mapping Intranet Application.
A total of 18 staff members where interviewed as follows:
Table 1: Users Interviewed
Name Position Station
1 Tami Bush PCAS Headquarters
2 Mike Ronezkowski Lieutenant Robbery Bureau
3 Halli Gomez Intelligence Analyst Sex Crimes
4 Vanesa Perez Intelligence Analyst Sex Crimes
5 Dante Fonseca Intelligence Analyst Airport District Station
6 Murean Shank PCAS Carol City District Station
7 Michael Gordon PCAS Cutler Ridge District Station
8 Sherry Smyly PCAS Cutler Ridge District Station
9 Danial Franquiz PCAS Doral District Station
10 Jorge Mackenzie PCAS Doral District Station
11 Lora Diaz Sergeant Hammock District Station
12 Anelis Gutierez PCAS Hammock District Station
13 Karen Gonzalez PCAS Hammock District Station
14 Yoli Rivera PCAS Intercoastal District Station
15 McCord Sergeant Northside District Station
16 Claire Leonard PCAS Northside District Station
17 Maceo Pickett PCAS Kendall District Station
18 Maria I. Trelles PCAS Kendall District Station
Most analyst sited are new and most, if not all, have very little or no experience
with native ArcView and definitely no formal training. The reason for this is that
most coordinating staff members have passed their responsibilities dealing with
the GIS Mapping Application to junior staff. In general, analysts are unaware of
their data and often fail to realize that “dots” are not analysis and that all cases
are not visually depicted.
Following are the summarized results of the questionnaire by section.
Section 2
In this section users where asked to: Briefly describe the most frequently
35

36. performed tasks in your job that involve maps or analyzing spatial relationships in
order of importance and state the frequency with which they are performed.
PCAS reported that the three most common tasks that involve maps or analyzing
spatial relationships are: Computer Statistics (COMSTAT), special map projects
and map analysis. The essence of the COMPSTAT process can be summarized
briefly as follows: collect, analyze and map or tabulate crime data and other
essential police performance measures on a regular basis and hold police
managers accountable for their performance as measured by these data.
Special map projects represent the collection, analysis and mapping of
information that is usually area and/or case specific. The frequency by which
each of these tasks resulted in a map product was reported as high as 5/week 12
for COMPSTAT functions and 15/week13 for special map projects.
Map Analysis involves the collection, analysis and mapping of information for the
purpose of finding patterns, identifying hot spots, and general spatial data mining
activities. These map products are usually for PCAS, investigators and staff use
only and usually do not become part of the general distribution of COMPSTAT or
special map projects although in many cases they are essential to the production
of these other products.
These map products are predominantly dot density and/or grid maps that depict
targeted crimes 94% of the time and non-targeted crimes 6% of the time.
Section 3
Question 3.1. Do you require the Tabular Reporting features of the GIS Mapping
application to perform your work?
No was the answer of 100% of the users. This response is attributable to: the
GIS Mapping to CAS System record discrepancy and that most if not all users
where unaware that the function even existed.
Question 3.2. Do you require the Mapping features of the GIS Mapping
application to perform your work?
Yes was the answer of 67% of the users. PCAS use the system to print either dot
density. Dot density maps are then compared to tabular data from CAS and are
corrected through manual cartographic methods or through the geocoding
functions built into the GIS Mapping Application
12
Reported by PCAS Michael Gordon at the Cutler Ridge District Station.
13
Reported by PCAS Maceo Pickett at the Kendall District Station.
36

37. No was the answer of 33% of the users. PCAS responding in the negative did so
because of infrastructure limitations and/or a functional knowledge of ArcView.
Infrastructure limitations included:
Slow bandwidth connections and antiquated computer equipment manifest
themselves as slow system performance. This is especially the case at the
more remote locations such as the Inter-coastal and Carol City District
Stations.
In some instances, PCAS have stated that record discrepancy alone is
sufficient to warrant the application useless.
Non-functional output devices inhibit the use of the application and exist in
the Sex Crimes Division, Inter-coastal and Northside District Stations.
Lastly, although a base map for the Airport exists considerable
manipulation of this data set is needed before it can be used to perform
geocoding and mapping functions.
PCAS who have a functional knowledge of ArcView stated that they do not use
the GIS Mapping Application because they find that ArcView “is a better product
than GIS Mapping”14 and they find ArcView to be a less restrictive environment
from which to create maps.
Question 3.3. Please define those functions of the GIS Mapping application that
you find to be user friendly.
55% of the users found some function of the GIS Mapping application to be user-
friendly. The most frequent comments included that in general all functions are
easy to use.
Question 3.4. Please define those functions of the GIS Mapping application that
are inflexible or limiting in nature and explain why.
45% of the users found some function of the GIS Mapping application to be
inflexible or limiting and did so for the following reasons:
First, the record discrepancy problem results in “inaccurate” maps that
require the employment of tedious manual cartographic methods in order
to depict the accurate number of cases.
Second, PCAS who receive special map projects and try to create non-
standard maps are unable to create these maps with ease. Some of the
more typical problems include: incorrect placement of crimes at
intersections; incidents at the same location result in overlapping crimes
14
Sergeant McCord at the Northside District Station and Lieutenant Ronezkowski at the Robbery
Bureau
37

38. that map as a single point; map extents often zoom out to a system
predefined scale when printing and the inability to use different marker
symbols.
Third, the system performance is so slow that the application can’t be
used. System performance is related to network connectivity and the
amount of data transmitted. In the case of the districts a common
statement is that the system loads too much data.
Question 3.5. Please define those functions that are not performed by the GIS
Mapping application that are required for you to be able to do your work?
The findings here are the same as for Question 3.4 above.
Question 3.6a. Would additional pre-defined menu options facilitate your use of
the GIS Mapping application?
Yes was the answer of 42% of the users.
Question 3.6b. If yes please define.
The most frequent comment was that if more predefined menu options for
specific queries where available it would help by eliminating some of the steps
that currently have to occur in order to create a map.
Question 3.7. What percentage of your queries can be conducted with the 12
months worth of data available on the system assuming there was no data
discrepancy problem?
95% - 100% was the response from most users; however, some PCAS reported
this percentage to be from 10% - 60%15 because of reports requiring year-to-year
comparisons. Year-to-year comparison reports are common to all divisions and
district stations and require 24 months of data. This data is presently extracted
from CAS because it is not available through the GIS Mapping Application,
however, even if it were available the record discrepancy problem would require
extraction from CAS.
Question 3.8. What percentage of your queries cannot be conducted with the 12
months worth of data available on the system?
0% - 5% was the response from most users and this was attributed to special
map projects that require the use of data beyond this 12-month period. With
15
Reported by PCAS Murean Shank at the Carol City District Station, Intelligence Analyst Dante
Fonseca at the Airport District Station.
38

39. regard to reports with year-to-year comparisons this percentage ranges from
40% - 90%.
Question 3.9. What percentage of your work involves targeted signals?
94% was the average response of users and predominantly represents dot
density and/or grid maps.
Question 3.10. What percentage of your work involves Non-targeted signals?
6% was the average response of users and predominantly represents dot density
and/or grid maps.
Question 3.11. What targeted queries do you perform that require subject, victim
and vehicle information?
100% of users responded with all targeted crimes.
Question 3.12. Are there any queries that do not require any subject, victim or
vehicle information?
100% of users responded with all non-targeted crimes.
Question 3.13a. What percentage of your work involves specific map queries?
94% was the average percentage reported by the users.
Question 3.13b. Which queries are they?
The most common answer to this question was queries to targeted crimes.
Question 3.14a. Do you utilize maps supplied by the Map Gallery?
Yes was the answer of 58% of users.
Question 3.14b. Should other maps be supplied?
39

40. Yes was the answer of 25% of the users and included additional maps such as:
specific area maps, those showing parcels, lakes and other features.
Question 3.15. Do you find the Charts functionality of the GIS Mapping
application useful in performing your work?
No was the answer of 100% of the users.
Question 3.16a. If standard information queries were predefined for selection
would that assist you in performing your work?
Yes was the answer of 67% of the users and is attributed to the wish to reduce
the number of selections needed in order to create a map.
Question 3.16b. Could you specify these?
In general, most PCAS believe there is too much drilling down of the data within
the Map Designer and that if a predefined query were available this might help
speed up the mapping process. These predefined queries could facilitate any of
the steps that currently involve menu selection such as the selection of districts,
crimes, dates, times and themes.
Section 4
Question 4.1a. Does the system performance hinder your use of the GIS
Mapping application?
Yes was the answer of 75% of the users.
Question 4.1b. Please explain.
The most frequent comments included that the system performance was too
slow. This comment is attributable to everything from opening the application,
doing queries, to printing maps. Additional comments included those issues
having to do with the record discrepancy as well as the limited editing capabilities
of the application.
Question 4.2a. Who do you contact to resolve GIS Mapping system problems?
Lourdes de la Nuez was the answer given by most users.
40

41. Question 4.2b. Are you satisfied with this support?
Yes, was the answer of most users.
Question 4.3a. Where do you go for support in the use of the GIS Mapping
application?
Lourdes de la Nuez was the answer given by most users.
Question 4.3b. Have your questions been readily addressed?
Yes, was the answer of most users.
Question 4.4a. Have you submitted any service requests for modifications to the
GIS Mapping application based upon your experience using it?
No was the most common answer to this question.
Question 4.4b. If yes, have they been completed?
Not Applicable.
Question 4.5. Do you feel your workstation configuration hinders you from
effectively using the GIS Mapping application?
No was the answer of 77% of the users.
Yes answers are attributable to slow operating workstations and/or non-
operational output devices.
Section 5
Question 5.1. How proficient are you in using GIS software?
Beginner was the most common answer.
Question 5.2a. Do you own and use the GIS ARCVIEW Users Manual?
In all except one instance users were unaware of the existence of this manual.
41

42. Question 5.2b. If no, why?
The most common response was that the manual was never made available.
Question 5.3a. Do you use the HELP button of the GIS ARCVIEW application?
No was the answer of 100% of the users.
Question 5.3b. If no, why?
The most common response was that the user was never trained in the use of
ArcView.
Question 5.4a. Have you had any formal training on the GIS ARCVIEW
application?
No. With only one exception users had no formal training in ArcView.
Question 5.4b. If yes, where you satisfied with the level of training received?
Users where not trained.
Question 5.4c. How long ago did you receive this training?
Users where not trained.
42

43. Appendix C: Isopleth Maps
43

44. Appendix D:Timeline
44