Oakland City Council
July 19, 2022

1 OAKLAND POLICE DEPARTMENT

Surveillance Impact Report:

CrimeView Product Suite

A. Description: The CrimeView Product Suite and Function

The CentralSquare1 geospatial CrimeView product suite has been the core technology resource for the Oakland Police Department (OPD) crime analysts since 2008. OPD law enforcement personnel and crime analysts have been using CrimeView software for several years. The CrimeView product suite comprises three geospatial applications.

1. CrimeView Desktop is a specialized application for dedicated crime analysts. With this unique software application, analysts can connect to the City’s Geographic Information Systems (GIS) ESRI (GIS software vendor) enterprise software ArcGIS (see Attachment A for the CrimeView Desktop Operating Manual). Integration with the City’s ArcGIS software is a feature that only CentralSquare offers. The connection of CrimeView Desktop with the City’s GIS system lets analysts create detailed geographical reports. With this information, police commanders and investigators can make informed, data-driven decisions on how best to reduce crime in Oakland.

2. CrimeView Analytics is an upgrade from the current CrimeView Dashboard product.2 This browser-based application connects with OPD incident data to let police officers and commanders access useful geographical data visualizations. CrimeView Analytics lets OPD personnel view data by crime or penal code, by police beat or area, and by time of day and day of week. These data views provide useful crime pattern analysis for officers, OPD commanders, and crime analysts. The CrimeView Analytics upgrade will allow for greater flexibility within the application’s paradigm, including support for on-demand queries, scheduled report generation, threshold alerting, and density maps.

3. Crimemapping.com is the public facing application, providing the public with a map-based view of crime incidents in the City of Oakland.3 This application complements the City’s already existing IDT-based CrimeWatch open-data initiative.

1 CrimeView was originally created by the Omega Group, which was later purchased by Tritech. TriTech merged with Central Square in Sept. 2018.
2 An online manual for the CrimeView Analytics can be found here.

3 An online manual for the CrimeMapping.com can be found here.

2 B. Proposed Purpose

CentralSquare’s CrimeView product suite (see Attachment B CrimeView Analytics Overview) provides three core services for OPD: 1) a specialized license-based desktop application for crime analysts; 2) a web-based application for OPD personnel; and 3) a public facing geospatial application for the public.

The CrimeView product suite provides geospatial and temporal information, which in turn supports crime analysts’ efforts to provide relevant intelligence to OPD’s law enforcement personnel. This precision data lets commanders and officers target environments where their intervention results in the most positive impact possible. This data-driven approach to command decision making supports OPD’s intelligence-led and precision-based policing initiatives. OPD’s data-driven and intelligence-led policing initiatives let OPD minimize the impact of policing across Oakland communities – while still providing police services.

1. CrimeView Desktop – This application is an extension to ESRI’s ArcGIS application. This extension lets crime analysts map OPD’s crime incident data and use ArcGIS’s spatial analysis tools to create detailed reports for OPD officers, investigators, and commanders. This application is only used by crime analysts and requires an advanced working knowledge of ESRI’s ArcGIS application and its geospatial analysis tools.

The generated reports provide critical information about crime from a geospatial perspective in an easy-to-view format, including temporal information, which assists in resource deployment and other operational decisions. This application is the workhorse of OPD’s Crime Analysis Section, letting analysts provide a depth and breadth of work that would otherwise be impossible. CrimeView Desktop streamlines the geospatial process, saving a huge number of staff hours. This lets analysts use their training and experience to interpret the results and provide critical analytical commentary to support the program’s findings.

2. CrimeView Analytics – This web-based application lets police officers and commanders access useful geographical data visualizations by crime or penal code, by police beat or area, and by time of day. These data views provide useful crime pattern analysis for officers, when a detailed, hand-built report may not be necessary. By giving OPD personnel the ability to perform simple visualizations on their own, they are empowered to make operational decisions when a dedicated crime analyst may not be available. Additionally, crime analysts can create snapshot views to give executive team members and area captains a high-level view of crime any time of the day.

3. Crimemapping.com – This application is the public-facing portion of the product suite. It provides a simple map-based view of crime. It is intended for general use; therefore, data is anonymized to protect the privacy of crime victims and the integrity of ongoing investigations. Members of the public can also see other jurisdictions that subscribe to the service and create their own alerts for areas they are concerned about. As mentioned previously, this application complements the City’s already existing IDT-based 3 CrimeWatch open-data initiative.

C. Locations where, and situations in which, the CentralSquare CrimeView product suite may be deployed or used.

The CrimeView product suite is separated into three different applications, so that different groups have access only to the application they are authorized to use.

1. CrimeView Desktop – Only crime analysts can use this application, which is an extension to ESRI’s ArcGIS desktop mapping application. This license- based software is installed only on devices solely used by crime analysts.

These computers are secured within the Police Administration Building (PAB) on floors and in sections that can only be accessed by an employee’s keycard. Each employee’s network profile is secured, and only authorized employees can access and use CrimeView Desktop.

2. CrimeView Analytics – Only OPD personnel can access this application.

OPD personnel are individuals who have undergone a complete background check and have fulfilled the California Department of Justice requirements for using computers on the OPD network. These requirements include, but are not limited to, a written test taken every two years on accessing the California Law Enforcement Telecommunication System (CLETS) and a state-mandated, four-hour in-person training covering the handling and release of confidential information. Everyone using CrimeView Analytics must have his or her own individual login and password; logins cannot be shared. The manager of the Crime Analysis Section personally approves and maintains the list of approved users. Information in CrimeView Analytics is considered internal confidential information, and it cannot be shared with the public – information in Analytics contains information that could compromise, if released, victim privacy and safety as well as compromise ongoing investigations.

3. Crimemapping.com – Any member of the public can access this application.

The information displayed in this geospatial application has been formatted to allow the public an anonymized view of crime in Oakland, which protects the privacy and safety of victims and the integrity of ongoing investigations.

Table 1 below provides 2020 and 2021 Part 1 Crime Data. This data illustrates the high levels of both violent crime and property crimes that occur in Oakland. OPD uses CrimeView Desktop and CrimeView Analytics to better strategize ways to confront the high levels of crime illustrated in this data table. These crimes occur throughout the City, although there are parts of the city that unfortunately see much higher concentrations of violent crime. The CrimeView Desktop and CrimeView Analytics products help OPD commanders and investigators efficiently leverage limited resources to confront areas where crime is most concentrated.

4 Figure 1 below is a screenshot taken from CrimeMapping.com on March 21, 2022. The CentralSquare product suite includes this public-facing website.

Members of the public can use this website to view crime maps and filter by crime type and locations within the City.

Part 1 Crimes
All totals include
attempts except homicides
01-01-2020
through
12-31-2020
01-01-2021
through
12-31-2021
Year-to-Date
% Change
2020 vs. 2021
3-Year
Year-to-Date
Average
YTD 2021
vs. 3-Year
YTD Average
Homicide - 187(a) 102 124 22% 100 24%
• Homicide - all other * 7 10 43% 7 50%
Aggravated Assault 3,315 3,559 7% 3,206 11%
• With Firearm 499 599 20% 462 30%
Rape 217 158 -27% 193 -18%
Robbery 2,417 2,693 11% 2,641 2%
Burglary Total 8,689 10,197 17% 11,291 -10%
• Auto 6,221 8,179 31% 8,921 -8%
• Residential 1,247 1,055 -15% 1,370 -23%
• Commercial 958 670 -30% 750 -11%
• Other/Unknown 263 293 11% 249 18%
Motor Vehicle Theft 8,722 9,010 3% 8,071 12%
Larceny 5,974 6,186 4% 6,643 -7%
Arson 193 170 -12% 172 -1%
Total Part 1 Crimes 29,636 32,107 8% 32,324 -1%
5 Figure 1: Oakland Crimemapping.com Screenshot

D. Impact

The aggregation of data will always cause concern regarding the impact to public privacy. Data used in CentralSquare’s CrimeView product suite originates solely from internal OPD database sources – namely the current police records management system (LRMS), including its adjunct field-based reporting module (FBR) and the communications computer-aided dispatch (CAD) system.

The purpose of the CrimeView product suite is to provide geospatial and temporal information about crime incidents, arrests, and calls for service. It uses minimal

6 personal identifying information, and only in the two applications available to OPD personnel, who are bound by the strict confidentiality rules previously detailed.

The personally identifying information is sourced solely from internal OPD database sources and does not include information about an individual’s immigration status. Oakland residents who may not have a legal immigration status have a right to privacy. The California Values Act (SB 544) is enacted to ensure that (barring exceptions contained in the law) no state and local resources are used to assist federal immigration enforcement.

CentralSquare complies with all federal (FBI CJIS requirements), state (e.g., SB 54) and local laws (e.g., Oakland Sanctuary City Ordinance5) associated with use of collected law enforcement data. This includes, in the state of California and many individual jurisdictions, the prohibition on the use of facial recognition and the analysis of body worn camera video data.

E. Mitigations

OPD and CentralSquare use several strategies to mitigate against the potential for system abuse or data breaches.

System Mitigations

CentralSquare Technologies system provides security for customer data through a layered approach. CentralSquare uses CJIS-level security for storage and access as a best practice for managing customer operational data within. This security includes:

1. Access controls to the application.

2. Secure infrastructure hosted at the hosting facility.

3. Access limited to CentralSquare personnel with the required security approval. Analytics products, such as CrimeView and crimemapping.com, include data imported from their customers’ public safety systems (such as CAD and RMS).

The CentralSquare Cybersecurity Program Overview (see Attachment C) “implements a series of comprehensive physical and logical controls that align with the NIST Cyber Security Framework and standards to provide a secure, layered defense for all hosted information. CentralSquare maintains annual Payment Card Industry (PCI) and Statement on Standards for Attestation Engagements (SSAE18) compliance through a series of ongoing assessments and security testing performed by a PCI Qualified Security Assessor and AICPA auditor. Adherence to these standards ensures all controls are met specific to access, transmission, processing, and storage of data.”

The CentralSquare Cybersecurity Program overview also explains the framework for secure software development, vulnerability management, security incident

4 https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180SB54 5 https://oakland.legistar.com/LegislationDetail.aspx?ID=3701155&GUID=8153C1B0 -B9FC-4B29-BDDE- DF604DEDAEAD&Options=&Search=
7 response protocols, government-standard cloud solutions (including audit compliance standards), and regulatory compliance protocols. The CentralSquare Analytics Product Security Overview (see Attachment D) provides more security standards.

The City of Oakland-Central Square draft contract (see Attachment E) also provides language on the contractual security system commitments.

Safeguards in Alignment with Oakland and California Immigrant Legal Protections

CentralSquare’s CrimeView product suite is geospatial by design. Minimal personally identifying information is only available in CrimeView Desktop and CrimeView Analytics. Use of these two applications is restricted to OPD personnel only, within a specific context. Users can only access these applications if they have a legitimate law-enforcement need for the information.

Data used in CentralSquare’s CrimeView product suite originates solely from internal OPD database sources – namely the current police records management system (LRMS), its adjunct field-based reporting module (FBR), and the communications computer-aided dispatch (CAD) system.

Data Access Safeguards

Within the CrimeView Desktop and Analytics applications, OPD data cannot be accessed by anyone outside OPD. Additionally, OPD personnel using the CrimeView Analytics application must have a unique username and password, issued by the Crime Analysis Section manager.

Personnel Oversight

Department General Order (DGO) I 29: CRIME ANALYSIS SOFTWARE, explains that: “While personally identifiable information (PII) is included in the data, the purpose of the product suite is to identify geographical and temporal trends and patterns. The data is not used to look at individuals as suspects or victims of crime.”

This product suite does not contain a predictive component. It is used to assist experienced and trained crime analysts create informed analytical commentary supplemented by temporal and visual information. This information helps OPD commanders make sense of the tremendous amount of crime data generated in Oakland. Furthermore, CrimeView Desktop and CrimeView Analytics do not import external data – they only use OPD data that already exists in OPD’s internal systems.

Anonymization

Crimemapping.com is accessible by the public. Prior to any data being available via this application, it is anonymized to protect victim privacy and safety as well as the integrity of ongoing investigations.
8 F. Data Types and Sources

CentralSquare has created a file transfer protocol data feed to automatically acquire data into the CrimeView product suite. This data is currently limited to the police records management system (LRMS), including the adjunct field-based reporting module (FBR), and communications CAD system.

The process by which CrimeView manages and purges expired data is as follows:

• An SQL script is run against the CAD and RMS databases. • The output is written to a Parquet file and pushed to an S3 bucket in the AWS Government Cloud.
• The Parquet file is read, and the contained data is loaded to the CrimeView SQL database.
• The Parquet files may be kept for several months for troubleshooting purposes but are deleted at regular intervals to enforce data history trimming. • The CrimeView SQL database is read, and an Elasticube database is rebuilt entirely using the data from SQL. No prior data is retained in the Elasticubes. • Another synchronization script is run against the CAD and RMS databases to check primary keys and enforce the subscribed date range.

Any records in the CrimeView SQL database that are no longer in the source CAD and RMS database or are earlier than the subscribed date range are subsequently deleted from the CrimeView SQL database.

The following is an exhaustive list of datasets acquired by CentralSquare’s CrimeView product suite from OPD data sources:

Data Source
Collected
Collection
Status
Database
Location
Access Conditions
Arrests Active LRMS Only authorized OPD
personnel
Field Contacts Active LRMS Only authorized OPD
personnel
Incident Reports Active LRMS Only authorized OPD
personnel
Calls for Service Active CAD Only authorized OPD
personnel
Stop Data Active FBR Only authorized OPD
personnel
Traffic Accidents Active LRMS Only authorized OPD
personnel

The purpose of the CrimeView product suite is to provide a geospatial view of crime in Oakland. This information assists police personnel, executives, and commanders with resource distribution, operational decisions, and long-term strategies.

9 G. Data Security

CentralSquare constantly processes large streams of criminal justice information (CJI) and must comply with the provisions of the Criminal Justice Information Services (CJIS) Division of the Federal Bureau of Investigation (FBI), the FBI Security Management Act of 2003, and the CJIS Security Policy.6 CentralSquare, along with its partner at Amazon Web Services (AWS) Government have developed strong CJIS-compliant data security protocols.

Supporting documentation from CentralSquare is attached: CentralSquare’s Cybersecurity Program Overview and CentralSquare’s Analytics Product Security Overview.

a. Account Management – OPD personnel who use CrimeView Desktop must be seated crime analysts with sole access to their computer and the ArcGIS desktop application with the Desktop extension. OPD personnel who use CrimeView Analytics must have a unique username and password to access the application. The users have access to accounts that are created, deleted, and managed by a local administrator within OPD (the Crime Analysis Section manager), who has special access permissions to the system.

b. Amazon Web Services (AWS) Government Cloud Protocols – CrimeView cloud data is stored in Amazon Web Services (AWS) Government and encrypted at rest using Microsoft BitLocker. CrimeView Cloud deployments hosted in AWS Government provide encryption through BitLocker (certified FIPS 140-2 encryption components and Microsoft BitLocker FIPS140-2-Jan2017-Certs-2932-2933- 2934).

c. CrimeView is hosted from an Amazon Web Services (AWS) Government facility. Each facility meets the stringent FBI CJIS Policy standards and guidelines with the following protection features on site:
• Monitored by both fixed and pan-tilt/zoom security cameras • Protected by intrusion detection system
• Two-factor authentication required for building access • Biometric iris authorization required for data center access • Extensive pre-employment background investigation process • On-site building security and data center monitoring staffed 24/7/365.

d. User Authentication and Authorization - All authorized users must maintain and enter a valid user ID and strong password combination to gain access to the system. Passwords must be changed every 90 days.

e. Personnel Screening, Training, and Administration – CrimeView cloud access to implement and support the system is limited to personnel that have completed CentralSquare Technologies’ CJIS compliant security approval process:
• Access to the Cloud CrimeView infrastructure requires approved

6 https://www.fbi.gov/services/cjis/cjis-security-policy-resource-center 10 personnel to complete a layered secure login process that includes personally assigned passwords, advanced authentication to gain access to the CentralSquare Technologies network, and a secure access login to the applicable Cloud CrimeView domain, application, and SQL Server database.
• Pre-employment background check.
• Security-approved employees must successfully complete the CJIS On- Line Security and Awareness training and testing. Their certifications must be current and must be renewed every two years. In addition to CJIS required training, CentralSquare Technologies also does periodic training for security approved personnel on CentralSquare Technologies security policies.
• Criminal background checks have been completed on CentralSquare Technologies personnel as part of employee screening and by one or more law enforcement agencies (CentralSquare Technologies customers and, in some cases, state law enforcement agencies).
• CentralSquare personnel have been fingerprinted, and their prints have been submitted to one or more law enforcement agencies for a background check.
• Security approved personnel are the same personnel that are used for supporting customers with on-premises deployments of CAD, Mobile, RMS, and other CentralSquare products (including the CrimeView product suite).

H. Costs

A new proposed contract will cost the City $260,203.00 for the period of January 1, 2022, to December 21, 2026 (approximately $41,240 per year). The City of Oakland- Central Square draft contract (see Attachment D) provides specific contract terms; Attachment E provides exact costing details.

I. Third Party Dependence

OPD relies on CrimeView’s product suite as a private company to provide OPD with a robust geospatial application environment. The entire product suite, especially CrimeView Desktop, is unique and cannot be mirrored with any internal OPD system.

Section G above explains that Central Square uses Amazon Web Services (AWS) Government for cloud-support services, and that AWS Government has developed strong CJIS-compliant data security protocols. Additionally, Crimemapping.com is hosted in the Microsoft Azure non-government cloud, where only non-sensitive data is stored. Crimemapping.com records are first transmitted to the CrimeView AWS Government cloud then sent to the Crimemapping.com environment in Microsoft Azure.

Hosted data at AWS and Azure is encrypted through Microsoft BitLocker and Microsoft FIPS 140-2 compliant encryption is used for data in transit (the same encryption components as CrimeView). Furthermore, CentralSquare also uses SecureLink Remote Access software (www.securelink.com) for remote access. SecureLink meets service level agreement (SLA) requirements and meets multiple regulatory requirements (such 11 as FIPS and the FBI CJIS Security Policy), while maintaining customer network security.

J. Alternatives Considered

No other product or company can realistically provide OPD with the advanced geospatial functionality required by crime analysts who are creating detailed reports for OPD police personnel.

The CrimeView Desktop extension to ESRI’s ArcGIS is unique. No other vendor provides this tool. The CrimeView Desktop application is crucial to the sustained operations of the Crime Analysis Section, letting them focus on analytical observations and expanding the number of work products distributed to key OPD personnel.

K. Track Record of Other Entities

Many other police agencies in the U.S. use the CrimeView product suite (a complete list is not available from the vendor). OPD is aware that the following agencies use the software:
• San Diego Harbor Police. This agency runs an intelligence-led policing strategy using CrimeView Analytics;
• OPD staff has personal experience using the CrimeView product suite while employed by the City of Richmond, CA, as the individual analyst. Having this powerful geospatial application meant that one analyst could serve the entire agency with timely actionable geospatial and temporal information; • Bedford Police Dept. (Texas);
• St. James Parish Sheriff’s Office (Louisiana); and
• Arizona State University Police Dept. (Arizona).

Attachments

A. Omega Desktop Manual
B. CrimeView Analytics Overview
C. CentralSquare Cybersecurity Program Overview
D. CentralSquare Analytics Product Security Overview
E. City of Oakland-Central Square draft contract
F. Contract Pricing Document
Omega Desktop is a suite of tools created by The Omega Group to work within ESRI’s ArcGIS application. Omega Desktop provides mapping solutions designed to aid decision makers in law enforcement, public safety and education agencies.

The different parts of Omega Desktop include:

CrimeView
CrimeView is an ArcMap extension that provides access to crime data for both novice and advanced users. Novice users, with minimal training, can easily navigate the features of CrimeView by using the simple interface provided.

An advanced user can take advantage of the power and flexibility of CrimeView’s analysis routines in combination with the analysis capabilities of ArcGIS to produce dynamic maps and reports.

FireView
FireView is an ArcMap extension that provides Fire and Emergency Response Agencies with mapping tools to help review existing deployment policies and develop new strategies. FireView integrates Fire and EMS data with GIS allowing agencies to easily map and analyze data. By identifying incident patterns and response effectiveness, resources can be more optimally redeployed.

School Planner
School Planner is an ArcMap extension that integrates student enrollment data in a mapping environment. School Planner has been developed specifically to meet the needs of a facility planner or demographer to assist in completing detailed enrollment analysis, boundary redistricting and facility planning.

Omega Data Manager
The preparation of accurate source information on which to base geographic analyses is important to the GIS process.

The Omega Data Manager contains tools available as an extension to ArcCatalog to assist in preparing standardized, accurate data for use with Omega Desktop routines.

Omega Import Wizard
Fundamental to Geographic Information Systems (GIS) is the data. To produce practical results for mapping and reporting with OmegaGIS, especially where the data is changing frequently from day to day, it is important the data be both accurate and up to date. The Omega Import Wizard provides a standardized, scheduled method for retrieving datasets from Database Management Systems (DBMS) or ASCII files, so that they may be geocoded for use with Omega Desktop and Omega Web applications.

Dashboard
Dashboard is an extension to CrimeView, FireView and School Planner that provides the ability to publish analytical information to the web in the form of maps, graphs or reports. Data is created using Omega Desktop software, and then posted to a web server which serves up the information through a web site. In addition to the web site that is set up to view the content, an administrative web site is provided to organize and manage the content that is published.

Welcome to
Omega Desktop 5.2

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc37AD/~hh810B.htm Attachment A
Licensing
All Omega Desktop products, CrimeView, FireView, School Planner, Dashboard and the Import Wizard, are protected from unauthorized use. Omega Desktop products are licensed to an individual computer and require a machine specific license. Concurrent licensing is not available.

When Omega software is purchased an installation number will be created for each license of the software.

The installation number is prefixed by the letters associated with the product. For instance, an install number for CrimeView will begin with CV2, FireView FV2, School Planner SP2, Dashboard DF2 and Import Wizard IW2. Each installation number should be associated with a specific machine.

Training licenses are available from Omega. A training license will time-out based on the amount of time required for training. Contact an Omega staff member to enquire about training licenses.

Steps to License a Product
Checking Available Licenses
Upgrading from a Previous Version
Steps to License a Product
The Omega Desktop Administrator application is used to manage the licensing of all Omega Desktop products. This application was introduced in the Omega Desktop 4.0 release to replace the "License Manager" application.
l After the Omega Desktop software is installed, open the Omega Desktop Administrator. From the Windows "Start" button, navigate to the "Omega Group" -> "Desktop Administrator". l With the application open, create a new license file. Navigate to the "License Software" view and ensure that the "Create New License" option is selected. Enter the required information.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc95C3/~hh326C.htm Attachment A
When the information is entered, click the 'Create' button to generate the new license file.

The license file is automatically saved to the <ProgramData folder>\OmegaGroup\Licenses folder. The new file name is a combination of the Install Number with the extension .ini. l Email the new license file (ie CV2xxxxx.ini) to [email protected]. The license file is received by the staff at the Omega Group, updated in order to unlock the software, and returned to the client. The updated file name will be the same as the original file name but with a 'j' added to the end of the file (ie. CV2xxxxxJ.ini).
l Open the Omega Desktop Administrator, and navigate to the "License Software" view. Select the "Unlock Software" option, and browse to the location of the updated license file. If the software is unlocked successfully, the updated license file is copied to the <ProgramData folder>\OmegaGroup\Licenses folder.

Checking Available Licenses

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc95C3/~hh326C.htm Attachment A
There are two methods available to determine which Omega Desktop applications are licensed.

Omega Desktop Administrator
The Product License Information table in the Product Information view displays the software that is unlocked.

To view the Product License table navigate to "Product Information" in the Omega Desktop Administrator.

Software that has been licensed will be identified in the Product License Information list.

The Unlocked field identifies when the software was initially unlocked for use. The Expiration field is available if a temporary license has been created. If a temporary license is created, the expiration date will be listed.

About Omega Desktop
To determine which ArcMap extensions extensions are enabled, use the "About Omega Desktop" dialog. To open this dialog, select "About Omega Desktop" item that is found on the CrimeView, FireView or School Planner pull-down.

This dialog has a tab for each extension. The tab has a key icon when the extension is licensed and a lock

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc95C3/~hh326C.htm Attachment A
icon when the extension is not licensed.

Upgrading from a Previous Version
If a previous version of Omega Desktop is installed and licensed, the upgrade to the latest version does not require updating the license.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc95C3/~hh326C.htm Attachment A
Building An Application
Building a CrimeView application is a complex process that is unique for each client. Building the CrimeView application is typically a service provided by The Omega Group. This section highlights the major tasks when building the application.

Retrieve Incident Data
Build Saved Queries
Build Crystal Reports
Set Default Fields
Create ArcMap Document
Create Map Templates
Retrieve Incident Data
One of the first tasks in building a CrimeView project is retrieving the incident data. The incident data is used for analysis and provides the source data to create maps and reports.

The Omega Import Wizard provides a means to import datasets from Database Management Systems (DBMS) or ASCII text files. Once retrieved, the datasets are geocoded so that they may be used with OmegaGIS.

An Import Profile (*.oiw) is a file used by the Omega Import Wizard to outline the steps needed to retrieve and process the datasets. The Import Profile provides a processing template that records how to extract the dataset from the DBMS, which OmegaGIS fields to create, the geocoding steps involved and the final destination for the resulting feature class. Refer to the Omega Import Wizard documentation for further information.

Build Saved Queries
Attribute queries using SQL syntax to select features from incident datasets can often become lengthy and complex. Saved Queries
hide the SQL syntax from the user while providing a more intuitive name or description for each query. Saved queries are created and edited with the Saved Queries Editor in ArcCatalog and are stored in the Omega_Query.MDB database.

Build Crystal Reports
CrimeView employs Crystal Reports for reporting functionality. Using the OmegaGIS Metadata Editor, reports are registered to layers.

Set Default Fields
Using the OmegaGIS Metadata Editor, set the default fields for the layers used by the CrimeView application. The default fields include:
¡ OmegaGIS Fields (date, day of week, time, response time). ¡ Incident Type for graphs.
¡ Default field for list boxes in dialogs.

Create ArcMap Document
An ArcMap document containing incident datasets and other geography such as street centerlines provides the backdrop for performing geographic crime analysis. Every ArcMap document that uses OmegaGIS has an associated project workspace where the results of the routines and preferences are stored.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\CrimeView.c...

Attachment A
When creating the ArcMap document, the points outlined below should be followed:
l All layers must have a unique name.

Layer names in the table of contents are used by OmegaGIS routines for identification. If layers share the same name, the first layer in the stack is always used by OmegaGIS. If the name of the layer changes, Cyclical Reports or Threshold Alerts created with that layer, will no longer be able to recognize the source data, and an error will result. Consequently, it is important that all the layers are assigned a unique name in the table of contents, and retain their original names.
l Data Frames must have a unique name.

The name of the data frame is used with OmegaGIS routines. Consequently, the data frame names must be unique and should not change.
l Use a projected coordinate system
All layers and data frames should have a projected coordinate system (as opposed to a geographic coordinate system). This is not a requirement but it is recommended as a projected coordinate system will result in more accurate results. l Performance checklist
The documentation contains a performance checklist that has recommendations for setting up an ArcMap document which should be followed.

Create Map Templates
Map templates
are used to define how the map elements in the layout will appear. Map elements include a title, agency logo, legend, north arrow and scale bar. Map templates can be used with both Cyclical Reports and Threshold Alerts.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\CrimeView.c...

Attachment A
Crystal Reports
Omega Desktop employs Crystal Reports for reporting functionality. Crystal Reports version XI,

11.5 and 12 are supported by Omega Desktop 4.3.2. The Create Reports utility enables the user to open reports created for OmegaGIS routines.

When building an application in CrimeView, FireView or School Planner there are several reports that should be generated or customized at the onset of the project. The following section describes these reports, many of which are provided as templates with the installation of OmegaGIS software, and can be customized to suit the project.

Reports Common to CrimeView, FireView and School Planner l Query Layer Reports
Query Layers are common to all OmegaGIS Software products; CrimeView, FireView and School Planner. Query Layers are data layers based on point type geometry that identify the location of a particular data type. For instance, in the case of CrimeView, a Query Layer might identify where auto thefts have occurred whereas in School Planner, the Query Layer may represent where students live within the school district.

Query Layer Reports are based on the data of the Query Layer, and so must be created with the data in mind, and customized to each new project. Once created, the report must be registered to the Query Layer using the OmegaGIS Metadata Editor . There is no limit to the
number of Crystal Reports that can be registered to a Query Layer.

The 'Sel_INCIDENTS' table found in the Selection.MDB within the project workspace, provides the source data for the Crystal Report that is based on a Query Layer. l Density Map Reports
Density Map reports are created based on layers that are created by the Density Map routine.

In order access the report, the boundary layer that is used to create the resulting density map layer, must have the name of the Density Map Report registered to it using the OmegaGIS Metadata Editor. When the new map layer is generated, the Create Reports utility can be used to view the report associated with the new layer.

The source of the Density Map Crystal Report is the 'Density_*' feature class found in the DensityMap.MDB, that is located in the Density folder of the project workspace. A template for the Density Map Crystal Report is located in <Installation Directory>\OmegaGroup\Desktop\Reports\Template_DensityMap.rpt. l Repeat Calls (Student Concentrations)
The Repeat Calls routine (Student Concentrations in School Planner) creates a layer that reveals the places that have numerous incidents (students) at the same location. The Repeat Calls (Student Concentrations) report summarizes the incidents (students) found at the same locations. The Query Layer
that was used to generate the Repeat Calls (Student
Concentrations) layer must have a Repeat Calls (Student Concentrations) Crystal Report

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
registered to the layer using the OmegaGIS Metadata Editor.

The 'Sel_RepeatCalls' table, found in the Selection.MDB within the project workspace, provides the source data for the Crystal Report. A text field named "OmegaGIS_XY" in the 'Sel_RepeatCalls' table can be used to group the incidents (students). l Exception Reporting (Enrollment Comparison)
The result of the Exception Reporting (Enrollment Comparison in School Planner) routine is both a layer and a Crystal Report. The report is named Exception.RPT and is located in the <Installation Directory>\OmegaGroup\Desktop\Reports folder. The source table for the report is "ExceptionData_*" which is located in the \Analyses\ExceptionData.MDB personal Geodatabase in the project workspace.

The Exception.RPT may be customized, such as adding an image to the report, but the report must have the original name. The report can be located in a location other than the default \reports folder within the project directory, however, the folder location must be referenced using the Locations category for Crystal Reports in Setup. The original fields found on the Exception Report should not be modified as they are based on standardized output created when the Exception Report routine is run.

CrimeView Reports
l Crime Rate Generator
Three report templates are provided with Crime Rate Generator and are found in the <installation folder>\OmegaGroup\Desktop\Reports folder. When a Crime Rate Generator routine is run, and the 'Report' option is selected on the dialog, the report template is copied to the project workspace
\Reports folder and is used to view the Crime Rate Generator results.

Each report is related to a specific census layer that is generated with the OmegaGIS Demographic Data Loader. When the census layer is created a metadata tag is created automatically to ensure that the correct report is used with the layer. For instance, the CrimeRate_Block.rpt report is used with the census blocks layer, the CrimeRate_Blockgroup.rpt report is associated with the blockgroup layer and the CrimeRate_Tract.rpt is used with the census tract layer.

When the Crime Rate Generator analysis is run, a new feature class is created in a personal geodatabase called CrimeRateData.mdb located in the project \Census folder. Each new

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
feature class is numbered chronologically and prefixed with 'census_'. The report can be customized in order to change the format, however the original fields on which the report is based should not be altered as they reference standardized data output created by the routine.

FireView Reports
l Response Comparison Analysis
The Response Comparison Analysis report (RespComp.rpt) is a template provided with OmegaGIS. It is found in the <installation folder>\OmegaGroup\Desktop\Reports folder of the project workspace. The Response Comparison Report is based on the Omega_Difference field in the results layer, and defines the difference in time between the actual arrival time of equipment to an incident, and the expected time calculated using the OmegaGIS Street Network Manager.

The Response Comparison report can be customized, renamed and located in any folder. To enable the Response Comparison report, the query layer on which the response analysis is based, must have a metadata tag attached to it that references the name of the Response Comparison report. Setting this tag can be accomplished with the OmegaGIS Metadata Editor. If the report is not placed in the default project workspace \Reports folder, the Locations category of Setup must reference the new folder. Although, the content of the report can be customized, the original fields of the report should remain as they are based on standardized fields that are available with the analysis.

Response Comparison feature classes generated by the routine are stored in a personal geodatabase called RespComp.mdb in the project \Analyses folder. Within the database, each feature class created is chronologically named using the prefix 'RespComp_' and an attached number.

School Planner Reports
l Demographic Analysis
Three report templates are provided with Demographic Analysis and are found in the <installation folder>\OmegaGroup\Desktop\Reports folder. When a Demographic Analysis routine is run, and the 'Report' option is selected on the dialog, the report template is copied to the project workspace
\Reports folder and is used to view the Demographic Analysis results.

Each report is related to a specific census layer that is generated with the OmegaGIS Demographic Data Loader. When the census layer is created a metadata tag is created automatically to ensure that the correct report is used with the layer. For instance, the Student_Block.rpt report is used with the census blocks layer, the Student_Blockgroup.rpt report is associated with the blockgroup layer and the Student_Tract.rpt is used with the census tract layer.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
When the Demographic Analysis routine is run, a new feature class is created in a personal geodatabase called StudentData.mdb located in the project \Census folder. Each new feature class is numbered chronologically and prefixed with 'census_'. The report can be customized in order to change the format, however the original fields on which the report is based should not be altered as they reference standardized data output created by the routine. l Projection Analysis (Attending and Residing)
There are two reports associated with Projection Analysis; the Residing report and the Attending report. Both reports are provided as templates in the <installation folder>\OmegaGroup\Desktop\Reports folder, and are called Template_Residing.rpt and Template_Attending.rpt.

These reports can be customized, renamed and stored in any accessible folder. If these reports are stored anywhere but the default \reports folder however, the folder location must be referenced by Setup under the Locations category for Crystal Reports. The reports must also be registered to the data layers on which the analysis is performed. For instance, each student layer used in the analysis should have the Residing and Attending report names registered to them using the OmegaGIS Metadata Editor
.

The data on which the Residing and Attending reports are based is stored in a personal geodatabase called Omega_Projection.mdb within the project \Analyses folder. When a Projection Analysis is run a new feature class (fclass_*) and a new table (scenario_*) are generated. Both data items are numbered chronologically. It is the scenario table that houses the data on which the reports are based.
l Boundary Redistricting
Boundary Redistricting
supports two reports; a boundary report and a scenario report. The Boundary Report displays a summary of the students that have been assigned to the school selected in the Facility list. The Scenario Report displays a summary of the number of assigned students to all of the school boundaries of the current scenario.

Both reports are provided as templates in the <installation folder>\OmegaGroup\Desktop\Reports folder and are called Redistricting_Boundary.rpt and Redistricting_Scenario.rpt respectively. These reports may be customized, renamed and stored in any folder, as long as that folder is referenced by the Locations category for Crystal Reports in Setup. The reports must also be registered to the query layers on which they are based using the OmegaGIS Metadata Editor
.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
The source tables for the reports are located in the Selection.MDB that is located in the project workspace.
l Residency Report
The Residency Report is associated with a report that is distributed as a template in the <installation folder>\OmegaGroup\Desktop\Reports folder. The report is called Template_Resident.rpt and includes both a summary and detailed section. The report can be customized, renamed and relocated, however the location of the report must be referenced by the Locations Category for Crystal Reports in Setup, and the report must be registered to the query layer using the OmegaGIS Metadata Editor.

The source data on which the report is based is stored in a personal geodatabase within the project \Analyses folder. The database is called ResidencyRpt.mdb. When a residency analysis is run, the resulting data is stored in a new feature class called Residency_* where the * represents a number that increases each time a new residency report is generated.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Project Workspace
An OmegaGIS project, such as CrimeView, is set up in an ArcMap document. Every project has an associated project workspace that is used to store the results of routines and preferences. This section describes the project workspace.

Name of Project Workspace
File Structure
Name of Project Workspace
The project workspace is a folder that has the same name as the ArcMap document. For example, if the ArcMap document is named MyMap.MXD and is located in the C:\CrimeView folder, then the project workspace is C:\CrimeView\MyMap.

File Structure
The files and folders that are automatically generated in the project workspace are outlined below:

MyMap.MXD
MyMap
The project workspace has the same name as the ArcMap document without the file extension.

Analyses
The Analyses folder is always created by OmegaGIS routines. The folder may contain a number of personal geodatabases depending on the Omega software product in use.

AddQueryLayers.MDB (common to all Omega products)
When additional query layers
are used in any of the OmegaGIS software
products, the incidents selected by the attribute query and/or spatial query, are exported into the same feature class in this personal Geodatabase. The AddQueryLayers.MDB is created dynamically, if it is not present it is created automatically.

ExceptionData.MDB (common to all Omega products)
This personal Geodatabase is used with the Exception Reporting routine. It
is created when the routine is run. If the database is deleted, it is regenerated automatically.

ResponseAnalysis.MDB (FireView)
This personal Geodatabase is used with the Response Analysis routines, such as First Due
. It is created when the routine is run, and is regenerated automatically if deleted.

AvgRespTime.MDB (FireView)
This personal Geodatabase is used with FireView's Response Time Map routine and is created when the routine is run. If the database is deleted, it is recreated automatically.

RespComp.MDB (FireView)
During the Response Comparison
routine in FireView, a new feature class is
generated in the RespComp.MDB personal Geodatabase. This file is created when the routine is run, and is regenerated automatically if deleted.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
StatProfiler.MDB (CrimeView, FireView)
This personal Geodatabase is used with the Statistical Profiler routine and is created when the routine is run. The database is regenerated automatically if deleted.

StnAnalyses (FireView)
The StnAnalyses folder is created by FireView's Station Analysis routine and contains the ProposedStations.MDB personal Geodatabase.

Omega_Projection.MDB (School Planner)
During the Projection Analysis routine in School Planner, a new feature class and scenario table are generated in the Omega_Projection.MDB personal Geodatabase. The geodatabase is created when the routine is run, and is regenerated automatically if deleted.

Redistrict.MDB (School Planner)
During the Boundary Redistricting routine in School Planner, a number of tables and feature classes are generated in the Redistrict.MDB personal Geodatabase. The geodatabase is created when the routine is run, and is regenerated automatically if deleted.

ResidencyRpt.MDB (School Planner)
During the Residency Report routine in School Planner, feature classes are generated in the ResidencyRpt.MDB personal Geodatabase. The geodatabase is created when the routine is run, and is regenerated automatically if deleted.

Density
The Density folder is always created by OmegaGIS routines. The folder may contain two personal Geodatabases:

DensityMap.MDB (common to all Omega products)
During the Density Map
routine, a new feature class is generated in the
DensityMap.MBD. The DensityMap.MDB file is created automatically while running the Density Map routine.

RepeatCalls.MDB (common to all Omega products)
The RepeatCalls.MDB file is created during the Repeat Calls routine
(Student Concentration routine in School Planner). It contains the feature class that has the repeat locations.

HotSpot
The HotSpot folder contains the rasters from the Hot Spot routine (Spatial Clustering in School Planner) and is always created by OmegaGIS routines. The rasters are temporary and are automatically deleted from disk when they are no longer referenced by ArcMap. This folder is common to all Omega products.

Census
The Census folder is always created by OmegaGIS routines. The folder may contain up to three personal Geodatabases:

CrimeRateData.MDB (CrimeView)
During the Crime Rate Generator routine, a new feature class is generated in the CrimeRateData.MDB personal Geodatabase. The
CrimeRateData.MDB file is created automatically while running the Crime

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Rate Generator routine.

StudentData.MDB (School Planner)
During the Demographic Analysis routine, a new feature class is generated in the StudentData.MDB personal Geodatabase. The StudentData.MDB file is created automatically while running the Demographic Analysis routine.

Omega_DemoViewer.MDB (common to all Omega products)
During the Demographic Viewer routine, a new feature class is generated in the Omega_DemoViewer.MDB personal Geodatabase. The
Omega_DemoViewer.MDB file is created automatically while running the Demographic Viewer.

The Census folder may also contain the personal Geodatabase that has the census feature classes.

Selection.MDB
The Selection.MDB personal Geodatabase is automatically created by OmegaGIS routines if not already present. It is used to store selected records that OmegaGIS graphs
and Crystal Reports use as a source.

Setup.MDB
The Setup.MDB file contains user defined preferences for the ArcMap document. There is a password on the Setup.MDB file. The only way to alter the preferences is with the OmegaGIS Setup
dialog.

Threshold_Alert.MDB
Cyclical Reports and Threshold Alerts are stored within the Threshold_Alert.MDB database.

MyMap.XML
The XML document has the same name as the ArcMap document and contains information on the last routine run. The document is created when a routine is run.

Other folders and files can be included in the project workspace. The other folders and files that typically make up the project workspace include the following:

Geography
This folder contains the geographic datasets used with the OmegaGIS routines.

Examples of geographic datasets include Police Beats, School Districts and street centerlines.

Reports
The Reports folder in the project workspace is the default search location for Crystal Reports. Search locations can be changed by using the OmegaGIS Setup dialog.

Network
This folder in the project workspace is the default search locator for Omega Street Network folders which are used with FireView. Search locations can be changed by using the OmegaGIS Setup dialog.

Omega_Query.ODB
The Omega_Query.ODB file contains the Saved Queries. The default location is in the

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
project workspace. This location can be changed by using the OmegaGIS Setup dialog.

In versions of OmegaGIS prior to Omega Desktop 4.0, this database was named Omega_Query.MDB (note the extension). This database can be updated from a previous version using the Omega Query Editor tool on the Omega Data Manager toolbar in ArcCatalog.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Map Templates
In ArcMap, the layout contains all of the elements of a map. These map elements may include a title, agency logo, legend, north arrow, scale bar and geographic layers. These map elements can be organized so that all maps, whether printed or created as an image, that are produced with ArcMap share a similar professional design.

One way to change the layout appearance of a map is to use the tools in ArcMap to insert new map elements, such as a north arrow. Once added, map elements can be moved by clicking on the element and dragging it to a new location. Another way to change the appearance of the layout is to use a map template. A map template contains these map elements so that there is no need to spend time creating a map.

This help section outlines the following:

Use of Map Templates
Creating a Map Template
Map Template Considerations
Use of Map Templates
When using Omega GIS products, such as FireView, map templates can be used with the following:
l Layout
The map layout can be quickly changed by loading a map template using the Change Layout tool available in ArcMap. This tool is on the Layout toolbar and is also available on the CrimeView/FireView pull-down menu.

The Change Layout tool opens a dialog that allows one to browse to an existing template.

Click the Browse button and navigate to an existing map template (.MXT). l Cyclical Reports and Threshold Alerts
Both Cyclical Reports and Threshold Alerts support the use of map templates. When a map template is used, the map template is automatically loaded when the routine is completed.

Creating a Map Template
The following steps outline how to generate a map template:

1. Make the layout view the active view in ArcMap. From the View pull-down menu item select Layout View.

Tip: Another way to make the layout view active is to select the layout view button located at the bottom left hand side of the data view.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A

2. With the layout view active, insert and arrange map elements. To insert map elements, such as a north arrow, from the Insert pull-down menu select the map element to insert.

To remove all the map elements but the data frame, use the Remove Layout Elements tool.

3. Once the map elements on the layout have been arranged, the next step is to save these changes as a map template. From the File pull-down menu select Save As which opens a new dialog. Change the save type from an MXD (ArcMap Document) to an MXT (ArcMap Template) and then provide a location and file name.

Once the document has been saved as a Template, the current ArcMap document provides the template. Any changes to the map elements on the layout are saved to the template.

Since Omega GIS routines require that ArcMap is not a template an error message [6700111] is issued when a dialog is opened. To return to the ArcMap document, from the File pull-down menu select Open and then navigate to the MXD.

Map Template Considerations
When using map templates with Omega GIS products, such as CrimeView, there are some considerations to be aware of:
l Pictures in Layout
When inserting pictures into the layout, such as an agency logo, save the picture as part of the document. Right click the picture and select Properties from the pop-up menu. On the Picture tab, check the Save Picture as Part of Document.

When the picture is not saved as part of the document, ArcMap must reference the picture on disk. If the pictures disk location is altered then an error message is issued every time the ArcMap document is opened.
l Legends
Omega GIS query routines, such as Incidents Within A Boundary, create a new selection layer based on the results of the routine. Unfortunately, these legends do not work well with map templates and it is recommend that the legends not be stored in the map template.

One solution is to insert the legend and then convert the legend to graphics which prevents the legend from dynamically changing when items in the table of contents are altered. To convert the legend, right click the legend in the layout and then select Convert to Graphics from the pop up menu.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Upgrading from previous versions
Upgrading from previous versions of OmegaGIS to Omega Desktop 4.3 requires three procedures in order to ensure that the analyses and tools provided with the software operate correctly.

Omega Query Database
At the Omega Desktop 4.2 release, the Omega Query Database format was revised in order to provide greater functionality when building Saved Queries, as well as accommodate new data formats issued with ArcGIS 9.0. The 4.0 version of the query database was named Omega_Query.ODB instead of Omega_Query.MDB. This version of the database persists in the Omega Desktop 4.2 version of the software.

If upgrading from a version of the Omega Desktop software, prior to 4.0, the Omega_Query.mdb can be upgraded using a tool provided within the Omega Query Editor.

The tool gives the user the ability to select the old database, and automatically convert the database format and the data within to the new version. The Omega Query Editor is available on the Omega Data Manager Extension to ArcCatalog.

Import Wizard
At the Omega Desktop version 4.0 release, the Omega Desktop installation was created as a single CD that includes all Omega Desktop products. All of these products are installed and the use of the products is controlled by the licensing.

One of the changes brought about by this installation is that the Omega Import Wizard program files have changed location in the installation directory. The automation of the Omega Import Wizard uses the path of the OmegaWizard.EXE file in the Windows Task Scheduler. This path change been change to <Installation directory>\OmegaGroup\Desktop\Bin.

Existing Window Task Scheduler task must be updated to use the new path to the OmegaWizard.EXE.

Threshold Alerts
The Windows Task Scheduler may be used to automate Threshold Alerts . This is done by
setting up a task that provides the path to the ThresholdAuto.EXE and the ArcMap document.

The folders that contain the Omega Desktop software have changed as of the version 4.0 release; including the path to the ThresholdAuto.EXE.

The path to the ThresholdAuto.EXE has been changed to <Installation directory>\OmegaGroup\Desktop\Bin.

Existing Window Task Scheduler task must be updated to use the new path to the ThresholdAuto.EXE.

Upgrades Prior to Service Pack 2
The following information applies only to those situations where an upgrade is made from an OmegaGIS release prior to Service Pack 2. Service Pack 2 and subsequent releases, include a number of new features that require making some updates to existing CrimeView applications.

This section highlights the issues faced when upgrading from a version of CrimeView that was installed prior to Service Pack 2.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Licensing
Normal.MXT
Extension and Toolbar
Cyclical Reports
Repeat Calls
Legacy Files
Licensing
CrimeView software that has been licensed prior to Service Pack 2 does not require updating. The license information is retained as long as the previous version of the software is not uninstalled prior to installing the new version.

Normal.MXT
If CrimeView was installed prior to Service Pack 2, and is upgraded the hot-key to run the Clear All, F11, will not work. A hot-key is a shortcut to a tool from the keyboard. This is a known issue with ArcMap.

The current work around to this issue is to delete the existing Normal.MXT. The Normal.MXT stores information on which toolbars are used in all ArcMap documents and is unique for each user that logs into the machine. The location of the Normal.MXT is in the \Documents and Settings\< Current User >\Application Data\ESRI\ArcMap\Templates folder. Close ArcMap and then delete the existing Normal.MXT, the file will be generated once ArcMap is opened.

If the Normal.MXT is not deleted, the Clear All can still be run from the OmegaGIS toolbar by clicking the Clear All button.

When the hot-key is working correctly, the OmegaGIS Step item on the CrimeView pull-down menu will have F11, otherwise the menu item will not have any hot-key information.

Extension and Toolbar
The OmegaGIS extension must be enabled and the toolbar must be added to ArcMap after the upgrade to Service Pack 2.

Enable Extension
From the Tools pull-down menu in ArcMap, select Extensions to open the Extensions dialog.

Check the "CrimeView" extension and close the dialog. A message is issued if the extension is not licensed
correctly.

Information on which extensions are enabled is based on the current user logged into the machine, and is stored in the computers registry (HKEY_CURRENT_USER). All new or existing ArcMap documents have the CrimeView extension enabled. If a different user logs into the machine, the CrimeView extension must be enabled.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Add Toolbar
To add the CrimeView toolbar, from the View pull-down menu in ArcMap, select Toolbars and then check the "OmegaGIS - CrimeView" item.

Once added to ArcMap, the CrimeView toolbar is available to all ArcMap documents for the current user. Information on which toolbars are in use for all ArcMap documents is stored in the Normal.MXT. As the Normal.MXT is stored in the \Documents and Settings\< Current User >\Application Data\ESRI\ArcMap\Templates folder and is user dependent, if a different user logs into the machine, the CrimeView toolbar must be enabled.

Cyclical Reports
Cyclical Reports built with a previous versions of CrimeView are not supported by Service Pack 2 or subsequent releases. This change is a result of accommodating the use of Threshold Alerts.

Consequently, all Cyclical Reports must be built again with Service Pack 2 or subsequent releases.

Repeat Calls
At Service Pack 2 and beyond, Query Layers that are used to generate Repeat Calls layers must have a Repeat Calls Report
registered to it. In previous versions, only one Repeat Calls Report was supported which limited the report to one dataset. To register a Repeat Calls Report, use the OmegaGIS Metadata Editor that is found in ArcCatalog.

The Repeat Calls Report uses the Sel_RepeatCalls table in the Selection.MDB file as the source for the Crystal Report. The Sel_RepeatCalls table has a field called "OmegaGIS_XY". The values in this field can be grouped in Crystal Reports to determine the repeat call location. The "OmegaGIS_XY" field was named "CV_XY" in previous versions of OmegaGIS, consequently, existing Repeat Call Reports must be updated to use the new field name.

Legacy Files
At Service Pack 2, the project workspace
is reorganized. Consequently, there are legacy files and folders that can be safely removed from the project workspace as they are no longer used. Below is a list of folders and files that can be removed:

Connectivity
The Connectivity folder is not used by any OmegaGIS routine.

Grid
The Grid folder is not used by any OmegaGIS routine.

Repeat

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
The Repeat Calls routine at Service Pack 2 uses the Density folder.

Cyclical.MDB
Cyclical Reports built with previous versions of CrimeView are not supported at Service Pack 2. The Cyclical.MDB file was used to store the Cyclical Reports, now the information is stored in the Threshold_Alert.MDB file.

Omega_QDSum.XSL
The stylesheet used with the summary dialog has been moved to the Windows TEMP directory.

QDSummary.HTM
This file contained information on the last routine run in HTML format. The information is now available with the Layout Metadata tool.

QDSummary.TXT
This file contained information on the last routine run in a text format. The information is now available with the Layout Metadata tool.

TOC.HTML
This file is no longer in use.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaBuildi...

Attachment A
Setup: General
The General Category in Setup contains generic settings that affect the ArcMap document, the Layout, and Omega Desktop routines. The General Settings are subdivided into three subcategories that represent tabs in the Setup Dialog. These subcategories are:

General
Measurement System
The two choices for Measurement System are English and Metric, where English is the default setting. The English system employs feet and miles, whereas the Metric system employs meters and kilometers
This setting alters appropriate OmegaGIS dialogs regarding measurement, such as default buffer units. This setting does not alter the Data Frame’s map units and distance units, which can be set by selecting the Data Frame Properties option from the View menu.

Saved Query Display
Saved queries can be displayed within analysis dialogs in tree view or in column view. The tree view presents the saved queries in a hierarchical structure. The column view has three columns, where the first two are populated by the child queries of a Level 1 query, and the third column shows the remaining saved queries in a hierarchical structure. The Omega Query Editor is used to set which queries will be displayed in the first two columns.

Upon Project Exit
Project exit settings are executed when the ArcMap document is closed. To apply the settings immediately without closing the ArcMap Document click the Apply Project Exit button. l Delete Selection Layers
This setting when checked specifies that all selection layers will be removed from the ArcMap document when closed. The default is to delete the selection layers.

General
Layout_Tools
Repeat Calls
Advanced

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Remove additional Query Composite Layers
When this box is checked, all composite layers will be removed from the ArcMap document when closed. The default is to delete the composite layers. l Clear Definition Queries
When this box is checked, all Omega Definition Queries will be removed all the layers when the ArcMap document is closed. The default is to clear the query definitions.

Layout Tools
The text entered for the Layout Tools updates the disclaimer used in the Layout Metadata Tool.

The text is limited in length to 255 characters. The default for this setting is as follows:

This agency is not responsible for the misinterpretation of this map and makes no inference or judgment as to the relative safety of particular areas. This map does not meet national map accuracy standards and should not be used for engineering purposes.

Repeat Calls

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Report Buffer Distance
When the repeat calls report is created, the records from the source Query Layer are exported to the Selection.MDB located in the project workspace. A spatial filter is used to select the records in the Query Layer to include in the export. This spatial filter uses the attribute query that was used to generate the Repeat Calls layer, if any, and the geometry of the repeat calls locations. The geometry of the repeat calls locations is buffered before being placed in the spatial filter and the Report Buffer Distance controls the size of the buffer.

The buffer distance is measured in meters and there is a default value of 0.5 m.

Advanced
Date Ranges
Date range settings are used with the Date and Time Query dialog that is typically located on the
When? tab of Query, Density, and some Analysis routines. The calendars display the available date range in white, while those dates that are unavailable are grayed out. Unavailable dates cannot be selected.
l Display the available ranges of dates for the query layer When this option is checked, the metadata for selected Query Layers will be searched to get the date range information. The date range information is created by the Omega Import Wizard and specifies the beginning date, the ending date, and the OmegaGIS date field. The default is to display the available ranges of dates for the query layers. l Search query layer's feature class for date range when missing metadata information
When this option is checked and the date range is not found in the metadata, the feature class will be searched to get the date range information. To accomplish this, each record in the feature class must be examined to determine the beginning date and ending date.

The searching of the feature class may result in a performance hit, especially if the feature class contains a large number of records. The field searched will be the default OmegaGIS date field. In an effort to improve performance, the default setting will not search the query layer's feature class for date range when missing metadata information.

For more information about date ranges see Available Date Range for Query Layer .

Unique Lists
One method to select features in the boundary layer is "By Field Value", which requires a unique list of values. Many OmegaGIS routines use a boundary layer to query incidents geographically.

This information is typically gathered on the Where? Tab of OmegaGIS routines. l Number of records used to determine list of unique values:

When the boundary layer and field are selected, a list of unique values is generated based on the selected field. This unique set of values is then displayed in the Field Values list. To populate this list each record in the feature class must be examined. In order to improve performance, this setting limits the number of records that are searched to generate a unique list. Therefore, if a feature class contains 100,000 records and this setting is set to 1,000, only the first 1,000 records will be cycled through to determine the values for the unique list.

The maximum number of records used to generate a unique list is 10,000. To override this setting while executing a routine click the Complete List button. This will cycle though all

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
records in the feature class regardless of this setting. The default for this setting is 1,000. l Number of records to display in list of unique values:

This setting limits the number of unique values displayed in the Field Values list. If a feature class has 10,000 unique values and this setting is set to 5,000, only the first 5,000 unique values will be displayed in the list. When the limit of unique values is reached, a warning is displayed to the left of the list. The maximum number of unique values that can be displayed in the Field Values list is 30,000. If this becomes an issue, use the By Pointing selection method. The default for this setting is 5,000.

Thumbnail
l Save thumbnail image in metadata when ArcMap closes (not recommended) This tool is analogous to the Save thumbnail image with map check box on the map properties dialog in ArcMap. This setting could result in a performance hit when saving the ArcMap document, therefore the default does not save the thumbnail image.

Default Settings Buttons
The default setup values are stored in the template Setup.mdb database located in the install directory. Initially default Omega setup values are populated in the template Setup.mdb database.

These values can be found in the table below and are also included in each setting topic in the help.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Return to default settings
This button replaces the current settings from the entire setup database with the values saved in the template setup database. If the template setup database has not been modified by the Set current settings as Default button, then the setup values will return to the Omega default values. If the template has been modified, the setup values will be set to the modified values.
l Set current settings as Default
This button takes all the current settings for the entire setup database and saves them to the template setup database. This tool can be used to override the default settings that Omega provides. Setting the template with amended values insures that all newly created OmegaGIS projects will use the current setup values as their defaults. It also allows the user to store amended default settings for reuse later by using the Return to default settings button.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Setup: Queries
The Query category in Setup contains settings that affect the input of data into OmegaGIS routines as well as the output from these routines. The Query Settings are subdivided into four subcategories that represent tabs in the Setup Dialog. These subcategories are:

Query
The Query tab includes several options for how the results of an OmegaGIS routine will be displayed.

Select one of the following for the query results:

OmegaGIS query routines use attribute and geographic queries to identify the particular incidents in the Query Layer.

Attribute queries are based on the data stored in the table of Query Layer. For example, you might choose to display only those incidents that involved Narcotics. This data is specified on the What? and the When? tabs. Geographic queries are based on the spatial relationship of the Query Layer with other layers in the map. For example, you might want to see the Incidents that occurred within 1,000 feet of a school. This data is specified on the Where? Tab.

This setting will by default create a new selection layer for each OmegaGIS routine run. l Show all values and highlight only the selection
This option will select the incidents in the Query Layer that meet the requirements of both the spatial and geographic queries. All other points in the Query Layer will be displayed but will not be selected. For example, if we wanted to see all narcotics incidents within 1,000 feet of a school, the incident query layer would display all Incidents in the Query Layer and select only the narcotics within 1,000 feet of the school. l Show only saved query values and highlight selection
This option will create a Definition Query on the Query Layer based on the attribute query and will select the incidents in the Query Layer that meet the requirements of the geographic queries. For example, if we wanted to see all narcotics incidents within 1,000 feet of a school, the incident query layer would display only the narcotics Incidents and select all the points within 1,000 ft of the school.

Query
Registered_Types
Additional_Query_Layers
Advanced

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Show only selection (as new layer)
This option will create a new selection layer from the Query Layer that meets the requirements of both the spatial and geographic queries. For example, if we wanted to see all narcotics incidents within 1,000 feet of a school, a new layer would be created that would display only the narcotics Incidents within 1,000 ft of the school.

The new selection layer takes the following properties from the Query Layer:
¡ Primary Display Field, the field is used with map tips and is used to represent the feature in the left side of ArcMap's Identify Results window when you use the Identify tool. ¡ The visible fields and the field alias for the layers attribute table. ¡ The label field.
¡ The text symbol used for the labeling.

Allow only one selection layer
This setting enforces that there is only one selection layer per data frame. If an OmegaGIS routine
is run and a new selection layer is output to a data frame with an existing selection layer, the existing layer is replaced with the new layer. This setting is only used when the query results are displayed as a new selection layer. This setting by default will only allow one selection layer.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Create a legend for new layer with only selected features This setting, if checked, will create a subset of the existing query layer legend based on the result of the query routine. The resulting layer will only include legend items that are present in the underlying data of the new layer. If this setting is not checked, the entire legend will be displayed for the new layer. This setting is only used when the query results are displayed as a new selection layer. This setting by default creates a legend for new layers with only selected features.

Other Query Results Settings
l Display the routine summary dialog
This settings, when checked, displays the routine summary dialog after the completion of the data input for query, density, and analysis routines. The summary dialog provides an overview of the parameters for the last routine run. Use the Back button on the summary dialog to return to the query, density, or analysis routine dialogs to make any edits. The Save button, which is only present when running a query routine, allows the parameters to be saved as a Cyclical Report
and/or Threshold Alert. This setting by default displays the routine summary dialog.
l Shrink the OmegaGIS dialog when routine is complete
This setting will either shrink or hide the routine dialog when the routine has completed. When the dialog is shrunk, it can be expanded by double clicking the green Sherlock icon. Once expanded the routine parameters can be edited and the routine rerun, producing new results based on the edited information. When the dialog is hidden, it can only be accessed by reopening the Main Menu. The default for this setting is to shrink the dialog when the routine is complete.
l Zoom to selection
This setting, if enabled, zooms the data frame to the visible extent when the routine has completed. Different routines zoom to different extents based on the parameters specified in the routine. If a routine has a boundary layer or a user defined area specified, this setting will zoom the data frame to the extent of the geographic boundary. If the routine only contains an attribute query, then the data frame will be zoomed to the extent of either the selected incidents or the new selection layer. If this setting is not enabled, then the data frames extent will not be changed. By default the data frame is zoomed to the selection.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Registered Types
This setting determines if only registered layers will be used as query layers in OmegaGIS routines. To register layers as 'Incident', 'Person', 'Student' or 'Other' use the OmegaGIS Metadata Editor in ArcCatalog. l Only use registered layers to make new queries
This settings, if checked, will only populate the list of query layers with layers that have been registered. The list box below lists the registered types that can be used as query layers. Checking the box next to each registered type adds each layer of that type to the list of query layers in the OmegaGIS routines. Depending on these settings, the list of query layers will be limited to only those layers of interest for querying. If this setting is enabled, a registered type in the list box must be checked. By default this setting is disabled.

Additional Query Layers
These settings specify the options to be used when using additional query layers.

When additional query layers are used, the incidents selected by the attribute query and/or spatial query, are exported as feature classes into a personal Geodatabase. The Geodatabase is named AddQueryLayers.MDB and is located in the "\Analyses" folder in the project workspace. l Create the 'OmegaGIS_Source' field that records the name of the source layer This setting when checked creates a new field in the new feature class named 'OmegaGIS_Source'. This new field will be populated with the name of the parent layer for each record. This allows for composite layers to be queried as to their source layer. The default for this setting adds the 'OmegaGIS_Source' field.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Only create one new composite layer from each master query layer This setting enforces that there is only one composite layer per data frame. If an OmegaGIS routine is run and a new composite layer is output to a data frame with an existing composite layer, the existing layer is replaced with the new layer. This setting by default will only allow one composite layer. l Additional Query Layer tool
The additional query layer tool allows the user to compare two different layers form a specified data frame to see if they can be used as additional query layers in OmegaGIS routines. The tool opens a new dialog which requires the input of the data frame, the master query layer and the additional query layer. Once these parameters are inputted the results will be displayed in the output frame.

Data Frame
Lists all the data frames in the current map document. This will allow the user to specify the data frame of interest. The two layers being compared must be in the data frame selected.

Layers
The layers frame lists all the layers in the selected data frame. This will allow the user to specify the master and additional query layers of interest. Both the master and the additional query layers can be changed at any time for different comparison results.

Output
The output is displayed in the Output frame. This tool compares the layer criteria for the additional query layer as compared with the master layer. The layer criteria are described in the additional query layer topic of the
help.

If a layer meets all the criteria of an additional query layer then a green check is displayed with the message 'Layer <master query layer> is an additional query layer of<additional query layer>.' If a layer does not meet all the criteria of an additional query layer then a red X is displayed with the first layer criteria not met by the layer.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Advanced
OmegaGIS Layers
l New layer added by OmegaGIS routine is selectable
Toggles the ability for all layers created by OmegaGIS routines to be selectable in the data frame. Most layers in the data frame are not selectable. The default for this setting is to leave the new selection layer not selectable.
l Exclude Composite layers created from OmegaGIS routines from being used in new queries This setting, when checked, will prevent composite layers from being used as query layers in OmegaGIS routines. Selection layers can never be used as a query layer regardless of this setting. This setting by default excludes Omega created layers from being used as query layers.

Other Layers
l Select features used as boundaries, such as 'Police Beats', that are used with OmegaGIS routines When geographic queries are preformed, this setting, if checked, will select the boundary layers which meet the queries criteria. By default boundary layers are selected.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Setup: Clear All
The Clear All category includes the options that will be performed when the Clear All command is executed. By default the Clear All command removes the selection for all layers in the active data frame. The Clear All command can be issued by clicking the button on the toolbar or by pressing the 'F11' button on your keyboard.

When a setting in the Clear All category says it will remove a layer(s), this means that the specified layer is deleted from the data frame and will not appear in the table of contents or be drawn on the map.

When a setting states that it will turn off visibility of layer(s), this means that the specified layer remains in the table of contents but is not drawn on the map. Toggling layers on and off is accomplished by clicking on the check box to the left of the target layer in the Display tab of the table of contents.

General Tab
l Clear Omega definition queries on query layers.

This setting clears any OmegaGIS created attribute definition queries on registered query layers. The default for this setting is to remove definition queries on registered layers. l Remove additional query composite layers.

This setting deletes all composite layers from the active data frame. The default for this setting is to remove all composite layers from the data frame.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Remove OmegaGIS graphics, labels, and buffers.

This setting deletes all graphics generated by OmegaGIS routines. This is accoplished by deleting all OmegaGIS annotation groups in the active data frame. Labels stored on the <Default> annotation group (typically street labels) will not be removed. The default for this setting is to clear all OmegaGIS graphics.
l Remove selection layers.

This setting will delete all of the selection layers from the active data frame. As a default, the selection layers will not be removed.
l Turn off selectability of all layers
This setting will cause the layers in the active data frame to not be selectable. Selectable layers can be set or unset on the Omega tab
or on the Selection tab on the Table of contents.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
This setting's default is to turn off the selectability of all layers. l Turn off visibility of registered query layers.

This setting will cause the registered query layers to not be drawn in the active data frame.

This setting only affects point layers. The default for this setting turns off the visibility of registered query layers.
l Turn off visibility of layers that are registered as 'Other'.

This setting will cause the registered query layers that are classified as 'Other' to not be drawn in the active data frame. As a default, layers registered as 'Other' will not be turned off.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Zoom to:

This setting when unchecked will not change of extent for the active data frame. If the setting is checked, the user has the choice of two options: Full Extent or Home. The Full Extent option will zoom to the full extent of all layers in the active data frame. The Home option will zoom to a preset bookmark named Home in the active data frame. If the bookmark is not found, the data frame will zoom to the full extent.

To create a bookmark, zoom the map to the area you want for Home; click the View > Bookmarks > Create item and name the bookmark "Home". The default for this setting zooms the data frame to Home.

Advanced Tab
The Advanced Tab contains a list of all of the different types of layers generated by Omega routines. When a new layer is created, metadata is attached to the data source of the layer to identify the routine that generated it. If a layer type is selected from the Clear All list, when the Clear All is activated, those layers found in the ArcMap table of contents with the selected routine type are removed from table of contents and map.

During a Clear All, layers are removed from the table of contents and map if they have the appropriate routine type, but the data source of the layer remains on disk. When the project is closed however, if these layers no longer exist in the table of contents, the data source is deleted.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Setup: Labels
OmegaGIS routines use annotation groups to organize map document graphics. Annotation groups control the draw order (weights) of text, which allow buffers and labels to be drawn on top of existing graphics without blocking them. Also, annotation groups can associate with a layer which turns off the visibility of the label when the layer is turned off. Label symbol properties can also be set to display OmegaGIS routine labels in the same format as the label properties of the layer that is being labeled. All of these settings can be applied using two subcategories:

Label Style
This subcategory sets the font, color, position, and look of the labels generated from running OmegaGIS routines.

Label Style:

This setting allows the user to choose the look of the labels generated from all routines other than the 'Near an Address' routine. The three options that can be set are as follows:
l Use layer label properties
The label font, color, size, position... are gathered from each layer in the labels tab on the layer properties dialog. The 'Layer Properties' dialog is accessed by right clicking on a layer in the table of contents and selecting the 'properties' item from the popup menu.

On the 'Label' tab, the 'Text Symbol' frame displays the current symbol used to label the text. Click the 'Symbol...' button to change these settings in the Symbol Selector dialog.

There are many options used to customize your text in the Symbol Selector dialog. Please refer to the ArcGIS Desktop help to further explore all the settings available in creating a customized text symbol.

The 'Use layer label properties' setting is used as the default, since it gives the most flexibility in setting the look of the labels.

Label_Style
Label_Weights

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Left Justified
This option displays left justified standard OmegaGIS font, which is black, Arial, 10 point, Italic, and Bold.
l Center Justified
This option displays center justified standard OmegaGIS font, which is black, Arial, 10 point, Italic, and Bold.

Near an Address label style:

This setting allows the user to choose the look of the labels generated from the 'Near an Address' routine. Each setting option will generate a label that contains the address text entered by the user in the Where? tab of the 'Near an Address' routine. All the labels generated from this routine will be included on the OmegaGIS Buffers annotation group. The three options that can be set are as follows:
l Buffer Balloon Callout
The text box that is generated from this setting is positioned just outside the upper right portion of the buffer and a leader line connects the box to the address. The address is

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
marked by a red 'X'. This is the default option.
l Point Balloon Callout
The text box that is generated from this setting is positioned at the upper right portion the address and has no leader line. The address is marked by a red 'X' that covered by the text box.
l Text Only
Text that is generated from this setting is positioned just outside the upper right portion the address and has no leader line. The address is marked by a red 'X'.

Label Weights
Annotation groups are stored in the map document and enable you to manage and organize graphics in the data frame.

Managing Annotation groups:

To manage the annotation groups in the active data frame, choose 'Data Frame Properties' from the 'View' menu and click the 'Annotation' tab. In this tab you can set a reference scale, assign an associated layer, toggle visibility, add new groups, and remove groups. To set a reference scale or associate the annotation group to a layer select an annotation layer and click the 'Properties' button.

A reference scale of 0 will draw text at the same size regardless of your data frame's scale. If a reference scale is specified then the labels will draw at the specified size only when zoomed to that scale. If another scale is applied then the text will either get smaller or larger.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Associating a layer to an annotation group will make the labels in the annotation group turn off when the layer is turned off.

Organizing Annotation groups:

Graphic elements in the data frame can be drawn on different annotation group layers. Like layers in the table of contents, annotation groups have a draw order. In the table of contents, the draw order of layers is established from bottom to top, meaning that the bottom layer is drawn first and the top layer drawn on top of all other layers. Annotation group layers can be placed in a draw order by setting up conflict detection rules in the data frame. The conflict detection rules can be manually accessed by choosing 'Data Frame Properties' from the 'View' menu and click the 'Labels' tab.

These rules specify which annotation group has the lowest drawing priority and which has the highest. Annotation groups can have a weight of low, medium, or high. The general rule is that a graphic or label with a higher weight cannot be overlapped by a label with a lower weight. It follows that the user should give more important labels higher label weights. Within annotation groups draw order is establish by the order by which the graphics are added. The first graphic is on bottom and the last graphic added is on top. The settings in this subcategory deal with assigning weights, or priority, to OmegaGIS annotation groups and to the default annotation group.

If you wish to know more about annotation groups and label placement, please refer to ArcGIS Desktop Help.

Note:

The settings for label weights will only take affect after an OmegaGIS routine is run. l Add labels to a new feature linked annotation group
This setting creates a new or replaces an existing annotation group for the layer to be labeled in OmegaGIS routines with the exception of the 'Near an Address' routine. The new annotation group will only get created if the label check box on the Where? tab is checked.

It will be associated to the boundary or feature layer that it is labeling. The name of the new annotation group is always "OmegaGIS LABEL >" followed by the name of its associated

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
layer. Because this setting replaces an existing annotation group, if a routine is run where a previously labeled layer is labeled again, the previous annotation group and all of its graphics will be removed and recreated with the labels from the new routine. The default for this setting is to create a new annotation group for each OmegaGIS routine that creates labels. l Weight of new annotation group:

This setting is used to specify the weight or drawing order of the new annotation group.

This setting by default is set to High.

Tip:

In general, this setting should always be set to the same level as the default annotation group.
l Weight of default annotation group:

This setting is used to specify the weight or drawing order of the default annotation group. By default this setting is set to High.

The default annotation group contains the text added by dynamically labeling features. Only features labeled in this way will respond to this setup setting. Therefore, all text and other graphics manually added to the default annotation group will be displayed either on top or on bottom regardless of this setting. Dynamically labeled features are labels generated by the user right clicking on the layer to be labeled and selecting the menu item 'Label Features'.

Tip:

In general the default annotation group should be set to a weight above that of the buffer annotation group, so that buffers don't overpost geographic labels such as street names. l Weight of OmegaGIS buffer annotation group:

This setting is used to specify the weight or drawing order of the OmegaGIS buffers annotation roup. By default this setting is set to Medium.

The OmegaGIS Buffers annotation group is automatically created when either a routine is run that creates a buffer or a label is created for the "Near an Address' routine. This annotation group is only created if it does not previously exist. If the OmegaGIS Buffers annotation group did previously exist and a routine is run where new graphics are created, these graphics will be added to the existing graphics in the annotation group. The name of the new annotation group is always "OmegaGIS Buffers", and this annotation group has no association to any layer.

Tip:

In general the OmegaGIS Buffers annotation layer should be set to at least one weight less than the default annotation group. This is so geographic labels, such as street names, show through the buffer.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Setup: Databases (Locations)
Setup stores path information to the saved queries database and Crystal Report locations. This category stores and manages that path data. The subcategories reflect the types of paths stored:

Crystal Reports
The Crystal Reports tab sets up the locations of the reports. These directories will be searched for Crystal Reports. One or more report locations can be defined. The order of the report locations is important. The Create Reports routine will search in the first directory, then the second, etc. The arrow keys can be used to change the priority of the report locations. The default report location is the reports folder in the project workspace.
l Add
Opens a browser dialog where the user can search the available local and network directories to select a file folder where Crystal Reports reside. The 'OK' button on this dialog will only be available when a folder is selected.
l Remove
This option deletes the selected Crystal Report location. This button will only be enabled when an location is selected.

To register specific reports to data layers use the Metadata Editor in ArcCatalog.

Saved Query
The Saved Queries tab is used to set up the locations of the saved query databases (Omega_Query.mdb). This is similar to setting the report locations on the previous tab. One or more saved query locations can be defined; the directories will be searched for existing saved query database. The order of the saved query locations is important. The saved query tree will search in the first saved query database, then the second, etc. The arrow keys can be used to change the priority of the saved query locations. The default location for the saved queries database is in the project directory.
l Add
Opens a browser dialog where the user can search the available local and network directories to select a file named Omega_Query.mdb. The 'OK' button on this dialog will only be available when this file is selected. This file contains the values used to populate the saved query tree used in OmegaGIS routines. To edit the saved query database use the Saved Query Editor in ArcCatalog.
l Remove
This option deletes the selected Saved Query database location. This button will only be enabled when an location is selected.

To register specific query groups to data layers use the Metadata Editor in ArcCatalog.

Crystal_Reports
Saved_Query
Street Network

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Street Network
The Street Network location tab is available for FireView Setup only. Street Networks are created using the Omega Street Network tools on the Omega Data Manager toolbar in ArcCatalog. The default location that is searched for street networks is within the project directory structure under \Networks. Any additional locations that should be searched, must be entered using the Add button. The Remove button will delete the location, so that any routines using street networks will no longer search this folder.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Setup: Threshold Alert
Threshold Alerts require information on who will be alerted, how they will be alerted and with what information they be alerted. All these parameters must be set in order for Threshold Alerts to run. Each of the first three subcategories deals with one of these three aspects. The subcategories are:

The Email Settings subcategory allows the user to set the header information for the email. Email Addresses sets the recipients names and email addresses. SMTP Settings deal with the location of the email server on the network. And finally, the Advanced tab relates to optimizing the threshold alerts database.

NOTE:

SMTP Settings and Email Addresses are related, in that every email address must be associated with a server. For this reason it is HIGHLY recommended that the SMTP Settings be set BEFORE any Email Addresses are entered.

Email Settings
Email Settings lets the user specify custom header and subject information that will be included in the Threshold Alert email.

From email address
l From email address
This setting includes a text box where the user specifies the email address that will shown in the from line of the email header. The address must be in the format [email protected] and be longer than 6 characters in length. l Send a copy to this email address (CC)
This setting carbon copies (CC) the email address entered in the text box above.

Email Subject Information
l Threshold group and alert name
This option will populate the subject line with the name of the Threshold Alert that is being run. This is also the name of the threshold alert group.
l Number that exceeded threshold
This will also include the number of incidents that occurred in the line of the subject.

Email_Settings
Email_Addresses
SMTP_Settings
Advanced

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Custom subject
This text box allows the user to enter a custom subject for Threshold Alert emails.

Email Addresses
Emails may be sent to any valid email address, however the Email Server must be identified for each address. Email addresses that are entered before any servers are set will be associated with a generic 'default' server. If the setup dialog is closed and a default server is not specified a warning message will be issued, the dialog will not close and the SMTP Settings tab will be displayed. For instructions on how to set a default server see the SMTP Settings header. l New...

Preferably after the SMTP server information is set recipient information can be added by clicking the 'New...' button that opens a new dialog. This dialog is used to gather information about the recipient and about the server specific to the new email.

Recipient information
l Name
The text entered into this box should be a descriptive name of the recipient. l Email Address
The text entered into this box specifies the email address for the recipient. The address must be in the format [email protected] and be longer than 6 characters in length. l Do not send email to this address
Checking this box will not allow email to be sent to the specified recipient. This setting could be helpful if the user wants to set up an email address and even include this email address in the alerts notification, but not have any mail sent to the addressee. Checking this box will give the email a grayed out icon.

SMTP server information (optional)
This setting is optional because by default all new emails are associated with the default SMTP server.

This setting allows the user to set emails to different servers.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
NOTE:

If only one SMTP server is used then this setting can be ignored.

This setting includes a tag that tells the user the current default SMTP server. There are two different messages displayed in this tag to aid the user in selecting the appropriate server for the email. The tags are as follows:

The Default SMTP server is: <SERVER NAME>
This will be displayed if a default SMTP server is set. If there is only one SMTP server set and it is designated as the default the rest of the settings in this option will not be available. Otherwise if there are multiple servers another could be assigned to this email.

There is no default SMTP server.

This message will be shown either if there are no servers set or if there are no default server set. In either case if another server is not assigned each new email would be given a generic 'default' server which would be assigned to the emails when the actual default server is set in the SMTP settings tab. l Select an SMTP server for this email that is different than the default The default server is always used for a new email by default. This checkbox allows the user to override that setting and specify a server that is not the default if it has been added to the SMTP server list in the SMTP settings tab.

If this box is checked then the list below will be populated will all the SMTP servers in the SMTP server list that are not the default. Another server must be chosen if this box is checked. l Edit...

Clicking this button, allows the user to edit all the information about a selected email address. The same dialog opens as when the 'New...' button is clicked, with the exception that it is populated with the information about the selected email. The recipients information or the SMTP server information can then be updated and saved. l Remove
This option deletes the selected email address. This button will only be enabled when an email is selected.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
SMTP Settings
In order to send Threshold Alerts to the appropriate personnel, an SMTP server must be selected. The first step in setting up the SMTP Server information is to research the names or IP addresses of the SMTP server used at your site.

Contact your system administrator for this information. l New...

When the Names or IP addresses are acquired, they can be entered into a list using the New button. Clicking on the New button opens a dialog which provides a text box for either the Name or the IP address. This information can be entered manually or browsed from a list of servers on your network. l Name or IP address of SMTP server:

The text entered into this box should contain the name of the IP address or the server name received from your system administrator. The server name can be manually typed in or the servers on your network can be accessed by clicking the browse button.
l Use this server as the default
Selecting this check box automatically assigns the server to any email address entered after the default server is set. The default server is identified by a red checkmark within the icon, next to its name in the list. This setting should always be used if there is only one server that will be added. If there are multiple servers being added then set the default server to the server which is associated to the most emails. l Edit...

Clicking this button, allows the user to edit all the information about a selected SMTP server or IP address. The same dialog opens as when the 'New...' button is clicked, with the exception that it is populated with the information about the selected server. The server name and default status can then be updated and saved.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
l Remove
This option deletes the selected SMTP server or IP address. This button will only be enabled when a server is selected. If a server that is attached to an email is attempted to be removed a message box will appear notifying the user. Emails associated with that server will have a letter icon with a red exclaimation point.

If this occurs go into the Email Addresses tab and repoint all the addresses that have the new icon to a new server by clicking the 'Edit...' button.

Advanced
The Advanced tab allows the user to use some simple database management tools to optimize the performance of the threshold alert database.

Database Tools
l Compress
Email address and server information is saved to the Threshold Alert personal geodatabase in the project folder.

If many edits to the database are made, it is a good idea to compress the database as it can become large due to the accumulation of edits and deletions.

History Files
l Clear History
This setting is available to keep the size of the database manageable. History records refer to those records that track when a threshold is sent. They should be deleted from the database when this information is no longer required.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Setup: Global
Global settings apply to all ArcMap Documents. Changes to the Global settings will take affect the next time the ArcMap document is opened.
l Splash Screen displayed on startup
The Omega Desktop splash screen is displayed on the start of ArcMap. When this setting is checked the splash screen will be displayed.
l All extensions used with OmegaGIS routines (ie. Spatial Analyst) will be automatically enabled if they are available
The Spatial Analyst extension is used in the OmegaGIS Density routines and in the Analysis routine Spatial Trend. To use these routines, Spatial Analyst must be licensed and enabled on the current machine. For information about installing and licensing ESRI extensions please use ArcGIS Desktop Help. This setting automatically enables Spatial Analysis or any other necessary extension when the OmegaGIS extension is enabled.
l Previous Week Date Range
The date/time control has the functionality to select a date range for the previous week. The day of the week to use for the start of the week is controlled by this setting. The default date of the week is Sunday.
l Crystal Reports
The Crystal Reports version to be used when opening the reports is controlled by this setting. The user can choose from the selection of available versions. The default version used is Crystal Reports

11.5. For information about the number and names of Crystal Reports versions installed on the users machine click "Get Installed Versions".

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaSetup....

Attachment A
Performance And Tuning
Enhancing the performance of ArcGIS and OmegaGIS software can be accomplished by using several of the tips and best practices that are outlined in the following sections. Designing a project that leverages all of the benefits of both ArcGIS and OmegaGIS requires some preparation during the initial stages of project design. It is important to spend some time reviewing the architecture, as well as the software settings in order to tune the project to run as fast and as efficiently as possible.

Performance Checklist
Hardware
l Computer meets Omega hardware requirements.
l Follow computer maintenance practices.
l Network is good operating order.

GIS Data
l Large datasets that rarely change are on local machine. l Geographic data stored in personal geodatabase rather than a shapefile. l Number of fields in incident data kept to a minimum.
l Limit the number of records in layer.
l All layers should share the same projected coordinate system. l Rasters should have pyramids built.

ArcMap Tuning
l Limit number of layers in ArcMap document.
l Use tools for map navigation.
l Do not use map tips.
l Use scale dependency for layers and labels.

ArcCatalog Tuning
l Use folder shortcuts.
l Limit files displayed.

OmegaGIS Setup Tuning
l Follow best practices for OmegaGIS setup.

OmegaGIS Tuning
l Limit number of saved queries.
l Compress personal geodatabases.
l Use spatial and attribute queries when using OmegaGIS routines.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Hardware
This topic outlines the best practices and recommendations for hardware when using ArcGIS and OmegaGIS.

Hardware requirements
Computer Maintenance
Network
Hardware Requirements
The Omega Group suggests that for Minimum Requirements, the following hardware suggestions be followed.

Processor: Intel Dual Core
Memory/RAM: 2 GB or greater
RAM and the Pagefile are used by Windows XP to store temporary data as operations are performed by the operating system. Windows XP tends to require significant amounts of RAM, and often exceeds the allotted RAM for the machine. When this overflow occurs, information is saved to the Pagefile.

Unfortunately, reading and writing to the Pagefile results in reading and writing to disk, and can bog down performance. If the Pagefile size is too small, it becomes fragmented across the disk, and can further slow down a machine.

It is therefore important to have enough RAM and a large enough Pagefile size to operate efficiently. Omega recommends at least 2 GB of RAM . The general rule for the Pagefile size is 2X the RAM. The Pagefile cannot exceed 4095 KB, as this is the limit set for Windows XP.

Free Disk Space: 10 GB NTFS
Disk space is critical to maintaining a stable system. When disk space becomes low, performance can degrade, and system crashes occur more frequently.

Video Card: 256 MB or greater
When dealing with complex graphic files it is important to have a good video card that enables applications to quickly draw and refresh images. If a video card can only cache a small amount of data, the result is slow performance.

Computer Maintenance
Disk Space
Disk space is critical to maintaining a stable system. When free disk space becomes low, performance can degrade, and system crashes occur more frequently. There are several places on a computer that can become bogged down with temporary files created by different applications.

The Temp directory is a common location for applications to store temporary files. In some cases these files are removed automatically, however, often they are not. Empty the temp directory of files to increase disk space where possible. When files are removed from the Temp folder in Windows Explorer, the files may be moved to the Recycle Bin. To ensure space is cleared on disk, clear the Recycle Bin of files.

If using the Internet frequently, numerous files can accumulate that are created when visiting different web sites. Using Internet Explorer click on Tools > Internet Options and select the General Tab. Delete the temporary internet files using the buttons provided, and clear the history folder.

Disk Fragmentation

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Disk fragmentation occurs when files are added to or removed from disk. As disk fragmentation worsens the reliability and stability of a system degrades. Four effects of a fragmented disk include, increased boot up time, increased shut down time, an increase in the number of system crashes and slower or no response times from applications and the operating system.

To avoid problems with fragmented disks, use the Disk Defragmenter tool available from Start > Programs > Accessories > System Tools.

Applications and Processes
Windows XP is configured to ’rsquor;multitask’ between applications so that it appears that these processes are occurring simultaneously. In fact, the operating system is actually switching rapidly between processes, executing one at a time. This rapid switching between applications or ’r;multitasking’ is the reason that as more processes are added, the slower the operating system performs.

The first defense for removing the effects of multitasking is to identify any applications, processes, features or services that are unnecessary. In the lower right corner of the computer screen, a system tray identifies some of the applications running in the background. Remove the applications that are not required. To turn off services, right click on My Computer and select ’r;Manage’.

Expand the ’r;Services and Applications’ menu item to identify those unnecessary services.

However, do not remove services if you are unsure.

Personalized Menus, a feature of Windows XP, tracks menu items opened frequently and hides those rarely used. This process requires significant memory and can slow down performance. To turn off this feature, access Start > Settings > Taskbar and Start Menu and uncheck the ’r;Use Personalized Menus’.

Other features requiring large memory overhead can be found by right clicking on the Desktop, and selecting Properties > Effects. Turn off ’r;Use Transition Effects&ldots;”, ”r;Smooth edges of screen fonts”, and ”r;Show window contents when dragging”. Finally, in Windows Explorer, select Tools > Folder Options > General and set the Web View to ’r;Use Windows Classic Folders”. Windows will no longer create thumbnails for each file, which is memory consuming when complex images are selected.

Network
Many agencies using ArcGIS require that data central to GIS analysis be housed on a central server so that current information can be shared effectively. Moving large GIS datasets across a network however, can result in significant degradation in performance. The following recommendations and suggestions are aimed at the practices of the IT department of an agency in order to optimize performance for users of GIS data and software. Omega recommends GigaBit Nic (Network Interface Cards) for good speed.

There is some evidence that in switching from Windows NT to Windows XP, there is a significant drop in performance over a network. Consequently, it is important to ensure that network cable problems are resolved, since any problems are exaggerated by the higher network traffic. To ensure cables are in optimum condition, check for shorted patch cables and bad switch connections.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
GIS Data
ArcGIS consists of ArcMap and ArcCatalog. Both of these components can be fine tuned in order to deliver faster performance when browsing or viewing large GIS datasets. In accessing GIS files, it is important to understand the impact of the file location on the speed and response time of these applications. This section has the following topics:

Local Data
Data Format
ArcSDE
Coordinate System
Raster Files
Local Data
Generally, GIS departments prefer to locate GIS data to be shared by all users in a central location, such as on a server, where it can be updated easily, and data redunancy is kept to a minimum. If users are accessing this data across a network, ArcMap and ArcCatalog may appear exceedingly slow.

Copying large datasets locally increases performance significantly, and should be considered when creating a GIS system architecture. Omega recommends that file-based data that rarely changes, such as street centerlines or police beats, be copied to the local machine. Only data that is updated frequently, such as incident data that is updated by the Omega Import Wizard, should be on a centralized server.

Data Format
With the advent of the personal geodatabase (MDB), a further advance is available to decrease the time it takes to access files across a network, or locally. As ArcGIS is tuned to work with the personal geodatabases, faster speeds can be achieved when shapefiles are converted to personal geodatabases.

In recent tests, the retrieval times of the personal geodatabase exceeded those of the shapefile both locally and over a network.

There is no longer a ten character limit on field names in the personal geodatabase as is the case with the shapefile format. The field name limit becomes a problem when creating shapefiles from other sources. When the field names are cut off to suit the ten character limit, occasionally duplicate field names are created.

Finally, the personal geodatabase supports a larger file size. The speed in retrieving information from a personal geodatabase does not start to degrade until the file size reaches about 250 MB.

Omega recommends the use of the personal geodatabase over shapefiles when possible.

ArcSDE
When working with large geographic datasets, ArcSDE provides an excellent alternative to storing geographic data in file based systems. ArcSDE is a gateway that enables the management of geographic data in database management systems. The software manages the access and distribution of spatial data to multiple users.

There are a number of ways to tune ArcSDE that can be used to increase performance depending on the architecture of the GIS system. The Omega Group can provide information as to whether ArcSDE is a viable investment as there are costs associated with the additional hardware and

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
software required to use this approach.

Limit Fields
To keep the incident data file small, the number of fields should be limited to those required to do analysis with OmegaGIS. OmegaGIS routines frequently cycle through field lists within layers. By keeping the number of fields down, the number of times a routine must loop through the list of fields is kept to a minimum. Additionally, limiting the number of fields will reduce the overall size on disk of the GIS file.

Limit Number of Records
Apart from limiting the number of fields within the incident data file, the number of records can be reduced by splitting up the GIS file either geographically or historically. Since OmegaGIS routines can accommodate querying multiple layers, sub-setting the data is now possible.

Omega recommends that a shapefile contain not more than 100,000 records and a personal geodatabase not contain more then 250,000 records.

Spatial Index
Indexes always increase the speed with which features can be searched within geographic files.

Ensure that spatial indexes have been created on all layers that are frequently used in geographic analysis. A quick way of determining whether a spatial index exists is to right click on the layer name in the table of contents, open &rsquor;Properties’ and select the &rsquor;Display’ tab. If a spatial index does not exist for the layer, the 'Map Tips’ option will be disabled. Spatial indexes are automatically created for personal geodatabase layers, while, shapefiles must have the index explicitly set.

Coordinate Systems
Coordinate systems provide the capability to locate points on the Earth's surface. A coordinate system may be either geographic or projected. A geographic system locates positions on the earth’s spheroid, while a projected coordinate system undergoes a &rsquor;map projection’ to locate points on a flat surface.

Omega recommends that a projected coordinate system should always be used when performing spatial analysis in ArcMap. This is because geographic coordinate systems do not deliver accurate measurements. Aside from creating a more accurate environment for spatial analysis, ensuring each layer within an ArcMap project is projected into the same coordinate system also increases performance. Since the layers share the same projection, they do not need to be re-projected on the fly, and this results in increased performance.

To determine a layer’s spatial reference in ArcMap, right click on the layer name and select Properties. Click the Source Tab, the Coordinate System is shown in the Data Source Textbox.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Raster Files
Raster files are images that are divided up by cells in order to create a smooth picture of a geographic area. Raster files typically take up significant amounts of disk space, and are slow to draw. Constructing pyramids for raster files is an excellent way to reduce on the amount of time it takes to refresh raster data on the screen.

Pyramids are multiscaled, resampled versions of the raster data. Without a pyramid the entire dataset is read from disk and resampled to a smaller size. Pyramids reduce the amount of time reading from the disk, by displaying less data as the user zooms out of the raster.

A pyramid can be created very easily by right clicking on the raster name in ArcCatalog and selecting the Build Pyramid option. To enhance performance further, switch the Display Quality option from Normal to Medium. This option is available in ArcMap, by right clicking on the layer name in the table of contents, selecting Properties and the Display tab.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
ArcMap Tuning
This section outlines Omega recommendations to improve the performance of ArcMap.

Data Inclusion
Map Navigation
Map Features
Data Inclusion
When designing a new ArcMap project, it is important to keep in mind the impact of the data included in the project on performance. The number of layers added to a project, should be limited to those used in analysis. If additional layers are required for visualization purposes, they can be turned off while running routines.

It is also possible to set the layers to be automatically invisible when they are added to the project by selecting the Tools menu > Options and the Application Tab.

Map Navigation
Bookmarks
Bookmarks provide an excellent way to create points of interest on a map that can be revisited easily. Navigating by use of a bookmark is often faster than using the pan and zoom tools available from the ArcMap toolbar.

To create a bookmark, zoom to the area of interest, and select View > Bookmarks > Create from the ArcMap menu. Enter the name of the bookmark. Zooming to the area is now easily replicated by clicking on the name of the bookmark.

Layer Overview Tool
To access the Overview tool, click on Window > Overview and an overview window appears on the screen, from which you can view the full extent of the data in the project. The red highlighted box represents the layer on which the overview tool is based.

The Overview tool can be used to easily pan throughout the extent of the active data frame while limiting the number of times the data frame must be refreshed.

Magnification Tool
The Magnification tool is useful to view details on the map without having to use the pan or zoom tools. The Identify and Select Features tools can be used within the magnification window. To access the tool, click on Window > Magnifier. A magnification window will appear on the map.

Right click on the title bar of the window and ensure that &rsquor;Update While Dragging’ is not selected. This feature updates the window frame by frame as it is moved across the map, and slows down the performance of the tool.

Map Features
Map Tips

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Map Tips show information about features in a layer based on their display field. By hovering over the feature on the map, a popup window opens to show the field value without the use of the interactive tool. Although this feature can be extremely helpful for users investigating the map, the tool does interfere with the Zoom In and Zoom Out capabilities of ArcMap, and may slow these processes down. To limit the impact of Map Tips, only turn the map tips on for those layers that are necessary.

To remove Map Tips from a layer, right click on the layer name in the table of contents, and select 'Properties’. Click on the display tab, and toggle the &rsquor;Show Map Tips’ setting.

Scale Dependency
Scale dependency refers to the scale at which a layer is displayed within the project. For layers with a high level of detail, at smaller scales it is a good idea to make them invisible as refreshing them on the screen can take considerable time and resources. To set the scale dependency of a layer, right click on the layer name in the table of contents and select Properties. Select the General Tab, and enter the appropriate maximum and minimum scale range at which to display the layer.

Graphics and Symbology
The greater the complexity of symbols, the slower they are to draw on the map. Keeping symbology and graphics simple improves performance. Halos on large amounts of text are especially slow to display. Text shadowing can be used in place of halos, and at a lower cost to performance. Simplicity of symbology to improve performance, also applies to lines. Dashed and patterned lines display more slowly. Limit the use of complex lines where possible.

The advanced drawing options available by right clicking on the data frame, control how the symbols on the map are drawn. This feature does slow performance due to the fact that multiple redraws must take place to display the symbols. Avoid the Advanced Draw Symbol options unless necessary.

Label Scale Range
When displaying labels on the map, a scale dependency can be set explicitly for the labels. Right

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
click on the layer name, select Properties, and the Labels Tab. A scale range can then be set to view labels only at an appropriate scale.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
ArcCatalog Tuning
ArcCatalog provides the interface for viewing and browsing GIS data. Depending on the size and complexity of the files, previewing and connecting to the data may occur more slowly. Outlined are Omega's recommendation for improving performance.

Folder Shortcut
Limit Files Displayed
Folder Shortcut
To reduce the amount of time browsing for files, create shortcuts to folders and databases containing GIS information. From the File pull-down menu in ArcCatalog, select Connect Folder and then dialog that opens, browse to the folder to create the shortcut for.

Limit Files Displayed
The types of files displayed by ArcCatalog can be narrowed by using the Tools > Options dialog to determine which top level entries and data types to display. A top level entry might be a folder or database connection, while a data type might include a shapefile or personal geodatabase.

An option exists in the same location to display only those files that contain GIS data. Enabling this option however slows down the rate at which files are displayed as they are searched each time for GIS data. Disable this option to ensure faster performance.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Omega Setup Tuning
Omega Setup is a feature of Omega Desktop software in which predefined settings can be maintained during the use of the routines in the project. Many of these settings and options are designed to improve performance while conducting analysis on large and complex geographic datasets.

The following items from Omega Setup are identified as performance saving features, and should be set appropriately when initiating a new Omega Desktop project.

Unique Field Values
Selection Layers
Summary Dialog
Registered Type
OmegaGIS Layers
Composite Layers
Map Thumbnail
Splash Screen
Unique Field Values
In most OmegaGIS routines, the 'Select By Field Value' option exists to select polygons from a map layer using the values from the attribute table associated with the selected layer. For very large datasets, with thousands of records, updating the field list on the dialog can be slow. There are two settings available that can speed the time it takes to update the field value list. Both settings are available on the Advanced Tab of the General Settings category.

The &rsquor;Number of records used to determine unique list of values’ option, displays a range of values from 300 to 10,000. Selecting one of these values determines the number of polygons in the layer that will be sampled for unique values in order to populate the field values list box on the routine dialog. For instance, for a parcel layer consisting of 50,000 polygons, if the value is set to 10,000, only 10,000 polygons within the parcel layer will be sampled for unique values.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
The &rsquor;Number of records to display in unique values list’ option describes the actual number of records that will populate the list of field values. For instance, if 10,000 records are sampled from the parcel layer, and this option is set to 5,000. Only 5,000 field values will be listed in the list. If not all the polygons are sampled before the maximum number of unique values in the list is hit, a warning message appears on the dialog next to the list.

The purpose of these settings is to limit the use of the field value list for very large datasets with thousands of records. In these cases, it is better to use the &rsquor;By Pointing’ method to select polygons from the map layer.

Selection Layers
Selection layers are subsets of a feature layer that share the same dataset. When performing many queries, selection layers can quickly overrun a project. Consequently the &rsquor;Allow only one selection layer’ option, available on the Query Tab of the from the Queries category overwrites the selection layer each time a query or analysis is run.

Summary Dialog
The summary dialog opens a window that summarizes the selections made during an OmegaGIS routine. The summary dialog also allows access to saving a query as a cyclical report or threshold alert. On the Query Tab of the Queries category, select the &rsquor;Display the routine summary dialog’ option to turn this dialog on. The summary dialog does interrupt the routine, so turning it off saves time.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Registered Types
When a data layer is used in an OmegaGIS routine it should be registered with a type. Registration is possible using the OmegaGIS MetaData Editor available in ArcCatalog. To avoid populating OmegaGIS routine layer lists with layers that should not be part of queries or analyses, the Queries category provides a Registered Types tab with a setting called &rsquor;Only use registered layers’.

This option can be set to show only those layers that apply to the specific registered layer types selected.

OmegaGIS Layers
As well as explicitly excluding non-registered layers from the layer lists during OmegaGIS routines, layers created by OmegaGIS routines can be excluded from the layer lists. Within the Queries category, on the Advanced tab, the &rsquor;Exclude layers created from OmegaGIS routines&ldots;’ can be checked in order to limit layers to be used in analyses to the original data sources and not the output from those sources.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Composite Layers
Composite layers are created when the &rsquor;Use Additional Queries’ checkbox is used during an OmegaGIS routine. This feature combines query layers during the analysis, and outputs a resulting &rsquor;composite’ layer. Similar to &rsquor;Selection’ layers, if a composite layer is created each time a routine is run, the project can quickly become overrun by resultant layers. From the Queries category, Advanced tab, the &rsquor;Only create one new composite&ldots;’ option can be selected to overwrite the single composite layer each time a new routine is run.

Map Thumbnails
Map thumbnails are overview images representing the GIS content of a project. From the Advanced tab of the General Settings in OmegaGIS Setup, a thumbnail can be created when the project is closed. Although thumbnails can present valuable overview information while browsing GIS projects in ArcCatalog, creating them automatically while closing a project degrades performance.

Splashscreen
The OmegaGIS splash screen opens during the startup of a project. The image can be turned off to save time. When the splash screen is visible, processing is interrupted to show the image. Turning the image off, allows processing to continue and increases performance.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
OmegaGIS Tuning
This section outlines some best practices to improve performance when using OmegaGIS routines.

Saved Query Database
Compressing Personal Geodatabase
Spatial and Attribute Queries
Saved Query Database
The saved query database is responsible for housing queries that are used on a regular basis. The database provides the data source for the Saved Queries Tree, located on many of the OmegaGIS routine dialogs. When a new layer is selected during an analysis, the Saved Queries Tree is populated with all of the saved queries from the database. It is important to keep the number of saved queries reasonable, to reduce the hit on performance while selecting a new layer with associated queries. Databases containing thousands of records can cause a significant reduction in performance as opposed to those with hundreds of records.

A way to limit the number of saved queries is to have one saved query database (Omega_Query.ODB) that contains the most commonly used saved query groups, such as RMS, and place this database in the project workspace
. Then have another saved query database that
has more detailed saved query groups, such as RMS_Detailed and place this database in a folder other than the project workspace. When it is necessary to use the detailed saved query group, add the path to the database in the OmegaGIS Setup dialog. Note, in this example, the layer would have to be registered to both RMS and RMS_Details saved query groups and the Saved Queries Tree would only be populated with the saved queries groups that were found.

Compressing Personal Geodatabase
Many of the intermediate temporary files created by OmegaGIS are stored in personal geodatabases. In most cases, these databases are compressed when exiting the project.

Compressing the databases is important because as they are used, they may become fragmented on disk, taking up more space than is necessary. The Threshold Alert database is the only database that is not compressed automatically. Within OmegaGIS Setup in the Threshold Alert category, an option exists to compress the database.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
Spatial and Attribute Queries
Often GIS layers can be extremely large. Sub-setting the data by using attribute or spatial queries while running an OmegaGIS routine can save significant amounts of time. Where possible, it is important to use the options available from the routine dialogs to subset the data by geographic boundary, time span or particular attributes.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\OmegaPerfor...

Attachment A
About the Dashboard
Availability by Extension
The Dashboard is an extension to Omega Desktop which provides the ability to publish analytical results to a web browser for distribution. The Dashboard extension is new at Omega Desktop 4.3, and can be licensed once Omega software is installed on a machine.

Dashboard content is created within Omega Desktop software, and once created can be automated so that the Dashboard is updated on a regular basis. Omega routines including all query routines, density routines, and the Response Time Map routine in FireView are available for automating content to the Dashboard. The results of all other routines can be posted to the Dashboard as maps or reports by using a publishing tool provided with the software.

It is important to consider hardware, software and personnel when determining the best approach for setting up the Dashboard. A desktop machine must be identified that will run Omega Desktop software, as well as a web server and a database server. The web server will host two web applications; one for viewing the published data, and one for managing the data. In addition, a web service running on this server will provide the means for moving data from the desktop machine to the web server. The database server will provide a repository for storing metadata about the information that is posted. Finally, it is necessary to identify the personnel that will be responsible for managing the Dashboard application.

CrimeView FireView School Planner
Dashboard Dashboard Not Available

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\Dashboard.ch...

Attachment A

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\Dashboard.ch...

Attachment A
Hardware Requirements
The Dashboard is a very lightweight software product which can take advantage of a department’s existing server architecture, as long as those servers are within the Local Area Network (LAN). A department server structure may include both a web server and database server, or just one server running both database and web applications. The database server must have SQL Server 2005 or SQL Server Express installed, the Web Server must have IIS 6.0 and .NET Framework 2.0 installed.

One recommendation to note is that a server used as a Domain Controller by an agency should not be used to host the Dashboard web applications database. A Domain Controller can be recognized by the fact that it is running Active Directory; a component used to control user names, passwords and permissions to all machines within the network.

Using Existing Hardware
If a department has an existing Database Server running SQL Server 2005 or SQL 2005 Express, the database component of Dashboard can be installed. The initial size of the SQL database is only 2Mb. 100 Mb of space on the Database Server is sufficient to ensure that data has plenty of room to grow as content is added to it.

If a Web Server is already set up, the Dashboard can be installed on the existing server. The Web Server will require a shared folder be created on disk to store all of the files that are posted from CrimeView or FireView up to the server. These files consist of .PDF and .JPG formats, and may vary in size from 100kb to 1Mb depending on the file. 5 GB of space on the Web Server will ensure there is plenty of room for the Dashboard content to grow. For example, a web server with about 400 files published to the server might take up about 300 Mb of space.

Workstation Option
If for some reason an agency does not have existing servers available, or they are outside of the LAN network, then new hardware will need to be purchased. For a small department, it is possible to purchase a Workstation instead of a Server, however the Workstation will eventually need to be upgraded to a Server if the agency opts to upgrade the Dashboard to receive content from ArcGIS Server.

Single Server Option
An upgrade to the Workstation Option is purchasing a single server that acts as both the Database Server and the Web Server. This server has SQL Server 2005 or SQL 2005 Express installed as well as IIS 6.0 to run the web applications. The drawback to this configuration is that SQL Server can slow down the web applications. However, for a small department this limitation is negligible. The following minimum specifications are recommended for this server:
• 4 GB RAM
• Dual Dual-Core Intel Xeon Precessors (3.0 Ghz or higher) • RAID 1 and RAID 10 Disk Configuration using SAS discs 15K RPM (6 discs total) • 1 Gigabit Ethernet network cards
Multiple Server Option

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\Dashboard.ch...

Attachment A
In a larger agency, it is standard practice to separate the Database Server from the Web Server. If an agency is interested in this
configuration, the Server specification above should be used as the Database Server, and the following specifications should be used for the Web Server. • Dual Dual-Core Intel Xeon Precessors (3.0 Ghz or higher) • 4 GB RAM
• RAID 10 Disk Configuration using SAS discs 15K RPM (4 discs minimum) • 1 Gigabit Ethernet network cards

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\Dashboard.ch...

Attachment A
The Dashboard Wizard
Introduction
The Dashboard Wizard is embedded in the Query, Density and Response Time Map routines of Omega Desktop software. The Wizard provides a way to save the results of these routines to a server, which can then be viewed using a web browser that displays the Dashboard application. To access the Dashboard publishing capabilities from these routines, simply configure Omega Setup to open the Summary dialog before the routines are run. A 'Dashboard' button on the Summary dialog will open the Dashboard Wizard.

Before using the Dashboard Wizard it is important that the Dashboard Administrator create the Viewers that will be used to group the published results. Viewers are the building blocks of the Dashboard, and each Viewer represents one panel on the Dashboard Viewer web site that can be displayed through an internet browser. Results may only be posted to predefined Viewers, and Viewers can not be created from the desktop application. To discover how to create Viewers, see the Omega Dashboard Administrator help guide.

Dashboard Wizard Dialogs
When the Dashboard Wizard is opened, the first panel that is presented enables the ability to select from a list of Viewers that have already been created by the Dashboard Administrator. If the Dashboard Administrator has not created any Viewers, there will be two Viewers available by default; the Image Bank and the Document Bank.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
The Image Bank can be used to store maps or graphs published from the Wizard, while the Document Bank may be used to store any reports that are created with the Dashboard Wizard. Other Viewer types that may have been created by the Dashboard Administrator will be listed, and the various Viewer types can be identified by the icon that is displayed with the Viewer name. The Viewer types are listed below with their icons.

Single Image
A Single Image Viewer stores an image and presents it as a panel on the Dashboard. With the Wizard, a map or graph can be created and saved to the Viewer.

Multiple Images
The Multiple Image Viewer builds upon the Single Image Viewer in that more than one map or graph can be added. When viewed on the Dashboard, the user is able to scroll through the images in an accessible manner.

Image with Report
In this viewer, a map image is always linked to a report. Similar to the Multiple Images Viewer, the user can scroll through the images, but in addition, a link to a report for each image is included.

Reports
The Report Viewer presents a list of report links. The user can click on any of the links in order to view the report in PDF format.

Image Bank
The Image Bank is simply a Multiple Image Viewer with a specific name. This Viewer is designated as the default Viewer for all images that are published with the Dashboard Publisher tool.

Document Bank
The Document Bank is a Reports Viewer with a specific name. This Viewer is designated as the default Viewer for all reports in PDF format that are posted using the Dashboard Publisher tool.
*MyLinks
An additional Viewer type called MyLinks is available when viewing Dashboard content through a browser. This type is not available from the Desktop Dashboard Wizard however as it does not involve generating content from the desktop application.

Content Type
Once a Viewer is selected, a content type may also be selected from a dropdown list. Only certain content types are available to certain Viewers. For example, the Document Bank Viewer may only receive 'report' type content, and so, only the Report type is listed in the Content Type dropdown list. If the Image Bank Viewer is selected, only content that can be produced as an image is listed, and so, a map or graph content type is listed in the dropdown list. Selecting the Viewer will predetermine the type of content that is available and may be published to that particular Viewer.

Name and Description
After clicking the 'Next' button a new panel will appear that offers the ability to save a name and description for the content to be pushed to the server. A name must be entered into the textbox, however the description is optional. Click the next button to proceed to the next panel in the Wizard.

The content name that is entered will be visible in the first line on the Viewer panel, while the description is accessible based on the type of content that is published. For instance, if a map or graph is published, the description can be accessed by hovering over the image, but if a report is published, the description is located next to the report name. An example of the location of both name and description are provided below.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Templates
The next panel that will appear on clicking the 'Next' button will depend on the type of content that is published, but in all cases a panel is presented that allows for the use of particular templates to be associated with the content produced. If a map type is selected, then a template panel for Map Layouts is presented, if a Report or Graph type is selected, then a list of report or graph templates will become visible. If the Image with Report content type is selected, the Map Layout template panel is presented after which time the 'Next' button can be used to move to the template panel for the report that will be associated with the map.

Report Templates
Report Templates are provided with the Omega Desktop software and are customized to show detailed information about incidents that are selected by Query analyses. Crystal Reports is used to create these templates and the files are stored in a standardized project folder called \Reports. The files stored in this folder are automatically found by Omega Desktop software, including the Dashboard component, however to store reports in an alternate location Omega Setup can be used to identify the new location of the reports.

Once the report templates are created, they must be registered to the corresponding incident layers using the Omega Metadata Editor available on the Omega Data Management extension of ArcCatalog. Once the report is registered to the incident layer, it will appear in the template dropdown list of the Dashboard Wizard.

Graph Templates
Graph templates are provided with Omega Desktop software, and can be located in the Omega Desktop installation folder under the folder \graphs. Any graph that is located in this folder will be picked up by the Dashboard Wizard and displayed in the graph template list. New graph templates can be created and used by the Dashboard Wizard as long as they are located in this folder.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Map Templates
If a map content type is selected, an option exists to create the map with a page layout. The page layout is used to add elements to the map such as a legend, scale bar, north arrow and disclaimer. Page layouts are created using ArcMap, and this file can be selected using the Dashboard Wizard, and the map will be posted with the page layout.

An additional option called 'Apply to Thumbnail' is provided so that the page layout can either be attached to the map thumbnail or disregarded. When an image is posted to the server, both a large size and a thumbnail are created. The thumbnail is the image that is presented on the Viewer panel when it is displayed within the Dashboard Viewer website. In some cases, adding the page layout to the thumbnail may prevent the map from being clearly legible which is the reason for omitting it from the posted thumbnail image.

Automation
The final step in the Dashboard Wizard involves identifying whether the content will be posted as static or as automated. If the content is posted as static, then it will not be able to be updated on a regular basis. This content will be posted only once to the server. If the Automated content option is selected, the content may be set up to run regularly. The date duration must be selected from a list to identify which time period will be selected when the automation is run.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Clicking the Finish button will post the results to the server. All individuals that have been granted permission to view the results in the Dashboard Viewer website will be able to see the posted data whether it be maps, reports or graphs within one of the Viewers created by the Administrator.

Where Is the Data Posted?
When data is posted, it is the Omega Desktop Administrator that determines where this data will be delivered. The data is posted to one or more servers where it is stored for future use. Different agencies will have different server architectures, but there may be a maximum of three servers that can be used to store data.

The File Server
The file server is where the image and PDF files are sent when they are posted from the desktop using the Dashboard Wizard, Dashboard Publisher or Dashboard Editor. The file server information is identified in the Omega Desktop Administrator within the Dashboard Category on the File Server tab. The name of the file server and the name of the Web Shared Folder can be determined from this tab. The Web Shared Folder is created by the Dashboard Administrator personnel. This folder is shared so that both the Dashboard Viewer and Dashboard Administrator websites can access the data.

The Database Server
The database server is the machine on which SQL Server 2005 or SQL Server 2005 Express is installed by the Dashboard Administrator personnel. The SQL Server software manages a SQL database called OmegaDashboard which can be placed in any folder on the database server. Information pertaining to the database server settings can be collected using the Omega Desktop Administrator, Dashboard Category, Database Server tab.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
The Web Server
The web server is the location where the Dashoboard Viewer and Administrator websites are run. The web server must have IIS 6.0 installed to run the websites. To determine information about this server the Omega Desktop Administrator, Dashboard Category, Web Server tab can be used. In addition to the websites, the web server also runs a web service that is used in the communication between desktop and server machines. This web service can be identified on the same tab.

In many cases, the data files, the database and the websites can all be located on the same server. As long as the server has SQL Server 2005 or SQL Server Express 2005 and IIS 6.0 installed, one server machine can be used to run all server components of the Omega Dashboard.

What Is Posted to the Server?
File Types
When data is posted to the server, it may be posted as a few different types such as maps, reports, graphs or pictures. Maps, reports and graphs may be published using the Dashboard Wizard or Dashboard Editor. If the type is a map or graph, these files are actually posted twice, as a thumbnail image, and as a larger sized image. The thumbnail image is what is used on the Dashboard Viewer website to show an immediate view of the map or graph within a Viewer panel. Notice in the image below that the map shown is the thumbnail image posted to the server.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
The larger sized image is displayed once the 'Enlarge Image' option is selected on the panel. The size of this larger image is determined by the screen resolution on the desktop machine that was used to publish it. Depending on the screen resolution, the image will be created at a size that will always fit within the same screen resolution on a browser.

If the file type is a report then the file is posted again to the server, but this time only one file is posted in a PDF format. These files types are available for viewing within a Reports list. In the example below, a single report has been published to a Multiple Report Viewer. Clicking the yellow arrow to the left of the report name, will open the report PDF file in a new browser window.

Any image in JPG format or document in PDF format may be published to the server using the Dashboard Publisher tool. These files are posted in the same way in that the image file is posted as a thumbnail and at an enlarged size, while the document is posted once as a PDF.

Obtaining the Best Results
Publishing Maps
There are a few considerations to take into account when publishing maps to the server. When publishing image files to the server, it is important to consider the screen resolution which a majority of the personnel will be using on their machines. If for instance, if images are published at 1280 x 1024, but most users are viewing the information through their browser at 1024 x 768, then they will have to use the mouse to expand the images in order to view the entire file. When publishing imagery, it is recommended that your screen resolution match that of the majority of users accessing the Dashboard Viewer website.

If in addition to publishing the map, a page layout is included it is important to create the page layout at the same screen resolution that will be used to publish the map. If for instance a screen resolution of 1280 x 1024 is used to create the page layout, but the map is actually published at 1024 x 768, the resulting layout will appear blurry as it is compacted during the publishing process to fit the screen size.

Publishing Pictures
Images other than maps may be posted using the Dashboard Publisher tool. When posting an image, it is a good idea to ensure that the image is smaller than the screen resolution. To be safe, publishing the picture at 65% of the size of the screen resolution will ensure that the picture does not need to be expanded when it is viewed through the Dashboard Viewer website. For instance, a picture published at 1024 x 768 should be no larger than 666 x 499 in size.

Publishing Documents
Documents are published in PDF format, and so a consideration of the size of the document is necessary when determining if a report is suitable to be viewed through the Dashboard website. Large sized documents will take longer to open.

The Dashboard Editor
Overview

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
The Dashboard Editor manages data that has already been published to a server to be displayed by the Dashboard Viewer. To review, the Dashboard Viewer is a website that provides the ability to view data published from Omega Desktop through Internet Explorer provided that they have the appropriate permissions. The Dashboard Editor tool can be accessed from the FireView or CrimeView dropdown menus.

Once opened, the Dashboard Editor loads all of the data that has been published to the server from the current ArcMap project into a tree that is located on the left side of the dialog. Depending on the network connection, loading the dialog may take a few moments as the data is being retrieved from a server. It is important to remember that the only information displayed within the dialog is that data that was generated with the current ArcMap project.

Dashboard Editor Dialog
On the right side of the dialog is a panel that contains detailed information about the node that is selected in the tree. When the dialog first opens, this information will describe the project that is currently open in ArcMap. The descriptive information provided is outlined below:

Project Name
The name that was entered using the Omega Desktop Administrator when the project was registered to the Dashboard.

Description
The description that was entered using the Omega Desktop Administrator when the project was registered to the Dashboard.

Dashboard Host Server Name
The name of the server that is currently hosting the Dashboard SQL Server database.

Dashboard Database Initial Catalog
The Dashboard Database Initial Catalog is the name that was used when the database was attached to SQL Server.

Date Registered
The date that the project was registered to the Dashboard using the Omega Desktop Adminstrator.

Dashboard Viewers
Clicking on the '+' icon to the left of the Project node will expand a list of Viewer nodes within the second tier of the Dashboard Editor tree.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Viewers are categories that are created with the Dashboard Administrator in order to group data together into logical units. The personnel responsible for administering the Dashboard must create these Viewers before the Dashboard Editor can be used. Only those Viewers that contain data that was published with the current ArcMap project will be visible within the Dashboard Editor.

Viewer Icons
Different types of Viewers are available in order to show different groupings of data. These types can be distinguished within the tree by their icon that is associated with the Viewer text. In addition to the icon displayed in the tree, hovering over these icons will display the Viewer type as well. The Viewer types are identified below:

Single Image
Viewer supports posting only one image.

Multiple Image
Viewer supports posting multiple images.

Image and Report
Viewer supports posting one map and an associated report.

Multiple Reports
Viewer supports posting multiple reports.

Image Bank
Viewer used with the Dashboard Publisher to house images, but can also receive content from the Dashboard Wizard.

Document Bank
Viewer used with the Dashboard Publisher to house documents, but can also receive content from the Dashboard Wizard.

Dashboard Content
Dashboard content refers to data that is posted to the server from the Dashboard Publisher or Dashboard Wizard tools that are used within the Omega Desktop products. The Dashboard Editor will only display content that is published to the server with the Dashboard Wizard.

This limitation is due to the fact that the Content Editor can only be used to modify content that is generated within the currently opened and registered ArcMap proeject.

There are several types of content, and these types can be distinguished using the icons that are placed next to the content text within the tree. The types can also be identified by hovering the mouse over the content icons. The types of content available to the Dashboard Editor are outlined below:

Map
A map can be generated using the Dashboard Wizard which is launched from the Summary dialogs of the Query, Density or Response Time Map routines.

Map with Report
A map with report type is generated using the Dashboard Wizard. When viewing this content within a browser, the map and report are always linked.

Graph
Graphs are also generated with the Dashboard Wizard. The graphs that are available depend on the graph templates that are stored in the OmegaGroup installation \graphs folder.

Report
A report is generated with the Dashboard Wizard. The reports that are available will be those reports that are registered with the incident layer that is selected by the Query, Density or Response Time Map routines.

Editing Options for the Dashboard Editor
There are five options that are available to the Dashboard Content. These options can be viewed by right-mouse clicking on a content item within the tree. The options are outlined below:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Edit Properties
This option opens a new dialog which will load the current name and description for the content item selected. After entering a new name and description, the text on the Dashboard Editor will be updated to reflect the changes. These changes do not take effect until the content is posted to the server.

Edit Query
Edit Query opens up the original analysis dialog so that the query that was used to select the incidents can be changed. Clicking the 'Save' button on the analysis dialogs will save the new query to the project XML file within the project workspace. The content is not updated with the new query, until it is posted to the server.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Post
Posting the content to the server saves the property and query edits, and updates the changes on the server. The data is posted both to the SQL Server database as well as updating the images or documents that are stored on the server. Posting content changes will run the analysis in order to recreate the results as a map, graph or report, whatever was specified originally when the content was first created.

Remove
Remove will delete the content from the server by removing the record in the SQL Server database that is associated with the content, as well as removing any stored images or PDF files on the server.

Run
This option runs the selected content to regenerate the report, map or graph that is selected. This option can be used if edits are made to the property or query in order to view the results without posting the changes to the server.

The Dashboard Publisher
Introduction
The Dashboard Publisher tool allows the analyst to select a file that is saved in PDF or JPG format and post that file to the Active Dashboard on the server. The Active Dashboard is defined as the dashboard that is currently receiving content from the desktop machine. This setting is configured using the Omega Desktop Administrator. The Dashboard Publisher is available to all desktop machines that have been licensed with a Single License of Dashboard.

Content that is posted to the server using the Dashboard Publisher is published one time and cannot be automated. Once the content is posted, it cannot be deleted from the desktop machine, but must be accessed by the Dashboard Administrator through the Dashboard Administration website.

When content is published, metadata including the alias name, description and date published are posted to the dashboard database, while the file (PDF or JPG) is saved to disk on the server. When the data is published, it is automatically routed to the 'Report Bank' and 'Image Bank' Viewers. Viewers are organizational tools that allow the Dashboard Administrator to organize content as it is posted. In this case the 'Report Bank' and 'Image Bank' Viewers are designed to receive either PDF reports or images that are published through the Dashboard Publisher tool.

When using the Dashboard Publisher, note the location to which the content is posted within the descriptive panel on the dialog. The Dashboard name is provided within the square brackets. In addition, before the content is published, a message is provided that indicates where the content will be posted. Once posted, the Administrator of the Dashboard may choose to make the Viewers that hold the content visible to other users or may maintain them as invisible until the content is ported to other visible Viewers.

To use the Dashboard Publisher, select the tool from the Omega Desktop dropdown list in order to open the dialog. Enter an alias name and description for the file, and select the file using the browse button. Ensure that the file type desired is selected at the bottom of the dialog (PDF or JPG). Use the Publish button to post the file to the Dashboard on the server.

Dashboard Automation
Description
Dashboard Automation is available to the content that is published using the Omega Dashboard Wizard. When the Wizard is used, an option is available that specifies whether the content should be tagged as 'Static' or 'Automated'.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
When content such as a map, graph or report is posted to the server as 'automated content', the query used to produce the results is written to the Dashboard database as metadata. The metadata ensures that each time the content is updated, the same query is used.

Once content is posted to the server, the Dashboard Administrator web site, can read this metadata to determine which content can be automated. All content tagged with the 'automated' option in the Dashboard Wizard can be assigned to a Job. The Job is then used to automate the content on the desktop machine using Windows Task Scheduler.

Creating a Job
To create a new Job to run the map, graph or report on a regular basis, the Dashboard Administrator web site must be opened to the Job tab. A new Job can be created which allows the administrator to select from a number of ArcMap projects that are currently publishing data to the Dashboard. When a project is selected, a list of automated content that has been published to the Dashboard is then available for selection. When the Job is saved, a new Job Number is created automatically. It is this Job number, that must be used on the desktop machine to set up a Windows Scheduled Task. For more information on administering Jobs, see the Dashboard Administrator help guide.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Scheduling a Job
Scheduling a Job to run is performed on the machine that initially posted the content. The Job is run from Windows Task Scheduler, and all content that was referenced to the Job number by the Dashboard Administrator will be run if the task is set up for the Job. Scheduling an automated Job is a function of the Dashboard Administrator. For more information, see the Dashboard Administrator help guide.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hh32A.htm Attachment A
Dashboard Administrator
Introduction
The Dashboard Administrator is a web site that is used to organize the content published to the server from any desktop machines running Omega Dashboard.

When content is published to the server, metadata is stored in a database, while the images or portable documents (PDFs) created are stored in a predetermined folder on disk. The Dashboard Administrator, reads the information from the database, and manages the organization of this content both within the database and on disk.

The Dashboard Administrator web site consists of eight tabs. The tabs divide the administration of the Dashboard content into sections for manageability. These tabs are described in the following sections of this help guide.

Overview Tab
The Overview tab provides information about which version of Dashboard is running. It is important to take note of the version as it is associated with the ArcGIS version publishing content to the server. If running ArcMap 9.2 on the desktop machines publishing Dashboard content, the Dashboard Version should be identified as 4.2.1. Alternatively, if running ArcMap 9.3, the version of the Dashboard on this tab should be 4.3.0.

The name and description of the Dashboard may be modified by the Administrator from this tab. When either of these items are updated, the date edited will be updated with the date and time that the name and description were modified.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Projects Tab
The Projects Tab of the Dashboard Administrator displays the ArcMap projects that are registered to the Dashboard. ArcMap projects are registered using the Omega Desktop Administrator. As the projects are registered, the information regarding where the project is located on the desktop machine, and which machine is housing the project is recorded in the Omega Dashboard database. The Dashboard Administrator web site retrieves this information to display it on the Projects Tab.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Projects Tab Layout
The list located on the left side of the Projects Tab displays the ArcMap projects that are registered to the Dashboard. Projects are registered using the Omega Desktop Administrator. Each of these projects has the capability of publishing content to the Dashboard. Once registered, these projects should not be moved on the machine or relocated to another machine without unregistering and reregistering the project from the Omega Desktop Administrator.

When a project is selected in the Registered Projects list, detailed information about the project is updated on the Project Tab. The information provided includes the project alias, the description, the date the project was registered, the last time project information was modified, and the machine name and path to the ArcMap project on the machine that is publishing the content. The Project Content list is also updated, and provides a quick overview of the content that has been posted to the server from the selected project.

Unregister Button
Before an ArcMap project can be unregistered, all content published from the project must first be detached. Detaching content from the project can be accomplished by deleting the content using the Dashboard Administrator Content tab. When all content has been removed, the best practise is to unregister the project using the Omega Desktop Administrator. However the 'unregister' button on the Project Tab has been provided in the event that the administrator cannot access the machine that was originally publishing content.

Viewers Tab
Viewers are the containers that are created to store and organize content. When a Viewer is selected from the Viewers list on the left side of the window, detailed information associated with the selected Viewer is updated. This information is described in the following sections.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Viewer Information
The Viewer tab displays detailed information about each Viewer that has been created. In addition, it is possible to create, edit or remove Viewers from the application. Depending on the Dashboard application, the list of Viewers created may grow very long. The 'Up', 'Down' and 'Save' buttons below the Viewer list are available to provide a way to order the Viewers for manageability.

When a Viewer is selected from the Viewer list on the left side of the page, the information associated with that Viewer is updated. The name, description, date created and edited, roles, Viewer type and the content contained within the Viewer are then available. Once a Viewer has been selected, information pertaining to that Viewer may be updated using the Edit button; such as the name, description, and roles that are able to access that Viewer from the Dashboard Viewer web site. The Viewer Type may not be changed once the Viewer is created as the type of content that has already been published to the Viewer is very specific to the type.

The 'Add' or 'Remove' buttons are also available to create or delete Viewers. To create a new Viewer, a type must be selected, and at least one Role should be assigned. The Role determines who will be able to view the content from the Dashboard Viewer web site, while the Viewer type determines the type of information that can be published to the Viewer. To delete a Viewer, all content that was published to that Viewer must either be removed or copied to another Viewer. Content can be copied to another Viewer as long as it shares the same 'type'.

Viewer Types
There are nine Viewer types that enable content to be posted and displayed in a number of different ways on the Dashboard. The source of this content may include results generated by the Omega Desktop software, any file that is stored in JPG or PDF format, or messages that are posted using the Dashboard Administrator. The Viewer types used to display this information are described below.

Image Bank
The Image Bank Viewer is provided with the Dashboard application and cannot be deleted. It is provided by default in order to store information that is posted in JPEG format to the server. When a user publishes content from the Dashboard Publisher tool on a client machine, the data is automatically posted to this Viewer.

Document Bank
The Document Bank Viewer is also provided with the Dashboard application and cannot be removed. This Viewer type is capable of storing information that is

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
provided in PDF format. When publishing information from the Dashboard Publisher tool on a client machine, the data is automatically posted to this Viewer.

RSS Notes
The RSS Notes/Messenger Viewer stores messages that have been published by an author of the Dashboard. These messages appear in a chronological order, whereby the most recent message appears at the top of the Viewer. The ‘Update Now’ button can be used to retrieve any messages that may have been posted after the Dashboard was opened in the browser.

The Single Image Viewer
The Single Image Viewer displays a single image that has been published to the Dashboard. Any image may be published to the dashboard as long as it is in JPG format. Typically, these images may be maps or graphs published by the Omega Desktop software or other image files stored on disk that require distribution.

The Multiple Image Viewer
The Multiple Image Viewer is similar to the Single Image Viewer in that it will display any image provided that is in JPG format. The difference in this Viewer is that multiple images may be accessed by scrolling through the list using the 'previous' and 'next' buttons.

The Report Viewer
The Report Viewer lists published Portable Documents (PDFs) within a table in the Viewer. A title and description for each document is listed in the table, along with a Last Edited date. By clicking on the report link icon, these documents can be opened in a new Internet Explorer window or tab depending on your Internet Explorer settings.

The Temporary Links Viewer
The Temporary Links Viewer provides the ability for anyone logged into the Dashboard Viewer web site to add their own personalized web links. If the Viewer is removed from the Dashboard Viewer page however, the links will be removed as well.

The Permanent Links Viewer
The Permanent Links Viewer is similar to the Temporary Links Viewer in that it allows anyone logged into the Dashboard Viewer web site to add their own web links which can be accessed at any time. The difference in this Viewer is that if the Viewer panel is removed from the page, when it is added again, the previously created web links will remain.

The Multiple Image and Report Viewer
The Multiple Image and Report Viewer displays the results of a desktop analysis in the form of a map or graph with a linked report. The ‘Enlarge Image’ text can be clicked in order to display the map or graph in a new tab or window. The ‘Review Report’ text will open the PDF report in a new tab or window.

Content Tab
Content forms the building blocks of the Dashboard. Content may be published as images (JPG) or portable documents (PDF) from the Dashboard client machines. As it is posted to the server, each piece of content must be assigned to a Viewer as these form the containers that organize the published content.

When the Content Tab is opened, a list of available content can be viewed on the left side of the page. By default all of the content published is displayed, however, this information can be sorted by Machine, Project or Viewer. Selecting one of the categories will enable the administrator to narrow down the content within the list to a particular subset.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Editing Content
When an item of content is selected, the descriptive information regarding the content is updated as well. As content is published from the Dashboard client machines, the name, description, and template may be updated. Templates are available with reports, maps and graphs and refer to the associated file that is used to generate the content. It is important when changing the template that the source data be considered. The source data on which the new template is based, must be identical to the source data used to generate the original content otherwise when the content is updated it will fail.

Automated Content
When content is posted from the Dashboard Wizard on the client machines there is the option to post the content as 'static' or 'automated'. Content posted from the Dashboard Publisher does not have this option; it is always static. If content is posted as 'automated', it can be selected on the Jobs Tab to form a job that can then be run from Windows Task Scheduler on the client machine. It is possible to change content from 'static' to 'automated' if it was posted from one of the routines that uses the Dashboard Wizard. In addition, the date query may be updated based on a previous date query.

Roles Tab
Roles are used to organize Users into groups so that the content they can view from the Dashboard Viewer web site is isolated to the Roles to which they belong. For example if a new User account is created, and they are assigned to the 'Narcotics Division' role, that means that the User will be able to see all of the Viewers that are also assigned to the 'Narcotics Division' Role. This allows the Administrator of the Dashboard to provide content to users that is appropriate to their specific discipline.

The Roles tab provides a means to add, edit or remove roles from the Dashboard application. If a role is to be removed however, all users assigned to that role must be removed prior to removing the role. Once a role is created, the name of the role cannot be changed. The role must be removed completely, and then added with the new name required.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Users Tab
Users are defined as those individuals that will be accessing the Dashboard information posted to the server through a web browser. A user account must be created for each individual as the data that is posted to the Dashboard is personalized. The personalization of the data means that if two individuals log into the Dashboard using the same user account, when one individual makes a change to their Dashboard, the second individual will see these changes take effect.

The Users Tab lists all of the Users currently able to access the Dashboard application from a web browser. There are two users that are created with the application, and these cannot be deleted. The 'admin' account is created for the administrator of the Dashboard so they can log into the Administrator web site and organize the content. The 'Author1' account is created for anyone who might be posting messages to the Dashboard. The individual who holds this account may log into the 'authoring' page of the Dashboard Administrator web site, but does not have access to all of the other administrative web pages.

Users may be added, edited or removed from accessing the Dashboard Viewer application. When a new User is added, they should be assigned to at least one Role, which will allow them to View data that is posted to the Dashboard. Each new user must have a unique email address, and a password and security question. If the individual forgets their password, it is the security question that will be used to validate their identity.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Jobs Tab
The Jobs tab is where automated content can be grouped in order to run it as a Scheduled Task in Windows Task Scheduler from the Dashboard client machine from which it was published. Only content that is posted from the same ArcMap project can be grouped into a single Job. When the Job is run, ArcMap is opened, and each of the content items that is selected for the Job is run in the order supplied.

When automating content that will be generated as maps, it is important to consider which content to group as a single job. When a Job is run, ArcMap is opened and each piece of content is run and added to the ArcMap project as a new layer. To avoid having layers piling up on top of one another, it is recommended to run each routine type together as one job. For instance, running several hotspot content maps together will only show one hotspot at a time, as previous layers are removed each time a new layer is created; this is a function of the Omega Desktop software.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Setting Up a Job
Creating a new job involves adding a new Job Name, Job Description, and then selecting from a particular project all of the content that should be run from that Job. When the 'Save' button is clicked, a new automated Job Number will be created. It is this Job number that must be used when creating the Automated Task in Windows Task Scheduler.

To set up the Job, the administrator must go to the client machine from which the ArcMap project is running, and create a new Windows Task in the Scheduler.

The task should point to the DashboardAuto.exe file in the \program files\omegagroup\desktop\bin folder, and the Job number should be referenced.

SMTP Server Tab
The SMTP Server tab is available in order to set up the SMTP server settings that will be used if an individual loses their user information. On the Dashboard Viewer and Administrator sites, the Forgot Password? hyperlink allows an individual to enter their email address in order to retrieve their login information. It is the SMTP server that will be used to email the individual their credentials. After updating this information, the Save button must be used in order to store the updates.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
The Dashboard Viewer
Introduction
The Dashboard Viewer is a web site that is used to bring together maps, graphs, reports or other files so that the information can be distributed easily over the intranet. The data that is published may be created using Omega Desktop products such as CrimeView or FireView, however, other files may also be accessed as long as they have been published in JPG or PDF format.

To view data that has been published to the Dashboard, a user must have been granted permissions by the administrator of the application. Depending on these permissions, the user will be able to see different ‘views’ of the data. For example, an officer working within the fraud unit of a police department may only see maps and reports related to incidents of fraud, while a firefighter working in District 1 may have a view of all relevant incidents related to that particular district.

The Dashboard Viewer is available from a URL that is set up by the Dashboard Administrator personnel. Contact your administrator to be provided with this URL.

Once the URL is identified, it is recommended that Internet Explorer 7 be used to view the web site. It is possible however to use IE6, however some of the features that are used with the Dashboard are not available in this version.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
Elements of the Dashboard
The layout of the Dashboard is divided into three parts. A panel on the left side of the Dashboard provides an area that is customized to the client’s Dashboard application. An options strip allows the user to add or remove content, or hide or show the left panel. The remainder of the browser window is available for placing Viewer containers onto the screen. These elements of the Dashboard will be discussed in detail within the following sections.

The Content Library
The Content Library is located on the left side of the Dashboard window. This library lists all of the Viewer containers that may be shown to the user. Viewers are assigned to roles, and so if the user is a member of the same role assigned to that Viewer, the Viewer container will appear in the Content Library list.

A user may have a different list of Viewers available than other personnel within the department depending on the permissions that have been granted. Viewers are collections of data, and come in several varieties. These will be discussed in detail later on in this document.

There are several varieties of Viewers that have been created in order to provide different ways of viewing the information posted to the Dashboard. The Viewer types can be discerned by the different icons located to the left of the Viewer name. Hovering over these icons with the mouse will open a tooltip that displays the Viewer type.

A Viewer may or may not have data residing within it at the time the Dashboard is opened. If a Viewer has data within it, a checkbox will appear next to the Viewer name. If data has not yet been published to the Viewer, a checkbox will not be available.

A user can always expand a Viewer within the Content Library by clicking on the plus sign to the left of the Viewer name. Expanding the Viewer will reveal a description about the content contained within it. If the administrator of the Dashboard has not included a description, the text ‘No Description’ will be supplied.

If a checkbox is located next to the Viewer name this indicates that data is available within the Viewer. After expanding the plus sign to reveal the description, the description itself can be expanded to reveal the content within the Viewer. Content may include reports, maps, graphs or pictures that are published to the Dashboard.

Dashboard Options
Above the Content Library is a section that is available to customize the Dashboard. The first item in this section is a link to the client’s website. This link may or may not be displayed depending on whether the Administrator configured the link to be available. The next two features are available in order to create a Default View that is available to each Dashboard user. When a user clicks the ‘Set Default View’ text, all Viewer panels that are currently available on the Dashboard screen are saved. If the user wishes to return to this particular view of the information, it has been saved. To return to the Default View, the ‘Return to Default View’ option can be clicked. Finally, the 'Refresh Dashboard’ option is available so that the user can update the Dashboard with any information that has been published to the server after the Dashboard was opened.

Showing and Hiding Content
Adding and removing all Viewers from the Dashboard can be accomplished using the options available at the top of the Dashboard window. ‘Add All Content’ adds all of the Viewers listed in the Content Library, while ‘Remove All Content’ clears the Dashboard of all Viewers. The Hide/Show Content Library can be clicked in order to temporarily hide the Content Library panel to provide more screen real estate.

The Dashboard Window
The Dashboard Window is the screen real estate to the right of the Content Library panel. Viewers can be added to the screen horizontally or vertically, and this option is configured by the Dashboard Administrator. This region appears as a single area for placing Viewers, however, it is actually divided into three columns.

Viewers that are placed within this region can be moved between columns or ordered within each column.

The Viewer
The Viewer is the building block of the Dashboard. Viewers are designed to present information in a variety of formats depending on the type of data on which

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
they are based. Although there are different types of Viewers available, there are certain elements that are common to all Viewers; these elements are outlined below:

The Viewer Title Bar
The Viewer title bar is common to all Viewers and is located at the top of each Viewer window. The title bar has several elements all of which are explained below.

Viewer Name: The Viewer name is displayed as the first line in the title bar. The name is created by the administrator of the Dashboard application.

Viewer Description: The Viewer description is visible by hovering the mouse over the title bar. The description is set by the administrator of the Dashboard when the Viewer is created.

Drag and Drop: All Viewers are capable of being moved within the three columns of the Dashboard Window. Moving the Viewer is accomplished by clicking on the title bar, holding down the left mouse button, and then dragging the Viewer to the new location.

Minimize: The Viewer window can be collapsed by clicking on the ‘minus sign’ icon in the title bar of the Viewer.

Maximize: The Viewer window can be expanded by clicking on the ‘plus sign’ icon in the title bar of the Viewer. The ‘plus sign’ icon is only visible when the Viewer is collapsed.

Remove: The Viewer can be removed from the Dashboard window by clicking on the ‘x’ icon in the title bar of the Viewer. When a Viewer is removed, it is only temporary. The Viewer can be added again by clicking on the Viewer checkbox in the Content Library and clicking ‘Add’.

Last Edited: All Viewers show a ‘Published’ date that indicates the last time the data was updated. In most cases the Last Edited date appears below the Viewer name in the title bar. This date reflects the last time the data showing within the Viewer window was updated.

In cases where there are multiple links to data within the Viewer window, the Last Edited date is displayed for each data item.

Viewer Types
There are seven Viewer types that enable content to be posted and displayed in a number of different ways on the Dashboard. The source of this content may include results generated by the Omega Desktop software, any file that is stored in JPG or PDF format, or messages that are posted using the Dashboard Administrator. The Viewer types used to display this information are described below.

The Messenger
The Messenger Viewer lists messages that have been published by an author of the Dashboard. These messages appear in a chronological order, whereby the most recent message appears at the top of the Viewer. The ‘Update Now’ text can be used to retrieve any messages that may have been posted after the Dashboard was opened in the browser.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
The Single Image Viewer
The Single Image Viewer displays a single image that has been published to the Dashboard. Any image may be published to the dashboard as long as it is in JPG format. Typically, these images may be maps or graphs published by the Omega Desktop software or other image files stored on disk that require distribution.

The Image Bank or Multiple Image Viewer
The Image Bank and Multiple Image Viewer are similar to the Single Image Viewer in that it will display any image provided that is in JPG format. The difference in these Viewers is that multiple images may be accessed by scrolling through the list using the previous and next buttons.

The Image Bank Viewer is a default Viewer that is provided for all content that is posted to the server using the Omega Desktop Dashboard Publishing Tool.

Content that is posted to this Viewer may be moved to a Single Image Viewer or another Multiple Image Viewer.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
The Document Bank and Report Viewer
The Document Bank and Report Viewer list published Portable Documents (PDFs) within a table inside the Viewer panel. The Document Bank is a Viewer that is provided by default to hold all PDF content posted using the ‘Publisher Tool’ within Omega Desktop. Only one Document Bank Viewer can exist, however the Report Viewer type can be created to hold other PDF material. In addition, PDF’s that are posted to the Document Bank Viewer can be moved or copied to other Report Viewers.

For these Viewer types, a title and description for each document is listed in the table, along with a Last Edited date. By clicking on the ‘open report’ icon, these documents can be opened in a new Internet Explorer window or tab depending on the Internet Explorer settings.

The Temporary and Permanent Links Viewers
The Temporary and Permanent Links Viewers are used to add links to other websites by identifying the web URL. The difference between these Viewers is that if a Temporary Links Viewer is removed from the Dashboard Screen, when it is reopened, the links are lost. The Permanent Links Viewer will retain these links if the Viewer is removed and then added back into the Dashboard.

These links are visible only to the person logged in using their specific account. When navigating with these links, the new website is opened in a new Internet Explorer window or tab depending on the IE settings.

The Multiple Images with Reports Viewer
The Multiple Images with Reports Viewer displays the results of a desktop analysis in the form of a map or graph with a linked report. The ‘Enlarge Image’ text can be clicked in order to display the map or graph in a new tab or window. The ‘Review Report’ text opens the PDF report in a new tab or window.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc4864/~hhC5DD.htm Attachment A
CrimeView Main Menu
The CrimeView main menu is the starting point for running crime analysis routines. To access the main menu select the Sherlock button on the CrimeView toolbar.

This button opens the Queries dialog that provides
four routines for selecting incidents. The routines
include; Attribute Query, Within A Boundary, Near
An Address and Near A Feature.

This buttons opens the Density Map dialog that
contains three routines; Density Map, Hot Spot
Map and Repeat Calls.

This buttons opens a dialog that allows one to
select one of the following routines: Exception
Reporting, Spatial Trend and Crime Rate
Generator.

This button opens the Cyclical Reports dialog that
allows one to edit and run saved query and density
map routines.

The button opens the Threshold Alert dialog.

3/4/2022mk:@MSITStore:C:\Program%20Files%20(x86)\OmegaGroup\Desktop\Help\CrimeView.c...

Attachment A
Building An Application
Building a CrimeView application is a complex process that is unique for each client. Building the CrimeView application is typically a service provided by The Omega Group. This section highlights the major tasks when building the application.

Retrieve Incident Data
Build Saved Queries
Build Crystal Reports
Set Default Fields
Create ArcMap Document
Create Map Templates
Retrieve Incident Data
One of the first tasks in building a CrimeView project is retrieving the incident data. The incident data is used for analysis and provides the source data to create maps and reports.

The Omega Import Wizard provides a means to import datasets from Database Management Systems (DBMS) or ASCII text files.

Once retrieved, the datasets are geocoded so that they may be used with OmegaGIS.

An Import Profile (*.oiw) is a file used by the Omega Import Wizard to outline the steps needed to retrieve and process the datasets.

The Import Profile provides a processing template that records how to extract the dataset from the DBMS, which OmegaGIS fields to create, the geocoding steps involved and the final destination for the resulting feature class. Refer to the Omega Import Wizard documentation for further information.

Build Saved Queries
Attribute queries using SQL syntax to select features from incident datasets can often become lengthy and complex. Saved Queries hide the SQL syntax from the user while providing a more intuitive name or description for each query. Saved queries are created and edited with the Saved Queries Editor in ArcCatalog and are stored in the Omega_Query.MDB database.

Build Crystal Reports
CrimeView employs Crystal Reports for reporting functionality. Using the OmegaGIS Metadata Editor, reports are registered to layers.

Set Default Fields

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Using the OmegaGIS Metadata Editor, set the default fields for the layers used by the CrimeView application. The default fields include:
¡ OmegaGIS Fields (date, day of week, time, response time). ¡ Incident Type for graphs.
¡ Default field for list boxes in dialogs.

Create ArcMap Document
An ArcMap document containing incident datasets and other geography such as street centerlines provides the backdrop for performing geographic crime analysis. Every ArcMap document that uses OmegaGIS has an associated project workspace where the results of the routines and preferences are stored.

When creating the ArcMap document, the points outlined below should be followed:
l All layers must have a unique name.

Layer names in the table of contents are used by OmegaGIS routines for identification. If layers share the same name, the first layer in the stack is always used by OmegaGIS. If the name of the layer changes, Cyclical Reports or Threshold Alerts created with that layer, will no longer be able to recognize the source data, and an error will result. Consequently, it is important that all the layers are assigned a unique name in the table of contents, and retain their original names. l Data Frames must have a unique name.

The name of the data frame is used with OmegaGIS routines. Consequently, the data frame names must be unique and should not change.
l Use a projected coordinate system
All layers and data frames should have a projected coordinate system (as opposed to a geographic coordinate system). This is not a requirement but it is recommended as a projected coordinate system will result in more accurate results. l Performance checklist
The documentation contains a performance checklist that has recommendations for setting up an ArcMap document which should be followed.

Create Map Templates
Map templates are used to define how the map elements in the layout will appear. Map elements include a title, agency logo, legend, north arrow and scale bar. Map templates can be used with both Cyclical Reports and Threshold Alerts.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Query Layer
A Query Layer is point layer in the active data frame that can be used in OmegaGIS routines. An attribute and/or spatial query is used to select the features in the query layer.

The Query Layer is set on the What? tab. When the Query Layer is selected, the Saved Queries tree (or columns) is updated with the saved query group(s) that are registered to the layer. The list of additional query layers is also updated.

Query Layer Criteria
When the OmegaGIS routine dialog opens, the list of query layers is populated. For a layer to be included in the list, the layer must meet the following criteria:
l The layer must be in the active data frame.
l The layer must be valid; the data source of the layer is not missing. When the data source is missing the layer will have a red exclamation mark in the table of contents.
l The layer must have the geometry type of point. Layers with the geometry type of multi-point, such as layers created by the Repeat Calls/Student Concentrations routine, are not supported as query layers. l The layer must have the data source of shapefile, Personal Geodatabase, File Geodatabase or ArcSDE. l The layer must not be a selection layer. A selection layer is created from a subset of feature selected from another layer in the active data frame. A selection layer may also be created by Query routines when the query results option is "Show only selection (as new layer"; this option is set in the OmegaGIS Setup dialog.

To determine if a layer is a selection layer, use the Layer Properties dialog; in the table of contents right-click the layer and select

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Properties; then make the Definition Query tab active. There will be a label at the bottom of the dialog if the layer is a selection layer, similar to the following image:
l The layer has the appropriate registered layer type. Layers may be registered in OmegaGIS as 'Incident', 'Person', 'Student' or 'Other' with the OmegaGIS Metadata Editor. There is an option in the OmegaGIS Setup dialog that will only populate the list of query layers with layers that have a certain registered type. With this option selected, the list of layers is limited to only those layers of interest for querying.
l The layer has not been created from an OmegaGIS routine. An example of layer created from an OmegaGIS routine would be a Composite Layer. There is an option in the OmegaGIS Setup dialog that controls whether to exclude layers created from OmegaGIS routines in the list of query and boundary layers.

Tip
l If a layer is added to the active data frame while the routine dialog is opened, the list of query layers will not be updated. To update the list of query layers, close the dialog and then open again.

Additional Query Layers
All Query and Density Map routines have the option to query multiple additional layers at a time. This functionality has been built into OmegaGIS to allow users to break apart point data into different layers (feature classes) to improve performance and still have the ability to query all of the features.

Omega recommends shapefiles contain 100,000 or fewer records while personal geodatabase be limited to 250,000 records.

Typically, feature classes are divided by a date range or geographic area to accommodate these restrictions.

This section is divided into the following categories:

Layer Criteria
Use of Additional Query Layers
AddQueryLayers.MDB
Composite Layer
Considerations when using additional query layers
Layer Criteria
In order for a layer to appear in the list of additional query layers, the layer must meet the following criteria:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The layer must be in the active data frame.
l The layer must be valid; the data source of the layer is not missing. When the data source is missing the layer will have a red exclamation mark in the table of contents.
l The layer must have the geometry type of point.
l The layer must not have the same feature class as the Query Layer. In other words, the layer must have the same data source as the Query Layer.
l The layer must not be a selection layer. A selection layer is created from a subset of features selected from another layer in the active data frame. A selection layer may also be created by Query routines when the query results option is "Show only selection (as new layer)"; this option is set in the OmegaGIS Setup dialog.

To determine if a layer is a selection layer, use the Layer Properties dialog; in the table of contents right-click the layer and select Properties; then make the Definition Query tab active. There will be a label at the bottom of the dialog if the layer is a selection layer, similar to the following image:
l The layer must have the same saved query group(s) of the Query Layer. A saved query group contains attribute queries that are used to select incidents. The saved query groups are registered to a layer using the OmegaGIS Metadata Editor. l The layer must have the same spatial reference as the Query Layer; it is not required that the layer share the same X-Y domain as the Query Layer because the X-Y domain is created dynamically. Consequently, layers that are based on a different geographic regions (i.e. City or Police Beat) can be used. l The layer cannot have been created from an OmegaGIS routine. The "Exclude layers created from OmegaGIS routines..." option in the OmegaGIS Setup dialog controls this check. l The layer must have at least the same fields as the Query Layer and the fields have the same type.

Use the utility in OmegaGIS Setup to determine why layers are not included in the list of additional query layers.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Use of Additional Query Layers
To enable the use of additional query layers, on the What? tab first select the Query Layer and then check the "Use additional layers in query" checkbox.

When the checkbox is selected, all of the layers in the active data frame that meet the criteria listed above are added to the list.

Check the layers to be included in the routine. When the Query Layer is changed, the list of additional query layers will be cleared and then updated with a list of layers that meet the criteria using the new Query Layer; the selection of the layers to use will be lost.

When there are no additional query layers, a message appears in the list.

At the completion of the Query and Density routines, the Query Layer and those layers selected as additional query layers will have the following done:
l The layers will not be visible.
l The selected features in the layers will be cleared.
l The OmegaGIS definition expression on the layers will be removed.

AddQueryLayers.MDB
When additional query layers are used, the features selected by the attribute query and/or spatial query, are exported into the same feature class in a personal Geodatabase.
l The Geodatabase is named AddQueryLayers.MDB and is located in the "\Analyses" folder in the project workspace.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The AddQueryLayers.MDB is created dynamically by the OmegaGIS Query and Density Map routines. If the Geodatabase is not present it will be created when the routine is run. l An option exists in the OmegaGIS Setup dialog that creates a field in the new feature class called "OmegaGIS_Source".

When this option is selected, this field is populated with the name of the source layer for each record. l When the feature class in the AddQueryLayers.MDB is no longer in the data frame, it is deleted by the OmegaGIS Project Exit.

Tip:
l To permanently persist the feature class created from a Query routine, use ArcCatalog to copy the feature class to another Geodatabase.

Composite Layer
When additional query layers are used with Query routines, the incidents selected by the attribute query and/spatial query are exported to a new feature class. This feature class is then added to the active data frame as layer. This layer is referred to as a "Composite Layer" in OmegaGIS since it has been generated from multiple layers. l The name of the new layer is copied from the Query Layer with "(Composite)" added to the end of the name. l The legend of the Query Layer is copied to the new layer, provided that the legend uses one of the following renderers:
¡ A Unique Value renderer. The renderer can only use one value field. ¡ A the Single Symbol renderer.

If the Query Layer legend does not meet the conditions outlined above, a default Single Symbol renderer is used. l By default, a Query Layer can have only one "Composite Layer"; this can be changed in the OmegaGIS Setup dialog.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Considerations when using additional query layers
The following considerations should be taken into account when using additional query layers:
l When running a Query or Density Map routine, always use an attribute query and a spatial query when appropriate. The use of the query will limit the features selected which will assist in the performance of the routine. l When layers are broken apart by date, ensure that incidents are not duplicated among the layers.

For example, an incident occurring in January 2002, is imported from the client database, geocoded and inserted into the &rdquor;Incidents 2002” layer by the Omega Import Wizard. One year later in January 2003, the incident is updated in the client database and inserted into the &rdquor;Incidents 2003” layer. When the &rdquor;Incidents 2003” layer is used in conjunction with the &rdquor;Incidents 2002” layer during a query, duplicate information from the layers leads to an incorrect incident count.

To prevent an incorrect count of the incidents, layers should be free of duplicate values. Eliminating the potential for duplicate incidents in the resulting data can be achieved by correctly setting the Output Steps in the Omega Import Wizard (refer to the Omega Import Wizard Documentation).

Saved Queries
Attribute queries using SQL syntax to select features from a dataset can often become lengthy and complex. Saved Queries hide the SQL syntax from the user while providing a more intuitive name or description to each query. Saved queries are created and edited with the Omega Query Editor in ArcCatalog and are stored in the Omega_Query.ODB database.

This section is divided into the following topics:

Saved Query Group
Select Saved Queries
Support for Different Query Layer Formats
Editing the Query
Finding a Saved Query
Query Grouping
Unique Value Query
Query Viewer Information
Saved Query Group

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
A saved query group is comprised of a collection of saved queries. One or more query groups may be registered to layers used in ArcMap. Registering the query groups ensures that the saved queries are available to the assigned layers during OmegaGIS routines. Registration is possible through the use of the OmegaGIS MetaData Editor in ArcCatalog.

To determine the saved query groups that are registered to a layer, use the Omega tab in ArcMap. When the layer is selected in the table of contents, the metadata for that layer is displayed at the bottom of the Omega tab. The Query Groups item lists all of the registered saved query groups available to the selected layer.

Selecting Saved Queries
Saved queries are available on the What? Tab of Omega Desktop Query, Density and Analysis dialogs within the Saved Queries Tree or Saved Queries Columns structure. The tree or column structure is available based on a Setup setting.

Tree View
If the 'Tree' structure is selected in Setup, then a hierarchical structure of folders and checkboxes identify the queries associated with each Saved Query Group.

When the saved queries are loaded into the tree view, those saved queries that have invalid SQL query syntax or lack the query syntax for the format are loaded in the tree but are disabled.

Column View
In a 'Column' structure, the first two columns contain the children of level 1 saved queries, while all remaining saved queries and Saved Query Groups are presented within a 'Tree' structure within the third column.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When the columns are populated with saved queries, those saved queries that have invalid SQL query syntax or lack the query syntax for the format are not populated in the list (in the tree view, the saved queries are disabled).

The Omega Query Editor is used to identify those saved queries that are to be displayed in the columns. This is done by selecting a level 1 saved query for each column; the level 2 children of those saved queries are displayed in the column. The name of the level 1 saved query is displayed at the top of the column. If the selected level 1 saved query has level 3 children, then these children saved queries are not displayed and there is a warning.

Selecting Saved Queries in Tree
The content of the Saved Queries Tree (or columns) is made available once a query layer is selected during the routine. Displayed within the tree or columns, are all of the queries for each saved query group registered to the selected layer.

To select a saved query, select the check box in front of the name of the saved query. The selected queries are combined into a query string and shown to the right of the Saved Queries Tree.

A parent saved query is identified in the query tree with a checkbox icon. The distinguishing factor between a parent saved query and a simple saved query is the list of saved queries that appear below the parent query. These saved queries are also identified by checkboxes. Selecting the parent saved query does not select or use all of the saved queries below it, but rather uses its own attribute query.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
To select all saved queries under a parent saved query or category, right-click the item, and from the popup menu select "Select all child queries".

Select Saved Queries in Column
To select saved queries in the columns, simply select the saved query by clicking the mouse. Multiple saved queries can be selected by holding down the left mouse and while selecting all of the saved queries.

Another way to select multiple saved queries is to hold down the CTRL key while selecting the saved queries with the mouse.

Support For Different Query Layer Formats
Currently, layers used by OmegaGIS can be stored in one of four different formats: an ESRI Shapefile, a personal Geodatabase (MDB) feature class, File Geodatabase or an ArcSDE feature class. Each of these formats requires a different SQL syntax. The benefit of using saved queries on a layer is that the appropriate SQL syntax is automatically applied, regardless of the format.

The Omega Query Editor, available in ArcCatalog, can be used to build saved queries. In order for the saved queries to be available to all four layer formats, it must be built using the appropriate syntax for each of the data source types.

Editing the query
To manually edit the SQL syntax of a saved query, first select the query then click the Edit Query button. This button is only available when in Tree view.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
To edit the query manually in Column View, right click within any of the columns and from the pop-up menu select Edit query.

The Edit Query dialog allows one to manually edit the SQL syntax. The dialog provides similar functionality as ArcMap's Select By Attribute dialog.

Query Layer Information
The header of the dialog provides the name of the query layer, the data source of the query layer and whether or not text queries are case sensitive.

Field List
The list on the left contains the names of all of the fields in the Query Layer. When this list is first loaded, the fields are in the order found in the feature class; clicking the field header will sort the fields.

The fields are given an icon based on the field type.

Note: all other field types are excluded from this list.

Unique Values
When a field is selected in the list, a sample of the unique values for that field is populated in the list on the right and the complete list button is enabled. The sample size for the unique values and the number of unique values to display in the list are controlled by the parameters set on the Advanced tab on the General view in Setup.

Complete List
When the list of unique values is first populated, only a sample of the feature class is used to determine the unique values.

This sample size is controlled by Setup and the default value is set to 1,000. With this setting, only the first 1,000 records in the query layer are used to determine the unique values.

Text field
Numeric field
Date field

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
To populate the list of unique values using all of the records in the query layer, click the Complete List button. This processing may take a long time to complete and its use should be limited.

Restore
The Restore button clears the current attribute query and restores the original query from when the dialog was first opened.

Verify Query
The attribute query is tested when the Verify button is selected or when the OK button is selected. l There is a warning reported if no records are selected. This message is only issued when the Verify button is selected.

The message is not displayed when the OK button is selected as no records selected is still a valid query. l The process of verifying the query does not alter what is selected in the query layer. l The attribute query respects the definition expression and the selection layer features. l The Omega definition expression is not removed when testing the query. The Omega definition expression may be removed while the running the routine; this may be the cause as to why no features are selected when the Verify button is selected.

Load and Save
There is the ability to save the attribute query to an .EXP unicode text file. This file can be used with ArcMap's Select by Attribute dialog. There is an issue bringing the attribute query into ArcMap, a symbol is added to the beginning of the attribute query that must be removed manually.

Build Query
To add either a unique value or field name to the attribute query, double click the item in the list. When there is text selected in the attribute query text box, that text is replaced. When there is no text selected and the cursor is located in the text box, the new text is placed at the cursor location; otherwise the new text is added to the end of the attribute query.

Close Dialog
To close the dialog and use the attribute query click the OK button. When the OK button is selected there is a check to ensure that the newly constructed attribute query is valid. An attribute query that does not select any features is considered a valid query.

When the attribute query is manually edited, the query is enclosed with brackets. This is to prevent problems with the order of operations when the attribute query is used with date queries. The brackets are not added if the manual edit created no text.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Furthering this, there is no change in the syntax based on the format of the query layer when the attribute query is manually edited. This could result in issues when using additional query layers and these layers are stored in different formats.

Finding a Saved Query
To find a saved query in the Saved Queries tree, type the phrase to be found and click the button with the binoculars icon. When there is a selected node in the tree, the search starts at the saved query below the selected node. When there is no selected saved query node, the first node is the start point for the search.

If the phrase is found, the saved query node is selected and the font bolded. The bold is removed when the Find button is used again, another node is selected or the pop-menu is displayed.

The search for the phrase is not case sensitive and the use of wildcards is not supported.

Query Groupings
Query groupings are used in the construction of the SQL query when joining multiple saved queries. Those saved queries that have the same query grouping are joined together with the "OR" connector while different query groupings are joined with the "AND" connector. As a general rule, query groupings are based on different fields, since a single record's field value can never equal two different values at the same time.

At previous releases, Query Groups only supported two query groupings; primary and secondary. At the version 4.0 of Omega Desktop it is now possible to commit up to 50 query groupings and assign a customized color to each group in order to aid in identifying the different groups when they are displayed in the tree format.

Query groupings are distinguished by the font color. This color is set in the Omega Query Editor .

Building Query
The saved query view automatically combines the selected saved queries. Outlined below are the steps involved in generating the attribute query.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l All saved queries are surrounded with single brackets.

Example: UCR = 123 becomes (UCR = 123)
l All saved queries that share the same query grouping are surround with single brackets and joined with the OR operator.

Example: ((UCR =123) OR (UCR =124))
l Different query groups are joined together with the AND operator.

Example: ((UCR =123) OR (UCR =124)) AND ((MO = 84))
l When there are more then one query grouping, all of the saved queries are surround by brackets; this is to ensure order of operations when combined with date/time query.

Example: (((UCR =123) OR (UCR =124)) AND ((MO = 84)))
Unique Value Query
The Unique Value Query dialog contains the functionality to automatically generate the attribute query to manually select features based on a field value. This functionality is helpful when a specific case number is known.

Query Field
At the top left of the dialog is a drop down list that contains the names of all of the text and numeric fields found in the query layer. When there are no text or numeric fields, the dialog is not opened and a warning message is displayed. The attribute query is based on this field.

When the dialog is first loaded, the query field is selected based on the following criteria:
l Previous field used.
l The field identified as the "Default Field" in the query layers metadata. This information is set with the Omega Metadata Editor.
l The first field in the list.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Manually enter value
To manually enter a field value, type the value into the text box and select the ">" button to move the value to the Values to query list. The use of wildcards are not supported. When the query layer has the data source of a Shapefile or File Geodatabase, the search is case sensitive.

Field Values
The Field Values list contains a list of unique values that is populated when the query field is changed. Both the number of unique values displayed in the list and the number of features in the query layer to search through to determine the unique values is controlled by parameters in Setup (located on the Advanced tab on the General view).

To select a unique value to query, select the item in the list and then click the ">" button. The selected item is added to the Values to query list and removed from the Field Values list.

Those unique values that contain a single quote do not appear in the list.

When the Unique Value Query dialog is used, the previously selected saved queries are cleared and only the unique value query is used. Up to 100 values can be queried.

Query Viewer Information
The Saved Query Viewer contains detailed trouble shooting information. When there is a warning loading the saved queries, a warning icon is displayed.

The warning information is available in the Query Viewer Information dialog. This dialog is accessed by either double clicking the warning icon or from the pop-up menu.

Warnings
The Warnings view contains all of the warnings that were encountered when loading the saved queries. Typical warnings include the registered saved query group is not found or saved queries exist containing invalid syntax for the format.

Query Groups
The Query Groups view list all of the registered query groups found in the query layers metadata.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The order of the query groups is how the query groups are loaded when a Omega Query database is found. l The icon provides information as to whether or not the query group has been loaded. l When the query group is successfully loaded, the path to the Omega query database that was used is beside the name of the query group.
l When there are no registered query groups, there is a message on the list.

Database
The Database view contains all of the locations of the Omega query database that are searched for the query group information.
l The list is in search order. This search order is set on the Locations view in the Setup dialog. l The icon identifies whether the status of the Omega query database.

Date and Time Ranges
Date and Time ranges are used by OmegaGIS routines to define spans of time from which to query features in a layer. Selecting features from a specific date and time range is possible for all layers that include OmegaGIS fields in the attribute table.

This selection is divided in the following topics:

OmegaGIS Fields
Default OmegaGIS Fields
Selecting a Date Range
Selecting Day of Week
Organizing Date and Time Ranges
Clearing Date and Time Range
Available Date Range for Query Layer
OmegaGIS Fields

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Date and time attribute queries require fields that conform to a specific formatting standard. These fields are referred to as OmegaGIS fields, and can be created using the Omega Import Wizard. While importing data from a source database, the Import Wizard uses information from fields in the source dataset to generate the OmegaGIS fields.

The OmegaGIS fields currently supported include:

OmegaGIS Date: numeric field with the format of yyyyMMdd.

OmegaGIS Day of Week (DOW): numeric field with each day of the week having a different value. Sunday has a value of 0 and Monday has a value of 1. The value of -1 is assigned to incidents with invalid dates. The day of week field is created using the Date field.

OmegaGIS Time: text field with the hhmm format.

Although a standard data type and format are required for OmegaGIS fields, these fields do not require specific names. Unlike the date, time and day of week fields used with CrimeView and FireView for ArcView 3.x, multiple OmegaGIS date, time and day of week fields may be used within a single layer for analysis. Information about the OmegaGIS fields is stored in a layer’s metadata and can be viewed using the OmegaGIS stylesheet in ArcCatalog. Layers do not require OmegaGIS fields to be used with OmegaGIS routines, however date and time queries will be unavailable if they are omitted.

Default OmegaGIS Fields
Given that OmegaGIS supports layers with multiple Date, Time and Day of Week fields, it is important to identify which fields will be used for querying features. The OmegaGIS MetaData Editor is available to set the fields that will be used as defaults during an analysis.

Steps in Determining the OmegaGIS Field
OmegaGIS routines follow several steps to determine which fields to use for date and time queries. Since it is possible to store multiple OmegaGIS date, time and day of week fields within the same layer, it is important to understand the method OmegaGIS uses to identify the fields used within a given routine. The following steps identify the mode of field selection:
l The layer's metadata is read to determine the default OmegaGIS fields. l If no default OmegaGIS fields information is found in the metadata, the first date, day of week and time field found in the metadata is selected.
l If the layer has no metadata, such as when the layer has been created by legacy Avenue import scripts, the layer is searched for fields called "cvDate", "cvDOW" and "cvTime".

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Tool Tips
A method exists for quickly determining which OmegaGIS fields will be used for date and time attribute queries. On the When? tab, available within OmegaGIS routines, hover over the Date, Time or Day of Week labels to view the tool tip that identifies the fields used to select features in the Query Layer.

OmegaGIS Fields Dialog
To view or change the default fields temporarily for the current routine, click on the Options button of the When? tab to open the OmegaGIS Fields dialog. From this dialog, use the drop down list to alter the field.

Source field: Name of the field within the source feature class that has been identified in the metadata as an OmegaGIS field.

If the layer lacks metadata information about the OmegaGIS fields, the source field text box will be blank.

Date range: The date range text box for the OmegaGIS Date field provides information on the start and end date found in the feature class; the date information is in yyyymmdd format. The date range information is from the metadata of the feature class.

Selecting a Date Range
There are three ways to select a date range:

Previous Range
One option in selecting a date range employs the Previous duration selection. Select one of the duration types from the drop-down list: Hours, Days, Weeks, Months, or Years. The available numbers will change depending on the duration type that is selected. The ranges available include: 1 - 72 Hours; 1 - 90 Days; 1 - 52 Weeks; 1 - 24 Months; or 1 - 20 Years, respectively. When a duration is selected, the calendars at the top of the When? tab change to the range selected.

Date
Time
Day of Week

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The ranges identified by the Previous drop-down list describe completed blocks of time. If for instance, &rdquor;1 Month” is selected from the list, and the current date is January 10th, the calendar dates on the dialog read December 1st through December 31st. The previous date range is identified as the last complete month, and the dates January 1st through January 10th are omitted.

Similarly, selecting &rsquor;1 week’, updates the calendar dates with a range from December 29th through January 4th as that is the last complete week found. This concept carries on to days and hours.

The previous week date range uses a setup
option to determine the day of the week to use as the start day. The default day for the start of the week is Sunday.

Predefined Date Range
In situations where a range of dates is required, up to and including the current day, the Predefined Date Range list is available. For example, selecting &rsquor;Month to Date’ from the Predefined Date Range results in the selection of dates from January 1st to January 10th.

There are four standard predefined date ranges: Today, Week to Date, Month to Date, and Year to Date. Additional predefined date ranges can be created by manually selecting a date range and then clicking the Organize... button.

When the predefined date range is selected, the calendars at the top of the When? tab change to the selected date range.

Manually Select Dates
Manually select a date range using the calendars at the top of the When? tab. Using the FROM Date calendar, select the month and year by clicking on the arrows. The calendar defaults to the current month. The date selected is shown on the upper right side of the calendar. Using the TO Date calendar, select the month and year by clicking on the arrows. Again the selected date is shown on the upper right side of the calendar.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When the date range is selected, the Predefined Date Range reads as "OTHER". The calendar may have dates that are gray and cannot be selected. These are dates that fall outside of the layer’s available date range. In order to view a layer’s available date range, the OmegaGIS Setup option &rsquor;Display available dates&ldots;’ on the Advanced Tab of the General Settings must be selected. If a layer is missing metadata information, the option &rsquor;Search the layer’s feature class&ldots;’ for the date range may also be selected to determine the layer's available date range.

If the date range for a layer is not identified by the calendars on the When? tab, the settings in OmegaGIS Setup may not be selected. Alternatively, the routine may be using an additional query layer, in which case the layer’s date range is unavailable.

Selecting Day of Week
Days of the week can be singled out for analysis by selecting each day from the Day of Week list on the When? tab. To select a day, check the checkbox next to the day of interest. To clear the days selected, right-click on the list, and select &rsquor;Clear Day of Week’ from the popup menu. When all of the Day of Week values are cleared, the day of the week is not used in the attribute query.

If the OmegaGIS Day of Week field does not exist in the query layer, the Day of Week list is disabled.

Selecting a Time Range
A time range identifies the block of time used to select features from a layer during a routine. There are three ways to select a time range:

Previous Time Range
A previous time range based on hours is available from the Previous drop-down list. The number of available hours spans a time period of 1 to 72 hours. When a range is selected, both the FROM and TO calendars, as well as the FROM Time and TO Time controls are updated automatically.

Predefined Time Range
A time range can be selected using the predefined time range drop-down list on the When? tab. There are two standard predefined

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
time ranges: Day (0600 to 1759) and Night (1800 to 0559). Additional predefined time ranges can be created by manually selecting a time range and clicking the Organize... button to open the Range Definitions dialog.

When a predefined time range is selected, the FROM Time and TO Time controls are updated.

Manually Select Times
To set a time range manually, enter a time for the FROM Time and TO Time or use the arrow buttons to scroll to a time.

When a time range is entered manually, the predefined time range reads as "OTHER".

Organizing Date and Time Ranges
To manage the user created date and time ranges, click the appropriate Organize.. button. When saving a new date or time range, enter a title and click the Add New button.

The date and time ranges are stored in the Settings.MDB which is located in the OmegaGIS install directory; \OmegaGIS\Desktop\Databases. Predefined date and time ranges are available to any OmegaGIS application on the machine. The Organize button is disabled if the Settings.MDB cannot be found.

Clearing Date and Time Ranges
l Click the Clear All button to clear Date, Time and Day of Week selections. l To clear only the date range, from the Predefined Date Range list select "ALL DATES".

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l To clear only the time range, from the Predefined Time Range list select "ALL TIMES".

Available Date Range for Query Layer
The FROM and TO calendars display the query layer’s available date range based on whether the &rsquor;Display the available date&ldots;’ option is selected on the General Settings Advanced tab in OmegaGIS Setup. When this option is selected, the Query Layer’s metadata is read for the available date range. The metadata containing the date range is created if the layer is imported using the Omega Import Wizard.

If for any reason, the metadata is missing, the option &rsquor;Search query layer’s feature class&ldots;’ on the Advanced tab of the General Settings in OmegaGIS Setup can be used to search the feature class for the available date range. It is important to note that using this option may result in a performance hit, especially if the layer contains a large number of records.

Provided that the settings mentioned previously are used, and the &rsquor;Use additional layers in query ’ checkbox on the What?
tab is not selected, the calendars display the available date range in white, while those dates that are unavailable are grayed out.

Unavailable dates cannot be selected.

The tool tip can be used to determine the available date range. Hold the mouse over the FROM Date label for the beginning of the date range, hold the mouse over the TO Date for the end of the date range.

User Defined Area

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Many routines in OmegaGIS provide the option to create a user defined boundary to define a spatial filter. This tool is useful when there are no existing boundary layers that can be used to spatially query features.

Create User Defined Area
To create a user defined area follow these steps:
l On the Where? tab select the "User-defined area" option. If the Where? tab is disabled, then on the How? tab check the Subset by Boundary checkbox.
l With the "User-defined area" option selected, click the ellipses button. This button will shrink the dialog and make the ArcMap "Polygon" tool active.
l To create the polygon in the active data frame, click each point along the polygon's boundary. Double-click the last point to complete the boundary.
l To expand the dialog, double click the red flashing icon in the upper right corner.

Requirements of User Defined Area
A user defined area is a graphic element. In order to run a routine using the graphic element as the spatial filter, the graphic element must satisfy the following requirements:
l Only one graphic element may be selected. An element is selected when it has handles around it's envelope.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l A graphic element cannot consist of a group of elements. Grouped elements are created by selecting multiple elements and selecting "Group" from the Drawing toolbar.
l The element must be a polygon.
l The element can have only one exterior ring. Complex polygons as seen below are not supported. l The element cannot have an interior ring or donut.

Boundary Layer
Many OmegaGIS routines, including all Density routines, use a boundary layer to query features geographically.

Select Boundary Layer

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The first step in selecting boundaries to be used in a spatial query is to choose the boundary layer from the list of layers on the Where? tab. The criteria used to populate the list of boundary layers is as follows:
l The layer must be in the active data frame.
l The layer must be valid; meaning the data source of the layer is not missing. When the data source is missing the layer has a red exclamation mark in the table of contents.
l The layer must have the geometry type of polygon.
l There is an option in the OmegaGIS Setup dialog that controls whether to exclude layers created by OmegaGIS routines in the list of boundary and query layers. An example of a layer created by an OmegaGIS routine might be a density map. This layer can be excluded or included in the boundary layer list by toggling the setting in the OmegaGIS Setup dialog.

Selection Method
Once a boundary layer is selected, two Selection Methods are enabled, one of these options must be selected to continue.

By Field Value
The "By Field Value" selection method selects features in the boundary layer, such as a police beat or school district, based on an attribute value of the feature.

Field Name
From the Field Name drop-down listbox, select the field from the boundary layer that has values to be used to identify the features for the spatial query. The field should contain values that uniquely identify features in the boundary layer, such as the name of the school district. If an OmegaGIS default field is specified in the layer's metadata, this field is selected automatically.

The OmegaGIS default field is set with the OmegaGIS Metadata Editor.

Field Values
From the list of Field Values, select the values that represent the feature to use in the boundary layer. To select more than one value, hold down the CTRL key. To un-select a value from the list, hold down the CTRL key and select the value.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
To select all of the field values and use all of the features in the boundary layer, select the "Select all values" checkbox.

The Field Values list contains a unique list of values. In an effort to improve the performance of the OmegaGIS application, a predefined number of features in the boundary layer are used to determine the unique values. The number of features used to search for unique values is set in the OmegaGIS Setup dialog. For layers with a large number of features from which to search, select the Complete List button to sample each of the polygons found in the layer for unique values.

There is a limit to the number of unique values displayed in the Field Values list. This limit is set in the OmegaGIS Setup dialog.

When the limit of unique values is reached, a warning is displayed to the left of the list. The maximum number of unique values that can be displayed in the Field Values list is 30,000. If this becomes an issue, use the By Pointing selection method.

By Pointing
The "By Pointing" selection method allows interactive selection of the boundary layer features used in the spatial query. With this option selected, click the ellipses button to shrink the dialog which makes the boundary layer visible and ensures that the boundary layer is the only selectable layer in the active data frame.

Click on the feature to select a polygon. To select multiple features, hold down the SHIFT key and click on the other features.

Alternatively, select by dragging a box around the features. All of the features either touching or located within the box are selected.

When the selection is completed, double click the red flashing icon in the upper right corner of the dialog. The dialog will then expand to its normal size. The selectability of the layers will return to its state before the dialog was shrunk.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
OmegaGIS.STYLE
Styles are collections of symbols and map elements that are used when setting the symbology of a layer. Styles are stored in files that have the .STYLE extension. ArcGIS provides several styles out of the box. OmegaGIS comes with it's own style file called OmegaGIS.STYLE.

When a routine is run, the OmegaGIS style is added to the ArcMap document; if it is not already there. The OmegaGIS style file is located in the "< Install Directory >\OmegaGroup\Desktop\Symbology" folder.

The OmegaGIS style file contains the colour ramps used by routines, such as the Density Map routine and point symbols.

Modifying the OmegaGIS.STYLE
The color ramps used by the routines can be edited with the Style Manager in ArcMap. It is recommended that the OmegaGIS.STYLE file be backed up before any modifications are attempted. When editing the color ramps:
l The name of the color ramp cannot be altered.
l The category of the color ramp must be "OmegaGIS".
l The Exception_Report color ramp, used with the Exception Reporting/Enrollment Comparison routine and Exception Report Viewer/Enrollment Comparison Viewer, must be a 'Preset' color ramp. The figure below outlines which color is used with the class breaks of the layer.
l The DensityMap_* color ramps are used by Density Map, Crime Rate Generator/Demographic Analysis and Demographic Viewer routines. These color ramps must be an 'Algorithmic' color ramp. l The SpatialTrend_* color ramps, used by the Spatial Trend routine, are 'multi-part' which consist of two 'Algorithmic' color ramps.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Modifications made to the color ramps in the OmegaGIS style file will not be reflected in the routine dialogs, only with the resulting layers.

Omega Project Cleanup
The purpose of Omega Project Cleanup is to remove any temporary files that are created while using OmegaGIS software as well as clean up data sets that are generated by OmegaGIS but are not referenced by the ArcMap document. Project Cleanup is run automatically when the project is closed, but only if an OmegaGIS routine has been run. However, it may also be run manually from OmegaGIS Setup.

The clean up procedures involved in Project Cleanup are outlined below.

Remove Selection Layers
Remove OmegaGIS Feature Definitions
Remove Additional Query Layers
Remove Temporary Files
Clean Crime Rate Generator Database
Clear Demographic Analysis Database
Clean Demographic Viewer Database
Clean Exception Reporting/Enrollment Comparison Database Clean Additional Query Layers Database
Clean Density Map Database
Clean Repeat Calls/Student Concentrations Database
Clean Residency Report Database
Clean Raster Layers
Clean Shapefiles
Compress the Selection Database

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Remove Selection Layers
Selection layers are the result of running the Query routines provided with OmegaGIS. A selection layer is not distinct, but is linked to the source data on which it is based. For instance, the data source of a new layer showing only those crimes classified as assaults, actually leads back to the Part 1 Crimes layer from which the assault crimes were drawn.

Selection layers are identified in the Table of Contents with the text (Selection) added to the layer name. A selection layer may also be identified by right-clicking on the Properties dialog and selecting the Definition Query tab. The text &rdquor;*Layer based on a selection set&ldots;” identifies the layer as a selection.

Depending on the setting in OmegaGIS Setup
all Selection Layers are removed from the Table of Contents when Project Cleanup is run.

Remove OmegaGIS Feature Definitions
A feature definition is used in ArcMap to display features based on an attribute query. Only those features that satisfy the query are shown on the map. In OmegaGIS, this method is used as well when an OmegaGIS Query routine is run.

If the appropriate setting is selected in OmegaGIS Setup, only those features selected by the query in the routine are displayed on the map.

An Omega Feature Definition is simply the query used to identify the output features of an OmegaGIS Query routine. An Omega Feature Definition can be recognized by right-clicking on the layer name in the Table of Contents, clicking Properties, and selecting &rsquor;Definition Query’. An Omega Definition Query is delimited by a unique set of brackets &rsquor; (( ( (( ( (( Omega Query Here )) ) )) ) ))’.

During Project Cleanup, these feature definitions can be removed by setting an option in OmegaGIS Setup.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Remove Additional Query Layers
Composite layers are created when more than one layer is combined during an OmegaGIS Query routine. The layer can be recognized in the Table of Contents by the term &rsquor;(Composite)’ that is added to the layer name.

Composite layers may be removed from the project during a Project Cleanup by setting the appropriate option in OmegaGIS Setup.

Remove Temporary Files
Temporary files are created when OmegaGIS routines and tools are run. These temporary files are used only while the project is open, and an OmegaGIS routine is in progress. As they tend to build up on disk, they are removed automatically when the project is closed or can be removed manually using OmegaGIS Setup .

Clean Crime Rate Generator Database
The Crime Rate Generator Database (CrimeRateData.MDB) houses the data generated when a Crime Rate Generator routine is run in CrimeView. During a Project Cleanup, the feature classes in the Crime Rate Generator Database that are not referenced by layers in the table of contents are deleted.

Clean Demographic Analysis Database
The Demographic Analysis database (StudentData.mdb) houses the data generated when a Demographic Analysis routine is run in School Planner. During a Project Cleanup, the feature classes in the Demographic Analysis dtaabase that are not referenced by layers in the table of contents are deleted.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Clean Demographic Viewer Database
The Demographic Viewer Database (Omega_DemoViewer.MDB) houses the data generated by the Demographic Viewer.

During a Project Cleanup, the feature classes in the Demographic Viewer Database that are not referenced by layers in the table of contents are deleted.

Clean Exception Reporting/Enrollment Comparison Database The Exception Reporting/Enrollment Comparison Database (ExceptionData.MDB) houses the feature classes and tables that are generated when the Exception Reporting/Enrollment Comparison Analysis is run. Each new Exception Reporting layer is based on a feature class holding the geometry of that layer and a table that includes the attributes necessary for reporting crime statistics.

The feature class is linked to the table based on metadata that is stored in both the feature class and the table. The metadata tag <theomegagroup\exceptionreporting\featureclass> in the table identifies the feature class to which the table is linked. The metadata tag <theomegagroup\exceptionreporting\tablename> in the feature class identifies the name of the feature class.

To clean up the Exception Reporting/Enrollment Comparison database, each table in the database is identified and the metadata tag containing the name of the linked feature class is read. If the feature class is not being used as source data for any of the layers in the table of contents, both the table and feature class in the database are deleted.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Clean Additional Query Layers Database
The Additional Query Layers database (AddQueryLayers.MDB) stores the source data of Composite layers. Composite layers are created when two or more layers are combined during a Query or Density routine. To clean up the database, feature classes within the database are compared with the source data of the layers in the table of contents. If the feature class within the database is not being used as the source data for any of the layers in the table of contents, the feature class within the database is removed.

Clean Density Map Database
The Density Map Database (DensityMap.MDB) stores the source information used to display the results of the Density Map routine. Each time a new Density Map is created, a new feature class is created in the database on which the new layer is based. During a Project Cleanup, any feature class found in the database is removed, provided it is not referenced by any of the layers found in the table of contents.

Clean Repeat Calls/Student Concentrations Database
The Repeat Calls/Student Concentrations Database (RepeatCalls.MDB) houses the data generated when a Repeat Calls (Student Concentrations in School Planner) routine is run. During a Project Cleanup, the feature classes in the Repeat Calls (Student Concentrations) Database that are not referenced by layers in the table of contents are deleted.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Clean Residency Report Database
The Residency Report Database (ResidencyRpt.MDB) houses the data generated when a Residency Report routine is run in School Planner. During a Project Cleanup, the feature classes in the Residency Report Database that are not referenced by layers in the table of contents are deleted.

Clean Raster Layers
Raster layers are created by both the Hotspot (Spatial Clustering in School Planner) and Spatial Trend Analysis <LINK> routines.

The source data is stored in the \Hotspot folder, and it is this folder that is searched when a Project Cleanup is run. Raster data that is not used as the source data for any of the layers in the table of contents is removed.

Clean Shapefiles
During certain routines temporary shapefiles are created in order to generate the final layers. These shapefiles are removed when the

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
project is closed as they are not necessary to the results of the routines.

Compress the Selection Database
The Selection Database (Selection.MDB) stores and formats temporary selection sets that are used to display reports and graphs.

Since data is written to this database frequently, over time the database can become quite large due to the many additions and deletions of records. To keep the Selection Database size under control, it is automatically compressed when a Project Cleanup is run.

Persisting Routine Results
Most OmegaGIS routines create a new layer to display the results. These layers are typically removed from ArcMap's table of contents and deleted from disk with the Project Cleanup . This help section outlines methods to persist these layers.

Selection Layers
A selection layer is created by Query routines when the query results option is "Show only selection as new layer"; this option is set in the OmegaGIS Setup dialog. A selection layer is created from a subset of features selected from another layer in the active data frame. No new feature class is created on disk as the same datasource is used as the source layer.

To determine if a layer is a selection layer, use the Layer Properties dialog; in the table of contents right-click the layer and select Properties; then make the Definition Query tab active. There is a label at the bottom of the dialog if the layer is a selection layer, similar to the following image:

Selection layers may be removed with Clear All. Once removed from the active data frame, selection layers are lost as the layer was only a subset of an existing layer. Furthering this, the datasource of the layer may change which alters the features available in the selection layer. For example, CrimeView applications typically have a Calls for Service (CAD) layer that is updated nightly by the Omega Import Wizard. The Omega Import Wizard has the ability to get all the records that have occurred in the last 5 days. During the import process, duplicate features in the datasource of the layer are removed based on a primary key, such as a call number.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Once these duplicate features are removed, the newly imported features are appended. The selection layer may contain features that occurred 2 days ago which are removed and then replaced by the Omega Import Wizard. Although the call number remains the same, the ObjectID value is altered for the updated features and it is this ObjectID value that is used to determine the features in the selection layer. Consequently, there could be situations where after the import process, the selection layer will not contain the same features as when the selection layer was first created.

Follow these steps to permanently persist a selection layer so that it can be used at a future date:
l If necessary, in ArcCatalog create a personal Geodatabase that is to be used to permanently store the selection layer. Right- click in the folder to create the personal Geodatabase and select New from the pop-up menu and then Personal Geodatabase. l In ArcMap's table of contents, right click the selection layer and from the pop-up menu select Data and then Export Data. l From the Export Data dialog, select 'All Features' in the Export list and then click the browse button to navigate to a location to save the new feature class. A feature class is a term used to describe a layer that is store within a Geodatabase. It is recommended that the format of the new feature class be a Geodatabase. l On the Export Data dialog, click the OK button to generate the new feature class. The newly exported feature class only contains the data and not the symbology information. To permanently persist the symbology, select 'Yes' when prompted to add the exported data to the map as a layer.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Open the Layer Properties dialog for the newly created layer and click the Import button on the Symbology tab. On the Import Symbology dialog, select the import symbology definition from another layer and then from the layer drop down list select the selection layer. Click the OK button to import the symbology.

To permanently persist the symbology create a layer file (.lyr). A layer file contains information on both the datasource and symbology of the layer. In the table of contents, right click the new layer and from the pop-up menu select Save as Layer File.

The layer file can be added to an ArcMap document and the layer will contain the features from the selection layer and original symbology.

Result Layers
Result layers are those that are generated by an OmegaGIS routine, such as Density Map . These layers are typically based on a
newly generated feature class that are temporary stored in the project workspace. When these layers are no longer referenced in ArcMap's table of contents then the source feature classes are deleted during the Project Cleanup that occurs when ArcMap is closed.

The process to permanently persist these result layers is similar to that as selection layers which is described in detail above. The source feature class must be copied to new personal geodatabase and a layer file (.lyr) generated.

Attribute Query
Availability by Extension
CrimeView FireView School Planner
Attribute Query Attribute Query Attribute Query

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The Attribute Query routine selects features based on an attribute query. There is no Where? tab as a spatial query is not used.

The Attribute Query routine is the only Query routine that does not use a spatial query. Consequently, the routine is useful in selecting features that are not geocoded. Geocoding is the process of creating a geometric representation (such as a point) of a specific location from textual descriptive information, such as an address. Typically, not all addresses are geocoded therefore they do not have geometry (cannot be displayed on the map). However, these features are in the layer's attribute table. The Attribute Query routine selects those features that are both geocoded and not geocoded, provided that the feature satisfies the attribute query.

What?
The What? tab is used to specify the following query parameters:
l Query Layer
Select the Query Layer from a list of point layers in the active data frame. The features in the Query Layer that satisfy the attribute query and date or time range are selected by the Attribute Query routine. l Additional Query Layers
Select Additional layers that can be included with the Attribute Query routine. l Attribute Query
Once the Query Layer is selected, the saved query groups registered to the Query Layer are displayed in the Saved Queries tree or columns.

When?
The When? tab is used to specify a date or time range. This tab is only available if the Query Layer set in the What? tab has OmegaGIS date and time fields. For the School Planner product, this tab is not available since queries are always performed on a full year of student data.

Running the Attribute Query Routine
To run the Attribute Query routine, click the Finish button. The button is only enabled when all of the parameters for the routine are set. The required parameters for the Attribute Query routine require that:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l A Query Layer is set.

An attribute query and a date or time range are not required to run the routine.

When the Finish button is selected, the routine validates the parameters for the routine and then display a summary dialog. This dialog provides an overview of the Attribute Query routine parameters. Use the Back button to return to the query dialog to make edits to the Attribute Query routine. The Save button on the summary dialog allows the routine to be saved as a Cyclical Report and/or Threshold Alert.

The "Display the routine summary dialog" option in the OmegaGIS Setup dialog controls whether the summary dialog is shown.

The default option displays the summary dialog.

Results of the Attribute Query
When the Attribute Query routine is complete, the following events occur:
l The query dialog shrinks. To restore the query dialog, double click the icon in the upper right corner of the dialog. The OmegaGIS Setup dialog has a setting to hide rather than shrink the query dialog. l The active data frame zooms to the selected features. The "Zoom to selection" option in the OmegaGIS Setup dialog controls this action.
l The selected features are displayed based on the "query result" option in the OmegaGIS Setup dialog. When a selection layer is created, the label information, including whether or not to display the labels, is copied from the original layer.

If no features are selected by the Attribute Query routine, the following events occur:
l The query dialog is maximized.
l A message box reports that the routine cannot be completed. If additional query layers are used, the number on the message box reads 7810306 otherwise the number reads 7810308.
l The OmegaGIS definition expression of the Query Layer and the additional query layers are removed.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The visibility of the Query Layer reverts to its state before the Attribute query routine was run. If additional query layers were used all of the layers, including the Query Layer, will not be visible.

Tip:
l The selection layer must be exported to permanent persist the layer.

Date Updated: May 27, 2009
Within A Boundary
Availability by Extension
The Within A Boundary routine selects featurs within one or more selected boundaries in addition to using an attribute query.

What?
The What? tab is used to specify the following:
l Query Layer
Select the Query Layer from the list of point layers in the active data frame. The features in the Query Layer that are within the selected boundaries and satisfy both the attribute query and date or time range are selected by the routine. l Additional Query Layers
Select the Additional layers that can be included with the Within A Boundary routine. l Attribute Query
Once the Query Layer is selected, the saved query groups registered to the Query Layer are displayed in the Saved Queries tree or columns.

CrimeView FireView School Planner
Within A Boundary Within A Boundary Within A Boundary

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Where?
The Where? tab is used to select the boundaries used for the spatial query when running the routine. There are two boundary types:
l Existing Boundary Layer
The features of an existing boundary layer are used to spatially query features. Select the boundary layer and then the features to include in the spatial query.

When editing a Cyclical Report or Threshold Alert, if the By Pointing selection method has been used, the features in the boundary layer will be selected.
l User Defined Area
The User Defined Area boundary type is useful when there are no existing boundary layers that can be used to spatially query features.

When editing a Cyclical Report or Threshold Alert the user defined graphic element is created on the active data frame is automatically selected. To change the user defined boundary, delete the element and create a new one.

When?
The When? tab is used to specify a date or time range. This tab is only available if the Query Layer set in the What? tab has OmegaGIS date and time fields. For School Planner this tab is not available as queries are performed on the full year of student data.

Running the Within A Boundary Routine
To run the Within A Boundary routine, click the Finish button. The Finish button is only enabled when all of the routine parameters are set. The required parameters for the Within A Boundary routine include:
l A Query Layer must be set.
l When the Existing Boundary Layer boundary type is selected, the boundary layer is selected. When the selection method of By Field Value is used, at least one field value must be selected. When the By Pointing selection method is used, there is no check to ensure that features in the boundary layer are selected until the Finish button is clicked.

An attribute query and a date or time range are not required to run the Within a Boundary routine.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When the Finish button is selected, the routine validates the routine parameters and displays a summary dialog. The validation includes checking that there are features selected in the boundary layer when the Existing Boundary Layer boundary type is used with the By Pointing option. When the boundary type of User-Defined Area is used, the graphic element is checked.

The summary dialog provides an overview of the Within A Boundary routine parameters. Use the Back button to return to the query dialog to make edits to the Within a Boundary routine. The Save button on the summary dialog allows the routine to be saved as a Cyclical Report and Threshold Alert.

The "Display the routine summary dialog" option in the OmegaGIS Setup dialog controls whether the summary dialog is shown.

The default option displays the summary dialog.

Results of Within A Boundary
When the Within A Boundary routine is completed, the following events occur:
l The query dialog shrinks. To maximize the query dialog, double click the icon in the upper right corner. The OmegaGIS Setup dialog has a setting to hide rather than shrink the query dialog. l The active data frame zooms to the boundary. The "Zoom to selection" option in the OmegaGIS Setup dialog controls this action.
l The selected features are displayed based on the "query result" option in the OmegaGIS Setup dialog. When a selection layer is created, the label information, including whether or not to display the labels, is copied from the original layer. l The boundary layer will be visible.
l The features in the boundary layer that were used in the spatial query will be selected. The "Select features used as boundaries" option in the OmegaGIS Setup dialog controls this action. l The features in the boundary layer will be labeled if that option was selected on the Where? tab. The style of the label is set in the OmegaGIS Setup dialog.

If no features are selected by the Within A Boundary routine, the following events occur:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The query dialog is maximized.
l A message box reports that the routine cannot be completed. If additional query layers are used, the number on the message box reads 7810306 otherwise the number reads 7810308.
l The OmegaGIS definition expression of the Query Layer and the additional query layers are removed. l The visibility of the Query Layer reverts to its state before the Within A Boundary routine was run. If additional query layers are used all of the layers, including the Query Layer, are set to invisible. l The features in the boundary layer are selected, the "Select features used as boundaries" option in the OmegaGIS Setup dialog determines if the features are selected.
l The features in the boundary layer are labeled if that option is selected on the Where? tab. Use the Clear All to remove the labels.
l The active data frame zooms to the buffer. The "Zoom to selection" option in the OmegaGIS Setup dialog controls whether the zoom occurs or not.

Tip:
l The selection layer must be exported to permanent persist the layer.

Date Updated: May 27, 2009
Near An Address
Availability by Extension
The Near An Address routine selects features based on their proximity to a location determined by a street address or street intersection.

CrimeView FireView School Planner
Near An Address Near An Address Near An Address

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The Near An Address routine uses address locators. Address locators are built as a method of geocoding which is the process of creating a geometric representation (such as a point) of a specific location from textual descriptive information, such as an address.

An address locator is created by ArcGIS and is used to determine the location of an address or intersection. In ArcGIS versions previous to 9.0, the address locator was referred to as a geocoding service.

What?
The What? tab is used to specify the following query parameters:
l Query Layer
Select the Query Layer
from the list of point layers in the active data frame. The features in the Query Layer that are within the designated buffer around the address or intersection and satisfy both the attribute query and date or time range are selected by the routine.
l Additional Query Layers
Select the Additional layers that can be included with the Near an Address routine. l Attribute Query
Once the Query Layer is selected, the saved query groups registered to the Query Layer are displayed in the Saved Queries tree or columns.

Where?
The Where? tab is used to specify the address or intersection and buffer distance. l Address
Enter the address or intersection used to select features based on their proximity.

When geocoding to large geographic regions, such as to an entire county, Omega recommends using an address locator style that supports zones. The zone provides additional information used to resolve ambiguity between addresses by identifying a region in which the address is located. The zone can be a ZIP code, city name or police beat. If the address locator has a style that uses zone, a zone text box is visible.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When the address locator has a style that uses zone, the zone information entered is not used when the address contains an intersection connector. The intersection connectors are set with the address locator properties dialog and typically include "&" or "/". Click the Geocoding Properties button to view and edit the intersection connectors. l Check address
To determine if the entered address or intersection can be found by the selected address locator, select the Check Address button. A message box states whether or not the address is geocoded. If the address is not geocoded attempt the following:
¡ Ensure that the address is spelled correctly.
¡ Alter the geocoding properties by reducing the spelling sensitivity or minimum match score. l Address Locator
All of the address locators referenced by the ArcMap document are listed in the drop-down list. Select the address locator to use for the Near An Address routine.

Only valid address locators are available in the drop-down list. The most common reason for an invalid address locator is that its reference data, such as the street centerlines feature class, has been moved, renamed or deleted. Use ArcCatalog to determine the address locator issue.

Address locators based on the ESRI StreetMap are not currently supported and are not available in the drop-down list of address locators.

If the ArcMap document does not reference any address locators, there is a red exclamation mark beside the drop-down list of address locators.

To add or remove an address locator, select the Add/Remove button. This selection opens ArcMap's Address Locator Manager dialog to add additional address locators to the ArcMap document. l Buffer Distance
The buffer distance is the radius around the selected address or intersection which is used in the spatial selection. The available measurement units for the buffer distance are Meters and Kilometers when using the Metric measurement system or Miles and Feet when the English measurement system is used. The measurement system is set in the OmegaGIS Setup dialog.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When the "Only at address (no buffer)" checkbox is selected, the buffer distance text box is disabled since there is no user defined buffer. The geocoded location is buffered 0.5 meters (1.64 feet) which creates the polygon that is required to make the spatial selection.
l Geocoding Properties
To alter the properties of the address locator selected in the drop-down list, select the Geocoding Properties button. The button opens the Properties dialog for the address locator.

Any changes to the properties of the address locator, such as the spelling sensitivity, apply to the current ArcMap session only.

When ArcMap closes, the changes to the geocoding properties are lost. Use ArcCatalog to make permanent changes to the properties of the address locator.

The parameters for the Near An Address routine may be saved as a Cyclical Report or Threshold Alert. However, only the
minimum match score and the spelling sensitivity geocoding properties are saved. Any edits to the minimum match score and spelling sensitivity address locator properties in ArcCatalog are not used when running a Cyclical Report or Threshold Alert. The Cyclical Report or Threshold Alert must be edited in order for the new geocoding properties to be saved.

When?
The When? tab is used to specify a date or time range. This tab is only available if the Query Layer set in the What? tab has OmegaGIS date and time fields. For School Planner, this tab is not available as all queries are performed on the full year of student data.

Running the Near An Address Routine
To run the Near An Address routine, click the Finish button. The Finish button is only enabled when all of the routine parameters are set. The required parameters for the Near An Address routine include:
l A Query Layer
is set.
l An address is entered. If the address locator uses zone information, the zone does not have to be entered for the Finish button to be enabled.
l An address locator is selected.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
An attribute query and a date or time range are not required to run the Near An Address routine.

When the Finish button is selected, the routine will validate the routine parameters and then display a summary dialog. This dialog provides an overview of the Near An Address routine parameters. Use the Back button to return to the query dialog to make edits to the Near An Address routine. The Save button on the summary dialog allows the routine to be saved as a Cyclical Report and/or
Threshold Alert.

The "Display the routine summary dialog" option in the OmegaGIS Setup dialog controls whether the summary dialog is shown.

The default option displays the summary dialog.

Results of Near An Address
When the Near An Address routine is complete, the following events occur:
l The query dialog shrinks. To restore the query dialog, double click the icon in the upper right corner. The OmegaGIS Setup dialog has a setting to hide rather than shrink the query dialog. l The active data frame zooms to the buffer around the address or intersection. The "Zoom to selection" option in the OmegaGIS Setup dialog controls this action.
l The selected features are displayed based on the "query result" option in the OmegaGIS Setup dialog. When a selection layer is created, the label information, including whether or not to display the labels, is copied from the original layer. l The buffer is drawn around the address. The buffer is an element in the OmegaGIS buffer annotation group. l The address is labeled if that option is selected on the Where? tab. The style of the label is set in the OmegaGIS Setup dialog.

If no features are selected by the Near an Address routine, the following events occur:
l The query dialog is maximized.
l A message box reports that the routine cannot be completed. If additional query layers are used, the number on the message box reads 7810306 otherwise the number reads 7810308.