Oakland City Council
July 19, 2022

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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 Near an Address routine was run. If additional query layers were used all of the layers, including the Query Layer, they will not be visible. l The buffer around the address is drawn and the active data frame zooms to the buffer. The "Zoom to selection" option in the OmegaGIS Setup dialog controls whether the zoom occurs. Use the Clear All to remove the Near an Address buffer.

Tip:
l The selection layer must be exported to permanent persist the layer.

Date Updated: May 27, 2009
Near A Feature
Availability by Extension
The Near A Feature routine selects features based upon their proximity to one or more selected features in addition to an attribute query. Features can be point (e.g. schools or banks), line (e.g. streets or rivers) or polygon (e.g. parks or report districts).

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 buffer around the selected features and satisfy both the attribute query and date or time range are selected by the Near a Feature routine.

CrimeView FireView School Planner
Near A Feature Near A Feature Near A Feature

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Additional Query Layers
Select Additional layers that can be included with the Near A Feature 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 feature layer, selection method and the buffer distance. l Feature Layer
Select the feature layer from the drop-down list. The criteria used to populate the list of feature layers includes:
¡ The layer must be in the active data frame.
¡ The layer must be valid; 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.
¡ The layer must have a geometry type of point, polygon or line. ¡ If the layer was generated by an OmegaGIS routine, such as a composite layer or density map, an option in the OmegaGIS Setup dialog must be set to include these layers.
l Selection Method
There are three methods available which can be used to select features for the Near A Feature Routine:

Use Selected Features
This selection method is only available if the layer has selected features when the query dialog is loaded. The number of selected features found in the feature layer are displayed beside the option.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
By Pointing
The "By Pointing" selection method allows interactive selection of the layer's features to be used in the spatial query. With this option selected, click the ellipses button to shrink the dialog, make the feature layer visible and ensure that the feature layer is the only selectable layer in the active data frame.

Click the feature to be selected. To select multiple features, hold down the SHIFT key and click the other features. Alternatively, select features by dragging a box around a group of features. All of the features touching or within the box are selected.

When the selection is complete, double click the flashing icon in the upper right corner of the dialog. The dialog expands to its normal size and the selectability of the layers returns to its original state before the dialog was collapsed.

By Field Value
The "By Field Value" selection method selects features in the layer, such as a police beat, fire district or school district, based on the features attribute value.

From the Field Name drop-down listbox, select the field from the feature layer that has values that are to be used to identify the features for the spatial query. The field should contain values that uniquely identify features in the layer, such as a school name. If an OmegaGIS default field is specified in the metadata for the feature layer, this field will automatically be selected. The OmegaGIS default field is set with the OmegaGIS Metadata Editor .

From the list of Field Values, select the values that represent the features to use in the feature 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 it again.

To select all of the field values and use all of the features in the layer, check the "Select all values" checkbox.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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 feature 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 features 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. l Buffer Distance
The buffer distance is the radius around the selected feature 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.

When the "Only at feature (no buffer)" checkbox is selected, the buffer distance text box is disabled since there is no user defined buffer. The feature is buffered 0.5 meters (1.64 feet) which creates a polygon that is required to make the spatial selection.

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 always performed on the full year of student data.

Running the Near a Feature Routine
To run the Near a Feature routine, click the Finish button. The Finish button is only enabled when all of the parameters for the routine are set. The required parameters for the Near a Feature routine include:
l A Query Layer is set.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The feature layer is selected.
l When the selection method of By Field Value is used, at least one field value must be selected. When the By Pointing or Use selected features selection methods are used, there is no check to ensure that features are selected in the feature layer until the Finish button is clicked.

An attribute query and a date or time range are not required to run the Near a Feature routine.

When the Finish button is selected, the routine validates the parameters and then displays a summary dialog. The validation includes checking that there are features selected in the feature layer when either the By Pointing or Use selected features options is used.

The summary dialog provides an overview of the parameters for the Near A Feature routine. Use the Back button to return to the query dialog to make edits to the Near A Feature 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 Near A Feature
When the Near a Feature 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 extent of the buffer(s). 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 feature layer is visible.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l The features in the feature layer used in the spatial query are selected. The "Select features used as boundaries" option in the OmegaGIS Setup dialog controls this action.
l The features in the feature layer are 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 A Feature 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. l The visibility of the Query Layer reverts to its state before the Near A Feature routine was run. If additional query layers were used all of these layers, including the Query Layer, will not be visible. l The features in the feature 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 feature 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 around the selected features. The "Zoom to selection" option in the OmegaGIS Setup dialog controls whether the zoom occurs.

Tip:
l The selection layer must be exported to permanent persist the layer.

Date Updated: May 27, 2009
Density Maps
There are three different routines that may be run from the Density dialog. Use the buttons along the top of the dialog to choose the routine. The selected routine button will be in colour and the label at the top right will display the name of the routine.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When a different routine is selected, the What? tab will become active and the How? tab will change based on the routine selected.

Density Map
The Density Map routine creates a choropleth map using either the count of features or density of features (count of features / area) in an existing boundary layer.

Hot Spot Map (Spatial Clustering in School Planner)
The Hot Spot routine creates a raster layer that displays the concentration of features. ArcGIS Spatial Analyst is required to run the routine.

Repeat Calls (Student Concentrations in School Planner) The Repeat Calls routine creates a layer that reveals places that have numerous features at the same location.

Tip
l When the Density dialog is opened, the routine that was last used is selected. If no Density routine was used, the Density Map routine is selected.

About Density Map Routine
Availability by Extension
A choropleth map symbolizes the magnitudes of statistics as they occur within boundaries, such as Police Beats or School Districts.

The Density Map routine creates a choroplethic map of either the count of features or density of features (count of features / area) in an existing boundary layer.

The Density Map layer, created by the routine, provides a way to view the variability of features in the boundary layer. If the boundary layer has large areas, the Density Map routine will process quickly but the spatial variation of the incident tends to be reduced or averaged out. On the other hand, if the boundary layer has small areas, the spatial variation is preserved at the cost of increased processing time for the routine.

D
H
R
CrimeView FireView School Planner
Density Map Density Map Density Map

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The layers generated by the Density Map routine can have a Crystal Report associated with them. The Density Map Crystal Report provides a statistical summary of the count and density values in order to identify statistical outliers or potential problem areas.

Classification of Layer
The count or density field for the Density Map layer are broken into arbitrary classes and these classes are used in the legend for the Density Map layer. The Jenks Natural Breaks statistical formula is used to inspect the data and determine the class breaks. This method attempts to minimize the variance within the class and to maximize the variance between the classes. Hence, the natural breaks method highlights the 'natural grouping'.

The classes are related to the data, as opposed to predefined class breaks. Consequently, the class breaks will change for each Density Map layer created.

These class breaks can be edited after the routine is completed by using the Symbology tab in the Density Map layer's Properties dialog.

Create Density Map Layer
There are four tabs available that contain options and settings for creating and displaying a Density Map layer. The tabs included What?, How?, Where? and When? School Planner does not support the When? tab, as all queries are expected to be made on the full year of student data.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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 incidents in the Query Layer that satisfy both the attribute query and date or time range are used to generate the Density Map. l Additional Query Layers
Select Additional layers that can be included with the Density Map 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.

How?
The How? tab includes settings that control the way in which the Density Map is created and displayed. l Boundary Layer
From the drop-down list, select the polygon layer to be used as the boundary layer. The features that satisfy both the attribute query and the date or time range will be summarized for each feature in the boundary layer. The criteria used to populate the list of boundary layers includes:
¡ The layer is in the active data frame.
¡ The layer is valid; this means 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.
¡ The layer must have a geometry type of polygon.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
¡ 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. By default, layers created by OmegaGIS routines are not included in the boundaries list. l Normalize Field
To normalize the summarized feature data, select the "Normalize by demographic or other data" checkbox and then the field to use from the drop-down list. This list contains numeric fields from the boundary layer.

The "Shape_Length" and "Shape_Area" fields found with layers stored in a personal geodatadatabase or the "Shape.Len" and "Shape.Area" fields found with layers stored in ArcSDE are not available in the list of normalize fields.

Normalizing divides the count of the summarized features by the value of the normalization field for that boundary feature; the result is used in the creation of the density map legend.

Normalized Value = (Count of Features / Normalize Field Value) Normalizing data minimizes differences in values based on the numbers of features in each area. For example, dividing a count of emergency medical incidents by the number of persons over 65 years of age in each census track will minimize the effect on the incident density distribution map resulting from concentrated elderly population. l New Layer Name
Enter the name for the new density layer which is used when the density map layer is added to the active data frame's table of contents.
l Color Scheme
From the drop-down list, select the color ramp that is used to generate the legend of the new density map. These color ramps are stored in the OmegaGIS.STYLE
file.
l Classify By
There are two options that determine how the new density map legend will be classified:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Density
The count of features are divided by the area of the boundary feature. When the Metric measurement system is set in the OmegaGIS Setup dialog, the density is calculated as feature per square kilometer. When the English measurement system is used, the density is calculated as features per square mile.

The Density option is not enabled when the "Normalize by demographic or other data" checkbox is selected.

Count
The count of the features found in the boundary feature are used. l Options
Two options are available in controlling the placement and look of the new density map.

Show below point and line layers
Use the "Show below point and line layers" checkbox to have the new density map layer placed below all point and line layers in the active data frame. By default, the new density map layer will be added at the top of the table of contents and may obscure point and line layers below it.

Transparency
The transparency setting can also be used to ensure that points and lines below the new density map layer will not be obscured. Set the percentage of transparency for the new density layer, where 0% means that the layer is opaque and 100% means that the layer is invisible. This transparency value can also be changed later by using the Display tab in the Layer Properties dialog. The default transparency value is 20%.

Where?
The Where? tab provides options to narrow down the number of features in the boundary layer used in the creation of the density map. The Where? tab is only enabled when the "Subset by boundary" checkbox is selected on the How? tab.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Select the features in the boundary layer that are to be used in the spatial query. The "Select all values" checkbox is not available on the Where? tab; if all of the features in the boundary layer are to be used then do not use the subset by boundary option.

When editing a Cyclical Report and the By Pointing selection method has been selected, the boundary features are selected.

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. When using Density Map in School Planner, this tab is not available as all queries are made on the entire school year.

Running the Density Map Routine
To create the density map, click the Finish button. The Finish button is only enabled when all of the parameters for the routine are set. The required parameters for the Density Map routine require that:
l A Query Layer is set.
l The boundary layer is selected.
l when the "Normalize by demographic or other data" option is selected, a field in the normalize fields drop-down list is selected.
l When the "Subset by boundary" option is selected and the By Field Value selection method is used, the field name drop-down list has a field selected and at least one field value is selected. When the By Pointing selection method is used, there is no check to ensure that features are selected in the boundary layer until the Finish button is clicked.

An attribute query and a date or time range are not required to run the Density Map routine.

When the Finish button is selected, the routine validates the parameters and then displays a summary dialog. The validation includes checking that there are features selected in the boundary when the By Pointing option is used.

The summary dialog provides an overview of the parameters for the Density routine. Use the Back button to return to the query dialog to make edits to the routine. The Save button on the summary dialog allows the routine to be saved as a Cyclical Report.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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 Density Map Routine
This section describes the results of the Density Map routine and is divided into the following topics:

Results of Routine
DensityMap.MDB
Density Map Layer
Results of Routine
When the Density Map routine is successfully completed, the following events occur:
l The density dialog shrinks. To maximize the density dialog, double click the icon in the upper right corner. The OmegaGIS Setup dialog has a setting to hide rather than shrink the density dialog. l The extent of the active data frame is changed to the extent of the newly created Density Map layer plus a 5% buffer. l The Query Layer and any additional query layers that are used to generate the Density Map layer have the following done to them:
¡ Layer has visibility turned off.
¡ The OmegaGIS definition expression is removed from the layer. ¡ The selected features are cleared.
l The boundary layer will have following done:
¡ Any selected features will be cleared. The "Select features used as boundaries..." option in the OmegaGIS Setup dialog does not apply to the Density Map routine.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
¡ The visibility of the layer is not altered. If the boundary layer was visible when the Density Map routine is run then it will be visible when the routine is completed.

If no incidents are selected by the Density Map routine, the following events occur:
l The density 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 7810434.
l The OmegaGIS definition expression of the Query Layer and the additional query layers are removed. l The visibility of the Query Layer is the same as before running the Density Map routine. If additional query layers are used, all of the layers, including the Query Layer, are not visible.

DensityMap.MDB
During the running of the routine, a new feature class is generated in a personal Geodatabase. The Density Map layer is based on this feature class.
l The Geodatabase is named DensityMap.MDB and is located in the "\Density" folder in the project workspace. l The DensityMap.MDB is created dynamically by the Density Map routine. If the Geodatabase is not present it is created when the Density Map routine is run.
l The feature class has all of the boundary layer fields plus two new fields that are created by the routine.

OmegaGIS_Count
This field contains the number of features that are found in the boundary.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
OmegaGIS_Density
The density (count of features/ area) is in this field. The area is in square Kilometers or in square miles, depending on the measurement system selected in the OmegaGIS Setup dialog.

The "Shape_Area" field is not used in the calculation of the OmegaGIS_Density field. The "Shape_Area" field is created and maintained by the Geodatabase and the values in this field are in the units of the spatial reference of the feature class which may not be in Kilometers or Miles.
l When the feature class in the DensityMap.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 density routine, export the feature class to a different personal Geodatabase.

Density Map Layer
The Density Map routine adds a layer to the active data frame whose data source is from a feature class in the DensityMap.MDB.

The Density Map layer has the following settings:
l Class Breaks
The graduated colors renderer is used with the Jenk's Natural Breaks statistical formula that is used to determine the class breaks used in the legend. While f ive class breaks are used by default, the number of classes is automatically reduced if the data does not support being broken into five classes. l Legend Heading
The heading of the legend in the table of contents changes based on how the layer was classified. The heading can be altered by double-clicking the text which makes the text editable.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Round Values
When using the Density classify method, the values for the class breaks in the legend are rounded to two decimal places. l Labels
The label properties, the label field or the label expression and the text symbol, are copied from the boundary layer. l Primary Display Field
The primary display field is set to either the OmegaGIS_Count or OmegaGIS_Density field; based on which was selected to classify the layer. The primary display field is used with the ArcMap Identify tool. The value of the field is shown on the right side of the Identify Results dialog rather than scrolling through the list of field values. l Color Ramp
The color ramp used with the layer is from the OmegaGIS.STYLE and is set to the layer.

About Hot Spot / Spatial Clustering Routine
Availability by Extension
The Hot Spot routine (Spatial Clustering in School Planner) creates a raster layer that displays the concentration of features. The ArcGIS Spatial Analyst extension is required to run the routine.

CrimeView FireView School Planner
Hot Spot Hot Spot Spatial Clustering

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Spatial Analyst Extension
There are two main types of Geographic Information System (GIS) data, vector and raster. Vector data takes a study area, such as a city, and converts the features into points, lines and polygons. On the other hand, raster data converts the study area into a regular grid of cells. Each cell contains a single value.

Spatial Analyst is an extension to ArcGIS and allows for the creation, querying and analysis of cell-based raster layers. OmegaGIS will automatically enable the Spatial Analyst extension, if licensed from ESRI, when the Density dialog opens. The "all extensions used with OmegaGIS routines..." option in the OmegaGIS Setup dialog controls the enabling of the Spatial Analyst extension. To manually enable the extension, from the Tools pull-down menu in ArcMap select Extensions and from the dialog select the Spatial Analyst extension; there is a message box that states if the extension is not licensed from ESRI.

If the Spatial Analyst extension is not enabled, when the routine button is selected a message box (780026) will report that the routine cannot be run without the Spatial Analyst extension enabled. Additionally, the tool tip over the routine button that states that the Spatial Analyst extension is not enabled.

Creating Raster Layers

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The resulting layer from the Hot Spot routine (Spatial Clustering in School Planner) is a raster. A raster is made up of individual cells that all have the same size and a single value.

The Hot Spot routine (Spatial Clustering) creates the raster from the point data using the Density function in Spatial Analyst. The value assigned to each cell is based on the frequency of features found in proximity to the cell. By default, the cell size is 75 meters by 75 meters when using the Metric measurement system or 250 feet by 250 feet when using the English measurement system. The search distance, which is the radius measured from the center of the cell that is used to locate nearby features, the default value is 250 meters or 800 feet.

The density type of Kernel is used as opposed to the Simple density type. With the Simple density type, the value of each cell is calculated by counting the number of points found within the radius and that value is divided by the area of the search radius. The Kernel type works the same as Simple, except points lying nearest the center of the cell are given a greater weight. If a population field is identified, the values in that field are used to weight the points in the cell value scoring.

The result of the Hot Spot Routine (Spatial Clustering) is a raster layer that represents a continuous density surface of features.

Tip
l The cell size should be small enough to capture the detail but large enough to limit the amount of storage space on disk that the raster requires and improve performance of the routine. The cell size is depend on the study area and data accuracy.

Create Hot Spot / Spatial Clustering Layer
There are four tabs available that contain options and settings for creating and displaying a Hot Spot (Spatial Clustering) layer. The tabs included What?
, How?, Where? and When? The term Hot Spot is used within the CrimeView and FireView products, while Spatial Clustering is the term used within the School Planner product. School Planner does not support the When? tab, as all queries are expected to be made on the full year of student data.

What?

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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 satisfy both the attribute query and date or time range are used to generate the Hot Spot layer. l Additional Query Layers
Select additional layers that can be included with the Hot Spot 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.

How?
The How? tab includes settings that control the way in which the Hot Spot layer is generated and displayed. l New Layer Name
Enter the name for the new hot spot (spatial clustering) layer which is used when the layer is added to the active data frame's table of contents.
l Color Scheme
From the drop-down list, select the color ramp that is used to generate the legend of the new hot spot (spatial clustering) map. These color ramps are stored in the OmegaGIS.STYLE file.
l Population Field
A population field is used for weighting each feature when generating the raster.

The population field list contains all of the numeric fields in the Query Layer. The "Shape_Length" and "Shape_Area" fields found with layers stored in a personal geodatadatabase or the "Shape.Len" and "Shape.Area" fields found with layers stored in ArcSDE are not available in the population field list.

Select "< Do not use population field >" item in the list to not use a population field.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Layer Extent
Set the spatial extent of the new raster. The list contains "< Same as selected features >", "< Same as current extent >", "< Same as data frame >" and all valid layers in the active data frame. The list is disabled when the "Subset by boundary" option is selected as the extent of the selected boundary layer features are used.

When the "< Same as selected features >" option is selected, the extent of the selected features is expanded by 10% to prevent the raster from cutting off a hot spot.
l Raster Options
There are two options that can be set that control how the raster is generated.

Cell Size
Specifies the size of individual cells in the raster
. The smaller the size of the cell the longer time it will take to generate the raster.

The default cell size is 75 meters when the Metric measurement system is set in the OmegaGIS Setup dialog with a valid range of 3 to 1000 meters. The default cell size is 250 feet when the English measurement system is used with a valid range of 10 to 3280 feet.

If a cell size is entered outside the valid range, the default value for that measurement system will be used.

Search Distance
The search distance is the radius around each cell that is searched for features. The default search distance is 250 meters when the Metric measurement system is set in the OmegaGIS Setup dialog with a valid range of 5 to 4000 meters. The default search distance is 800 feet when the English measurement system is used with a valid range of 15 to 13200 feet.

If the search distance provided is outside the valid range, the default value for that system of measure will be used. Furthering this, the search distance must be 1.5 times greater than the cell size, this is to ensure that the search distance is large enough to include the entire cell. If this is not the case, then the search distance value is automatically increased while the routine is run. The metadata of the hot spot (spatial clustering) map contains information on the cell size and search distance that were used to generate the raster.

Select the Reset button to return to cell size and search distance to the default values. l Options
Two options are available in controlling the placement and look of the new hot spot (spatial clustering) layer.

Show below point and line layers
Use the "Show below point and line layers" checkbox to have the new hot spot layer placed below all point and line layers in the active data frame. By default, the new hot spot layer will be added at the top of the table of contents and may obscure point and line layers below it.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Transparency
The transparency setting can also be used to ensure that points and lines below the new hot spot (spatial clustering) layer will not be obscured. Set the percentage of transparency for the new hot spot layer, where 0% means that the layer is opaque and 100% means that the layer is invisible. This transparency value can also be changed later by using the Display tab in the Layer Properties dialog.

The default transparency value is 20%.

Where?
The Where? tab is used to select boundaries for a spatial query when running the routine. The Where? tab is only enabled when the "Subset by boundary" checkbox is selected on the How? tab. 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 features to include in the spatial query.

When editing a Cyclical Report and 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 a useful when there are no existing boundary layers that can be used to spatially query features.

When editing a Cyclical Report the user defined graphic element will be created on the active data frame and it is 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. This tab is not available in School Planner where it is necessary to create queries on the entire year

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
of student data.

Running the Hot Spot / Spatial Clustering Routine
To create the Hot Spot (Spatial Clustering) layer, click the Finish button. The Finish button is only enabled when all of the parameters for the routine are set. The required parameters for the Hot Spot routine include:
l A Query Layer is set.
l When the "Subset by boundary" option is selected and existing boundary layer is used at least one field value has been selected when the By Field Value selection method is used. When the By Pointing selection method is used, there is no check to ensure that features are selected in the boundary layer until the Finish button is clicked.

An attribute query and a date or time range are not required to run the Hot Spot (Spatial Clustering) routine.

When the Finish button is selected, the routine validates the parameters and then displays a summary dialog. The validation includes checking that there are features selected in the boundary when the By Pointing option is used when subsetting by boundary.

When the boundary type of User-Defined Area is used, the graphic element is checked.

The summary dialog provides an overview of the parameters for the Hot Spot (Spatial Clustering) routine. Use the Back button to return to the query dialog to make edits to the routine. The Save button on the summary dialog allows the routine to be saved as a Cyclical Report.

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.

Date Updated: May 27, 2009
Results of Hot Spot / Spatial Clustering Routine
This section describes the results of the Hot Spot (Spatial Clustering in School Planner) routine and is divided in the following topics:

Results of Routine

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Raster
Hot Spot (Spatial Clustering) Layer
Results of Routine
When the Hot Spot (Spatial Clustering) routine is successfully completed, the following events occur:
l The density dialog shrinks. To maximize the density dialog, double click the icon in the upper right corner. The OmegaGIS Setup dialog has a setting to hide rather than shrink the density dialog. l The extent of the active data frame is changed to the extent of the new Hot Spot (Spatial Clustering) layer plus a 5% buffer. l The Query Layer and any additional query layers that are used to generate the Hot Spot (Spatial Clustering) layer have the following done to them:
¡ Layer has visibility turned off.
¡ The OmegaGIS definition expression is removed from the layer. ¡ The selected features are cleared.
l If a boundary layer is used as a spatial query, the boundary layer has the following done:
¡ The features used in the spatial query will be selected. The "Select features used as boundaries..." option in the OmegaGIS Setup dialog controls this option.
¡ The boundary layer will be visible.

If no features are selected by the Hot Spot (Spatial Clustering) routine, the following events occur:
l The density dialog is maximized.
l A message box reports that the routine can not be completed. If additional query layers are used, the number on the message box reads 7810306 otherwise the number reads 7810439.
l The Query Layer and the additional query layers have their OmegaGIS definition expression removed. l The visibility of the Query Layer will be the same as before running the Hot Spot (Spatial Clustering) routine. If additional

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
query layers were used, all of the layers, including the Query Layer, will not be visible. l The active data frame does not zoom.

Raster
The Hot Spot (Spatial Clustering) routine creates a raster layer. The raster is stored in the "\HotSpot" folder in the project workspace. This raster is permanent and will be automatically deleted from disk when it is no longer referenced by ArcMap by the Omega project clean up routine.

Hot Spot / Spatial Clustering Layer
The Hot Spot (Spatial Clustering) routine adds a layer to the active data frame. The Hot Spot (Spatial Clustering) layer has the following settings:
l Class Breaks
The classified renderer is used with the Jenk's Natural Breaks statistical formula which determines the class breaks used in the legend. While five class breaks are used by default, the number of classes is automatically reduced if the data does not support being broken into five classes.

The label of the class breaks does not use the range of the cell values but rather categories describing the concentration of the features.
l Legend Heading
The heading of the legend in the table of contents states "Concentration of incidents" or "Concentration of Students" in School Planner. The heading may be altered by double clicking the text which makes the text editable.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Color Ramp
The color ramp used with the layer is from the OmegaGIS.STYLE. However, since the lowest class break does not use the color ramp for its symbology, the color ramp displayed on the Symbology tab in the Layer Properties dialog is not the OmegaGIS color ramp.
l Resampling Technique
The Bilinear Interpolation resample technique is used to display the layer since the raster created by the routine contains continuous data. This technique gives a smooth appearance to the data.

About Repeat Calls/Student Concentrations Routine
Availability by Extension
The Repeat Calls / Student Concentrations routine creates a layer that reveals the places with multiple features occurring at the same location. This routine calculates the repeat calls (student concentrations) spatially and does not use any attribute information to determine repeating locations.

There is the ability to register a Crystal Report to a Repeat Calls (Student Concentrations) layer that summarizes the features found at the same location.

CrimeView FireView School Planner
Repeat Calls Repeat Calls Student Concentrations

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The Repeat Calls (Student Concentrations) Identify tool is used to identify the features at a specific location.

Known Issue
There is a known issue with the Repeat Calls routine and migrating to the high precision spatial reference. ArcGIS 9.2 introduced the ability to store coordinates in high precision. Compared to low precision, high precision storage allows one to store coordinates closer together.

When the source query layer is updated to use the high precision spatial reference, the location of existing features does not change.

However, new features that are added to the layer that have the same address as before the update of the spatial reference, may now have a different location. Since the Repeat Calls routine uses the geometry of the features to determine repeat calls locations, the results of the routine may not be accurate after the upgrade in spatial reference.

If this issue is encountered, the only resolution is to import the source query layer again so that features with the same address will share the same location. It is only necessary to update those features that were created in low precision.

Create Repeat Calls / Student Concentrations Layer
There are four tabs available that contain options and settings for creating and displaying a Repeat Calls (Student Concentrations) layer. The tabs included are What?
, How?, Where? and When? The term Repeat Calls is used with CrimeView and FireView, while Student Concentrations is used in School Planner. School Planner does not support the When? tab, as all queries are expected to be made on the full year of student data.

What?

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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 satisfy both the attribute query and date or time range are used to generate the Repeat Calls (Student Concentrations) layer. l Additional Query Layers
Select additional layers that can be included with the Repeat Calls (Student Concentrations) 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.

How?
The How? tab includes settings that control the way in which the Repeat Calls (Student Concentrations) layer is generated and displayed.
l New Layer Name
Enter the name for the new Repeat Calls (Student Concentrations) layer which is used when the layer is added to the active data frame's table of contents.
l Address Field
Select the field from the Query Layer that contains the address or location description. The values in this field are included in the resulting Repeat Calls (Student Concentrations) layer for reference only. The repeat calls (students) are determined spatially, consequently, it does not matter if the Address Field selected has different values in it, such as the different spelling of an address. l Minimum Number
Enter the minimum number of features per location that are to be considered a repeat call (student concentration). The default value is 2 and the valid range is 1 to 5000.
l Top 10 Locations
Select the "Show only top 10 locations" checkbox if only the top 10 locations are to be displayed with the Repeat Calls (Student Concentrations) Layer.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Options
There is one option available in controlling the look of the new Repeat Calls (Student Concentrations) layer.

Transparency
The transparency setting can also be used to ensure that points and lines below the new Repeat Calls (Student Concentrations) layer will not be obscured. Set the percentage of transparency for the new Repeat Calls (Student Concentrations) layer, where 0% means that the layer is opaque and 100% means that the layer is invisible. This transparency value can also be changed later by using the Display tab in the Layer Properties dialog. The default value is 20%.

Where?
The Where? tab is used to select the boundaries used as the spatial query features when running the routine. The Where? tab is only enabled when the "Subset by boundary" checkbox is selected on the How? tab. 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 features to include in the spatial query.

When editing a Cyclical Report and 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 a useful when there are no existing boundary layers that can be used to spatially query features.

When editing a Cyclical Report the user defined graphic element will be created on the active data frame and it is selected. To change the user defined boundary, delete the element and create a new one.

When?

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
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, the When? tab is not available since queries are expected to be made on a full year of student data.

Running the Repeat Calls / Student Concentrations Routine To create the Repeat Calls (Student Concentrations) layer, click the Finish button. The Finish button is only enabled when all of the parameters for the routine are set. The required parameters for the Hot Spot routine include:
l A Query Layer is set.
l When the "Subset by boundary" option has been selected and existing boundary layer is used at least one field value has been selected when the By Field Value selection method is used. When the By Pointing selection method is used, there is no check to ensure that features are selected in the boundary layer until the Finish button is clicked.

An attribute query and a date or time range are not required to run the Repeat Calls (Student Concentrations) routine.

When the Finish button is selected, the routine validates the parameters and then displays a summary dialog. The validation includes checking that there are features selected in the boundary when the By Pointing option is used when subsetting by boundary.

When the boundary type of User-Defined Area is used, the graphic element is checked.

The summary dialog provides an overview of the parameters for the Repeat Calls (Student Concentrations) routine. Use the Back button to return to the query dialog to make edits to the routine. The Save button on the summary dialog allows the routine to be saved as a Cyclical Report
.

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 Repeat Calls / Student Concentrations
Routine
This section describes the results of the Repeat Calls (Student Concentrations in School Planner) routine and is divided into the

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
following topics:

Results of Routine
RepeatCalls.MDB
Repeat Calls / Student Concentrations Layer
Results of Routine
When the Repeat Calls (Student Concentrations) routine is successfully completed, the following events occur:
l The density dialog shrinks. To maximize the density dialog, double click the icon in the upper right corner. The OmegaGIS Setup dialog has a setting to hide rather than shrink the density dialog. l The extent of the active data frame is changed to the extent of repeat call (student concentration) locations that are displayed plus a 5% buffer. If the there is a spatial query, the active data frame zooms to the extent of the selected boundary features. l The Query Layer and any additional query layers that are used to generate the Repeat Calls (Student Concentrations) layer have the following done to them:
¡ Layer has visibility turned off.
¡ The OmegaGIS definition expression is removed from the layer. ¡ The selected features are cleared.
l If a boundary layer is used as a spatial query, the boundary layer has the following done:
¡ The features used in the spatial query are selected. The "Select features used as boundaries..." option in the OmegaGIS Setup dialog controls this option.
¡ The boundary layer is visible.
l If the Repeat Calls Identify tool is the active tool in ArcMap then Select Elements tool is made the active tool.

If no features are selected by the Repeat Calls (Student Concentrations) routine, the following events occur:
l The query dialog is maximized.
l A message box reports that the routine can not be completed. If additional query layers are used, the number on the message

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
box reads 7810306 otherwise the number reads 7810439.
l The Query Layer and the additional query layers have their OmegaGIS definition expression removed. l The visibility of the Query Layer reverts to its state before running the Repeat Calls (Student Concentrations) routine. If additional query layers were used all of the layers, including the Query Layer, will not be visible. l The active data frame does not zoom.

RepeatCalls.MDB
During the running of the routine, a new feature class is generated in a personal Geodatabase. The Repeat Calls (Student Concentrations) layer is based on this feature class.
l The Geodatabase is named RepeatCalls.MDB and is located in the "\Density" folder in the project workspace. l The RepeatCalls.MDB is created dynamically by the Repeat Calls (Student Concentrations) routine. If the Geodatabase is not present it will be created when the Repeat Calls (Student Concentrations) routine is run. l When the routine runs, different feature classes are created in the RepeatCalls.MDB.

RepeatCalls_*
This feature class with the geometry type of multi-point is displayed in ArcMap as the Repeat Calls (Student Concentrations) layer.

The "CNT_OmegaGIS_XY" field contains the count of the features at that location, this field name alias is "Incident_Count" in the Repeat Calls (Student Concentrations) layer. The "FIRST_< Name of Address Field>" field contains the value from the Address field that is identified on the How? tab. The field name alias for this field is "Address" in the Repeat Calls (Student Concentrations) layer. The feature class is deleted when it is no longer referenced in the ArcMap document.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
RC_AddLayers_*
This feature class is created when additional query layers are used and contains all of the features from the different layers that are used when determining repeat calls (student concentrations). This feature class is used with the Repeat Calls (Student Concentrations) Report and the Repeat Calls (Student Concentrations) Identify tool. The RC_AddLayers_* feature class is only deleted when the "RepeatCalls_*" that was created from it is removed from the ArcMap document.

RC_Temp
This feature class is created when there is only one Query Layer. This feature class contains all of the features to be used when determining repeat calls (student concentrations. The feature class is deleted during the OmegaGIS Project Exit and when a new Repeat Calls (Student Concentrations) routine is run.

Tip:
l To permanently persist the feature class created from a density routine, export the feature class to a different personal Geodatabase.

Repeat Calls / Student Concentrations Layer
The Repeat Calls (Student Concentrations) routine adds a layer to the active data frame whose data source is from a RepeatCalls_* feature class in the RepeatCalls.MDB. The Repeat Calls (Student Concentrations) layer has the following properties:
l Graduated Symbol
The graduated symbol renderer is used with the Repeat Calls (Student Concentrations) layer. The size of the symbol changes based on the number of repeat calls (students) for the location.

Top Ten
When the top ten locations are displayed, the legend will have ten class breaks. The manual classification is used to determine the class breaks. There could be more than ten features in the Repeat Calls (Student Concentrations) layer as two separate locations may have the same number of repeat calls (students). There may also be fewer than ten class breaks if there are less then ten unique repeat call (student) values based on the minimum number of features per location.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Display All Repeat Calls (Student Concentrations)
When the top ten locations are not being displayed but rather all of the locations that have repeat calls (students), the Jenk's Natural Breaks statistical formula is used to inspect the data and determine the class breaks. This method attempts to minimize the variance within the class and to maximize the variance between the classes. Five class breaks are used. l Legend Heading
The legend heading will report "Top ten locations" when the top ten option was selected on the How? tab. If the there were fewer then ten repeat call (repeat student) locations, the legend heading will be altered to state the number of repeat call (student) locations. The heading can be altered by double-clicking the text which makes the text editable.

There will be no legend heading if all of the repeat calls (student) locations are displayed. l Collapsed Legend
When there are more than five class breaks, the legend will be collapsed in the table of contents. To expand the legend click the plus icon to the left of the Repeat Calls (Student Concentrations) layer name. l Definition Expression
A definition expression limits the features that are displayed to those that satisfy an attribute query. The RepeatCalls_* feature class contains all of the locations that satisfied the attribute and spatial query and the definition expression is used to limit the Repeat Calls (Student Concentrations) layer to those locations that have a minimum number of features.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Primary Display Field
The primary display field is used with the ArcMap Identify tool. The value of the field is shown on the right side of the Identify Results dialog rather than scrolling through the list of field values. The address field is set as the primary display field.
l Label
The address field is set to the label field of the Repeat Calls (Student Concentrations) layer.

Repeat Calls / Student Concentrations Identify Tool
Availability by Extension
The Repeat Calls / Student Concentrations Identify tool is used to retrieve information about the original features that made up a particular repeat call (student concentration) location. The tool is available when any OmegaGIS extension is enabled.

Active Repeat Calls / Student Concentrations Identify Tool To make the Repeat Calls / Student Concentrations Identify tool active, select the tool from the CrimeView, FireView or School Planner toolbar.

If there are multiple Repeat Calls (Student Concentrations) layers in the active data frame, a dialog will open with a list of Repeat Calls (Student Concentrations) layers. Select the Repeat Calls (Student Concentrations) layer to select features from and select OK.

CrimeView FireView School Planner
Repeat Calls Identify Repeat Calls Identify Student Concentrations Identify

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
If there is only one Repeat Calls (Student Concentrations) layer, the tool will become active.

When the Repeat Calls / Student Concentrations Identify tool is active, the Repeat Calls (Student Concentrations) layer becomes visible. The mouse also changes to a pointer with a red letter "R" beside it when placed over the active data frame.

Identify Repeat Calls / Student Concentrations
To retrieve information about the original featurse that made up the repeat calls (student concentrations), with the Repeat Calls / Student Concentrations Identify tool active, select the center of the repeat calls (student concentrations) location. The tool uses the ArcMap snapping tolerance for selecting locations. When a location is selected by the tool, an attribute table will open with the features that made up that repeat calls (student concentrations) location selected.

The original Query Layer must be in the active data frame and have the same name as when the Repeat Calls (Student Concentrations) layer was created for the identify to work. If the Query Layer cannot be found there is a message box (12505) and the Repeat Calls / Student Concentrations Identify tool will not longer be the active tool.

When additional query layers are used to create the Repeat Calls (Student Concentrations) layer, the RC_AddQueryLayers_* feature class in the RepeatCalls.MDB is used as the source of the original features.

Map Navigation
In ArcMap, only one tool may be active at any one time. Consequently, when the zoom or pan tools are used the Repeat Calls / Student Concentrations Identify tool will no longer be active. Below are two suggested map navigation options that keeps the Repeat Calls / Student Concentrations Identify tool active:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
l Use the ArcMap Magnification dialog which is available from the Windows pull-down menu in ArcMap. The Repeat Calls / Student Concentrations Identify tool works inside of this window. l Use the scroll bars on the active data frame to pan to different locations.

About Exception Reporting / Enrollment Comparison
Availability by Extension
Exception Reporting and Enrollment Comparison are based on the concept of comparing information from different periods in time in order to view trends in the data. Exception Reporting is available with CrimeView and FireView software products. In this case, Exception Reporting compares the number of incidents occurring over time in order to determine whether the area under observation has experienced stability, increasing or decreasing trends in activity.

Available with School Planner, Enrollment Comparison in the same way focuses on trends in the data, but in this case, examines the differences in student populations over time. Unlike Exception Reporting, Enrollment Comparison bases the analysis on the full year of student data. Exception Reporting has the functionality to select specific periods of time throughout the year.

Map Layer
The result of running an Exception Report or Enrollment Comparison is a new map layer that identifies the increase, decrease or stability of the data by geographic boundary.

CrimeView FireView School Planner
Exception Reporting Exception Reporting Enrollment Comparison

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
To calculate the change in the number of incidents (or students) that have occurred over time, there must be a historical record of the incidents (students) in question. If no incidents (students) are found in the previous layer based on the query run with the analysis, the percent change cannot be calculated. The change in the number of incidents (or students) is calculated as:
(Current Data/ Previous Data – 1) * 100
As this equation is not divisible by zero, the data count from the historic layer must be included in the calculation to proceed.

In cases where the count for previous incidents or students for an area is zero, the percent change is given a value of No Data.

Map Legend
The change in incidents (students) over time is identified by classifying the increase or decrease into different thresholds of percent change. Based on the analysis run, these classifications vary due to the fact that the change in students over time is usually on a much smaller scale than that found for incidents of crime or fire.

The divisions for Exception Reporting are as follows:

The divisions for Enrollment Comparison are as follows:

Map Results
Legend Value Legend Description
-100 to -50 Considerable Decrease
-50 to -10 Decrease
-10 to +10 Stable
+10 to +50 Increase
+50 to +100 Considerable Increase
100 to 10000 Problem Area
NO DATA No crimes occurred initially
Legend Value Legend Description
-6 to -3 Considerable Decrease
-3 to -1 Decrease
-1 to +1 Stable
+1 to +3 Increase
+3 to +6 Considerable Increase
6 to 100 Problem Area
NO DATA No historic students found

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
When an Exception Report or Enrollment Comparison is run, a new layer is generated and placed in the ArcMap table of contents. The new layer is based on the total number of incidents (or students) involved in the query. As there is a 10,000 percent increase cap on the incident data (100 percent increase in the case of students), those areas exceeding this value will not show up in the new layer. To view these areas, open the properties dialog of the layer, and increase the upper limit of the 'Problem Area' to the maximum found in the new layer.

Report Results
In addition to the new layer created by the analysis, a Crystal Report is generated. The report is based on a template that is provided with the software installation, and can be found in the \reports folder. The format of this report can be modified however, the data should not be altered as it is based on the standardized output of the Exception Reporting / Enrollment Comparison analysis.

Exception Reporting / Enrollment Comparison Setup
Exception reporting (Enrollment Comparison) is a comparison between historical and current data. The routine enables the identification of changes in the data within a geographic area. In order for layers to become available to the Exception Reporting (Enrollment Comparison) routine there are several options that should be set prior to using the utility.

Setting Up Layers
Saved Queries
Reporting
Field Schema

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Maximizing Performance
Setting up Layers
Current Layers
Two layer lists exist on the What? tab (Current Layers and Previous Layers) that provide the basis for comparing historic to more current data. By selecting a Current Layer, the Previous Layer list box is populated with layers that meet specific requirements based on the Current Layer selected.

The Current Layer in the analysis, represents the layer that is compared to historical events in order to determine changes that have occurred over time. To appear in the list, the Current Layer must have a geometry type of point. Multipoint layers are not supported. The data source of the layer must be valid. If the data source is invalid, a red exclamation mark appears at the left hand side of the layer name in the map table of contents.

Selection layers are not included in the layer list. Selection layers are created as a result of running OmegaGIS routines.

Selection layers share the same data as the layer on which they were based during the query. Consequently, including these layers in the layer list, essentially results in displaying duplicate data.

Often a project can become confusing when many different layers exist within the map from which to query. To narrow down the list of layers that may be displayed in the layer list, two options can be set using Setup . The first option deals with the
use of registered layers. As layers are created, they can be registered as different types using the OmegaGIS Metadata Editor in ArcCatalog . Once registered, the setting 'Only use registered layers to create new queries' within the Queries category in Setup can be toggled to display only those layers registered as a specific type.

To limit the layer list further, those layers created by OmegaGIS routines may be excluded from the list explicitly using the 'Exclude layers...' checkbox on the Advanced tab of the Queries category. Setting this option ensures that layers created by any of the OmegaGIS routines cannot be selected.

Previous Layers
Previous Query Layers are point layers used as the historical comparison to the Current Layer. The list is populated based on the Current Layer selected. The Current Layer is included in the list so that comparisons can be made using date ranges within the same layer. Previous Layers are only available to those Current Layers that share the same Query Groups and field list. However, they may include additional fields not found in the Current Layer.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Saved Queries
The Saved Queries database ( Omega_Query.odb ) is an extremely important component of any OmegaGIS project. The database stores common queries that will be used frequently to query the available datasets . This database is usually compiled at the beginning of a project, in a combined effort between the Omega Project Manager and the Client. Queries that will be used frequently to analyze data are identified and added to the database using the Omega Query Editor so that they may be accessed from OmegaGIS routines.

Most OmegaGIS routines display saved queries within a Saved Queries Tree or Column view on the What? tab of the dialog.

Exception Reporting (Enrollment Comparison) is slightly different in that the Saved Query Tree or Column view is accessed through the 'Add' button on the What? tab. As each Saved Query is added to the active project, the name of the saved query is added to the 'Queries' list on the What? tab.

Since the Current and Previous Layers must share the same Query Groups if they are to be compared, the Query Groups must be registered to both layers. A Query Group is simply a container for all of the related queries collected within it. The Query Group can be recognized as the root folder(s ) in the Saved Query Tree. The OmegaGIS Metadata Editor can be used to register the Query Groups to the appropriate layers.

Reporting
The Exception Report is a Crystal Report that has been customized to work with the Exception Reporting routine. A template for this report can be found in the <installation folder>\OmegaGroup\Desktop\Reports folder called Exception.rpt. The report can be modified in format and fields in order to display additional information. The original fields however, should not be altered as they are based on standardized data output from the routine.

When the report has been customized, it can be placed in any folder, as long as the path to that folder is referenced in the Locations Category for Crystal Reports in Setup. The report name should not be changed however, as it is searched for by name in the Exception Reporting routine.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Field Schema
A field schema refers to the fields that make up a layer's dataset. Each field is defined by field characteristics such as a field name, data type, precision etc. In order to compare Current and Previous layers, the Current Layer must contain all of the fields contained within the Previous Layer, as well as retain the same field characteristics as that of the Previous Layer.

Maximizing Performance
Sample Rate
The exception report (enrollment comparison) and map generated by the analysis, may be limited to specific geographic regions by selecting polygon field values available on the dialog. When using layers with a large number of geographic boundaries, the field value list may become quite long and difficult to update and navigate, and thereby impede performance.

To assist in performance, a sample rate can be set to limit the number of polygons that are used to create the unique field values list. The sample rate is accessed through Setup
.

Maximum Unique Values
The maximum unique values setting in Setup is also useful in gaining performance when dealing with layers with many boundaries. The maximum unique values setting identifies the maximum number of unique field values that may be displayed in the field value drop-down list. If the maximum number is hit, a warning message is displayed next to the list to indicate that not all values are displayed.

Exception Reporting / Enrollment Comparison Menus

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The Exception Reporting and Enrollment Comparison Menus are identical with the exception of the When? tab. The When? tab is absent from the Enrollment Comparison analysis, as student population comparisons are always created on the entire student year. The following sections identify the What?, Where? and When? tabs, and describe the choices that are available on each.

What?
Where?
When?
What
The What? tab includes the ability to select from available current and historic data layers of interest. Previous layers (or historic layers) are included in the dropdown list based on the layer selected from the Current Layer list box. For a description of the way in which the Previous layers are updated, read the Reporting Setup section.

Below these layer choices, the New Layer Name textbox can be used to enter a name that will appear in the ArcMap table of contents once the analysis is complete and the map layer has been added to the active view.

Queries
Queries are created by accessing Saved Queries available to the Previous and Current layers. A query may be added, edited or removed from an Exception Report (Enrollment Comparison) analysis. Each query represents a category that may be viewed by the Exception Report (Enrollment Comparison) Viewer. On completion of an Exception Reporting (Enrollment Comparison) routine, the initial map and report generated are based on the total number of data points selected using all of the queries in the list.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Query Selection
Queries may be composed of one or more saved queries. Saved queries are created during the installation of the project, and are stored in one or more Saved Queries databases. The syntax of the Saved queries may not be edited within the Exception Reporting (Enrollment Comparison) analysis menu, however, queries, which are the combination of the saved queries may be modified or updated.

Where
The Where? tab controls from which geographic boundaries the data points are selected to complete the analysis. A boundary layer is selected from a list available on the dialog. To narrow down the analysis to a specific geographic region, individual boundaries within the layer may be selected by choosing a field value on the menu, or by interactively pointing to boundaries on the map.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Performance
Two settings are available in Setup that boost performance when populating the field value list box. These settings influence performance by limiting the number of unique values displayed. They are important when using very large data sets, where populating the list box may impede performance.

The sample rate setting identifies how many features will be used to retrieve unique field values from the boundary layer. The maximum unique value option determines the number of unique values that can be displayed in the list box. The Complete List button below the field values list box on the dialog can be used to sample all of the features in the layer to create the unique values list. If the maximum number of unique values exceeds the limit set in Setup, a warning message appears on the dialog, indicating that all field values are not displayed.

When
The When? tab displays a summary of date and time range information for both the Previous and Current layers. To change the date settings for either of these layers, use the 'Modify Date Range' buttons to open a DateTime dialog. Remember that this tab is only available with Exception Reporting in CrimeView and FireView as Enrollment Comparisons are always performed on a full year of student data in School Planner.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
From Date & To Date
The From and To Date calendars set the date range from which incidents are selected for the analysis. Dates falling outside the available date range are colored grey.

Hovering over the From Date or To Date text displays the date field on which the calendars are based. If multiple OmegaGIS Date fields exist in the layer, the Options button may be used to modify the date used by the calendars.

From Time & To Time
From Time and To Time are available to limit the incidents included in the routine to a specific range.

Note: A date and time range of March 1st to March 5th from 1:00pm to 6:00pm indicates that incidents from the 1st to the 5th of March that occurred between the hours of 1 and 6 pm will be included in the analysis.

Previous Range
The Previous Range is available in order to select a date duration. Select the number of hours, days, weeks, months or years

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
from the drop-down lists available, and the From and To Date calendars are set automatically. * It is important to note that the duration represents the last complete block of dates. For instance, given that the current date is December 9th, a previous duration of 1 month returns the dates between November 1st and November 30th. The dates between December 1st and the 9th are excluded as they are not a part of a complete month.

Predefined Date Range & Predefined Time Range
Four predefined date ranges are available for use which include Today, Week To Date, Month To Date and Year To Date.

Predefined time ranges include Day (6am to 6pm) and Night (6pm to 6am). Additional date and time ranges may be created using the Organize button on the dialog. Date and time ranges can be entered and are saved to the Settings.MDB so that they may be used again in future analyses.

Day of Week
If a Day of Week field is available in the data, incidents included in the analysis may be limited to specific days of the week.

Options
The fields on which date and time ranges are based may be selected using the Options button. To change the default date and time fields permanently, use the OmegaGIS Metadata Editor <LINK> available within the OmegaGIS Data Manager extension in ArcCatalog.

Exception Report Viewer / Enrollment Comparison Viewer
The Exception Report Viewer, also known as the Enrollment Comparison Viewer in School Planner, displays the results of

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Exception Reporting (Enrollment Comparison). When an analysis is run using one of these routines, it is possible to create multiple queries that display different aspects of the data.

For example, in Exception Reporting, several queries might be included to reveal different incident types that have occurred.

In the case of Enrollment Comparison, queries may be designed to view the number of students enrolled in different grades.

When the Exception Report (Enrollment Comparison) results are generated, the results are based on the total number of incidents or students generated by all of the queries. The Viewer tool creates the ability to view the individual queries involved in the analysis.

On opening the Viewer, a list of available reports that have been generated by the Exception Report / Enrollment Comparison tool is displayed in the Reports list box. After selecting a report to view, metadata describing the report, and a list of queries that were used in generating the report is populated.

After selecting a query, and entering a name for the new layer that will be generated, clicking 'Finish' creates the new map layer. The transparency and placement of the new layer in the ArcMap table of contents can be modified using the Advanced button.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
In addition to creating a map, a report can be generated by clicking on the 'View Report' checkbox. The report summarizes the data for each query used in the routine. In order to display the report, the report template called Exception.rpt MUST be located in the project's \reports folder.

Exception Report Data
Exception Report data is stored within the ExceptionData.MDB geodatabase located in the Project Workspace \Analyses folder. The feature classes and tables stored within the geodatabase are automatically deleted when the project is closed, as long as they are not found in the map table of contents. In order to manually delete a layer from the Exception Reports list box on the dialog, the layer must be removed from the geodatabase.

Within the geodatabase, the data associated with the exception reporting layer is divided into a feature class and a table. The link between the feature class and table can be identified by the number within the filename. To identify the report name found in the exception report view list box, the metadata tag /theomegagroup/exceptionreporting/reportname can be viewed from the metadata tab in ArcCatalog.

Deleting Exception Reporting Data
In general it is not a good idea to manually remove the exception reporting data from the geodatabase. Deleting the unused feature classes and associated tables from the geodatabase can be accomplished using Setup. In the General category, click the 'Apply Project Cleanup' on the General Tab. The 'Apply Project Cleanup' button removes any OmegaGIS files that are not currently used in the project. Consequently, it clears the ExceptionData.mdb of all unused files when applied.

About Crime Rate Generator / Demographic Analysis
Crime Rate Generator and Demographic Analysis are very similar in design and in how they process data to create statistical results. Crime Rate Generator is available with CrimeView while Demographic Analysis is accessible using School Planner. Due to the similarity in the nature of their design, they are both described below. Where there is variation in the parameters required by the routine, or the results generated, these items are identified.

Availability by Extension

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Crime Rate Generator
Crime rates are used to tie demographic characteristics to crime data. Crime Rate Generator provides an easy method for creating thematic maps used to view and analyze crime rates. Crime rates are calculated by dividing the number of incidents within a given boundary by the population count. The equation used in calculating crime rates is defined below:

Crime Rate = (Incidents / Population) * Constant
The constant in the above equation may vary between 100 and 100,000, and is used to create meaningful crime rate statistics dependent on the size of the population. For instance in a town of 8,000, with the number of crime incidents totaling 500, using a constant of 1,000 results in a crime rate of 62.5 crimes per 1,000 people. A constant of 100,000 (crimes per 100,000 persons) is typically used to compare crime rates for much larger areas such as between states or countries.

Crime rate results are displayed in a thematic map, which is added to the data frame of the current ArcGIS project.

Crime Rate Generator is available from ArcMap when both incident and census layers can be found within the active data frame.

Considerations in calculating crime rate statistics begin with ensuring that comparative analyses use similar durations. For instance, a crime rate calculation based on a yearly sampling of data, is not suitable for a comparison of monthly data. In addition, when looking at different neighborhood types, crime rates may appear unusually high. For instance, a commercially zoned neighborhood may indicate abnormally high crime rates, due to a low residential population. An understanding of the spatial and temporal information used in any analysis is important when attempting to produce meaningful results.

Crime Rate Generator Results
CrimeView FireView School Planner
Crime Rate Generator Not Available Demographic Analysis

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The result of a Crime Rate Generator routine is a new layer and report that identify the crime rate statistics for geographic regions. The new Crime Rate layer is displayed on the map, while the data source of the layer is stored in a database called CrimeRateData.mdb in the project \Census folder. When the ArcMap project is closed, any crime rate layers that are not saved in the map table of contents are deleted automatically from the database.

Running the Crime Rate Generator Routine
In order to run Crime Rate Generator, layers with point type geometry must exist in the table of contents. These layers should contain the incident data used in the analysis. In addition, census layers must exist in the map table of contents and are identified using metadata tags associated with the layer. These tags are generated automatically when the Omega Demographic Data Loader is used to create the data. However, the OmegaGIS Metadata Editor may also be used to register the layers as census layers. Once census layers are created, they may be stored as shapefiles, in a personal geodatabase or as ArcSDE layers.

Demographic Analysis
Demographic Analysis is an excellent tool for calculating student generation rates based on school zones. A student layer is selected, and then compared against the number of housing units found in a particular school zone. In addition, this tool can be used to generate population statistics to compare the number of students queried with census data available for any block, blockgroup or tract in the school district.

Demographic Analysis Results
The result of a Demographic Analysis is a new map layer and report that identify either the student generation rates for a particular school zone, or student statistics compared against the available census data. The new Demographic Analysis layer is displayed on the map, while the data source of the layer is stored in a personal geodatabase called StudentData.mdb in the project \Census folder.

When the ArcMap project is closed, any layers generated by this analysis that have not been saved with the project, will be removed automatically from the map, and deleted from the source database.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Running the Demographic Analysis Routine
To run a Demographic Analysis, layers with point type geometry representing the students for each school year must exist in the table of contents. In addition, census layers must exist in the table of contents. Census layers are identified using metadata tags associated with the layer. The tags are generated automatically when the Omega Demographic Data Loader in ArcCatalog is used to create the data. However, the OmegaGIS Metadata Editor may also be used to register the layers and set the appropriate metadata tags. Once census layers are created, they may be stored as shapefiles, in a personal geodatabase or as ArcSDE layers.

Crime Rate Generator / Demographic Analysis Setup
Both Crime Rate Generator and Demographic Analysis are designed to provide an easy method for comparing incident or student data found within geographic boundaries to census data available for the region. These tools were designed to use census data downloaded from the ESRI
website as the demographic component, however, it is possible to use other sources of census information provided the data conforms to the requirements set by the routines. The following sections outline the work flow for creating meaningful statistical results using these analytical tools.

Assemble the Census Personal Geodatabase
Create Saved Queries
Register Query Groups to Layers
Set Table of Contents
Assemble the Census Personal Geodatabase
Crime Rate Generator and Demographic Analysis use census data to produce statistical results. In other OmegaGIS routines that provide the option to select areas geographically, any polygon layer found in the table of contents is available to delineate the spatial extent of the query. These two routines however, are based solely on census boundary layers. Census tracts, block groups and blocks are the only boundaries that may be used to calculate statistics.

Census data is available on the ESRI website , and once downloaded can be compiled using the OmegaGIS Demographic Data Loader. This utility is available on the Omega Data Manager extension in ArcCatalog . For a description of how to obtain the data as well as create the census boundary layers, read the information pertaining to the OmegaGIS Demographic Data Loader. In using sources of census information outside of ESRI, the data must be provided as a shapefile, personal geodatabase feature class or ArcSDE layer. Each census layer must be registered using the OmegaGIS Metadata Editor with a layer type of 'Census_Tract', 'Census_Blockgroup' or 'Census_Block'.

Accessing Crime Rate Generator or Demographic Analysis requires that the census data adhere to the rules mentioned above.

If the data does not exist in this format, a warning is issued when trying to open the routine dialog. The OmegaGIS Demographic Data Loader provided, formats the data automatically so that it is ready for these routines.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Create Saved Queries
Saved Queries are essentially stored queries that can be accessed by OmegaGIS routines, including Crime Rate Generator and Demographic Analysis. When designing a project, the queries that will be used frequently on the data are identified, and saved. Each Saved Query provides an intuitive description to the user on the dialog, while behind the scenes storing the SQL syntax required by the source database. Saved Queries may be displayed as a tree view or alternatively in a column view.

These options are available using OmegaGIS Setup.

For detailed information on this topic see Saved Queries.

Register Query Groups to Layers
Query Groups must be linked to the appropriate layers in order to display the Saved Queries contained within the Group on the dialog. Before Crime Rate Generator or Demographic Analysis will display the Query Groups related to the layer, they must be registered using the OmegaGIS Metadata Editor. The Metadata Editor is provided as a component of the Omega Data Manager extension in ArcCatalog . Once registered, these routines have access to any of the Saved Queries found within the registered Query Group.

Set Table of Contents

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The last stage in accessing Crime Rate Generator or Demographic Analysis is to ensure that the data required for querying crime statistics or student statistics and the census data is located within the table of contents in ArcMap . If either the crime/student data or the census boundary layer information is missing, a warning message is issued that Crime Rate Generator or Demographic Analysis is unavailable.

Crime Rate Generator / Demographic Analysis Menus
Three tabs, What?, How?, Where? contain the options and settings necessary for calculating and displaying the results of Crime Rate Generator or Demographic Analysis. A fourth tab When? is available to Crime Rate Generator only. The questions that must be answered in order to fill in the parameters of the analysis include: Which incidents or students are to be selected for the analysis? How are the results to be displayed on the map? From which geographic areas are the incidents or students to be selected? and for Crime Rate Generator; Within what time frame should the incidents have occurred? What? Tab
How? Tab
Where? Tab
When? Tab
What?
The settings on the What? tab are used to identify the incidents or students of interest. A layer must be picked from the Query Layer list. The incidents or students may be narrowed down further by selecting a query from the Saved Queries Tree (or saved Queries Columns). Only those features matching the criteria of the saved query are used in generating the statistics. A saved query may also be modified using the 'Edit Query' button on the dialog.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
In order for layers to show up in the Query Layer list, the data source must be valid, and the layer must have a geometry type of point. Additionally, if the 'Use registered type...' setting is checked in OmegaGIS Setup, then only those registered types selected will be shown in the layer list.

How?
Statistics
The How? tab includes settings that control the way in which the map is displayed, as well how the statistics are calculated. The Census boundary layers are used to geographically group data for statistical calculations. The population field identifies the attribute within the census layer that will be used to calculate statistics.

With Crime Rate Generator, calculating crime rates is accomplished using the following equation: Crime Rate = Incidents / Population) * Constant
With Demographic Analysis, the same calculation can be used (Students / Population) however, in this case the option for the constant is not necessary, and it is not available on the dialog. In addition to comparing student populations to general populations, using housing units in the equation allows for the calculation of Student Generation Rates. A Student Generation Rate is calculated by selecting the housing unit field available in the census data instead of the population field; so that the equation becomes (Students / Housing Units).

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Layer Display
Several settings are available to modify the look of the new layer. The color ramp provides several color options for displaying the resultant data. Color ramps are found in the OmegaGIS.STYLE file.

The name of the layer can be edited in the 'New Layer Name' text box.

Options
Show Below Point and Line Layers
Use the Show Below Point and Line Layers checkbox to have the new layer placed below all layers that have point and line geometry in the active data frame. By default, the new layer is added at the top of the table of contents and may obscure point or line layers below it.

Show Report
Each census layer (tracts, blockgroups or blocks) has a report template that is provided within the Omega Desktop installation folder. These reports can be found within the \omegagroup\desktop\reports folder, and can be customized and placed anywhere on disk. If the reports are placed in a location other than the project workspace's \report folder, the location must be identified in Omega Setup within the Locations category for reports.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Population Constant (available with Crime Rate Generator only) The constant in the crime rate equation may vary between 100 and 100,000, and is used to create meaningful crime rate statistics dependent on the size of the population. For instance in a town of 8,000, with the number of crime incidents totaling 500, using a constant of 1,000 results in a crime rate of 62.5 crimes per 1,000 people. A constant of 100,000 (crimes per 100,000 persons) is typically used to compare crime rates for much larger areas such as between states or counties.

Transparency
Transparency can be set to prevent the new layer from obscuring features in the layers below. Default values fall between 0 and 100, where 100 results in an invisible layer, and 0 is opaque. The default value is set at 20, allowing features below the new layer to remain visible. The transparency of the new layer may also be altered by using the Display tab in the Layer Properties dialog.

Where?
The Where? tab provides options to narrow down the number of polygons selected from the census layer on which to perform the calculations. Polygons may be selected by using the unique field values found in the layer or, alternatively, by pointing to the polygons on screen. Limiting the number of polygons involved in the statistical calculations improves the overall performance of the query.

Field Value

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
To use the Field Value selection method, click on the Field Value radio button, then select from a list of field names in the Field Name list. Once a field name is selected, the field values available are updated and can be selected.

Complete List
The Complete List button at the bottom of the field values list box controls the number of field values that are added to the list. Within OmegaGIS Setup there are two important settings that control the field values list box. On the Advanced Tab of the General Settings category, the 'Number of Records used...' setting controls the number of polygons that are sampled in the boundary layer to get the unique list of values. The 'Number of records to display...' setting identifies how many of these unique values are displayed in the field values list. The complete list button ensures that all polygons in the boundary layer are sampled. If the number of unique values exceeds the value of the setting in Setup, a warning is displayed beside the list box.

By Pointing
The By Pointing method of polygon selection provides a means to selecting boundaries geographically. Click on the By Pointing radio button, then click the ellipses button (...). The routine dialog shrinks, and pauses while polygons are selected.

When finished, click on the flashing icon in the top right corner to maximize the dialog.

When? (only available with Crime Rate Generator)
The When? tab displays a Date-Time dialog that can be used to select data from a specific date range. The dialog is common to most OmegaGIS routines. This tab is excluded from the Demographic Analysis routine as student statistics should be generated on the student data for the entire year.

From Date & To Date
The From and To Date calendars set the date range from which incidents are selected for the analysis. Dates falling outside the available date range are colored gray.

Hovering over the From Date or To Date text displays the date field on which the calendars are based. If multiple OmegaGIS Date fields exist in the layer, the Options button may be used to modify the date used by the calendars.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
From Time & To Time
From Time and To Time are available to limit the incidents included in the routine to a specific range.

Note: A date and time range of March 1st to March 5th from 1:00pm to 6:00pm indicates that crimes from the 1st to the 5th of March that occurred between the hours of 1 and 6 pm will be included in the analysis.

Previous Range
The Previous Range is available in order to select a date duration. Select the number of hours, days, weeks, months or years from the drop-down lists available, and the From and To Date calendars are set automatically. * It is important to note that the duration represents the last complete block of dates. For instance, given that the current date is December 9th, a previous duration of 1 month returns the dates between November 1st and November 30th. The dates between December 1st and the 9th are excluded as they are not a part of a complete month.

Predefined Date Range & Predefined Time Range
Four predefined date ranges are available for use which include Today, Week To Date, Month To Date and Year To Date.

Predefined time ranges include Day (6am to 6pm) and Night (6pm to 6am). Additional date and time ranges may be created using the Organize button on the dialog. Date and time ranges can be entered and are saved to the Settings.MDB so that they may be used again in future analyses.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Day of Week
If a Day of Week field is available in the data, incidents included in the analysis may be limited to specific days of the week.

Options
The fields on which date and time ranges are based may be selected using the Options button. To change the default date and time fields permanently, use the OmegaGIS Metadata Editor available within the OmegaGIS Data Manager extension in ArcCatalog.

About Spatial Trend Analysis
Availability by Extension
Spatial Trend Analysis is available in all of the products created by Omega, and can be used to look at changes in data that occur over time. In CrimeView, Spatial Trend Analysis can be used to identify whether the number of incidents in an area has increased or decreased. In FireView, the routine might be used to visually examine changes in the number of false alarms and false calls. Alternatively, in School Planner the analysis might provide a means to view whether student populations have increased or decreased over the years.

Although similar to Exception Reporting
(Enrollment Comparison in School Planner) in that the result of the analysis is a comparison of historical data, Spatial Trend Analysis provides a few important differences. Spatial Trend Analysis is not limited to comparing a single layer of events. Multiple historical layers may be selected as the basis for evaluation, as well as specifying date and time ranges for each individual layer.

CrimeView FireView School Planner
Spatial Trend Analysis Spatial Trend Analysis Spatial Trend Analysis

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The quantitative results of Spatial Trend Analysis differ from Exception Reporting (Enrollment Comparison in School Planner) in that they are raster based as opposed to vector based. Changes in the data are compared cell by cell, and then interpolated to create contoured areas of change. Comparing events in this manner targets change, and does not stretch the results to the selected boundaries, as is the case when using the vector approach with Exception Reporting (Enrollment Comparison). Unlike the percentage results of Exception Reporting (Enrollment Comparison), Spatial Trend Analysis displays the output as classes of relative change based on the cell by cell calculations. The results create smooth relative changes calculated by the following expression:
[Target Layer Raster ] - Average [Historic Layer1...Historic Layern ] / n Spatial Trend Setup
Extension Requirements
Spatial Trend Analysis is based on cell by cell calculations using raster layers. In order to perform these calculations, ESRI's Spatial Analyst Extension must be installed on the machine running the analysis, and the extension must be enabled. To check whether the extension is installed, click on the 'Tools' menu in ArcMap, and select 'Extensions' from the drop-down list.

Spatial Analyst is shown in the list of extensions if it is available, and may be enabled by clicking on the checkbox.

In addition to Spatial Trend analysis, a few OmegaGIS routines require extensions supplied by ESRI. These extensions must be installed manually, however once on the machine, they can be enabled automatically by toggling a Global Setting in OmegaGIS Setup.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Analysis Requirements
Target Layer
The target layer in the analysis, represents the layer that is compared to historical events in order to determine changes that have occurred over time. To appear in the list, the target layer must have a geometry type of point. Multipoint layers are not supported. The data source of the layer must be valid. If the data source is invalid, a red exclamation mark appears at the left hand side of the layer name in the ArcMap table of contents.

Selection layers are not included in the layer list. They are created as a result of running OmegaGIS routines. Selection layers share the same data as the layer on which they were based during the query. Consequently, including these layers in the layer list, essentially results in displaying duplicate data.

Often a project can become confusing with a growing number of layers in the table of contents. To avoid showing all of the layers in the OmegaGIS dialog layer lists, two options can be set using OmegaGIS Setup. The first option deals with the use of registered layers. As layers are created, they can be registered as different types using the OmegaGIS Metadata Editor in ArcCatalog. Once registered, the setting 'Only use registered layers to create new queries' within the Queries settings in OmegaGIS Setup can be toggled to display only those layers registered as a specific type.

To limit the layer list further, those layers created by OmegaGIS routines may be excluded from the list explicitly using the 'Exclude layers...' checkbox on the Advanced tab of the Queries Settings. Setting this option ensures that layers created by any of the OmegaGIS routines are not listed in any of the layer lists for Spatial Trend Analysis.

Additional Query Layers
Additional Query Layers are point layers used as the historical comparison to the target layer. The list is populated based on the target layer selected. Additional query layers are only available to those target layers that share the same Query Groups and field list. However, they may include additional fields not found in the target layer. If no additional query layers exist for the selected target layer, Spatial Trend Analysis cannot continue.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Spatial Trend Dialog
Spatial Trend Analysis is composed of three types of questions that must be answered in order to produce results; which features should be selected (What?), what are the parameters to be used during the raster calculations (How?) and finally where is the geographic area of interest for the analysis (Where?). These questions are divided up as the What?, How? and Where? tabs on the Spatial Trend Analysis dialog.

What Menu
How Menu
Where Menu
When Menu
What?
The What? tab identifies which features to select for the subsequent Spatial Trend Analysis. Features are selected from a target layer and then compared to features selected from one or more additional query layers. The features selected in each of these layers may be narrowed down further by using one or more queries from the Saved Queries Tree or Columns.

As there is no date/time query involved in Spatial Trend Analysis, it is important when comparing layers to ensure that the date range for each layer does not overlap.

How?
The How? tab contains a number of options that identify specific parameters required to set up both the input and output of the analysis.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
New Layer Name
The result of Spatial Trend Analysis is a new raster layer. The New Layer Name identifies the name that is displayed in the table of contents in ArcMap. A layer name must be entered in order to perform the analysis.

Map Color Scheme
The Map Color Scheme displays the results of the raster analysis as an array of predefined colors on the map. The default color scheme is Green to Red, where shades of green reflect decreases in the data and variations in red indicate a relative increase. Altogether four color schemes are available, however additional schemes may be created by modifying the OmegaGIS.Style file.

Population Field
The population field is essentially a weighting field that identifies the influence of data on the final analysis. For instance in CrimeView, violent crimes might be given greater weight than petty theft during an analysis to determine where to allocate additional personnel and resources.

Fields listed in the population field dropdown list are those that have a numeric field type. However, length and area fields are excluded.

New Layer Extent
The New Layer Extent defines the outer boundaries of the resulting raster layer. The list includes 'Same as the Data Frame' and 'Same as the Current Extent'. The difference between these two choices is that the first uses the extent of the layer spanning the most area, while the second selection defines the envelope of the new raster as the current viewable area on the map. In addition to these two options, each of the layers within the table of contents is available as a basis for the extent of the new raster layer.

If the Subset by Boundary checkbox is checked, the New Layer Extent is no longer available. Instead, the new raster layer's extent will be based on the envelope surrounding the boundaries selected.

Cell Size

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The new raster layer output by Spatial Trend Analysis is based on cell statistics. With this approach, the change in the data is calculated on a cell by cell basis. The default cell size for English units is 250 feet, while 75 meters is used for Metric units.

The cell size must remain between 10 to 3280 feet when using English units or between 3 and 1000 meters when using Metric, if changing the cell size during a routine.

It is important to understand the implications of changing the cell size on the results of the analysis. Although decreasing the cell size may improve the resolution of the final result, it may also significantly impact performance. Conversely, increasing the cell size may enhance performance, but omit detail from the final analysis.

Search Distance
The search distance limits the data used to calculate the value of each cell by providing a maximum distance that will be searched for points around the center of the cell. The search distance should be set at 1.5 times the cell size. The default range of values falls between 15-13200 feet for English units or 5-4000 meters for Metric units. If the search distance entered is not within a valid range, it is recalculated during the routine to use the default values.

Reset
The Reset button can be used to set the cell size and search distance back to their default values.

Options
Two options are available for altering the placement of the new layer in the table of contents and the transparency of the new layer on the map.

Show Below Point and Line Layers
Selecting this checkbox places the new raster layer below point and line layers in the active data frame. By default the new layer is placed at the top of the table of contents, which may obscure features in the layers below.

Transparency
Transparency can be set to prevent the new layer from obscuring features in the layers below. Default values fall between 0 and 100, where 100 results in an invisible layer, and 0 is opaque. The default value is set at 20, allowing features below the new layer to remain visible. The transparency of the new layer may also be altered by using the Display tab in the Layer Properties dialog.

Where?
The Where? tab limits the raster analysis to a specific geographic region defined by either predefined or user-defined boundaries.

User-Defined Boundary
The user-defined boundary option is useful when no boundary layers exist on which to base the analysis. The ellipses button located next to the User-Defined Boundary option provides access to the map in order to delineate a polygon to use as the area of interest. For the routine to run, only one boundary can be selected, and its shape must be defined as a valid polygon.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Existing Boundary Layer
When the existing boundary layer option is selected, the drop-down list is populated with valid polygon layers found in the table of contents. Boundaries from any of these layers may be selected either 'By Field Value' or 'By Pointing'. Multiple boundaries can be selected using both of these options.

When selecting boundaries 'By Field Value' the 'Select All' checkbox can be toggled to select each of the unique values in the list. The complete list button is used to increase the listing of unique values by sampling all of the polygons in the layer instead of the maximum number set in OmegaGIS Setup.

When?
Not available in School Planner products.

The When? tab provides the functionality to add date, time, and day of week range query values to the target and historical layers, in order to restrict the incidents that are being used in the raster analysis calculation.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The When? tab is arranged into two main sections, Target Layer and Historical Layers, based on the types of layers being used for the analysis. The only layers that will be available on the When? tab will be the ones that were selected to be used in the analysis on the What? tab. If a layer is not displaying, ensure that it has been selected for analysis on the What? tab, as it is not possible to change layers using the When? tab, but instead provides functionality only to add date and time queries to layers that have already been selected for analysis.

Within each section, a summary of the Date/Time Query information including the Date Range, Time Range, and Day of Week values set for that layer, is available. Since only one target layer is available for a Spatial Trend Query, the Target Layer section only displays the selected target layer query. Since multiple historical layers can be used when performing a spatial trend analysis, the selected layers from the When? tab are displayed in the list in the historical layers section. When a layer is selected in the list, the summary to the right will display any date and time information related to that layer.

In order to add a date/time query to a layer, select the layer (if it is a historical layer) and then press the appropriate Add Date/Time Query button. Note that if a date/time query is already present, then the button will say Edit Date/Time query instead. Pressing the button will bring up the following date/time query editor window:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The date/time query editor window is organized into the following areas, it is not necessary to set parameters for all areas of the date/time query.:

1. Date

2. Time

3. Day of Week (DOW)

4. Predefined Date/Time Ranges

5. Previous Ranges

6. Other Controls

1. Date:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Use this section to apply a date range to the query, including month, day and year. Use the arrows next to the month and year indicators to scroll through the months and years, and select a calendar day by clicking on the day. The control will only allow dates which are present within the layers date range to be selected. Note however, that the viewer will default to the current date and so if the layer is historical it will be necessary to scroll back to the date range of the historical layer.

2. Time:

Use the arrows to scroll through the time and to set the FROM and TO times. Times are displayed in a 24 hour format. If no range is set (00:00 to 00:00) then a time range will not be used in the query.

3. Day of Week (DOW):

Simply check off the days of week which are necessary for the query. If no days are checked then no Day of Week values will be used in the query.

4. Predefined Date/Time Ranges:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
It is possible to store predefined date and time ranges in order to retrieve them if they are used frequently with the same settings.

This is done using the Predefined Date Range and Predefined Time Range controls. The drop-down lists are pre-populated with the following predefined ranges including:

All Dates: Select all of the dates available in the layer.

Other (Default): Use to manually set the date range.

Today: Select just the current day.

Week to Date: Select all of the days in the current week to the current day.

Month to Date: Select all of the days in the current month to the current day.

Year to Date: Select all of the days in the current year to the current day.

The Predefined Time Ranges offer the following settings:

All Times: Equivalent to not setting a range.

Other (Default): Use to manually set a time range.

Day: Daytime hours between (06:00 to 17:59).

Night: Nighttime hours between (18:00 to 05:59).

The purpose of using predefined date and time ranges is simply to save time in selecting commonly or frequently used date and time queries.

It is also possible to build custom Predefined Date and Time Ranges. For additional help regarding this, see the section in this document titled: Working with Custom Date and Time Ranges .

5. Previous Ranges:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The Previous section allows a duration of a time period, defined in either hours, days, weeks, months, or years to be set using the current date as the end date. This is a fast way to enter the information if a date or time range up the current date or time is needed.

Select the number of date time units from the first drop down list and then select the date or time units from the second one.

6. Other Controls:

The Other Controls on the page include the Clear All and Options... buttons, as pictured above.

Clear All: Resets the date/time query controls and clear all of the stored query information for the layer.

Options...: Opens the following dialog which allows the selection of which fields to use in the date/time query calculation.

To change the field to use, select the field from the drop-down menu for the appropriate parameter, either Date, Time, or Day of Week. Note that only fields which have been registered in the layers metadata as additional date/time fields can be selected from this list. In order to access OmegaGIS metadata, use the OmegaGIS Metadata Editor, available through the OmegaGIS Data Manager Toolbar in ArcCatalog. The default field can also be changed in the Metadata Editor.

Working with Custom Predefined Date and Time Ranges
Custom predefined Date and Time ranges can be created in OmegaGIS by using the Organize... functionality beside the Predefined

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Date Range list. This brings up a window that allows the modification of or creation of predefined date or time ranges.

Setting a new Date or Time range:

In order to set a date or time range, first set the range as normal on the Date and Time Query controls before opening the appropriate Organize Range button. For additional help on using the controls found on the When? tab, see the When? section in this help document. When a custom range is set on the Date and time dialog, the default option on the Predefined Date Range, or Predefined Time Range window will change to "OTHER". When OTHER is selected, then the option to edit or add a date range will be available when the Options... button is pressed. Once the date or time range to store has been set, select the appropriate Organize... button to open the Organize Date or Time Ranges dialog. If there are no previously stored ranges, then the list of available ranges will be empty (as in the image above) and the range selected will be displayed at the bottom of the form. Give the stored range a name by entering it in the "New date range" text box, and press the "Add New" button. The range is now stored and will be selectable from the respective Predefined Date Range or Predefined Time Range drop down lists on the main Date and Time Query window.

The Organize [Date/Time] Ranges menu also provides functionality to either rename or delete previously created Date or Time ranges. To rename or delete the date or time range, use the Organize... button to open the appropriate Organize Range dialog and then select the Range to rename or delete from the list. Use either the "Rename" or "Delete" button to perform the desired action, then press OK to exit the Organize Date Ranges window.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Spatial Trend Results
Map Layer
The result of a Spatial Trend Analysis is a new map layer that identifies whether changes in the data have occurred over time.

The new layer is based on cell statistics performed on the raster data generated by the analysis.

In this process, the Target Layer is first converted to a raster layer using the parameters entered into the dialog. Kernal Density is used as the method to create the raster layer. In this method, a smoothly curved surface is fitted over each point.

The kernal value is highest directly over the point, and diminishes outward to zero when the search radius distance is reached. The density of each raster cell is calculated by adding the values of all kernal surfaces within the cell, provided they overlay the cell center. If the Population field is used then the population value found for each point encountered is used to weight the individual point. For example, if a value of '4' is found, then the point is counted as four points before the raster density is calculated.

After the Target Layer is calculated, Kernel Density is used to create the raster layers for each of the Historic Layers used in the analysis. Once these raster layers are created, the raster results are averaged together to create the 'mean' historic raster layer. At this point, cell statistics are performed using the following equation:
[Output Raster] = [Target Raster] - [History Raster]
To display the new raster layer, bilinear interpolation is used as the resampling method. This method samples four of the neighboring raster cells to produce an average for each raster cell in the layer. Averaging cells in this manner produces a smoother surface as a result.

Map Legend

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The map legend illustrates the categories that are used to display the Spatial Trend raster results. The legend is always divided into five classifications ranging from 'Relative Decrease' to 'Relative Increase'. These classifications are generated using Jenk's Natural Breaks method of classification.

The Natural Breaks method subsets similar data values into classes by determining the partitions for these classes based on a statistical formula (Jenk's optimization). The partitions or breakpoints are calculated by finding the sum of absolute deviations about the class median, or alternatively, the sum of squared deviations about the class mean.

Although Omega uses the Natural Breaks method for classification, careful study of the data may indicate that other classification methods are more appropriate. The method of classification can be changed after the analysis is run by accessing the Symbology tab from the Properties page of the new raster layer.

The following information is taken from the ESRI Online Help, and provides a brief summary of the classification methods available:
"There are several different classification methods you can choose to organize your data when doing thematic mapping.

These include equal interval, natural breaks, quantile, equal area, and standard deviation.

In the Equal Interval classification method, each class has an equal range of values; that is, the difference between the high and low value is equal for each class. You should use this method if your data is evenly distributed and you want to emphasize the difference in values between the features.

With the Natural Breaks classification method, data values that cluster are placed into a single class. Class breaks occur where there is a gap between clusters. You should use this method if your data is unevenly distributed; that is, many features have the same or similar values and there are gaps between groups of values.

With the Quantile classification method, each class has roughly the same number of features. If your data is evenly distributed and you want to emphasize the difference in relative position between features, you should use the quantile classification method. If, for example, the point values are divided into five classes, points in the highest class would fall into the top fifth of all points.

With the Equal Area classification method, classes are formed so that the total area in each class is approximately the same (available only when working with areas).

With the Geometrical Interval classification method, class breaks are based on class intervals that have a geometrical series. The geometric coefficient in this classifier can change once (to its inverse) to optimize the class ranges. The algorithm creates these geometrical intervals by minimizing the square sum of element per class. This ensures that each class range has approximatley the same number of values with each class and that the change between intervals in fairly consistent. This algorithm was specifically designed to accomodate continuous data. It produces a result that is visually appealing and cartographically comprehensive.

With the Standard Deviation classification method, class breaks are placed above and below the mean value at intervals of 1, 0.5, or 0.25 standard deviations until all the data values are included in a class." Map Data Source

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
The data source for the new layer is stored in the \hotspot folder within the project directory structure. When a new raster layer is created, the raster data source name is created with a consecutive numbering system; raster1, raster2 etc. This name is created automatically during the processing.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhCE07.htm Attachment A
Project Clear All
Availability by Extension
Project Clear All is used to reset the project to its original state based on options set in OmegaGIS Setup. Clearing the project includes removing layers generated by OmegaGIS routines, removing selection sets and graphics, and resetting the map view.

Access to Project Clear All is available from both the CrimeView dropdown menu, as well as the CrimeView toolbar. The following events take place when using the Project Clear All.

Selection Layers Removed
Turn Off Selection Layers
Set Visibility of Registered Query Layers
Set Selectability of the Layers
Clear Omega Feature Definitions
Remove Additional Query Layers
Clear Selection Sets
Remove OmegaGIS Graphics
Zoom to the Project Bookmark
Save Map as Thumbnail
Remove OmegaGIS Layers from Map
CrimeView FireView School Planner
Clear All Clear All Clear All

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Selection Layers Removed
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) placed after 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 “*Layer based on a selection set…” identifies the layer as a selection. Depending on the setting in OmegaGIS Setup all Selection Layers are removed from the Table of Contents when the Project Clear All is run.

Turn Off Selection Layers
Instead of removing Selection Layers, they may be turned off by setting the appropriate option in OmegaGIS Setup.

Set Visibility of Registered Query Layers
Registered Query Layers are those layers that have been assigned a registered type using the OmegaGIS Metadata Editor. Although any name can be used as a registered type, currently OmegaGIS only recognizes ‘Incident’, ‘Person’, ‘Student’ and ‘Other’. Consequently, if the ‘Use registered type…’ setting is selected in OmegaGIS Setup, only those layers matching a registered type of ‘Incident’, ‘Person’, ‘Student’ or ‘Other’ will show up in the layer list of an OmegaGIS routine. Layers registered with different names are excluded.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
During the ‘Project Clear All’ event, the visibility of the Registered Query Layers is controlled based on two settings in OmegaGIS Setup. The ‘Turn off visibility of registered query layers’ setting controls the visibility of the ‘Incident’, ‘Person’ and ‘Student’ layers, while the ‘Turn off visibility of the layers registered as 'Other’ option controls the visibility of layers registered as ‘Other’.

Set Selectability of the Layers
The selectability of a layer refers to whether features in the layer can be selected on the map.

Depending on the setting in OmegaGIS Setup, layers can be set to retain their selectability or automatically set to unselectable .

Clear Omega Feature Definitions
A feature definition is used in ArcMap to display features based on an attribute query. Only those features that obey the query are shown on the map. In OmegaGIS , this method is used as well when an OmegaGIS Query routine is run. If the setting 'Show only saved query values and highlight selection' is selected in OmegaGIS Setup, only those features selected by the query in the routine are displayed on the map.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
An Omega Feature Definition is simply the query used to identify the output features of an OmegaGIS routine. An Omega Feature Definition can be recognized by right-clicking on the layer name in the Table of Contents, clicking Properties, and selecting ‘Definition Query’. An Omega Definition Query is delimited by a unique set of brackets ‘(( ( (( ( (( Omega Query Here )) ) )) ) ))’.

During a Project Clear All, these feature definitions can be removed by setting an option in OmegaGIS Setup.

Remove Additional Query Layers
Composite layers are created when more than one layer is combined during an OmegaGIS routine.

The layer can be recognized in the Table of Contents by the term ‘(Composite)’ that is added to the layer name.

Composite layers may be removed from the project during a Project Clear All by setting the appropriate option in OmegaGIS Setup.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Clear Selection Sets
While querying the data, selection sets may be created to identify the results of the query.

Features that appear highlighted on the map, are those that have been added to a selection set.

During a Project Clear All, every layer is cleared of any selection sets placed on it.

Remove OmegaGIS Graphics
In the case of OmegaGIS routines that create labels and buffers, these graphics are added to two distinct annotation layers called ‘ OmegaGIS Buffer’ and ‘Omega Label >’. During a Project Clear All, graphics from both of these layers are removed if the setting is selected in OmegaGIS Setup.

Zoom to the Project Bookmark
The Project Bookmark can be set to either Full Extent or Home. The Project Bookmark identifies the extent that the map will zoom to during the Project Clear All event. Zooming only takes place if the option is set in OmegaGIS Setup.

Save Map as Thumbnail
A map thumbnail can be used when viewing the project data using ArcCatalog . It provides a quick visual overview of the data contained within the project. Project Clear All creates the thumbnail, provided the option is set in OmegaGIS Setup. It is recommended that this option not be set as it

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
impedes performance when closing ArcMap .

Remove OmegaGIS Layers from Map
Within OmegaGIS Setup, the Advanced Tab of the ClearAll settings is available in order to select specific OmegaGIS layers that should be removed from the map's Table of Contents when the ClearAll tool is used. Each routine and tool that generates layers can be specifically selected to remove only those layers from the map.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Clear OmegaGIS Definitions
Availability by Extension
A feature definition is essentially a filter that enables the display of features meeting specific criteria while hiding those that do not. An OmegaGIS Definition is generated when one of the OmegaGIS Query routines is run. This definition query can be recognized by the special characters that delimit the query.

By right-clicking on the layer name in the table of contents, and selecting 'Properties', the 'Definition Query' statement that is used to filter features can be viewed. An OmegaGIS Definition query is delimited by the following series of brackets (( ( (( ( ((Omega Query)) ) )) ) )). By using a unique series of characters, the Clear OmegaGIS Defintions utility can remove those filters applied by OmegaGIS routines, while leaving queries created directly in ArcMap intact.

This feature is not available on the OmegaGIS toolbar but can be accessed using the 'Customize' menu item from the 'Tools' menu. The utility is found in the Commands tab, within the OmegaGIS category.

CrimeView FireView School Planner
Clear Definitions Clear Definitions Clear Definitions

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Go To Home
Availability by Extension
The Go To Home button is available on an Omega GIS toolbar, such as CrimeView. The utility is based on the concept of Bookmarks in ArcMap. A bookmark is a spatial place holder that is defined by a specific map extent. Bookmarks can be placed anywhere on a map, and once they are set up, they provide a quick method for zooming quickly to locations in the project.

The Go To Home utility uses the map extent employed by the HOME bookmark. Each time the Go To Home button is used, the project's active view is reset to the user defined map extent of the HOME bookmark. To create the HOME bookmark, in ArcMap, select the 'View' menu, 'Bookmarks', and 'Create'.

CrimeView FireView School Planner
Go To Home Go To Home Go To Home

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Create Order Labels
Availability by Extension
Create Order Labels is available from the OmegaGIS dropdown menu. The utility provides a quick method for viewing the chronological order of a series of events. A layer must be selected from the list provided. The layers that populate the list are those containing OmegaGIS date fields on which a chronological order can be based. If multiple date fields exist, the fields of interest may be selected from the dropdown lists.

CrimeView FireView School Planner
Create Order Labels Create Order Labels Not Available

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
The resulting graphics that are created by the routine include a numbering of the events, as well as directional arrows. Arrows are only displayed if the option is selected on the dialog. The symbology of the text is based on that of the source layer. Use the layer properties 'label' tab to set the symbology for the base layer, and consequently for the labelling that is used by the Create Order Labels tool.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Remove OmegaGIS Graphics
Availability by Extension
Some OmegaGIS routines and tools include options for generating graphics when the results are displayed. When graphics are added to the output of an OmegaGIS routine, the resulting labels and/or buffers are placed in two new annotation layers called 'OmegaGIS Buffer' and 'Omega Label >'. The layers ensure that graphics created by OmegaGIS do not become confused with graphics created directly through the ArcMap interface.

The Remove OmegaGIS Graphics utility can be used to eliminate only those graphics created in running OmegaGIS routines and tools. Graphics created through the ArcMap interface remain intact.

This feature is not available on the OmegaGIS toolbar but can be accessed using the 'Customize' menu item from the 'Tools' menu. The utility is found in the Commands tab, within the OmegaGIS category.

CrimeView FireView School Planner
Remove OmegaGIS Graphics Remove
OmegaGISGraphics Remove OmegaGIS Graphics

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Statistical Profiler
Availability by Extension
Overview
Statistical Profiler is a statistical tool for profiling crime series data. Running the statistical profiler results in the creation of rectangular polygons on a map, outlining the area where the next incident in a series is likely to occur. In addition to the new probability rectangles, a report is generated indicating the most likely occurrence of the next crime.

Before using this utility, a crime series should be identified that shows some logical link between the crimes in question. These crimes can either be selected from a layer, or created as a new selection layer by using one of the OmegaGIS Query
routines.

The Statistics
For the purpose of this utility, it is assumed that the data is normally distributed. With this CrimeView FireView School Planner
Statistical Profiler Statistical Profiler Not Available

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
assumption in place, the mean and standard deviation of the X and Y coordinates for the selected incidents are calculated. The three rectangles created in the analysis represent three standard deviations from the mean.

In general, sample data sets that are found to be normally distributed are based on standard deviations of 68%, 95% and 99.7%. In this case however, where we are dealing with probability distributions for a rectangular area, the standard deviation must be calculated for both an X and Y direction. Consequently, the standard deviations of 46%, 90% and 99% are used instead. These figures are calculated by multiplying the original standard deviations together to create .68 x .68 = .46%, .95 x .95 = .90% and .997 x .997 = .99%.

Selecting a Query Layer
The first task in performing a statistical analysis on a layer is to select the layer of interest. Only point or multipoint feature layers are available in the drop-down list. In addition, if the 'Use Registered Types' setting is checked in OmegaGIS Setup, only those layer types matching those selected in Setup are available. To edit or view a feature layer's registered type, the OmegaGIS Metadata Editor tool may be used from within ArcCatalog.

To run the analysis on a selection set within the feature layer, select the 'Selected records only' checkbox on the dialog. An example of a selection set of incidents might include a subset of burglaries with similar Modus Operandi (MO).

Selecting an Output Type
The results of the analysis can be output to the map as a layer or graphic. When creating a new layer, the advanced button can be used to set the placement of the new layer within the table of contents, and the transparency.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
If 'Graphic' is selected, the results are placed in an annotation layer called 'OmegaGIS Buffers'. The new annotation layer may be viewed by right-clicking on the data frame, and selecting 'Properties'.

Turning the annotation layer on and off, toggles the display of the new graphics. These graphics are also associated with the layer on which the analysis is based. Turning off this layer, turns off the graphics on the map.

Date Time Profiler
Provided that the attributes of the selected feature layer include OmegaGIS date and time fields, the Date-Time Profiler analysis may be run. The routine estimates the probable date and time range for the next crime in a series, based on the data selected.

The routine calculates the mean (average) number of days between occurrences and the standard deviation, assuming a normal distribution. The standard deviation represents the amount the mean will differ from the true population mean, given a 68% confidence interval.

The mean number of days is then added to the date of the last occurrence. The upper and lower limits of the next expected occurrence are based on one standard deviation from the mean date.

The same process is used to estimate the time frame of the next occurrence.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Advanced
If there are multiple OmegaGIS fields in the data, it is possible to select the field to use during the Date-Time Profiler analysis using the Advanced button. The Advanced dialog provides the opportunity to both select the field, and view the source field on which the OmegaGIS field is based.

Create Reports
Availability by Extension
The Create Reports tool is the central location for creating formatted reports presented in a custom Crystal Reports Viewer. The Crystal Reports Viewer allows the user to view and navigate through the report, zoom in and out, change printer settings, print and export.

Select Layer
Select Crystal Report
Generate Report
CrimeView FireView School Planner
Create Reports Create Reports Create Reports

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Select Layer
When the Create Reports dialog is opened, each valid layer in the active data frame that has a registered Crystal Report is added to the list of layers on the dialog. The type of layers that are available in the list are identified by a unique icon placed before the layer name and include:
l Query Layers
Crystal Reports can be registered to Query Layers (point feature classes) using the OmegaGIS Metadata Editor. There is no limit as to the number of Crystal Reports that can be registered to a Query Layer. Selection layers and Composite layers created by query routines, such as Incidents Within A Boundary, are also added to the list of layers on the dialog provided that their parent layer had a registered Crystal Report.

If the selected Query Layer has selected features the 'Selected records only' check box is enabled and is checked by default. When checked, only the selected records are exported and used to generate the Crystal Report, otherwise all of the records in the layer are used. l Repeat Calls Layers
The Query Layer that is used to generate the Repeat Calls layer must have one and only one Repeat Calls Report registered to it. The OmegaGIS Metadata Editor in ArcCatalog is used to register a Repeat Calls Report to a layer.

When the Repeat Calls layer is created, the information on the Repeat Calls Report from the Query Layer is copied to the new layer. The registered Repeat Calls Report can be altered on an existing Repeat Calls layer by using the OmegaGIS Metadata Editor.

OmegaGIS Metadata Editor

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Unlike reports for Query Layers, all of the features in the Repeat Calls layer are used in the report.

The "Selected records only" checkbox is always disabled on the dialog. l Density Map Layers
The Density Map Crystal Report provides a statistical summary of the count and density values in order to identify statistical outliers or potential problem areas.

The polygon layer that is used to generate a Density Map layer must have one and only one Density Map Crystal Report registered to it. The OmegaGIS Metadata Editor in ArcCatalog is used to register the Density Map Crystal Report to a layer.

Similar to the Repeat Calls layer, when the Density Map layer is created, information on the Density Map Crystal Report is copied to the new layer. The registered Density Map Crystal Report can be altered on an existing Density Map layer by using the OmegaGIS Metadata Editor.

Similar to Repeat Calls, all of the features in the Density Map layer are used in the report. The "Selected records only" checkbox is always disabled on the dialog.

When the dialog is opened, the layer that is currently selected in table of contains is selected in the list, provided that the layer has a registered report.

Select Crystal Report
When a layer is selected, the list of registered Crystal Reports is populated. The location(s) of the reports is set using OmegaGIS Setup
. There can be one or more locations for reports. The
locations are searched in the order they are defined in OmegaGIS Setup until a Crystal Report whose name matches the registered report is found. Only registered reports names are shown in the list; to get the full path of a Crystal Report hover the mouse over the report and a tool tip appears showing the full path. Reports that are not found are preceded with the report icon with a red 'X'.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
When a valid Crystal Report is selected the 'OK' button is enabled.

Generate Report
The Crystal Report Viewer is opened and displays data from the selected layer when the 'OK' button is clicked. The source of the data for the report is dependent upon the type of layer selected.
l Query Layer
Depending on the users specifications, either all of the layers records or only the selected records are exported to the 'Sel_INCIDENT' table in the Selection.MDB located in the project workspace.

All of the fields in the Query Layer, excluding the geometry, are exported to the Selection.MDB.

The Selection.MDB is automatically created if it is not present in the project workspace. If the 'Sel_INCIDENT' table already exists in the Selection.MDB it is deleted and replaced. l Repeat Calls Layer
All of the records from the source Query Layer that were used to generate the Repeat Calls layer are exported to a point feature class named 'Sel_RepeatCalls' in the Selection.MDB located in the project workspace. The 'Sel_RepeatCalls' is used as the source of the Crystal Report. When additional query layers are used to create the Repeat Calls layer, the records are exported from the RC_AddQueryLayer_* feature class located in the RepeatCalls.MDB.

A spatial filter is used to determine the records from the source Query Layer that were used to Sel_INCIDENT is
the source for the

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
generate the Repeat Calls layer. This spatial filter contains the attribute query, if any, that was used along with the geometry from the repeat call locations. The point geometry of the repeat calls locations is buffered before being placed in the spatial filter; the buffer distance is controlled by a parameter that is set in the project setup.

The Selection.MDB is automatically created if it is not present in the project workspace. If the 'Sel_RepeatCalls' feature class already exists in the Selection.MDB it is deleted and replaced.

The 'Sel_RepeatCalls' table has a field in it called "OmegaGIS_XY". The values in this field can be grouped in Crystal Reports to determine the repeat call locations.

When the Repeat Calls Report is opened, the Repeat Calls layer is made visible and any selected features are cleared. Any other Repeat Calls layers in the table of contents are made invisible. l Density Map Layer
The source of the Density Map Crystal Report is the 'Density_*' feature class located in the DensityMap.MDB in the Density folder in the project workspace. The source table of the report is dynamically updated to use the appropriate table in the DensityMap.MDB.

The 'Density_*' table contains all of the boundary layer fields plus two new fields that are created by the Density Map routine that can be used in the report.

Sel_RepeatCalls is
the source for the
OmegaGIS_XY field that can be
used to group repeat calls
locations.

Density_* table is
the source for the
Crystal Report.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
OmegaGIS_Count
This field contains the number of incidents that are found in the boundary.

OmegaGIS_Density
The density (count of incidents / area) is in this field. The area is calculated in square kilometers or in square miles, depending on the measurement system selected in the OmegaGIS Setup dialog.

The "Shape_Area" field is not used in the calculation of the OmegaGIS_Density field. The "Shape_Area" field is created and maintained by the Geodatabase and the values in this field are in the units of the spatial reference of the feature class which may not be in Kilometers or Miles.

Tip: If there are no records in the report, click the Refresh button in the Crystal Report Viewer.

Create Graphs
Availability by Extension
The Create Graphs button is used to create three dimensional graphs for Query Layers.

CrimeView FireView School Planner
Create Graphs Create Graphs Create Graphs

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Select Layer
When the Create Graphs dialog is opened, each layer in the active data frame is added to the list if it is a valid point layer. When a layer is selected, the Select Graphs list box is populated with the graphs that are available to the layer.

If the layer has selected features, the 'Selected records only' check box is enabled and is checked by default. If this box is checked when the routine is run, only the selected records are exported and used to generate the graph. Otherwise, the graph is generated using all of the records.

Select Graph
There are 6 standard three dimensional graph templates available with Omega GIS.

Select_Layer
Select_Graph
Change Default
Fields
Generate_Graph

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
7-24 Graph
The 7-24 Graph is a vertical bar chart counting selected points by what time and day of the week they occurred. This graph requires an OmegaGIS date field and time field.

Incident Type Graph
Incident Type Graph is a vertical bar chart counting selected incidents for each incident type.

This graph requires a field identified as the Incident Type Graph Field in the layers metadata.

This graph is always available, if there is no metadata information on the Incident Type Graph Field, then one is prompted when the 'OK' button is selected.

Day of Week Graph
The Day Of Week Graph is a vertical bar chart counting selected incidents by the day of the week they occurred. This graph requires an OmegaGIS day of week field.

Month of Year Graph
The Month of Year Graph is a vertical bar chart counting selected incidents by the month they occurred. This graph requires an OmegaGIS date field.

Time of Day Graph
The Time Of Day Graph is a vertical bar chart counting selected incidents by the hour of the day they occurred. This graph requires an OmegaGIS time field.

Response Time Graph
This graph is a vertical bar chart counting the selected incidents by the response time. This graph requires an OmegaGIS Response Time 2 field. The Response Time 2 field is generated using the Omega Import Wizard or the OmegaGIS Fields Manager. This field contains the same results as the Response Time field but includes 2 decimal places in the calculations.

Change Default Fields
OmegaGIS fields are used in the creation of the graphs. Default OmegaGIS fields set initially with the OmegaGIS Metadata Editor
. These fields can be altered by clicking on the Fields button to open a

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
dialog. The dialog allows one to change the default fields to other fields available in the selected layer.

The list of fields are populated based on information from the layer's metadata. This metadata information is set with the Omega Import Wizard or the OmegaGIS Field Manager. To alter the field to be used in the creation of the graph, change the appropriate list and click OK to close the dialog.

The Incident Type field is any text or numeric field that is used in the graph to display the number of incidents per incident type. The default Incident Type field is set with the OmegaGIS Metadata Editor.

If the default Incident Type field has not been set, then the 'cvLegend' field is used when present in the layer.

Generate Graph
The selected graph(s) are opened displaying data from the selected layer when the 'OK' button is clicked. Each type of type graph calculates the incidents uniquely and exports the summarized data to a different table in the Selection.MDB that is located in the project workspace.

The Selection.MDB is automatically created if it is not present in the project workspace. If the summarize table already exists in the Selection.MDB it is deleted and replaced.

The table in the Selection.MDB is then used with the graph template that is stored in the \Desktop\Graphs\ folder in the OmegaGIS installation directory.

Change the default OmegaGIS
field used in the creation of the
graph.

Selection.MDB contains
the sources for the
graphs.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
For more graph options, right-click the title bar of the graph window.

Layout Metadata Editor
Availability by Extension
The Layout Metadata Editor adds information to the layout about the last OmegaGIS routine run.

This tool will only be available when the Layout View is visible. To make the Layout View active, select 'Layout View' from the 'View' menu.

CrimeView FireView School Planner
Layout Metadata Editor Layout Metadata Editor Layout Metadata Editor Inputting_Information
Advanced_and_Preview_Buttons
Generating_Output

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Inputting Information
To add information to the layout, select the desired checkboxes and edit the text, if needed. The text is only editable if the checkbox has been selected. There are three subdivisions of information that can be included in the output. The text between each of these divisions is separated with a light cyan (red=140 green=178 blue=210) dashed line.

Disclaimer
This text is inserted as the last division of text in the output text box. The default disclaimer text can be updated on the 'General' category of the OmegaGIS Setup. The text is limited to 255 characters.

Title Information
This information is added to the layout as the first division of the output text as the title. This information is stored in the OmegaGIS routine metadata that is saved when a routine is created. If the routine metadata cannot be found, this information will not be available to add to the layout. l Name
This setting will be displayed as a medium cyan (red=70 green=130 blue=180) color. The maximum length of text inserted into this box is 100 characters. The default for this text box is the name of the last OmegaGIS routine run, for example, 'Near a Feature'. l Date
This setting will be displayed in black text and can be a maximum of 30 characters long. The default for this text box is the date that the last OmegaGIS routine was run. The maximum number of characters that can be typed into this text box is 30.

Last Routine Information
This information is added to the middle division of the output text. Each setting in this division will be prefixed by the label describing the text in the each text box. For instance, the Layers: setting will include not only the text inputted in the text box but also the word 'Layers: ' as a prefix. All of the settings in this section produce black text. This information is stored in the OmegaGIS routine metadata that is saved when a routine is created. If the routine metadata cannot be found, this information will not be available to add to the layout. l Layers:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
This text box by default contains the list of layer(s) separated by commas used in the last OmegaGIS routine run. This text box can accept characters up to 255. l Query:

This text box includes the query used during the last OmegaGIS routine. The query that is displayed is the query that is shown in the 'Edit Query' box on the What? tab of OmegaGIS routines. This box can be up to 500 characters in length. l Dates:

This text box shows any date queries that were specified on the When? tab of the last run OmegaGIS routine. The beginning and end dates are separated by a dash. The maximum number of characters that can be entered into this text box is 50. l Times:

This text box shows any date queries that were specified on the When? tab of the last run OmegaGIS routine. The beginning and end times are separated by a dash. The box can be up to 50 characters in length.
l Days:

This text box shows any day queries that were specified on the When? tab of the last run OmegaGIS routine. Each day is separated by semicolons. The maximum length of text inserted into this box is 50 characters.

Advanced and Preview Buttons
Advanced Properties
l Text Box Placement
By default, the text box is added to the lower right corner of the layout. Select another location from the drop-down list, if desired.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
l Text Box Width
By default, the text box is 46 characters wide. This means that sentences that contain more than 46 characters will wrap to another line. Enter a different number to change the width of the text box. The width must be between 10 and 100 characters. l Text Box Border
Checking this setting adds a border around the text. Otherwise, only the text is added to the layout. By default, a border is created around the text. l Show disclaimer in italics
Checking this setting displays only the disclaimer text in italics in the layout. Otherwise the text is shown as regular text. This setting by default puts the disclaimer in italics.

Preview
When the 'Preview' button is clicked the following events will occur:
l The text based on the current settings will be added to the layout.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
l The Layout Information dialog will shrink and the icon will blink. Click the blinking icon to restore the Layout Metadata Editor dialog.

Generating Output
Clicking 'OK' will add the specified text to the layout. Each time the 'OK' or 'Preview' button is selected any existing text generated by this tool will be removed.

Editing after clicking 'OK'
To edit the text you specify with this dialog, either double-click it with the Select Graphics tool (the black pointer), or click the Text tool (the black A) and then click inside the text on the map and make your edits. If a border is included around the text box, use the 'Ungroup' option on the Drawing toolbar to be able to edit the text.

The text in this tool is drawn using its symbol settings. In some cases these symbol settings are overridden for particular portions of the text by inserting ArcMap text formatting tags. This lets you create mixed-format text where, for example, one word in a sentence is underlined. The ArcMap text formatting tags follow XML syntax rules. Each start tag must be accompanied by an end tag.

Tags can be nested, but you must close the inner tag before closing an outer tag. The case of tag

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
pairs must match exactly. Tag attributes may be surrounded by either single or double quotes. '&' and '<' are special characters and are not valid in your text if formatting tags are used. Use the equivalent character codes &amp; and &lt. A list of common XML tags are shown below.

For more information about formatting text see ArcGIS Desktop Help.

Remove Layout Elements
Availability by Extension
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.

CrimeView FireView School Planner
Remove Layout Elements Remove Layout Elements Remove Layout Elements

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
When creating a new layout, it may be necessary to remove these map elements and start again. The Remove Layout Elements tool removes all map elements from the layout. The only map elements that are not removed are the data frames and any neatlines around a data frame.

The Remove Layout Elements tool is available from the pull-down menu of an Omega GIS toolbar, such as CrimeView. The tool is only enabled when the layout is the active view in ArcMap. When the tool is selected, one is prompted as to whether or not to remove all the map elements in the layout.

Create Grid
Availability by Extension
The Create Grid tool is used for the creation of polygon rectangular grid layers in a personal Geodatabase. To use the tool, the ArcMap document must be saved.

1. Select the extent for the polygon grid layer from the pulldown list, the options include:
l Using the extent of an existing layer.

CrimeView FireView School Planner
Create Grid Create Grid Not Available

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
l Using the extent of the selected features.
l Using selected rectangle graphic.

2. From the pulldown list of valid layers in the active data frame, select the layer to use as the extent of the grid layer. This list is disabled when using a rectangle graphic.

3. Select a pre-defined cell size of the grid from the pulldown list. Below the list will be the width and height of the grid cell in map units. The width and height of the grid cell can only be edited when the cell size of 'user-defined' is selected.

4. Provide a name for the new grid layer and the location of the personal geodatabase (pGDB). By default, the tool will generate the layer in the Grids.mdb in Grid folder located in the OmegaGIS project directory.

If the pGDB does not exist, it will be created. There must not be a layer within the pGDB that already has the same name of the new grid layer.

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

5. Click the Create Grid button to generate the new grid layer.

About Demographic Viewer
Availability by Extension
Demographic Viewer is designed to quickly display census data as thematic map layers in ArcGIS.

The tool displays either population count or population density based on a demographic attribute selected from the census layer.

Demographic Viewer was first designed to be used with the data format of Tiger Line/Census files available from ESRI at www.esri.com. Demographic data used with this utility can be downloaded and formatted according to the specifications outlined in the Accessing Demographic Data document. The Demographic Data Loader, available in ArcCatalog, provides an easy method for preparing the demographic data provided by ESRI for the Demographic Viewer. Census information outside of that provided by the U.S. Bureau of the Census, can be used as well, but must be formatted appropriately in order to be used with the utility.

To access Demographic Viewer, open up the Tools menu from the ArcMap toolbar, and select extensions. Select the OmegaTools extension to ensure access to the tools. Click on 'Customize' from the 'Tools' menu, and again select the OmegaTools extension to open the new extension as a toolbar.

CrimeView FireView School Planner
Demographic Viewer Demographic Viewer Demographic Viewer

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Creating Census Data
Census data can provide an excellent source of additional information when analyzing crime statistics. Incorporating census data into an analysis, can lead to a better understanding of how and why crimes occur, while determining resources necessary for crime prevention.

As a part of OmegaGIS, Demographic Viewer and Crime Rate Generator enable the incorporation of census information into viewing and analyzing crime data. Both utilities were initially designed to be based on standardized census information available from the ESRI website, under the Data section of their main webpage (www.esri.com
). However, it is possible to use other sources of
census information with these tools provided the data is formatted appropriately.

Description of Source Data

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Accessing Census Data
Description of Source Data
The U.S. Bureau of the Census provides census data that is distributed by ESRI. The data is created at three resolutions, census blocks, census block groups and census tracts and is available nationwide. Detailed metadata about the data can be acquired from both the ESRI website and the U.S. Bureau of the Census. http://www.census.gov/
Census Tracts
Census Tracts form the largest of the three boundary types. The boundaries tend to be relatively stable, covering subdivisions of a county or equivalent entity. Census tracts represent a continuous land area, where all parts are internally accessible by road. The total area and population of a county must be covered by the Census Tracts.

Census Block Groups
Census Block Groups are subdivisions of Census Tracts. Their boundaries always follow Census Tract boundaries, and generally are delineated by visible and identifiable features such as rivers, roads or power lines. Each Census Tract comprises between one and nine Census Block Groups.

Block Groups form a compact and contiguous group of Census Blocks, and provide a summary of block information.

Census Blocks
Blocks are the smallest geographic units for which demographic information is compiled by the U.S.

Bureau of the Census. In many cases, Census Blocks follow individual city blocks and are bounded by streets. There are cases however, especially in rural areas where blocks may span many miles, and where their boundaries do not relate to streets.

Data Format
The data provided is distributed as a shapefile and an associated flat file. The shapefile houses the census geographic boundaries. When unzipped, the shapefile consists of the three standard files that make up a shapefile on disk; .shp, .shx and .dbf. The flat file is distributed in .dbf format and includes all of the population statistics compiled by the U.S. Bureau of the Census for each polygon in the shapefile.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Do not alter the names of the files if planning to use the Demographic Data Loader to create the census data. An option exists in the Demographic Data Loader utility to automatically select all of the census files for data compilation, which then updates the various text boxes on the form. This option may save some time in browsing for each of the files, but does not automatically recognize the files if the names have been changed.

Accessing Census Data
Census information used by OmegaGIS is available through the ESRI website. The following steps outline the method for accessing and downloading the necessary files:

1. Go to the following URL:
http://
www.esri.com/data/download/census2000_tigerline/index.html

2. Click on the Download Data link.

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

3. In the map, click on the State for which you want to extract data.

4. Select the County you need data for and click Submit Selection.

5. From the Available data layers, select the following three (3) layers to download (these are the boundaries in shapefile format):
l Block Groups 2000
l Census Blocks 2000
l Census Tracts 2000

6. From the Available Statewide Layers, select the following three (3) layers to download:

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
l Census Block Demographics (SF1)
l Census Block Group Demographics (SF1)
l Census Tract Demographics (SF1)
If the Census Block Demographics are not available with a check box, you may need to download the entire state separately. There may be a link to do this on this same page.

Omega has already downloaded all of the block data for California.

7. Click Proceed To Download.

8. When your file is ready, click Download File.

9. Save the file in your \temp folder and extract all of the data layers into their own folder on your hard drive to start processing for use.

10. Load the data using the Demographic Data Loader.

Using the Demographic Viewer
The dialog provided with Demographic Viewer is relatively simple and intuitive to use, however it is important to keep in mind the way in which data is made available to the tool. The following topics describe the way in which data is loaded into the Demographic Viewer. The sections also outline how to use this data to create new demographic layers.

Census Layer
Fields
Count and Density

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
Below Point and Line Layers
Transparency
Resultant Census Layer
Census Layer
When the dialog is loaded, the table of contents is searched for layers containing a registered type of 'Census_Block', 'Census_Blockgroup' or 'Census_Tract'. When compiling the data using the Demographic Data Loader in ArcCatalog, the registered type is set automatically. If the data is not created with the Demographic Data Loader, the OmegaGIS Metadata Editor can be used to set the layer's registered type to 'Census_Tract', 'Census_Blockgroup' or 'Census_Block'.

Once the registered type is identified as one of the 'census' types above, the layer's data source is searched. If the data source is valid, the layer has met two of the three requirements necessary to add the layer to the list box. The final qualifier is that the layer must have a geometry type of 'Polygon'.

If no layers are found in the table of contents meeting these requirements, a warning message is issued to indicate that the Demographic Viewer is unavailable. At least one Census layer must be found in the table of contents to enable the tool.

Fields

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
The Fields list box lists the attributes found in the census layer selected in the 'Census Layer' list box. The fields are added to the field list box if they meet the following requirements:
l The field is not a length or area field.
l The field is numeric.

The census data provided by ESRI includes the following fields which are automatically omitted from the field list as they cannot be summarized:
l Med_age Median Age
l Med_age_M Median Age Male
l Med_age_F Median Age Female
l Avg_hh_sz Average household size
l Avg_fam_sz Average family size
l Hse_Units Household units
l Rural
l Urban
l Vacant
l ID
Count and Density
Count and Density options are available to display the resulting census data. The count option simply displays the population for each polygon in the census layer. The population data rendered depends on the field that is selected in the layer.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
To create the thematic layer, the data is divided into five classes based on the Jenks Natural Breaks classification method. Natural Breaks determines the class intervals by grouping similar values into the same class. Each class is then assigned a color based on the color ramp selected in the Viewer. The color ramps available are those found in the OmegaGIS.STYLE file.

The Density option displays the demographic data in exactly the same manner but normalizes the data by dividing the population count by the area of the polygon. The area of each polygon is calculated in square miles or square kilometers depending on the OmegaGIS Setup setting that sets the units of measure to either 'English' or 'Metric'.

If the census layer is in a projected coordinate system, the area calculation is straight forward.

However if the layer is in a geographic projection, the area cannot be calculated directly. The results are dependent on the latitude of the study area due to the nature of geographic projections.

In order to accommodate these calculations, if a geographic projection is encountered, the geometry of the census layer is projected temporarily to the coordinate system 'North America Lambert'.

Population Count Population Density
Display Below Point and Line Layers

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
The default position in the table of contents for new layers is at the very top of the stack. Placing a layer here, may obstruct features in layers below. The Display Below Point and Line Layers places the new census layer below any layers with a geometry type of point or polyline, so that these features are not blocked.

Transparency
Setting the transparency on a layer is used to both view the layer, while also being able to see the features of underlying layers. Transparency ranges from 0 to 100, where 100 is completely transparent and 0 is opaque.

Resultant Census Layer
The census layer created by the Demographic Viewer is placed in the map table of contents. It adopts the coordinate system of the source layer on which it is based. The new layer's source data is located in the project workspace
\census folder within a database called
Omega_DemoViewer.mdb. The new feature class is always called census_*. Where * is a numeric value used to create unique feature class names. When the layer is no longer referenced by the ArcMap document, it is removed automatically during Project Cleanup.

Omega Tab
Availability by Extension
CrimeView FireView School Planner
Omega Tab Omega Tab Omega Tab

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
ArcMap contains two tabs in the table of contents: the Display and Source tab. When an OmegaGIS extension is enabled such as CrimeView, FireView or School Planner, the Omega tab is added to ArcMap. The Omega tab is used to set which layers are selectable and to view layer metadata.

To prevent the Omega tab from being added to ArcMap automatically when an OmegaGIS extension is enabled, un-check the setting in the OmegaGIS Setup
dialog. The change occurs when ArcMap is
reopened.

Selectable Layers
The list at the top of the Omega tab contains all of the feature layers in the active data frame that are selectable and are valid. Layers are not valid if the reference data is missing (layer has a red exclamation mark in the ArcMap Display tab).

Layers that have a check mark in front of their name are selectable. The Select Feature tool in ArcMap only selects features in those layers that have been set to be selectable.

After the layer name in brackets is the number of selected features for that layer. This number is updated when there is a change in the selection in the active data frame. This functionality can be disabled by a setting in the OmegaGIS Setup dialog.

Metadata
The metadata for the selected item in the Selectable Layers list is displayed at the bottom of the tab.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
The metadata displayed includes:

Type: Layer type which is set in the OmegaGIS Metadata Editor.

Default Field: Name of the field that is automatically selected in OmegaGIS routines. The default field is set with the OmegaGIS Metadata Editor.

Query Groups: Saved query group to which the layer is registered. The OmegaGIS Metadata Editor is used to register the saved query groups.

Reports: Name of the Crystal Reports registered to the layer. Reports are registered to a layer with the OmegaGIS Metadata Editor.

Updated: Date (yyyy-mm-dd) That the layer was last updated by the Omega Import Wizard.

If an item outlined above is missing, then there is no information for the layer.

Tip
l Limit the number of selectable layers to improve performance while using the Select Feature tool.

ArcMap must perform a spatial query on each layer that is selectable when using the tool. l For metadata information about the import process, use the OmegaGIS stylesheet in ArcCatalog.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hhC24D.htm Attachment A
About Cyclical Reports
Cyclical Reports are created in order to store the parameters of common queries and density routines so that they may be run repeatedly and without spending time resetting the parameters. A query or density map created with either of the OmegaGIS Query
or Density routines can be stored as a Cyclical
Report. When run, the Cyclical Report recreates the query or density request, and produces the results geographically as a map layer, as well as opening any reports or graphs that have been saved as a part of the Cyclical Report.

Cyclical Reports Setup
Creating a Cyclical Report
Cyclical Reports are based on Query and Density routines. It is extremely important to note that when designing a Cyclical Report, the date range must be identified using the 'Previous' control on the When tab of the dialogs. Interactively setting the date range using the calendars will result in incorrect results when the Cyclical Report is run.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Once a Query or Density routine is set up, saving the routine as a Cyclical Report can be accomplished from the Query routine Summary Dialog available in OmegaGIS. The Summary Dialog appears after the options of a query or density routine are set, and the Finish button is clicked. If the Summary Dialog does not appear before the routine finishes running, check OmegaGIS Setup to ensure that the 'Display the routine summary...'
option is checked under the Queries category.

To open the Cyclical Report menu, click on the Save button from the Summary Dialog.

When the new menu opens, a Group must either be selected from the drop-down list, or a new Group must be entered into the text box. The Group identifies to which collection the particular Cyclical Report belongs. The Group allows Cyclical Reports to be organized into different categories. Sub-dividing the reports creates a more manageable project as the number of reports increases.

A Name must be entered for each Cyclical Report, and must be unique to the Group to which it belongs. If a duplicate name is entered, a message box issues a warning. The Description field is not required, however adding detail to a Cyclical Report can increase the manageability of the project as the number of reports grows.

When the Group, Name and Description are determined, check the 'Save as Cyclical Report' to save the query or density routine as a Cyclical Report. In addition to saving the query or density routine that will run using the parameters specified on the query or density dialog, the Cyclical Report can save a number of reports or graphs that will be generated the next time the report is run. These reports can be sent with a Threshold Alert as PDF files when the alerts are emailed.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Reports
The list presented in the Reports window is a compilation of all of the reports that have already been registered to the Query layer. For instance, during the creation of the query or density routine, the Query Layer '2001 Part I Crimes' is selected. From the Query Summary dialog, the Save button is clicked to open the 'Save as Cyclical Report...' dialog. The reports that appear in the Cyclical Report window consist of those reports that were registered to this layer using the OmegaGIS Metadata Editor.

Any report registered to the Query layer for a Query routine is shown in the Report list. For Density routines however, the report list is disabled for both Density and Hot Spot maps. For Repeat Calls, the Repeat Calls report may show up in the list if it has been registered to the query layer using the OmegaGIS Metadata Editor.

Crystal Reports is used by the Omega Project Manager to create the standard reports that are issued with each OmegaGIS project. Additional reports can always be created and customized, and will appear in the report list box if they are also registered to the appropriate layers using the OmegaGIS Metadata Editor. In addition, it is important to ensure that OmegaGIS can find all of the reports necessary for the project. Use the Database category in OmegaGIS Setup
to set the locations on disk that are searched for reports.

Graphs
The list presented in the Graphs window represents the standard graphs that are delivered with OmegaGIS.

The graphs that show up in this list are based on whether OmegaGIS Date, Time and Day of Week fields are available in the layer that is being queried. If multiple OmegaGIS fields exist within the layer, the default OmegaGIS field is selected for calculations. The default OmegaGIS field can be set using the OmegaGIS Metadata Editor.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Any standard graph that meets the OmegaGIS field requirement for a Query layer based on the Query routine will show up in the list. However, the Graph list will be disabled for any Query layer created using the Density, Hotspot, or Repeat Calls routines.

Map Template
Map templates are used to define how the map elements in the layout appear. Map elements include a title, agency logo, legend, north arrow and scale bar. Check the Use Map Template checkbox and then click the browse button to navigate to an existing map template (.MXT).

With the release of ArcGIS 10, creating map templates is no longer supported by ESRI. Existing map templates may be used to create Cyclical Reports, however, no new templates may be created.

When a map template is selected, the following items are checked:
¡ The MXT contains a layout.
¡ The MXT contains the same number of data frames as the current ArcMap document.

When editing a Cyclical Report the map template is verified and if there is a problem a red exclamation mark is visible beside the path to the template. The following checks are made on the template:
¡ The MXT file can be located on disk.
¡ The MXT contains a layout.
¡ The MXT contains the same number of data frames as the current ArcMap document.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
When the Cyclical Report is run, the same validation of the map template occurs. If the template is valid, the layout is made the active view in ArcMap and the template is loaded. If the map template is not valid, the template is not used and there is no warning provided.

Editing Cyclical Reports
On the 'Save Cyclical Report...' dialog, an Edit button is visible, however it remains disabled. The Edit button references the actual Query or Density routine used to create the Cyclical Report. Since it is possible to edit the query by simply canceling the dialog, and then clicking the back button on the Summary Dialog, this feature is unnecessary and is disabled.

The Edit button is enabled when the 'Save Cyclical Report...' form is opened from the 'Cyclical Report' dialog.

In this case, you cannot backtrack to the Query or Density dialog directly, so the Edit button is necessary to edit the parameters of the initial Query or Density routine.

The Cyclical Reports Database
The database housing all of the information important to Cyclical Reports is called Threshold_Alert.mdb and is found in the project workspace
. In pre-Service Pack 2 versions of OmegaGIS, the Threshold_Alert database was referred to as the Cyclical.mdb database as it stored files pertaining to cyclical reports only. However, to accommodate the new functionality of Threshold Alerts, this database has been updated to include the data pertinent Threshold Alerts as well.

As a consequence of these updates, any projects created with previous versions of OmegaGIS software in the ArcGIS environment, must replace the cyclical.mdb database with the new threshold_alert.mdb database. Any cyclical reports created in the old environment must be recreated in the new environment, in order to save them in the format required.

Running a Cyclical Report

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Opening a Cyclical Report
Once created, a Cyclical Report can be opened at any time by accessing the report from the 'Cyclical Reports' Button of the Main Menu. If there are no Cyclical Reports in the project, a warning message is issued and Cyclical Reports is unavailable.

Cyclical Reports Dialog
When the Cyclical Reports dialog is opened, any of the reports created previously can be viewed and run again. On the left hand side of the dialog is a listing of the Groups, and the Cyclical Reports contained within those Groups. To select a Cyclical Report, click on the report name in the list. Once a report is selected, the right hand side of the dialog is updated with a general description.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Cyclical Report Options
Each Cyclical Report can be run simply by clicking on the Run button at the bottom of the dialog. However, by right-clicking on the Cyclical Report name, a number of additional options become available.

The following options are provided on the pop-up menu when the Cyclical Report is selected:

Rename
Create a new name for the Cyclical Report.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Edit
The Edit menu item opens up the 'Save Cyclical Report...' dialog. In this dialog, the Cyclical Report name and description may be modified, as well as the reports and graphs that are saved as components of the cyclical report.

Run
Run the selected Cyclical Report.

Copy To
Copy the selected Cyclical Report to a different Group.

Move To
Move the selected Cyclical Report to a different Group.

Remove
Delete the Cyclical Report.

About Threshold Alert
Threshold Alert is a versatile utility that can be used to notify decision makers when incidents exceed an acceptable threshold. The distribution of information is made immediate, by setting up email addresses in advance. The results of OmegaGIS queries can then be automatically made available to the appropriate personnel when a critical number of events have occurred.

Three important steps must be accomplished in order to create and distribute threshold alerts. The first step is to identify what type of threshold alerts are required. Threshold Alert is similar to Cyclical Reports and is
available to any of the Query routines. Once the alerts required are created, the next step is to identify who will receive the information. During this stage, the email server and email addresses of the recipients must be identified. Finally, each threshold alert must be assigned to the appropriate personnel. When these steps are complete, it is possible to automate the process.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Understanding Threshold Alerts
In setting up a system of Threshold Alerts, it is important to understand the process whereby information is retrieved from the source database, and processed for analysis. Typically, two streams of data exist, Computer Aided Dispatch (CAD) and Records Management System (RMS). CAD information is immediate, as it is collected as incidents are called in, whereas RMS data is filtered from the CAD calls, and is only as current as the data processing to enter new records into the system.

If for example, it takes three weeks to enter records from the initial CAD database into the RMS system, sending a Threshold Alert based on the RMS records is not beneficial to assist in an immediate response to specific incidents. It is important to understand the flow of information before creating a series of threshold alerts.

Threshold Alert Results
Threshold Alerts may be emailed as both a map, and a series of Crystal Reports. A map template may be used in order to include map surround elements. The format of the map that is emailed depends on whether the ArcMap project was last saved in a data view or layout view. If ArcMap was saved in 'layout view', the map can include any of the map surround elements included with the page; such as a legend or disclaimer. Any reports generated by the cyclical report on which the threshold alert is based, can be sent as attachments to the email as PDF files. The limitation on the number of reports that can be sent is associated with the file email attachment file size limitation.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Threshold Alert Setup
Creating a Threshold Alert
Setting Threshold Alert Email Servers
Setting Threshold Alert Emails
Managing the Threshold Alert Database
Limiting Alert Notifications

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Creating a Threshold Alert
Threshold Alerts are based on Query Routines. It is extremely important to note that when setting a date range for a Threshold Alert, the 'Previous' control on the date-time dialog must be used to select the beginning and end dates. Interactively setting the dates using the calendars will result in incorrect results when the Threshold Alert is run.

Threshold Alerts are accessed from the Query routine
Summary Dialog available in OmegaGIS. The
Summary Dialog appears after the options of a query are set, and the Finish button is clicked. If the Summary Dialog does not appear before the routine finishes running, check Omega Setup to ensure that the 'Display the routine summary...' option is checked under the Queries category.

To open the Threshold Alert form, click on the Save button from the Summary Dialog.

When the new dialog opens, a Group must either be selected from the drop-down list, or a new Group must be entered into the text box. The Group identifies to which collection the particular Threshold Alert belongs. The Group becomes important when designing email notifications, as all of the threshold alerts belonging to the Group are mailed as a collection to the designated personnel.

An additional note about Groups is important when using Threshold Alerts and Cyclical Reports. Both routines use the concept of a 'Group' in order to categorize reports and alerts. This means that the Group list will contain Group names for both Cyclical Reports and Threshold Alerts.

A Name must be entered for each threshold alert, and must be unique to the group to which it belongs. If a

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
duplicate name is entered, a message box issues a warning. The Description field is not required, however adding detail to an alert can increase the manageability of the project as the number of alerts grows.

When the Group, Name and Description are determined, check the 'Save as Threshold Alert' to save the query as an alert. The Threshold refers to the number of incidents that must be exceeded in order to produce an alert.

Using the Previous text boxes, a specific duration can be set to search for the incidents in question.

Through this menu, an Edit button is visible, however it remains disabled. The Edit button references the actual query used to create the threshold alert. Since it is possible to edit the query by simply canceling the dialog, and then clicking the back button on the Summary Dialog, this feature is unnecessary from this menu and is disabled. The Edit button becomes enabled when accessing this menu from the Threshold Alerts and Notifications dialog.

Map Template
Map templates are used to define how the map elements in the layout appear. Map elements include a title, agency logo, legend, north arrow and scale bar. Check the Use Map Template checkbox and then click the browse button to navigate to an existing map template (.MXT).

With the release of ArcGIS 10, creating map templates is no longer supported by ESRI. Existing map templates may be used to create Threshold Alerts, however, no new templates may be created.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
When a map template is selected, the following items are checked:
¡ The MXT contains a layout.
¡ The MXT contains the same number of data frames as the current ArcMap document.

When editing a Cyclical Report the map template is verified and if there is a problem a red exclamation mark is visible beside the path to the template. The following checks are made on the template:
¡ The MXT file can be located on disk.
¡ The MXT contains a layout.
¡ The MXT contains the same number of data frames as the current ArcMap document.

When the Cyclical Report is run, the same validation of the map template occurs. If the template is valid, the layout is made the active view in ArcMap and the template is loaded. If the map template is not valid, the template is not used and there is no warning provided.

Setting Threshold Alert Email Servers
In order to send Threshold Alerts to the appropriate personnel, an email server must first be selected, and the addresses of those receiving Threshold Alerts must be entered. To set up these options, open OmegaGIS Setup and click on the Threshold Alert Icon.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
The first step in setting up the Email Server information is to research the fully qualified domain name(s) or IP addresse(s) of the SMTP Server at your site. Contact your system administrator for this information. The SMTP Server must be accessible from the computer where the Threshold Alerts are to be run. URL addresses, such as http://mail.yourdomain.com are not supported.

When the name(s) or IP addresse(s) 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.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Selecting the checkbox 'Use this server as the default' 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 server icon.

Setting Threshold Alert Emails
After the SMTP servers are set, the email address from which the threshold alerts will be sent must be identified. When personnel receive a threshold alert, this address indicates who sent the alert. Click on the Email Settings tab of the Threshold Alert Setup dialog to enter a valid source email address. A copy of the threshold alert can be mailed to the source address if the option 'Send a copy of this email address...' is selected.

Setting the subject line of the email is also possible from this dialog. Two options exist for the subject line.

Either the Group and Name of the alert along with the number that exceeded the threshold can be placed in the subject line of the email, or a standard phrase may be entered.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Finally, now that the From email address is set, the email addresses of those personnel that are to receive threshold alerts can be entered. Emails may be sent to any valid email address, however the SMTP Server must be identified for each address.

As mentioned above, the email address entered is automatically assigned a default SMTP server name, if the default is set. If the default SMTP server is not set, a list of available servers is provided from which one must be selected. If a server is not assigned to an email address when the Apply or OK button is hit, a warning message is issued to set the email address' server before continuing.

Managing the Theshold Alert Database

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Email address and server information is saved to the Threshold Alert database in the project workspace. 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.

To compress the database, click on the Advanced tab, and click the button 'Compress'.

The 'Clear History' button 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.

Limiting Alert Notification
When a threshold has been reached, a Threshold Alert is sent to the appropriate personnel. The next time the Threshold Alert is run, the same incidents may result in the threshold being reached but the personnel have already been notified. For example, a Threshold Alert has been set to run nightly. The alert checks if there have been 5 incidents within the last 10 days in the downtown district. On Monday night, there are 7 incidents in the downtown district and consequently the Threshold Alert is sent to the local officials. On Tuesday night, there were no new incidents but since there were 7 incidents the day before the threshold has been reached and the Threshold Alert is sent again.

To prevent this repeated notification there is a setting in OmegaGIS Setup to limit alert notification. On the

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Advanced tab, check the "Check for incidents within the last day" checkbox. This setting applies to all Threshold Alerts run. When the Threshold Alert is run manually, there is an option to override this setting.

The Limit Alert Notification is used to stop threshold alerts from being sent out repeatedly when there are no new incidents. If ’r;Limit Alert Notification’ is selected in OmegaGIS Setup, Threshold Alert checks the previous day for incidents. If no new incidents have occurred then even if the number of incidents for the date range requested exceeds the threshold value set, the threshold alert is not sent. In this case the threshold alert would simply be a repeat of a threshold alert sent previously. If however, new incidents are found, the date range is searched for previous incidents and a new threshold alert is sent.

Using the 'Limit Alert Notification' requires that data entering the system is kept up to date on a daily basis.

Any lag time introduced from the time the incident data enters the system will work against the successful use of Threshold Alert.

The setting only works when the date range specified with the threshold is 'Days', 'Week to Date', 'Month to date' and 'Year to date'. When a different date range is selected, there is no check for incidents within the last day.

When no new incidents are found the email or summary report will state "Threshold Alert was not run as there were no incidents within the last day".

Alerts and Notifications
When the Threshold Alert setup is complete, Alerts and Notifications can be organized and run using the Threshold Alert Dialog available from the Main Menu. Alerts refer to the Threshold Alerts that are saved during a Query routine. Notifications are set up to link the Alerts with the email addresses that receive them.

Alerts Tab

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Alert Details
Notification Tab
Running the Alert
Alerts Tab
When a Threshold Alert is first created during a Query routine, it is assigned to a Group, is given a Name, and a specific number of incidents is set as the threshold. The Group can be recognized in the Threshold Alert Dialog by a pink background. Individual Threshold Alerts belonging to this Group are listed below the Group name.

In the Threshold Alert dialog, on the Alerts tab, the following columns describe different aspects of the threshold alert:

Name
The name entered when the Threshold Alert was first created during a Query routine.

Run
Threshold Alerts are run based on the Group to which they belong. To select specific Alerts to run within the Group, the Run checkbox can be toggled to either run or omit the Alert.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Dates
The Date column refers to the duration used to search for incidents that meet the criteria set for the Alert. It is important to note that the duration represents the last complete block of dates. For instance, given that the current date is December 9th, a previous duration of 1 month returns the dates between November 1st and November 30th. The dates between December 1st and the 9th are excluded as they are not a part of a complete month.

Threshold
The Threshold is an arbitrary number that determines when a critical number of events have occurred. When the Threshold is met or exceeded, the pin on the left side of the table for that particular Alert turns from green to red.

Last Query
This column reveals the number of incidents returned by the last query.

Date of Last Query
As Alerts can be run multiple times, this column displays the last time the Alert was run.

Alert Details
Alert Tab
A detailed description of each Alert within the Group is available by clicking on the Details button. The Alert Details dialog contains two tabs; an Alert tab and an History tab. The Alert tab contains a window summarizing the query used to select the incidents for the Alert. Clicking on the Edit button beside this window, opens the Save Cyclical Report and Threshold Alert dialog where the Group, Name, Description or characteristics of the Threshold Alert may be modified. From this dialog, the Edit button at the bottom of the form returns to the original Query dialog used to create the Threshold Alert initially.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
History Tab
The History tab reveals when the Alert was run previously. The table provided lists the date, the threshold value, whether the threshold was exceeded, and whether the Alert was completed. Clicking on a row in the table, updates the Results window below with a more detailed description about the Alert.

Selecting 'Recreate' runs the Alert using the original date parameters on which the query was based. Before running the Alert, a Clear All
is performed on the project to clear any pre-existing selection sets. Although it would appear that using the original dates should give the same 'snap-shot' of incidents, there may be some differences in the resulting dataset. As the Import Wizard is continually modifying records with the most up to date information from the source database, the number of incidents matching the initial query may have changed.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Notification Tab
The Notification Tab includes summary information about who is to receive the Threshold Alerts. The Alert is identified by a pink background. Alerts are assigned email addresses which are listed below each Alert. The format and content of the email is set using the options available on the Notifications Group Properties Dialog.

The Alert summary information on the Notification tab includes a listing of the email addresses to which the Alert will be sent. Also found on the dialog is information regarding whether a Group Summary, Map and Report are to be included with the email, as well as whether the email is to be sent only when the threshold is met or every time the Alert is run.

Attach Reports
When the option to include a Crystal Report with the email notification is selected, the Crystal Report is exported to a PDF file. It is this PDF file that is attached to the email. The name of the PDF is a concatenation of the name of the alert item and the report name.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Report Parameters
Typical Crystal Reports are created with parameters that allow for a dynamic report with the user making changes before the report is opened. An example is the title used with the report. When exporting the report to a PDF file, these parameters are suppressed.

Tip: Create a version of the Crystal Report specifically for automation with Threshold Alert.

Email Size
The total size of the email attachment must be taken into consideration. This is especially the case when multiple reports per alert are sent. Typically, an organization will limit the size of email attachments. Emails with attachments larger than the limit are not sent.

Tip: Only include a single report for each alert in an attempt to reduce the size of the email.

Another option is not to select the Group Summary. When the Group Summary option is used, all of the alerts are sent in a single email.

Notification Group Properties Dialog
The Notification Group Properties dialog is accessed from the New or Edit button on the Notification Tab.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
This dialog contains options for adding email addresses to a particular Alert as well as setting the format and content of those emails. An Alert Group must first be selected from the list. Clicking the Add emails... button opens a dialog from which the email addresses set up previously using OmegaGIS Setup can be selected.

Each email address selected will receive the Threshold Alert email when it is sent.

In addition to adding email addresses to a list of recipients, the format and content of the email can also be set.

Email can be sent as plain text or in an HTML format, a map can be included in the content of the email or excluded as well as reports, the email can be sent only when the threshold is met, or each time the Alert is run, and the email can contain a Group Summary, or the individual Alert. Each of these items is set for the Alert Group and applies to all of the email addresses within that Group.

It is possible to attach a map image as a .jpg as well as Crystal Reports in PDF format by selecting the appropriate checkboxes on the dialog. If automating the Threshold Alert, the report should not prompt the user for any parameters, such as the report title as this will interrupt the automation of the alert, and it will not be sent.

Notification History
The historical record of a Notification is accessed by selecting a Group on the Notification Tab, and clicking on the History button. The history identifies errors that occur when the Threshold Alert Group is sent by writing an error message to the history list. A list of prior errors is displayed in the table on the form. Clicking on the error, reveals more information in the Results window below.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Running the Alert
Although Alerts can be set to run automatically, they can also be run directly from the Threshold Alert dialog by clicking Run. A small dialog opens, and an Alert Group can be selected from a drop-down list.

There are a few options that can be activated once Threshold Alerts are completed:

Show Summary
With this setting selected, the Threshold Alerts summary dialog opens when processing is complete. This dialog contains information on each of the Threshold Alerts that were run.

Email Results
With this setting selected, email notifications are sent to the appropriate personnel.

Check for Incidents Within the Last Day

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
With this setting selected, it is determined whether there have been any incidents within the last day before proceeding to run the Threshold Alert. The checkbox is selected based on the setting in OmegaGIS Setup.

Either the Show Summary or the Email Results checkbox must be selected for the Run button to be enabled.

Running the Alerts manually provides an easy method to check whether Notifications are sent properly before the system is automated.

Automating Threshold Alerts
When Threshold Alerts and their corresponding Notifications are set, it is possible to automate the process of alerting personnel when incidents exceed a certain threshold. Automating the distribution of information allows personnel to be notified of significant events, while removing the need to search through repetitive analysis queries for spikes in the number of incidents.

It is extremely important that if automating reports, parameters such as prompting the user for a title not be included. Using parameters interrupts the automation of the threshold alert so that it cannot be sent.

The Microsoft Windows Task Scheduler
The Microsoft Windows Task Scheduler handles the automation of Threshold Alert. The Task Scheduler is already installed on Microsoft Windows 2000 and XP operating systems.

To create a new task using Microsoft Windows Task Scheduler:

From the Windows Start button...

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
l Select Settings/Control Panel and then Scheduled Tasks. l Select Add Scheduled Task
In the Task Scheduler wizard...
l Select the ThresholdAuto.exe as the program to be run by Windows l Use the Browse button to locate the ThresholdAuto_2.exe (Installed on the C:\Program Files\OmegaGroup\Desktop\Bin) Note: ThresholdAuto_2.EXE was introduced at the Omega Desktop 4.3 release and it is an upgrade to the ThresholdAuto.EXE. The ThresholdAuto.EXE will continue to work but it is recommended that new implements use the ThresholdAuto_2.EXE. l Enter a name for the task and select when to perform the task. l Enter the Windows user name and password. The task will run under the permissions of this user.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
Note: Using the password of the current user requires that the user be logged in for the automated task to complete successfully.

When task wizard is completed open the advanced dialog...

Add the path to the ArcMap document to the command line.

On the Task tab on the Advanced dialog, add the ArcMap document path at the end of the existing command line. The path to the ThresholdAuto.exe should be in double quotes due to spaces in the file names. For example: "C:\Program Files\OmegaGroup\Desktop\Bin\ThresholdAuto_2.exe" c:\CrimeView\MyMaps.mxd If there is an error automating the Threshold Alert, the Write_File.EXE utility may provide trouble shooting
information.

Note: This ArcMap document should already contain Threshold Alerts with email notification. See the help document for how to create Threshold Alerts.

When ThresholdAuto.exe is run, a log file, ThresholdAlert.log, will be written to the ArcMap document’s project workspace
. For the document c:\CrimeView\MyMaps.mxd, the log file would be found at c:\CrimeView\MyMaps\ThresholdAlert.log.

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

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc2808/~hh4CEB.htm Attachment A
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.

The extension includes the following tools:

Saved Queries Editor
Metadata Editor
OmegaGIS Field Manager
Demographic Data Loader
Clone Omega Metadata
Accessing the Extension
Before any of the tools can be used, the Omega Data Manager extension must be enabled. To enable the extension follow the these steps:
l Open ArcCatalog and from the Tools pull-down menu select Extensions. l Select the checkbox next to "OmegaGIS Data Manager". The extension is protected from unauthorized use; at least one Omega Desktop product, such as CrimeView or the Omega Import Wizard, must be licensed for extension to be enabled.

After the Omega Data Manager extension is enabled, the toolbar must be added to ArcCatalog. This is done by selecting Toolbars from the View pull-down menu in ArcCatalog. From the list of toolbars select 'OmegaGIS Data Manager'.

OmegaGIS Metadata Editor
Metadata is descriptive information about data. OmegaGIS uses metadata to increase performance as well as store commonly used parameters that are necessary for OmegaGIS routines. The OmegaGIS Metadata Editor is available as one of the OmegaGIS Data Manager tools in ArcCatalog. It provides a dialog to set information common to most OmegaGIS routines.

Accessing the OmegaGIS Metadata Editor
Feature Class Geometry Types
OmegaGIS Metadata Editor Dialog
SchoolPlanner™ Metadata
Accessing the OmegaGIS Metadata Editor
To view metadata for a dataset, select the desired object in ArcCatalog and use the Metadata Editor button on the Omega Data Manager extension toolbar to open the editor. This button is only available when the Omega Data manager extension is enabled and the selected object is a feature class with the geometry type of point, multi-point, polygon or line. The feature class may be stored in a File Geodatabase, Personal Geodatabase, ArcSDE or shapefile format.

When the feature class is stored in ArcSDE, the spatial database connection used to connect to the feature class must be the owner of the feature class. That is, the same login that generated the feature class must be used to update the metadata of that feature class.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Feature Class Geometry Types
There are four main geometry types that are supported in the Metadata Editor. These types include, point, multipoint, polyline and polygon. It is important to distinguish between these types, as certain options on the Metadata Editor are available to some types and not others. If an option is unavailable to a particular feature type, the option is disabled and my not appear as an option, or a warning message may be displayed.

Point Geometry Type
A point layer can access all of the options on the Metadata Editor Dialog, with the exception of options that are reserved for specific registered types.

Polygon and Polyline Geometry Type
Options available to polygon or polyline layers are limited to Registered Type, Default Field, and an associated Density Map Report. A polygon layer might represent a city boundary, an example of a polyline layer might include streets or rivers. The other options are not displayed on the dialog by default. If a specific registered type is selected, then other options related to that type may appear such as the Facility Name Field option associated with the School Boundary registered type.

Multipoint Type
Using OmegaGIS, a multipoint type layer is generated by the Repeat Calls routine. The layer identifies the source of multiple crimes. The Metadata Editor options available to this type of layer include the registered type, the default field and the repeat calls report option.

OmegaGIS Metadata Editor Dialog
The Metadata Editor has a number of settings that attach metadata information to the data selected in ArcCatalog. Layer Settings, Query Groups and OmegaGIS fields are represented by three tabs available at the top of the dialog. By clicking on each of these tabs, metadata for each of these categories can be set. The Query Groups and OmegaGIS Fields tabs are not available to polygon, polyline or multipoint layers. In addition, if the Student registered type is selected, then additional tabs specifically related to student metadata used by SchoolPlanner™ will appear. For more information on the SchoolPlanner™ metadata, see the SchoolPlanner
™ section in this document.

Layer Settings
Registered Type

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
A layer's registered type assigns the layer to a user specified category. The default registered types available for point layers include Incident, Student, Station, Person and Other, while polygon layers may be assigned to the Census_Blockgroup, Census_Block, Census_Tract, or Other layer types. In the event that additional types are required, the user may type them into the text box that provides the predefined list.

The benefit to assigning registered types arises when a project becomes complex with many different layers. Without the registered type, all layers are available to OmegaGIS routines regardless of whether or not they are compatible with the type of analysis to be performed. By adding a registered type to layers in a project, the layer list is limited to only those layers appropriate to the selected routine. Options are available in OmegaGIS Setup to determine whether to use the
registered type to limit the layer list, as well as to select which registered layer type(s) to use.

It is important to note that if the option in OmegaGIS Setup is selected to limit the layer lists on OmegaGIS dialogs, only layers of registered types will be shown. All other layers are omitted from the lists.

Default Field
The default field is automatically selected by OmegaGIS routines if it is set in the Metadata Editor. It applies to boundary layers, where the 'By Field Value' option is used to select polygons in the layer based on a particular field in the attribute table. Setting the default field in advance bypasses the need to select the field of interest each time a new routine is run.

Setting the default field becomes especially efficient when there are a large number of fields within the layer to sort through.

Default Incident Graph Field
The default incident graph field is used as the default field when creating graphs for an incident layer. The default field is set automatically if it can be found. If not found, each time a graph is created, a field must be selected in order to identify the data that should be graphed.

Registered Crystal Reports
The reports referred to in the Metadata Editor are designed in Crystal Reports to display information contained in the data layers. These reports can be viewed through the 'Create Reports' tool available on the OmegaGIS Toolbar in
ArcMap. However, they must already be registered to the appropriate layer.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
When registering reports using the Metadata Editor, one or more report may be selected for a single layer. The 'Add' button on the Layer Settings tab can be used to browse for reports that have been created for the layer of interest.

Notice that in the figure below, the path to the report is not saved. The default location for reports in within the project workspace \reports folder. For instance, in the project C:\MyProject, the default report folder is C:\MyProject\Reports.

If additional report locations are required, OmegaGIS Setup can be used to create these search locations. For instance, the 'Create Report' tool must find the report selected in order to display it. Since the report path is not saved with the report name, the first location searched is the default report location within the project workspace \reports folder. If the report is not located, each subsequent path in the OmegaGIS Setup Crystal Report list is searched.

Repeat Calls Report
The Repeat Calls Report is used exclusively for layers that have the 'Repeat Calls' report registered to them. A layer may be registered with this report either through the OmegaGIS Metadata Editor, or automatically when it is created with the OmegaGIS Repeat Calls routine. The result of the routine is a multipoint layer that identifies the locations of multiple incidents. The new layer contains the 'Repeat Calls Report' metadata as it is copied over from the layer on which the analysis was based.

Density Map Report
A Density Map Report can be registered to any polygon layer using the Density Map Report setting. This setting replaces the 'Repeat Calls Report' setting when the Metadata Editor is opened while a polygon feature class is selected.

Registering a Density Map Report to a polygon layer, ensures that the report can be opened through the 'Create Reports' tool when the appropriate polygon layer is selected.

Query Groups
A query group is a container housing related queries that are commonly used with OmegaGIS routines. Query groups are designed during the initial stages of a project, and can be created using the 'Saved Queries' tool found in the OmegaGIS Data Manager extension in ArcCatalog. All of the OmegaGIS routines use the Saved Queries tree to display query groups.

When a layer is selected for use in an OmegaGIS routine, the query groups registered to the layer are displayed.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
To access and link the query groups to a layer, a reference must be made to the Saved Query Database. The database is commonly located in the project folder. For instance, the database for C:\MyProject is found in the same folder; C:\MyProject. The reference is created by clicking on the 'Reference Database' button within the Query Groups tab of the OmegaGIS Metadata Editor.

Once a database is selected, the query groups found within the database are listed in the Query Groups window. Clicking on these query groups registers them to the selected layer, and makes them available in the Saved Queries Tree during an OmegaGIS routine.

OmegaGIS Fields
OmegaGIS fields are used to query data based on date ranges or response times. OmegaGIS fields can only be created using Import Wizard or the Omega Field Manager
. Legacy fields such as cvDate and cvTime created in the 3.x product can be used with Omega routines, however they will not show up as options in the OmegaGIS Default Field lists in the MetaData Editor. Multiple date and time fields are supported; the Metadata Editor allows the user to select a default date, time, response time, and response time 2 field that will be used with OmegaGIS routines.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
SchoolPlanner™ Metadata
The SchoolPlanner™ registered types include Student, Housing, and School field options for point layers, and School Boundary and Census types for polygon layers. Census registered types have been further refined to selections of Census_Block, Census_Blockgroup, and Census_Tract in order for Omega routines to differentiate between the layers use.

SchoolPlanner™ Layer Settings
School Boundary (Polygon)
If the School Boundary registered type is selected then an additional field to enter the Facility Name Field will appear.

This field is used throughout OmegaGIS routines primarily for reporting considerations.

Census_Block, Census_Blockgroup, Census_Track (Polygon) Census layers do not require the registration of additional metadata information outside of the default polygon information, which includes the default field and an optional density map report.

Student (Point)
When a student layer is registered, aside from requiring the default point layer information, a Student Fields tab will also activate. Since the student layer is used in many SchoolPlaner™ routines, both analysis and reporting, additional metadata information is required. Fields that must be entered are marked by being contained within the Required section. These fields include:

Numeric Grade Field containing the grade of the student.

Attending School Name Field containing the name of the students school of attendance.

Descriptive Grade Field containing the description of the grade of the student (ie: Kindergarten for 0).

Student Year The applicable academic year of the student data (ie: 2004-05). The entry must be in the hyphenated format "yyyy-yy" in order to validate, where yyyy is the full first year and yy are the last two digits of the second year.

Minimum Grade The minimum grade of the students used in the field. The minimum value for all of the

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
The optional fields and reports should be set if available or as needed since the presence of their values will simplify the operation of Omega routines. Optional fields include:

Crystal reports (rpt extension) can be associated with the student layer to allow for rapid reporting of different common tasks. Add a report by browsing to its location by pressing the Add button next to the report and selecting it from the file browser. When the file has been added, it will appear in the box beside the report. To remove the report simply press the remove button associated with the report. The reports that can be associated with a layer include the Residing Report, Attending Report, Residency Report, Redistricting Scenario Report, and the Redistricting Boundary Report.

Additionally for student layers, the option to register a Student Concentration Report will appear under the Layer Settings tab.

Housing (Point)
students will be automatically calculated when the Numeric Grade Field is entered. The value can be adjusted for reporting and analysis purposes in order to use a subset of the available grades if necessary.

Maximum Grade The maximum grade of the students used in the field. The maximum value for all of the students will be automatically calculated when the Numeric Grade Field is entered. The value can be adjusted for reporting and analysis purposes in order to use a subset of the available grades if necessary.

Ethnicity Field containing the ethnicity of the student. Used primarily for reporting.

Student ID Field containing the Student ID number of the student. Used primarily for reporting.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Registering a layer as housing will activate an additional Housing Fields tab. This tab will allow the entry of metadata that will record additional fields used by OmegaGIS analysis and reporting routines. These include the Student Generation Rate field, the Development Name Field, and fields to indicate up to five years of data to base housing based trend analysis on. There is also a field that will allow the name of the developer to be recorded.

School (Point)
No additional information is required outside the default information for a regular point layer if a layer is registered as a School layer.

OmegaGIS Stylesheet
Stylesheets are documents that enable the display of metadata in different styles. They are similar to queries in that they work on the same information, but the output of the data can be viewed in alternate formats. There are a number of stylesheets provided with ArcCatalog. To view the stylesheets, select a dataset in ArcCatalog, click on the Metadata tab, then click on the Stylesheet listbox available on the ArcCatalog toolbar.

OmegaGIS Stylesheet Overview
The Project XML
OmegaGIS Stylesheet
Update Information
Dataset Date Range
Report Information
Import Profile
OmegaGIS Fields
Geocoding Information
Output Information
SQL Query Information

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
The Project XML
The OmegaGIS stylesheet is provided as a part of OmegaGIS. The stylesheet reads information in the project's XML document and displays it in a standard format. The project's XML document is located in the project folder and carries the same name as the project. For example, if the project is called MyProject.mxd, and is located in the c:\MyProject folder, the XML document is c:\MyProject\MyProject.xml.

Each time an OmegaGIS routine is run, the project XML document is updated with specific information recorded by the routine. This information is used to reset the dialog selections when the dialog is opened the next time. In this way, updating all of the settings on the dialog each time a routine is run is avoided. The following figure provides an example of the information that is recorded in the project XML document during an Exception Reporting routine.

The project XML document can be viewed in Internet Explorer by double-clicking on the document name in Windows Explorer. Editing the document in any way is not a good idea, as an invalid format cannot be read by the OmegaGIS stylesheet. If the XML document does not exist, or is damaged in any way, it can be deleted as it is recreated automatically by the OmegaGIS routines.

OmegaGIS Stylesheet
File Location
Stylesheets used in ArcGIS must all be located in the ArcGIS stylesheet folder. This folder is found in c:\arcgis\arcexe82 \metadata\stylesheets where arcexe82 represents the version of ArcGIS. In upgrading ArcGIS from 8.2 to 8.3, it becomes apparent that the location of the stylesheets is changed slightly. Instead of being located under the \arcexe82 branch of ArcGIS, it is now located under \arcexe83.

For this reason, OmegaGIS automatically loads the OmegaGIS stylesheet into the appropriate folder based on the current version of ArcGIS. This process takes place both when OmegaGIS is installed as well as when the OmegaGIS Metadata Editor is opened. If for some reason, the OmegaGIS.xsl file is missing from the \arcexe* folder, and is not copied automatically, it can be manually copied from the OmegaGIS installation folder; c:\program files\omegagis\common\style
Setting a Default Stylesheet
To set the OmegaGIS stylesheet as the default, click on the Tools menu, select 'Options', and choose the Metadata tab.

Select 'OmegaGIS' from the drop-down list as the default stylesheet.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Viewing the OmegaGIS Stylesheet
To access the OmegaGIS stylesheet, click on OmegaGIS in the stylesheet list if it has not already been set as the default.

The format of the OmegaGIS stylesheet follows that of the FGDC ESRI stylesheet. The only difference is the addition of the OmegaGIS tab which displays OmegaGIS specific information. The following sections provide a brief description of the metadata that the OmegaGIS stylesheet provides.

Update Information
In setting up a project, an import process can be created to retrieve records automatically from a source database. The Omega Import Wizard is used to generate this process. Update Information provides the date and time of the last data import, as well as the number of new records added.

Dataset Date Range
While using the Import Wizard to process data, an option can be set to search the layer for the range of dates that have been imported. The date range can then be used by the Omega Date-Time dialog to automatically update the calendars with the available dates. The format of the date is yyyyMMdd.

Report Information
Report information summarizes layer metadata that has been set using the OmegaGIS Metadata Editor <LINK>.

Descriptions of Registered Reports, Query Groups, Registered Type, and the Label Field are all outlined in the OmegaGIS Metadata Editor document.

Import Profile
The information in the Import Profile section of the stylesheet is compiled by the Import Wizard. When an import profile is created, the following information is updated:

ID

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
The ID is generated automatically by the Omega Import Wizard. It uniquely identifies an Import Profile.

Name
The Name refers to the name of the Import Profile, entered when the Profile is first created with the Omega Import Wizard.

Type
There are two types of connections that can be made when creating an Import Profile. The type is identified either as a 'Database Connection' or a 'Text Import'.

Version
The version information is a reflection of the Revision History available in the Profile Overview of the Import Wizard. The version number is automatically updated as changes are made to the Import Profile.

OmegaGIS Fields
OmegaGIS Fields are used by the Date-Time dialog in OmegaGIS routines to determine date and time ranges.

OmegaGIS Fields are created using the OmegaGIS Field Manager in the Omega Data Manager extension in ArcCatalog.

The name, type, source field and whether the field is selected as the default are listed in a table in the stylesheet.

Geocoding Information
Geocoding Service
In this section of the stylesheet, Geocoding Services and Geocoding Statistics are defined for the layer. Geocoding Services refer to the process used to convert non-spatial information into spatially referenced data that can be used in spatial analysis.

The first column in the table identifies the name of the Geocoding Service. A Geocoding Service is created in ArcCatalog where a name is assigned to the service. The second column of the table shows the geocoding service style used to create the geocoding service. There are numerous geocoding service styles including 'Single Field' and 'US Streets'.

Within the address field of a dataset, various text characters are used to represent street intersections. When designing a Geocoding Service, Intersection Connectors, are those textual delimiters that create the intersection in the address. More than one connector can be incorporated into a Geocoding Service.

Geocoding Statistics
When a layer is geocoded against a source dataset, it is rarely the case that all records are matched up to a source location. In many cases, the address may not be found, in which case the record is not given a feature on the map.

Understanding Geocoding Statistics is important when trying to identify why features are missing from the new layer, even though they have been imported by the Import Wizard process.

A quick overview of geocoding statistics is possible with the OmegaGIS stylesheet. The following statistics are valid for the last time the import process was run.

Overall Match Rate
The overall rate is the number of records matched divided by the total number of records processed.

Matched
This statistic refers to the number of records matched to an address.

Unmatched
Unmatched refers to the number of records that could not be matched to an address or a coordinate.

XY Coordinate Match
The XY Coordinate Match is the number of records matched to an XY coordinate.

Total Features
This statistic refers to the total number of features processed.

Output Information

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
As data is retrieved from the source database or text file using the Omega Import Wizard, it is processed, and output into a new file. There are several methods of moving the data to the new dataset. Each of these Output Types can be identified with a number between 0 and 6. The number indicates the way in which new features are appended to the dataset.

It is extremely important to recognize the difference between Output Types, as the type used to process the records can produce very different results. The Output Types available in the Omega Import Wizard are outlined below.

New Feature Class [0]:

Creates a new feature class. Will not overwrite an existing feature class.

Replace Feature Class [1]:

Deletes the existing feature class, if any, and then creates a new feature class.

Append Only [2]:

Appends records to an existing feature class; no duplicate records are removed. If the existing feature class is not found then a new one is created.

Remove Duplicate Records [3]:

Removes duplicate records in the feature class that is being appended to based on a primary key. Once the duplicate records are removed, the new records are appended. If the existing feature class is not found then a new one is created.

Remove Duplicate Records with Date Range [4]:

Removes duplicate records in the feature class that is being appended to based on a primary key. Once the duplicate records are removed, the new records are appended. If the existing feature class is not found then a new one is created. After the appending process, the feature class is queried to remove old records based on a date range.

Append Only with Date Range [5]:

Appends records to an existing feature class; no duplicate records are removed. If the existing feature class is not found then a new one is created. After the appending process, the feature class is queried to remove old records based on a date range.

Truncate Feature Class [6]:

Deletes all records from an existing feature class, if any, and then inserts the new records. This output type should be used with a feature class stored in ArcSDE rather than the Replace Feature Class output type.

SQL Query Information
If a database connection is used to extract records from the source database, the SQL statement can be viewed from the OmegaGIS stylesheet. The SQL statement is valuable if field names or tables change in the source database. The statement can be reviewed and compared to the source database to catch any revisions made to the source.

OmegaGIS Fields Manager
The OmegaGIS Fields Manager creates OmegaGIS fields used with the date and time Query dialog. The OmegaGIS Fields Manager can convert a user specified source field to a new field with the format required by OmegaGIS routines.

In most cases Omega Import Wizard is used to create OmegaGIS fields; this tool has been developed to aid in creating these same fields in a non-automated fashion.

OmegaGIS Fields

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Adding, Removing and Updating OmegaGIS Fields
Adding an OmegaGIS Field
Removing an OmegaGIS Field
Updating an OmegaGIS Field
OmegaGIS Fields
The OmegaGIS Fields Manager provides a means to add, edit and delete OmegaGIS Fields. An OmegaGIS Field is defined by metadata found in the XML that is associated with the dataset. To view a dataset's metadata, select the data in question in the ArcCatalog table of contents. When the data is selected, use the drop-down stylesheet list box and select the XML option.

A stylesheet is a tool for viewing XML tags. There are many variations of stylesheets available that display the XML tags in different formats. The XML stylesheet displays the XML metadata tags without modification. Once the XML stylesheet is selected, the right side of the window displays the metadata tags. OmegaGIS fields can be identified as those tags that occur within the
'theomegagroup\importwizard\omegagisfields' XML node.

For each OmegaGIS field, a name, type, source, format, description and a tag that indicates whether the field is set as the default are stored. It is very important that the information within this XML document only be modified using the OmegaGIS Field Manager or the OmegaGIS Metadata Editor. Attempting to modify the information without these tools may corrupt the data.

Note: In the ArcView 3.x version of Omega products an OmegaGIS field was identified by name as 'cvDate', 'cvTime' or 'cvDOW'. The limitation on this form of identification was that only one field could be used by OmegaGIS routines to identify date and time ranges. The fields created in the 3.x product cannot be used in the new product as OmegaGIS fields. Use the 'Add a new OmegaGIS Field' option in the OmegaGIS Fields Manager to recreate these fields.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Adding, Removing and Updating OmegaGIS Fields
The OmegaGIS Field Manager provides a means for adding, editing or removing an existing OmegaGIS field. The utility is provided on the OmegaGIS Data Manager extension in ArcCatalog. This tool is only available to those datasets with point feature geometry. While clicking on different datasets, the Fields Manager tool is either enabled or disabled depending on the feature geometry of the dataset selected.

When the OmegaGIS Fields Manager dialog is opened, three options are presented to the user; Add, Remove or Update an OmegaGIS field.

Adding an OmegaGIS Field
Field Type
If the 'Add a new OmegaGIS Field' option is selected, clicking on the 'Next' button opens a dialog that presents a list of OmegaGIS field types that can be created. The list includes 'Date', 'Time', 'Response Time' and 'Response Time 2' fields.

The first step in defining a new OmegaGIS field is to select the field type to create. The field types available are described below.

Date
Selecting the 'Date' type creates a new OmegaGIS field formatted as an eight character numeric field. The format is as follows: yyyyMMdd. Once created, the new date field can be used to select dates from the calendars on the Date/Time dialog which is common to many routines.

Time
The 'Time' field type creates a string field of four characters formatted as 'hhmm'. The new OmegaGIS time field can be used to select from the drop-down lists on the Date/Time dialog which is common to many routines.

Response Time
The 'Response Time' field type generates a new OmegaGIS response time field using a start time field and an end time

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
field found in the data. The response time is created as a number with two decimal places. During the calculation of the response time if the two years are found to be different between the start and end time, and the time duration is greater than four hours, the response time is set to zero.

Response Time 2
The 'Response Time 2' field that is generated also uses a start time field and an end time field to calculate a response time. The difference in the values of this numeric field is that it contains no decimal places.

Day of Week
The 'Day of Week' field is calculated in conjunction with the 'Date' type field. When the 'Date' type is selected, a check box becomes available that provides the option to calculate the 'Day of Week' field. This field contains an integer between 0 and 6 that represents which day of the week the date of the incident falls on. 0 represents Sunday, 1 represents Monday ... 6 represents Saturday.

Field Name
A new name must be entered for the OmegaGIS field. If the field name is already in the dataset, or it is an OmegaGIS reserved field name or a SQL reserved word, a warning is issued to the user when the tool is run. SQL reserved words include 'Date', 'Time', 'Update' and 'Select'. Additional SQL reserved words depend upon the dataset selected. Check the ArcGIS documentation for more detail. A list of OmegaGIS reserved field names is provided below. l iwStandard
l iwGeoName
l iwStep
l iwGeoSteps
l OmegaGIS_Source
l OmegaGIS_Count
l OmegaGIS_Density
l Omega_Difference
l Omega_Expected
l Omega_RespTime
l Omega_Station
l Omega_NetworkID
Source Field
In addition to the Field Type tab, the information on the Source Field tab must be filled out in order to move to the next step in the Field Manager. The source field identifies which field values will be used to generate the new OmegaGIS field values. The fields available in the OmegaGIS Source Field list are those fields that have a character or numeric data type in the data layer selected. When a source field is selected from the list, the 'Sample Value' textbox is populated with a sample value from the data layer. The sample value is found by searching through the first 100 records in the data for the first non-null value.

The 'Sample Value' is important in that it provides an example of the data so that a format may be selected from the 'Format' list box. The 'Format' is necessary so that the OmegaGIS Fields Manager can modify the original data into the format required by OmegaGIS routines. A 'Test' button is available in order to check quickly whether the format selected matches the data in the selected source field.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
The elements of a date-time format are described in the table below. The delimiter for the date-time value may be any value.

A list of the supported date and time formats are shown below. The currently supported formats are the ones Omega most commonly encounters and this list will continue to grow in the future. The formats that are displayed are dependant on the field format of the source field. For example, if the source field is a numeric date field then only the 'Numeric' date formats will be displayed in the field format drop down list.

Date Formats:

Time Formats:

Element Description
y year
M month
d day
h hour
m minute
s second
Source Field Type Format Example
Text yyMMdd 030131
Text yyyyMMdd 20030131
Text yyyy-MM-dd 2003-01-31
Text MMddyy 013103
Text M-dd-yy 1-31-03
Text MM-dd-yy 01-31-03
Text M-dd-yyyy 1-31-2003
Text MM-dd-yyyy 01-31-2003
Numeric yyMMdd 030131
Numeric yyyyMMdd 20030131
Date & Text MM-dd-yyyy hhmm 01-31-2003 1233
Date & Text yyyy-MM-dd hh:mm:ss OR
yyyy-MM-dd hh:mm:ss.sss
2003-01-31 1:33:29
2003-01-31 1:33:29.334
Date & Text M-dd-yy h:mm:ss AM 1-31-03 1:33:29 AM
Source Field Type Format Example
Text hhmm 0534
Text hmm 534
Text hhmmss 053428
Text h:mm 5:34
Text hh:mm 05:34
Text h:mm:ss 5:34:28
Text hh:mm:ss 05:34:28
Numeric hhmm 0534

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Summary
The 'Next' button becomes available when all of the information necessary to calculating the new field has been entered.

The Summary dialog is opened before the processing begins. The Summary dialog provides a review of the data that will be used to generate the new OmegaGIS Field
Adding the New Field
Clicking the 'Finish' button on the Summary dialog starts the data processing. The information provided is first validated to ensure that the new OmegaGIS field will contain valid data. The field name entered is checked to ensure that it is not already in the dataset. The source field selected is checked to ensure that it can be found in the dataset, the format selected is tested against the sample data to ensure the results of the processing will be valid. Finally the new field name is checked to ensure that it is not a reserved OmegaGIS field name or a reserved SQL word.

Removing an OmegaGIS Field
An OmegaGIS field can be removed from a dataset using the 'Remove OmegaGIS Field' option in the OmegaGIS Fields Manager. The field name can be selected from a list of OmegaGIS fields. Once selected, the 'Next' button moves to the Summary dialog. Clicking on the 'Finish' button removes the field from the dataset permanently.

Step 1. Select the option
Date & Text MM-dd-yyyy hhmm 01-31-2003 0534
Date & Text yyyy-MM-dd hh:mm:ss 2003-01-31 05:34:28
Date & Text yyyy-MM-dd hh:mm:ss.sss 2003-01-31 05:34:28.123 Date & Text M-dd-yy h:mm:ss AM 2003-01-31 5:34:28 PM
Numeric hhmmss 053428

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Step 2. Select the field to remove
Step 3. Review the results and begin processing
Updating an OmegaGIS Field
Updating an existing OmegaGIS field enables the user to change the values of the field by selecting a new source field on which the new values can be based. For 'Date', 'Time' and 'Day of Week' fields, a new source must be selected as well as

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
the format that describes the source information. Updating a 'Response Time' or 'Response Time 2' field requires that a new start source field and end source field be identified as well as their formats.

Step 1. Select the Update option
Step 2. Select the field to update
Step 3. Review the information and process field
Omega Query Editor
Saved Queries are used in Omega software to allow fast construction of the most commonly queried data attributes. The

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
queries are based on the information contained in a feature class, which links geographic data to attribute data. By storing queries for commonly used categories, queries can be quickly constructed interactively through various Omega tools and menu interfaces by simply checking off the attributes instead of entering full SQL based queries.

The role of the Omega Query Editor is to facilitate the pre-entry of SQL based queries that will be used to parse full queries in the interactive environment. It also provides tools to facilitate the import of previously used Omega_Query.MDB (used in versions of Omega software prior to version 4.0) to the new Omega_Query.ODB files.

Through the use of a dynamic interactive environment, the need for previous knowledge of the underlying database structure used for Omega Saved Queries is minimized, instead saved queries can be created and ordered through the use of options menus and interactive SQL query builders. Once the queries are saved to the database, they will persist for future use in the saved query environment within Omega products.

Accessing the Omega Query Editor
The Omega Query Editor is accessed through ArcCatalog by selecting the Omega Query Editor button located on the OmegaGIS Data Manager toolbar.

The Omega Query Editor is only enabled when the OmegaGIS Data Manager extension is turned on. From the Extensions dialog in ArcCatalog, that is available from the Tools pull down menu. Check the OmegaGIS Data Manager extension to enable the Omega Query Editor. The OmegaGIS Data Manager requires that one of the following Omega Desktop extensions is licensed; CrimeView, FireView, School Planer or the Omega Import Wizard.

Startup Dialog
When the Omega Query Editor is opened from ArcCatalog the Startup dialog appears. This dialog provides a starting point in using the editor. There are three options:

Create a new Omega query database
Create an entirely new Omega_Query.ODB saved query database. The initial database will be empty and tools for both populating and setting database options will be available.

Upgrade from Omega_Query.MDB
Imports a legacy Omega_Query.MDB saved query database file (found with Omega Desktop products prior to version

4.0) to the new Omega_Query.ODB supported format.

Edit existing Omega query database
Opens an existing Omega_Query.ODB database for editing.

Upgrade Query Database
Omega Desktop version 4.0 includes a new format for the saved query database. This new format is required due to the new functionality that has been introduced that includes:
l Improved tools to create and edit saved queries.
l Support the display of the saved queries in columns that is required by the School Planner extension. l Support for more query groupings; the previous release only supports two while the version 4.0 release now supports 50.
l Improved trouble-shooting tools.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
l Future support for the file based Geodatabase that is to be released with ArcGIS 9.2.

The Omega Desktop version 4.0 can no longer use the old version of the saved query database, Omega_Query.MDB.

Consequently, a wizard has been included with the Omega Query Editor that will upgrade the legacy version to the new Omega_Query.ODB. The wizard is accessible from the Startup dialog.

Note: There is no ability to convert the Omega_Query.ODB file that is used at version 4.0 to an older version.

Legacy Saved Query Editor
The old version of the Saved Query Editor is installed with Omega Desktop version 4.0. The button to open the editor is not added automatically to the OmegaGIS Data Manager toolbar, but can be added manually by using the Customize dialog in ArcCatalog.

Outlined below are the steps to add to the legacy Saved Query Editor to ArcCatalog.

1. Open ArcCatalog.

2. Open the Customize dialog; select the "Customize" item that is available from the Tools pull down menu.

3. Select the "Commands" tab; it may take some time for the lists to populate.

4. In the Catalogs list, select "OmegaGIS_DataManager".

5. In the "Commands" list, drag the "Saved Queries Editor" item to an existing toolbar.

Note: Omega will provide limited support to the legacy Saved Query Editor; it is recommended the new Omega Query Editor be used in its place.

Upgrade Query Database Wizard

1. Location for New Database
Enter the path to the destination folder where the new Omega Query database will be generated. Select the folder by using the browse dialog or by typing in the path.

Once the destination folder is specified, press the Next button. When the Next button is selected, the following checks occur:
l The destination folder cannot already contain an existing Omega_Query.ODB file. l The destination folder must exist on disk.

Tip: Omega Desktop extensions in ArcMap search for the Omega query database by default in the project workspace folder. This folder has the same name as the ArcMap document and is located in the same folder as the document.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Upgrade Query Database Wizard

2. Database to Upgrade
Omega_Query.MDB File
Use the browse button to select the Omega_Query.MDB file is to be upgraded into the destination folder selected in the previous step.

Query Groups
When a legacy query database is selected, the query groups contained in the database are loaded into the list. Select the query groups which are to be imported by checking the box. By default, all of the query groups will be selected for the import process. At least one query group must be selected in order to import the database.

To move onto the next step, select the Next button.

Upgrade Query Database Wizard

3. Summary
The final step in updating a legacy saved query database displays a summary of the information collected by the wizard.

Review the information to ensure that it is correct. If any changes need to be made, use the Back button, otherwise press the Run button to perform the upgrade operation.

Upgrade Query Database Wizard
Upgrade Processing
After the parameters have been collected from the wizard dialogs, the Omega Query Editor will upgrade the legacy saved query database to the new Omega_Query.ODB file.

Validation during upgrade
During the upgrade process, the following checks are made to ensure validity in the destination database including the following:
l Restricted characters ( < > ' ) are replaced with the underscore character ( _ ). l All query group names must be under 100 characters in length. l The query group name must not already be in use in the database (it must be unique). If it is found to already be in use, a unique name will be automatically reassigned to the query group.

Query Groupings
Previous releases of the saved query database only support two types of query groupings; primary and secondary.

During the import process, these two grouping types are created and the primary is set to be the default grouping.

The primary grouping is set with a black font color and the secondary is set with a blue color in order to easily differentiate between the different query groups. These settings can be changed through the Omega Query Editor.

About Omega Query Editor
The Omega Query Editor dialog is used to edit an existing Omega query database (Omega_Query.ODB file).

There are numerous panels that are available for editing. To navigate between the panels use the lists on the left side of the dialog. The panels are divided into two main sections:

Query Database
The options that are common to the Omega query database are divided into three panels that are always enabled.

Database

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Panel provides general information for the Omega query database and allows one to set a password.

Query Groups
This panel displays a list of all of the query groups that are contained within the database.

Utilities
The panel contains a list of utilities available for the Omega query database.

Query Group
Only one query group may be edited at a time. When editing a query group, the navigation list for the query groups is enabled. These panels have functionality that are specific to the query group being edited.

General
The panel contains information specific to the query group currently being edited.

Reference Data
Panel provides the ability to set reference to feature classes that are to be used in testing the attribute query syntax.

Query Grouping
The panel provides the ability to edit the query groupings.

Edit Queries
The panel allows one to create new saved queries or change how the saved queries are displayed to the user.

Columns
This panel provides the ability to organize the saved queries in columns.

The name of the query group that is currently being edited is provided on the status bar at the bottom of the dialog.

Edit Existing Query Database
To edit an existing Omega query database, from the startup dialog select the Edit existing Omega query database option.

There are two methods to select the Omega query database to edit:

Browse
Select the "Browse for database..." item in the list and then click the OK button. The browse dialog will open; from this dialog navigate to the Omega_Query.ODB file to edit. When the appropriate Omega_Query.ODB file is selected, click the Open button that will open the Omega Query Editor.

Recent database
Rather than browsing to an Omega_Query.ODB file, the list contains those databases that have been previously edited by the user currently logged into the computer. Up to eight databases are displayed. Only databases that are found on disk are displayed in the list.

Select a recently edited database in the list and then click the OK button to open the Omega Query Editor. Alternatively, double click the database in the list.

New Omega Query Database
A new Omega query database can be created with the wizard dialog. This dialog is accessed from the Startup dialog and
the Utility panel.

Outlined below are the steps in the wizard to generate a new Omega query database.

1. Location for new database
Provide the path to the folder where the new Omega query database is to be created. Either type in the path or browse

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
to the location.

The folder to create the Omega query database must exist and the folder must not already contain the Omega_Query.ODB file.

2. Summary
The final step in creating a new query database dispalys a summary of the information collected by the wizard. Review the information to ensure it is correct. If any changes need to be made, use the Back button, otherwise press the Run button to create the new database.

After the database has been created, the Omega Query Editor is opened.

Database Panel
The database panel provides generate information for the Omega query database and allows one set a password.

Database Description
The database description is for user defined information, such as the Omega client that database has been build for. The description is limited to 255 characters.

The description is saved to the Omega query database only when the database is saved.

Database Information
Database Version
Version of the Omega query database. Omega Desktop version 4.2 requires the Omega query database of version 4.0 or

4.1. Omega Desktop version 4.2 ships with the Omega query database template version of 4.1. Newly generated Omega
query databases use the template version 4.1. The only change with the version 4.1 template is that by default, the File Geodatabase field qualifier is used.

Date Edited
The date edited text box contains the date and time of when the last time the database has been saved.

Database Path
Path to the Omega_Query.ODB that is currently being edited.

Password Protection
A password can be set in order to prevent unauthorized use or alteration of the database. If a password is set, then the user will be prompted to enter the password whenever the Omega Query Editor is opened. If no password is entered or if an invalid password is entered, then an error will result and the Omega Query Editor will remain closed.

To set the password, click on the Set Password button. In the pop-up dialog, enter the desired password twice and press the OK button. Next time the Omega Query Editor is started, this password will need to be entered. The password must satisfy the following requirements:
l The Omega Query Editor password cannot contain any spaces. l The Omega Query Editor password must be 20 characters or less.

A password is not required in order to use the database with client applications, just to make changes through the editor.

Query Groups Panel
A query group is a collection of saved queries that are used to hide the creation of SQL attribute queries from users of

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Omega Desktop applications. A query group is registered to a feature class using the Omega Metadata Editor; this is how the Omega Desktop applications know which saved queries to display when the feature class is selected.

The Query Groups panel displays a list of all of the query groups that are contained in the database. A single Omega query database can contain up to 100 query groups.

The Query Groups panel contains the following functionality:

New
Edit
Copy
Append
Import
Remove
New
Creates a new query group in the database and starts an edit session for that new query group. A unique name for the query group is generated; the names of the query groups within the database must be unique.

Edit
For the selected query group in the list, starts an edit session. When a query group is being edited, the "Query Group" navigation items are enabled which allows for the editing of the query group.

If the Edit button is clicked and the selected query group is currently being edited, the General panel is displayed without reloading the query group information.

Copy
Entire query groups can quickly be copied from other Omega query databases (Omega_Query.ODB) by using the copy utility. When the Copy button is pressed, the Copy Query Group dialog is displayed that has the following parameters:

Omega query database
Use the browse button to select the database (Omega_Query.ODB) containing the query group to be copied.

Query group
Once the Omega query database has been selected, the list of query groups contained in the database is populated.

Select the query group to copied.

When the OK button is selected on the Copy Query Group dialog, the selected query group is automatically transferred to the current database. Once the transfer is completed, the newly copied query group is placed in an edit session.

The utility ensures that the name of the query group being imported is unique among the query groups in the database.

If the name of the query group is not unique, the name is automatically renamed.

During the transfer process, a new Query ID value is generated. The Query ID value to identify the saved queries selected with both the Cyclical Reports and Threshold Alert routines.

Append
Query Groups that are stored within the same Omega query database can be appended to each other. When the Append button is pressed, the Append Query Group dialog is displayed that has the following parameters:

Source query group
The drop down list contains all of the Query Groups located within the Omega query database currently being edited.

Select the Query Group to append. The selected Query Group is not altered.

Destination query group
The drop down list contains all of the Query Groups located within the Omega query database currently being edited except for the Query Group selected in the Source query group list. Select the Query Group to have saved queries appended to.

When the OK button is selected on the Append Query Group dialog, the selected source Query Group is appended to the destination Query Group. During this process, the following occurs:
l The Query Groupings
from the source Query Group are copied to the destination Query Group. There is a check to ensure that the name of the query grouping is unique among the query groupings in the destination Query Group; when the name is not unique it is automatically renamed. The default query grouping in the destination Query

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Group is not altered.
l The saved queries from the source Query Group are appended to the bottom of the existing saved queries in the destination Query Group.
l All saved queries are given a new unique Query ID value. l Any Query Viewer Columns or Exclude Saved Queries identified in the source Query Group are not copied to the destination Query Group.
l The attribute syntax of all of the saved queries from the source Query Group are verified using the reference data of the destination Query Group.

After the append process is completed, the destination Query Group is made editable.

Import
Opens the wizard that creates a query group from a pre-existing MS Access database table.

Remove
Removes the selected query group from the Omega query database. Once removed, the query group cannot be retrieved.

Utilities Panel
The Utilities panel contains the functionality outlined below.

New Database
Opens a wizard that creates a new Omega query database.

Compact Database
Edits to the Omega query database may result in an increase of the Omega_Query.ODB file size. The "Compact Database" utility attempts to reduce the size of the Omega_Query.ODB file.

To compact the Omega query database currently being edited, select the Compact button.

Export to Web.config XML
The utility exports a single query group to an XML file. The format of the query group within the XML file is the same used by Omega web applications (version 1.0).

To export a query group from the current Omega query database, select the Export button.

General Panel
The General panel contains information specific to the query group currently being edited.

Query group name
Query Group ID
Description
Statistics
Save edits
Query group name
The name of the query group can be altered. This name is registered in the metadata of the feature class for which the query group contains the saved queries for.

Before the query group information is saved to the database, there are the following checks:
l The name is 100 characters or less.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
l A name is provided. Both the leading and trailing spaces are removed. When no name is provided, a name is automatically provided.
l Invalid characters are replaced with an underscore character "_". These characters include "<", ">" and single quotes.
l The name is unique among the query groups in the database. When the name is not unique, the query group is not saved to the database and there is a message displayed.

Query Group ID
The read-only ID for the query group. This ID used by Omega Desktop when constructing the SQL query syntax.

Additionally, this ID is required for assigning query groups to a layer that is used in an Omega Server application.

Description
User defined description of the query group. The name is limited to 255 characters. When no name is provided, the word "Required" is automatically entered when the changes are saved to the database.

At the Omega Desktop version 4.0 release, the description is only seen within the Omega Query Editor.

Statistics
Statistics are displayed for the saved queries contained within the query group and are useful to get an overview of the status of the saved queries.

The statistics are calculated when the query group is first loaded and after the edits are saved to the Omega query database.

The statistics include the following information:

Total saved queries
Includes those saved queries that lack an attribute query; these are the saved queries that appear as a folder in the tree view.

Format details
For each of the supported formats, Personal Geodatabase, ArcSDE, File Geodatabase and shapefile, the number of saved queries with an attribute query and their status.

Valid - attribute query has been tested and it successfully selected at least one feature.

Warning - When the attribute query has a warning, it has either been tested and no records were selected or the attribute query has not been tested as there was no reference data to test against.

Error - There is an error with the attribute query.

No attribute query - The attribute query is missing for the format.

Save edits
All edits made to the query group are not persisted to the Omega query database until the Save button is selected.

Failing to save before exiting the Omega Query Editor will result in all edits being lost.

The File pull down menu also contains a Save menu item that also saves the query group.

Reference Data Panel
Reference data is used to test the attribute query syntax while editing the saved queries.

Add Reference
To add reference to a feature class, select the browse button and then navigate to the feature class. When the feature class is selected, the following checked:
l Geometry of point.
l Valid feature class.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Note: The ArcGIS 9.2 release introduced the File Geodatabase. One of the changes that also occurred was that when one browses for a Personal Geodatabase feature class, one is also able to select a File Geodatabase. When adding reference to a feature class stored in a Personal Geodatabase, there is a check of the source format after the feature class is selected to ensure it is a Personal Geodatabase.

After the feature class has been referenced, the field qualifiers are updated but not whether or not to use those field qualifiers.

Remove Reference
To remove the reference to a feature class, simply click the Remove button.

Missing Reference
Adding reference to the feature class does not alter the feature class; the Omega query database only stores information on how to find the feature class. When the Query Group is opened in an edit session, reference is made to the feature classes. If the feature class cannot be found, such as when it has been renamed, there is a red exclamation mark beside the path to the workspace. The tool tip contains the information on why the feature class could not be found.

When the reference to the feature class is missing, one will not be able to open the Query Builder dialog or verify the attribute query syntax.

Field Qualifiers
The Field Qualifiers button opens the Field Qualifiers dialog.

Query Grouping
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.

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 groups 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.

New Query Grouping
To add a new query grouping, press the New button. The bottom of the Query Grouping panel contains the details for the new query group. The following items may be edited for the query grouping:

Grouping Name
The name must be unique among all other query groupings for the query group being edited. The name must also not contain single quotes.

Text Color
The text color is used in the tree view to assist in easily identifying different query groupings. Click the color button to open the color picker dialog. This dialog is used by ArcGIS to select colors. The "No color" option is not supported; consequently when this option is selected, the text color is changed to black.

Default Grouping
One query grouping must be set to the default grouping; the first grouping created is always set as the default. When a new saved query is created in the editor, it is assigned to the default query grouping.

The edits to the query grouping details are not updated until the Apply button is selected.

Removing a Query Grouping
To remove a query grouping, select the grouping in the list and press the remove button.

When a query grouping is removed, a check is performed to determine if any saved queries have been assigned to the query grouping. Since all saved queries must be assigned to a query grouping, a new query grouping has to be assigned. This is done with a dialog that provides a list of all of the query groupings excluding the one to remove.

If the default query grouping is removed, the first query grouping in the list is set as the default query grouping.

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Edit Queries
The Edit Queries panel allows one to create new saved queries or change how the saved query is displayed to the user.

The saved queries are displayed in a tree on the left side of the Edit Queries panel. The details of the selected saved query node are displayed on the right side of the panel.

View of saved Queries
Saved Query Status
Toolbar
Saved Query Details
View of Saved Queries
The saved queries are displayed on the left side of the Edit Queries panel. How those saved queries are presented is based on the View. The View is controlled by the drop down list on the toolbar.

Outlined below are the different views available.

Tree View
This view displays all the saved queries in an expandable list. This view illustrates the presentation of the saved queries in Omega Desktop applications and shows a hierarchical relationship between the saved queries. Three levels of saved queries are supported.

While in the tree view, all of the functionality provided on the toolbar is available. This includes; add a new saved query, editing, cut-copy-paste and changing the location of the saved query node.

Query Grouping
In Query Grouping view, the saved queries are divided into their query groupings . Although the saved queries can be
edited, the saved query nodes cannot be moved or removed.

All formats - Errors & Warnings
All saved queries that have either an error or warning associated with the attribute query syntax for any of the support formats are displayed in the tree. Although the saved queries can be edited, the saved query nodes cannot be moved or removed.

When all of the issues have been resolved for a saved query, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

All formats - Errors
Displays a list of all the saved queries that have outstanding errors with the attribute query syntax for any of the supported formats. The saved queries can be edited but the saved query nodes cannot be moved or removed.

When all of the issues have been resolved for a saved query, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

Personal GDB - Errors & Warnings
Displays a list of all the saved queries that have outstanding errors or warnings associated with their Personal Geodatabase feature class attribute queries. The saved queries can be edited but the saved query nodes cannot be moved or removed.

When all of the problems with the personal Geodatabase attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

ArcSDE - Errors & Warnings
Displays a list of all the saved queries that have outstanding errors or warnings associated with their ArcSDE feature class attribute queries. The saved queries can be edited but the saved query nodes cannot be moved or removed.

When all of the problems with the ArcSDE attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

Shapefile - Errors & Warnings
Displays a list of all the saved queries that have outstanding errors or warnings associated with their shapefile feature

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
class attribute queries. The saved queries can be edited but the saved query nodes cannot be moved or removed.

When all of the problems with the shapefile attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

File GDB - Errors & Warnings
Displays a list of all the saved queries that have outstanding errors or warnings associated with their File Geodatabase feature class attribute queries. The saved queries can be edited but the saved query nodes cannot be moved or removed.

When all of the problems with the File Geodatabase attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

Personal GDB - Errors
Displays a list of all the saved queries that have outstanding errors associated with their Personal Geodatabase feature class attribute queries.

When all of the problems with the Personal Geodatabase attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

ArcSDE - Errors
Displays a list of all the saved queries that have outstanding errors associated with their ArcSDE attribute queries.

When all of the problems with the ArcSDE attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

Shapefile - Errors
Displays a list of all the saved queries that have outstanding errors associated with their shapefile attribute queries.

When all of the problems with the shapefile attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

File GDB - Errors
Displays a list of all the saved queries that have outstanding errors associated with their File Geodatabase attribute queries.

When all of the problems with the File Geodatabase attribute query are resolved, the icon of the saved query node is updated but the saved query remains in the tree until the tree is reloaded.

Saved Query Status
The saved query nodes displayed in the tree on the left side of the Edit Queries dialog have an icon that provides information on the status of the attribute query.

Query Group
Name of the query group which can be edited on the General panel .

Folder
Saved query node that lacks an attribute query. Only level 1 and 2 saved queries can be a folder as level 3 saved queries must include an attribute query.

Valid Query
The attribute query is valid. The attribute query has been tested; the query was successful and at least one feature was selected.

Valid Query with Warnings
The attribute query is valid but there is a warning. The warning is issued if the attribute query has not be tested with the reference data or the attribute query was tested and no records were selected.

Query with Error
The attribute query is invalid. This error occurs when the attribute query is tested and returns an error or no syntax has been provided for the format.

When the saved queries are displayed in a view that is feature class specific, such as Shapefile Errors, the status of the saved query is based on that feature class format. Otherwise, the status is based on all of the formats; the most severe status being used as the saved query node icon.