MN007396A01 D Enus PremierOne GIS Configuration Guide

PremierOne™
GIS Configuration Guide

System Release: 4.6.13
NOVEMBER 2023 *MN007396A01*

© 2023 Motorola Solutions, Inc. All Rights Reserved. MN007396A01-D
MN007396A01-D
Intellectual Property and Regulatory Notices
Intellectual Property and Regulatory

Notices
Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola Solutions
computer programs. Laws in the United States and other countries preserve for Motorola Solutions
certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola Solutions
computer programs contained in the Motorola Solutions products described in this document may not be
copied or reproduced in any manner without the express written permission of Motorola Solutions.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into
any language or computer language, in any form or by any means, without the prior written permission of
Motorola Solutions, Inc.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the
property of their respective owners.
License Rights
The purchase of Motorola Solutions products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola Solutions,
except for the normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a
product.
Open Source Content

This product may contain Open Source software used under license. Refer to the product installation media
for full Open Source Legal Notices and Attribution content.
European Union (EU) and United Kingdom (UK) Waste of Electrical and Electronic
Equipment (WEEE) Directive
The European Union's WEEE directive and the UK's WEEE regulation require that products sold into
EU countries and the UK must have the crossed-out wheelie bin label on the product (or the package in some
cases). As defined by the WEEE directive, this crossed-out wheelie bin label means that customers and
end-users in EU and UK countries should not dispose of electronic and electrical equipment or accessories in
household waste.
Customers or end-users in EU and UK countries should contact their local equipment supplier representative
or service centre for information about the waste collection system in their country.
Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable
to or licensed for use on a specific system, or may be dependent upon the characteristics of a specific mobile
subscriber unit or configuration of certain parameters. Please refer to your Motorola Solutions contact for
further information.
© 2023 Motorola Solutions, Inc. All Rights Reserved
2
MN007396A01-D
Contact Us
Contact Us
The Centralized Managed Support Operations (CMSO) is the primary contact for technical support included
in your organization's service agreement with Motorola Solutions.
Service agreement customers should be sure to call the CMSO in all situations listed under Customer
Responsibilities in their agreement, such as:
● To confirm troubleshooting results and analysis before taking action
Your organization received support phone numbers and other contact information appropriate for your
geographic region and service agreement. Use that contact information for the most efficient response.
However, if needed, you can also find general support contact information on the Motorola Solutions website,
by following these steps:
1. Enter motorolasolutions.com in your browser.
2. Ensure that your organization's country or region is displayed on the page. Clicking or tapping the name
of the region provides a way to change it.
3. Select "Support" on the motorolasolutions.com page.
Comments
Send questions and comments regarding user documentation to documentation@motorolasolutions.com.
Provide the following information when reporting a documentation error:
● The document title and part number
● The page number or title of the section with the error
● A description of the error
Motorola Solutions offers various courses designed to assist in learning about the system. For information, go
to https://learning.motorolasolutions.com to view the current course offerings and technology paths.
3
MN007396A01-D
Document History
Document History
The following changes were made to this document:
Version Description Date

MN007396A01-001 Initial release of the PremierOne GIS Configuration August 2020
Guide Version 4.6.0.
MN007396A01-002 Initial release of the PremierOne GIS Configuration January 2023
Includes updated formatting and updates to Installing
ArcGIS Pro on page 122.
MN007396A01-003 Initial release of the PremierOne GIS Configuration April 2023

Includes updates to:
● Uninstalling Previous Versions of PremierOne Data
Import Tools on page 23
● Common Place Name Aliases on page 54
● Floor-Specific Layer Additions to a PremierOne Map
on page 61
● Importing Contractor Boundaries on page 75
● Importing Feature Classes on page 95
● CostAttributes Modification on page 96
● Creating GIS Server Connections on page 107
● Modifying Layer Connectivity Properties on page
114
● Added Changing the Route To Settings on page 116
● Mobile Clients Map Data Sources on page 170
● Author Mobile Client Maps on page 170
MN007396A01-D Initial release of the PremierOne GIS Configuration November 2023

● Updated Verification by Location and City Only on
page 176
4
MN007396A01-D
Contents
Contents
Intellectual Property and Regulatory Notices................................................................... 2
Contact Us............................................................................................................................3
Document History................................................................................................................4
List of Figures.................................................................................................................... 10
List of Tables......................................................................................................................14
List of Procedures............................................................................................................. 15
About PremierOne GIS Configuration Guide.................................................................. 18
Chapter 1: Geospatial Data in PremierOne......................................................................20
1.1 Services Data...................................................................................................................................20
1.1.1 Services Data Import..........................................................................................................20
1.1.2 Services Data for Mobile Client..........................................................................................20
1.2 Routing Data and Map Data............................................................................................................ 20
1.2.1 Routing Data Generation................................................................................................... 20
1.2.2 Client Data Maps................................................................................................................21
1.2.3 Routing and Map Data for Mobile Client............................................................................ 21
1.3 Premise/Hazards Data.....................................................................................................................21
1.3.1 Premise/Hazards Data Importation.................................................................................... 21
1.3.2 Premise/Hazards Data for Mobile Client............................................................................ 21
1.3.3 Production and Staging Databases....................................................................................21
1.4 Establishing a General Workflow for GIS Data................................................................................ 22
Chapter 2: PremierOne Data Import Tools Installation...................................................23
2.1 Uninstalling Previous Versions of PremierOne Data Import Tools................................................... 23
2.2 Installing PremierOne Data Import Tools......................................................................................... 23
2.3 Adding PremierOne Data Import Tools to ArcToolbox..................................................................... 24
2.4 Disabling Background Geoprocessing.............................................................................................25
Chapter 3: GIS Validator Tools..........................................................................................27
3.1 Adding GIS-Validator Tools to the PremierOne Toolbox.................................................................. 27
3.2 Address Point Validator....................................................................................................................27
3.2.1 Executing the Address Point Validator............................................................................... 28
3.2.2 Correcting Duplicate Address Points................................................................................. 30
3.3 Common Place Validator..................................................................................................................32
3.3.1 Executing the Common Place Validator.............................................................................32
3.3.2 Correcting Duplicate Common Places............................................................................... 35
3.4 Street Centerline Validator............................................................................................................... 36
5
MN007396A01-D
Contents
3.4.1 Executing the Street Centerline Validator...........................................................................36

3.4.2 Overlapping Street Centerlines Correction Overview........................................................ 38
3.4.2.1 Correcting Overlapping Street Centerlines...........................................................39
3.4.3 Street Centerline Validator Errors.......................................................................................40
3.5 Tools Assignment.............................................................................................................................41
3.5.1 Assigning City Names to Streets........................................................................................41
3.5.2 Assigning City Names to Points......................................................................................... 42
Chapter 4: GIS Data Import into PremierOne.................................................................. 44
4.1 Supplemental Tables Creation......................................................................................................... 44
4.1.1 Creating File Geodatabases.............................................................................................. 44
4.1.2 Importing the Support Geodatabase Schema....................................................................46
4.1.3 Adding Support Data Using ArcMap.................................................................................. 49
4.1.4 Support Geodatabase Data Import Overview.................................................................... 49
4.1.4.1 Importing Data into Support Geodatabases......................................................... 50
4.1.5 Common Place Name Aliases........................................................................................... 54
4.1.6 Standardization Exceptions................................................................................................55
4.1.7 Street Name Aliases.......................................................................................................... 56
4.1.8 Street Types....................................................................................................................... 57
4.1.9 Creating Staging Geodatabases........................................................................................ 57
4.1.10 Importing Staging Geodatabase Schema........................................................................ 58
4.1.11 GIS Data Import................................................................................................................60
4.1.12 Floor-Specific Layer Additions to a PremierOne Map...................................................... 61
4.1.13 Importing Street Centerlines............................................................................................ 61
4.1.14 Address Point Import Tool Overview................................................................................ 65
4.1.14.1 Importing Address Points................................................................................... 66
4.1.15 Importing Common Place Points......................................................................................68
4.1.16 Response Boundaries Import Tool Overview................................................................... 71
4.1.16.1 Importing Response Boundaries........................................................................ 71
4.1.17 Reporting District Import Tool Overview...........................................................................73
4.1.17.1 Importing Reporting Districts.............................................................................. 73
4.1.18 Contractor Boundary Import Tool..................................................................................... 75
4.1.18.1 Importing Contractor Boundaries....................................................................... 75
4.1.19 Importing Warrant Districts...............................................................................................77
4.1.20 Importing Map Books....................................................................................................... 79
4.1.21 Importing Cellular Towers.................................................................................................80
4.1.22 Importing Motorway Junctions......................................................................................... 82
4.1.23 Creating PremierOne Mobile Client Data Packages........................................................ 83
4.1.24 Copying GIS Data to the Enterprise Database................................................................ 85
4.1.25 Premise Hazard Area Import Tool.................................................................................... 87
6
MN007396A01-D
Contents
4.1.25.1 Creating Premise Hazard Area Feature Classes............................................... 88

4.1.25.2 Populating Premise Hazard Area Feature Classes............................................88
4.1.25.3 Importing Premise Hazard Areas Layers........................................................... 88
4.1.26 Network Dataset Creation................................................................................................ 90
4.1.27 Travel Costs Calculation Overview.................................................................................. 90
4.1.27.1 Creating Average Speed Columns..................................................................... 91
4.1.27.2 Creating Cost Columns...................................................................................... 94
4.1.28 Network Dataset Source Data Overview..........................................................................95
4.1.28.1 Copying Feature Classes................................................................................... 95
4.1.28.2 Importing Feature Classes................................................................................. 95
4.1.29 Network Dataset XML Specification Configuration.......................................................... 95
4.1.29.1 Network Dataset Attributes Modification............................................................ 95
4.1.29.2 EdgeSource Attributes Modification................................................................... 96
4.1.29.3 CostAttributes Modification.................................................................................96
4.1.29.4 RestrictionAttributes Modification....................................................................... 98
4.1.29.5 Directions Attributes Modification....................................................................... 99
4.1.29.6 Verifying XML Files...........................................................................................100
4.1.30 Creating Building Network Datasets.............................................................................. 100
4.1.31 ArcCatalog New Network Dataset Wizard Overview..................................................... 102
4.1.32 Verifying Network Datasets Using ArcMap.................................................................... 102
4.1.33 Model Creation to Import Data....................................................................................... 105
Chapter 5: Introduction to ArcGIS Server......................................................................106
5.1 ArcGIS Server User Security......................................................................................................... 106
5.2 GIS Server Connections Overview................................................................................................ 106
5.2.1 Creating GIS Server Connections....................................................................................107
5.3 Accessing Server Managers...........................................................................................................111
Chapter 6: Network Analyst Service Publication.......................................................... 113
6.1 Publishing a Network Analyst Service............................................................................................113
6.2 Modifying Layer Connectivity Properties........................................................................................114
6.3 Changing the Route To Settings.....................................................................................................116
6.4 Publishing Network Analyst Services.............................................................................................117
Chapter 7: Mobile Map Packages for Mobile Map......................................................... 122
7.1 Installing ArcGIS Pro......................................................................................................................122
7.2 ArcGIS Pro Licensing Overview.....................................................................................................122
7.3 Initializing ArcGIS Pro Projects...................................................................................................... 123
7.4 SQL Queries Overview.................................................................................................................. 124
7.5 Basemaps...................................................................................................................................... 125
7.6 Network Analyst Support Additions................................................................................................125
7
MN007396A01-D
Contents
7.6.1 Defining Global Turn Delays............................................................................................ 125

7.6.2 Creating Network Dataset Layers.................................................................................... 127
7.7 Creating Address Locators............................................................................................................ 128
7.8 Creating Mobile Map Packages..................................................................................................... 130
7.9 Mobile Map Package Deployment................................................................................................. 131
Chapter 8: Map Authoring Requirements for PremierOne CAD and Mobile Clients. 132
8.1 Relative File Paths Overview......................................................................................................... 132
8.1.1 Enabling Relative Paths................................................................................................... 132
8.1.2 Relative File Path Data Sourcing Examples.................................................................... 133
8.2 Raster Data Overview....................................................................................................................135
8.3 Efficient Maps Overview.................................................................................................................135
8.3.1 Setting Scale Levels at Which Layers Should be Drawn................................................. 135
8.3.2 Specifying Definition Queries........................................................................................... 136
8.3.3 Creating Attribute Indexes................................................................................................137
8.3.4 Feature Classes Reuse Example.....................................................................................138
8.3.5 Simple Symbols Usage.................................................................................................... 139
8.3.6 Features Labels............................................................................................................... 140
8.3.6.1 Dynamic Labels vs. Annotation.......................................................................... 140
8.3.6.2 Enabling Dynamic Labels for Map Layers..........................................................140
8.3.6.3 Setting Placement Properties.............................................................................141
8.3.6.4 Label Scale Levels............................................................................................. 144
8.3.6.5 Label Classes.....................................................................................................144
Chapter 9: CAD Client Maps............................................................................................148
9.1 CAD Client Map Data Sources...................................................................................................... 148
9.2 ArcGIS Server Services................................................................................................................. 148
9.2.1 Mapping Services.............................................................................................................149
9.2.1.1 Advantages of Cached Map Services................................................................ 149
9.2.1.2 Disadvantages of Cached Map Services........................................................... 149
9.2.2 Provisioning CAD Map Auto Zoom Levels....................................................................... 149
9.2.3 Creating Cache Tiling Scheme Files................................................................................ 150
9.2.4 Publishing the Dynamic Mapping Service........................................................................151
9.2.5 Creating Cached Mapping Services.................................................................................154
9.2.5.1 Publishing Mapping Services............................................................................. 154
9.2.5.2 Analyzing Map Documents.................................................................................157
9.2.5.3 Configuring Cache Settings................................................................................158
9.2.6 Publishing Services..........................................................................................................160
9.2.7 Building Caches............................................................................................................... 160
9.2.8 Exporting Caches.............................................................................................................161
9.2.9 Mapping Service Publication on PremierOne GIS Virtual Machines................................163
8
MN007396A01-D
Contents
9.2.9.1 Importing Caches............................................................................................... 163

9.2.10 Overwriting Existing Mapping Services..........................................................................165
9.2.11 Restarting Services on a PremierOne GIS Virtual Machine........................................... 167
9.2.12 Adding Mapping Service Layers.................................................................................... 168
Chapter 10: Mobile Client Maps and Data Overview.....................................................170
10.1 Mobile Clients Map Data Sources................................................................................................170
10.2 Stage Map Data........................................................................................................................... 170
10.3 Author Mobile Client Maps...........................................................................................................170
10.4 Exporting Enterprise GIS Data.....................................................................................................170
Chapter 11: Address Verification Basics....................................................................... 173
11.1 Address Validation in PremierOne............................................................................................... 173
11.2 Default Behavior of Location Fields..............................................................................................174
11.2.1 Location Field................................................................................................................. 174
11.2.2 Subdivision and City Field.............................................................................................. 174
11.2.3 Apartment and Building Field......................................................................................... 175
11.2.4 Location Name Field.......................................................................................................175
11.2.5 Description......................................................................................................................175
11.2.6 Floor............................................................................................................................... 176
11.2.7 Zip Code.........................................................................................................................176
11.3 Default Behavior Modification of Address Verification..................................................................176
11.3.1 Disabling Automatic Address Verification....................................................................... 176
11.3.2 Verification by Location and City Only............................................................................176
11.3.3 Base Address Point Use When Apartment/Building Match is not Found....................... 177
11.3.4 Base Address Point Use as the Endpoint When Routing Units to Incidents or
Destinations......................................................................................................................... 177
11.3.5 Other Address Verification Settings................................................................................178
9
MN007396A01-D
List of Figures
List of Figures
Figure 1: ArcCatalog – Add Tool Dialog Box.................................................................................................... 25
Figure 2: Address Point Validator Dialog Box...................................................................................................28
Figure 3: Address Point Validator Report Dialog Box....................................................................................... 30
Figure 4: Address Point Validator Dialog Box...................................................................................................31
Figure 5: Common Place Validator Dialog Box.................................................................................................33
Figure 6: Common Place Select By Attribute Dialog Box................................................................................. 35
Figure 7: Street Centerline Validator.................................................................................................................37
Figure 8: Street Centerline Query Dialog Box.................................................................................................. 40
Figure 9: Assign City Names to Streets............................................................................................................42
Figure 10: Assign City Names to Points........................................................................................................... 43
Figure 11: ArcCatalog – Create File Geodatabase...........................................................................................45
Figure 12: ArcCatalog – Naming Database...................................................................................................... 45
Figure 13: ArcCatalog – Create PremierOne Geodatabase............................................................................. 46
Figure 15: ArcCatalog – PremierOne Geodatabase Contents......................................................................... 48
Figure 16: ArcCatalog – Simple Data Loader Wizard Dialog Box.................................................................... 50
Figure 17: ArcCatalog – Simple Data Loader Input Data Dialog Box............................................................... 51
Figure 18: ArcCatalog – Simple Data Loader Subtypes Dialog Box.................................................................52
Figure 19: ArcCatalog – Simple Data Loader Field Mappings Dialog Box....................................................... 53
Figure 20: ArcCatalog – Simple Data Loader Query Dialog Box......................................................................54
Figure 21: ArcCatalog – New File Geodatabase.............................................................................................. 57
Figure 22: ArcCatalog – Naming New File Geodatabase.................................................................................58
Figure 24: ArcCatalog – Create PremierOne Geodatabase Execution Dialog Box..........................................59
Figure 25: ArcCatalog – Refreshed PremierOne Geodatabase....................................................................... 60
Figure 26: ArcCatalog – Street Centerline Import Tool..................................................................................... 62
Figure 27: ArcCatalog – Street Centerline Import Tool Progress Dialog Box................................................... 64
Figure 28: ArcCatalog – Address Point Import Tool..........................................................................................66
Figure 29: ArcCatalog – Address Point Import Tool Progress Dialog Box........................................................68
Figure 30: ArcCatalog – Common Place Import Tool....................................................................................... 69
Figure 31: ArcCatalog – Common Place Import Tool Progress Dialog Box......................................................71
Figure 32: ArcCatalog – Response Boundary Import Tool............................................................................... 72
Figure 33: ArcCatalog – Response Boundary Import Tool Progress Dialog Box..............................................73
Figure 34: ArcCatalog – Reporting District Import Tool.................................................................................... 74
Figure 35: ArcCatalog – Reporting District Import Tool Progress Dialog Box...................................................75
Figure 36: ArcCatalog – Contractor Boundary Import Tool...............................................................................76
10
MN007396A01-D
List of Figures
Figure 37: ArcCatalog – Contractor Boundary Import Tool Progress Dialog Box............................................. 77
Figure 38: ArcCatalog – Warrant District Import Tool....................................................................................... 78
Figure 39: ArcCatalog – Warrant District Import Tool Progress Dialog Box......................................................78
Figure 40: ArcCatalog – Map Book Import Tool................................................................................................79
Figure 41: ArcCatalog – Map Book Import Tool Progress Dialog Box.............................................................. 80
Figure 42: ArcCatalog – Cell Tower Import Tool............................................................................................... 81
Figure 43: ArcCatalog – Cell Tower Import Tool Progress Dialog Box............................................................. 81
Figure 44: ArcCatalog – Motorway Junction Import Tool.................................................................................. 82
Figure 45: ArcCatalog – Motorway Junction Import Tool Progress Dialog Box................................................ 83
Figure 46: ArcCatalog – Create Mobile Client Data Package Dialog Box........................................................ 84
Figure 47: PremierOne Provisioning Console – GIS Data................................................................................85
Figure 48: Copy Geodatabase to SQL Server Import Tool............................................................................... 86
Figure 49: Copy CopyStagingToSql Dialog Box............................................................................................... 87
Figure 50: ArcCatalog – Premise Hazard Area Import Tool..............................................................................89
Figure 51: ArcCatalog – Premise Hazard Area Import Tool Progress Dialog Box............................................90
Figure 52: ArcCatalog – ArcMap Open Attribute Table.....................................................................................91
Figure 53: ArcCatalog – ArcMap Attribute Table.............................................................................................. 92
Figure 54: ArcCatalog – ArcMap Add Field...................................................................................................... 92
Figure 55: ArcCatalog – ArcMap Add Field Properties.....................................................................................93
Figure 56: ArcCatalog – ArcMap Select by Attributes...................................................................................... 93
Figure 57: ArcCatalog – ArcMap Field Calculator............................................................................................ 94
Figure 58: ArcCatalog – Create Network Dataset Import Tool........................................................................101
Figure 59: ArcCatalog – Create Network Dataset Import Tool Progress Dialog Box......................................101
Figure 60: ArcCatalog – ArcMap Add Data.................................................................................................... 102
Figure 61: ArcCatalog – ArcMap Add Data.................................................................................................... 103
Figure 62: ArcCatalog – ArcMap New Route..................................................................................................104
Figure 63: ArcCatalog – ArcMap Create Network Locations.......................................................................... 104
Figure 64: ArcCatalog – ArcMap Network Directions..................................................................................... 105
Figure 65: ArcGIS Server Ports – F5 Connections.........................................................................................107
Figure 66: ArcGIS Desktop – Add ArcGIS Server Role Select.......................................................................108
Figure 67: ArcGIS Desktop – Server User Connection Properties................................................................. 109
Figure 68: ArcGIS Server Manager – Login.................................................................................................... 111
Figure 69: ArcGIS Server Manager – Services...............................................................................................112
Figure 70: ArcMap – Network Analyst Toolbar................................................................................................113
Figure 71: ArcMap – Network Analyst Map.....................................................................................................114
Figure 72: Network Analyst Layers................................................................................................................. 114
Figure 73: ArcMap Layer Properties – Network Locations..............................................................................115
Figure 74: Layer Properties Window - Analysis Settings Tab......................................................................... 116
Figure 75: ArcMap – Share As Service...........................................................................................................117
11
MN007396A01-D
List of Figures
Figure 76: ArcMap – Share as Service Dialog Box.........................................................................................118

Figure 77: Overwrite An Existing Service Dialog............................................................................................ 119
Figure 78: Publish Service from Service Definition File..................................................................................120
Figure 79: Publishing a Service Dialog...........................................................................................................121
Figure 80: My Esri Downloads Page.............................................................................................................. 122
Figure 81: ArcGIS Pro – Start Without A Template.........................................................................................123
Figure 82: ArcGIS Pro – Add Folder Connection............................................................................................124
Figure 83: ArcGIS Pro – Select Global Turn Delay.........................................................................................126
Figure 84: ArcGIS Pro – Define Global Turn Delay........................................................................................ 126
Figure 85: Geoprocessing Tools – Analysis – Tools....................................................................................... 127
Figure 86: Geoprocessing Tools – Make Network.......................................................................................... 127
Figure 87: Make Network Dataset Layer Wizard............................................................................................ 127
Figure 88: Search For Create Address Locator Tool...................................................................................... 128
Figure 89: Create Locator Wizard...................................................................................................................129
Figure 90: Search For Create Mobile Map Package Tool...............................................................................130
Figure 91: Create Mobile Map Package Tool..................................................................................................131
Figure 92: ArcMap – Map Document Properties............................................................................................ 133
Figure 93: ArcCatalog – Relative File Path Example......................................................................................134
Figure 94: ArcMap – Layer Properties............................................................................................................136
Figure 95: ArcMap – Layer Properties (Definition Query Tab)........................................................................137
Figure 96: ArcToolbox – Add Attribute Index.................................................................................................. 138
Figure 97: ArcMap – Layer Properties (Labels Tab)....................................................................................... 141
Figure 98: ArcMap – Placement Properties....................................................................................................142
Figure 99: ArcMap – Label Placement Properties (Conflict Detection).......................................................... 143
Figure 100: ArcMap – Place Overlapping Labels........................................................................................... 144
Figure 101: ArcMap – Remove Duplicate Labels (No Overlapping)...............................................................145
Figure 102: ArcMap – Label Class................................................................................................................. 146
Figure 103: ArcMap – Label Class SQL Query.............................................................................................. 146
Figure 104: ArcMap – Label Class SQL Query.............................................................................................. 147
Figure 105: ArcToolbox – Generate Map Server Cache Tiling Scheme......................................................... 150
Figure 106: ArcMap – Share as Service.........................................................................................................151
Figure 107: ArcMap – Share as Service Dialog Box...................................................................................... 152
Figure 108: Overwrite An Existing Service Dialog.......................................................................................... 153
Figure 109: ArcMap – Share as Service Dialog..............................................................................................154
Figure 110: Share as Service Dialog Box....................................................................................................... 155
Figure 111: Overwrite An Existing Service Dialog...........................................................................................156
Figure 112: Publish a Service Dialog..............................................................................................................157
Figure 113: ArcMap – Service Editor Caching Advanced Settings Tab.......................................................... 159
Figure 114: ArcGIS Desktop – Manage Tiles..................................................................................................160
12
MN007396A01-D
List of Figures
Figure 115: Windows Explorer – Cache Folder.............................................................................................. 161

Figure 116: Export Map Server Cache dialog.................................................................................................162
Figure 117: Import Map Server Cache Dialog.................................................................................................164
Figure 118: Share As Service Menu............................................................................................................... 165
Figure 119: Share as Service Dialog – Overwrite An Existing Service........................................................... 166
Figure 120: Overwrite An Existing Service Dialog.......................................................................................... 167
Figure 121: Restarting A Service From The Catalog Window........................................................................ 168
Figure 122: ArcMap – Add Service Layer.......................................................................................................169
Figure 123: ArcCatalog – Create Mobile Client Deployment Package........................................................... 171
Figure 124: ArcCatalog – Create Mobile Client Data Package.......................................................................172
13
MN007396A01-D
List of Tables
List of Tables
Table 1: Cost Value Calculation Formulas........................................................................................................ 94
Table 2: ArcGIS Server Ports..........................................................................................................................107
Table 3: ArcGIS Server Connection Information.............................................................................................109
14
MN007396A01-D
List of Procedures
List of Procedures
Establishing a General Workflow for GIS Data ................................................................................................22
Uninstalling Previous Versions of PremierOne Data Import Tools ...................................................................23
Installing PremierOne Data Import Tools ......................................................................................................... 23
Adding PremierOne Data Import Tools to ArcToolbox ..................................................................................... 24
Disabling Background Geoprocessing .............................................................................................................25
Adding GIS-Validator Tools to the PremierOne Toolbox .................................................................................. 27
Executing the Address Point Validator .............................................................................................................28
Correcting Duplicate Address Points ............................................................................................................... 30
Executing the Common Place Validator ...........................................................................................................32
Correcting Duplicate Common Places .............................................................................................................35
Executing the Street Centerline Validator ........................................................................................................ 36
Correcting Overlapping Street Centerlines ...................................................................................................... 39
Assigning City Names to Streets ..................................................................................................................... 41
Assigning City Names to Points .......................................................................................................................42
Creating File Geodatabases ............................................................................................................................ 44
Importing the Support Geodatabase Schema ................................................................................................. 46
Adding Support Data Using ArcMap ................................................................................................................49
Importing Data into Support Geodatabases .................................................................................................... 50
Creating Staging Geodatabases ......................................................................................................................57
Importing Staging Geodatabase Schema ........................................................................................................58
Importing Street Centerlines ............................................................................................................................ 61
Importing Address Points .................................................................................................................................66
Importing Common Place Points ..................................................................................................................... 68
Importing Response Boundaries ..................................................................................................................... 71
Importing Reporting Districts ........................................................................................................................... 73
Importing Contractor Boundaries .....................................................................................................................75
Importing Warrant Districts .............................................................................................................................. 77
Importing Map Books .......................................................................................................................................79
Importing Cellular Towers ................................................................................................................................ 80
Importing Motorway Junctions ......................................................................................................................... 82
Creating PremierOne Mobile Client Data Packages ........................................................................................83
Copying GIS Data to the Enterprise Database ................................................................................................ 85
Creating Premise Hazard Area Feature Classes .............................................................................................88
Populating Premise Hazard Area Feature Classes ......................................................................................... 88
Importing Premise Hazard Areas Layers .........................................................................................................88
Creating Average Speed Columns .................................................................................................................. 91
15
MN007396A01-D
List of Procedures
Creating Cost Columns ....................................................................................................................................94

Copying Feature Classes ................................................................................................................................ 95
Importing Feature Classes ...............................................................................................................................95
Verifying XML Files ........................................................................................................................................ 100
Creating Building Network Datasets .............................................................................................................. 100
Verifying Network Datasets Using ArcMap .................................................................................................... 102
Creating GIS Server Connections ................................................................................................................. 107
Accessing Server Managers .......................................................................................................................... 111
Publishing a Network Analyst Service ............................................................................................................113
Modifying Layer Connectivity Properties ........................................................................................................114
Changing the Route To Settings .................................................................................................................... 116
Publishing Network Analyst Services .............................................................................................................117
Installing ArcGIS Pro ..................................................................................................................................... 122
Initializing ArcGIS Pro Projects ......................................................................................................................123
Defining Global Turn Delays .......................................................................................................................... 125
Creating Network Dataset Layers ..................................................................................................................127
Creating Address Locators ............................................................................................................................ 128
Creating Mobile Map Packages .....................................................................................................................130
Enabling Relative Paths .................................................................................................................................132
Setting Scale Levels at Which Layers Should be Drawn ...............................................................................135
Specifying Definition Queries .........................................................................................................................136
Creating Attribute Indexes ............................................................................................................................. 137
Enabling Dynamic Labels for Map Layers ..................................................................................................... 140
Setting Placement Properties ........................................................................................................................ 141
Defining Label Classes .................................................................................................................................. 145
Configuring Label Classes for Specific Map Scales ...................................................................................... 147
Provisioning CAD Map Auto Zoom Levels .....................................................................................................149
Creating Cache Tiling Scheme Files ..............................................................................................................150
Publishing the Dynamic Mapping Service ..................................................................................................... 151
Creating Cached Mapping Services .............................................................................................................. 154
Publishing Mapping Services .........................................................................................................................154
Analyzing Map Documents ............................................................................................................................ 157
Configuring Cache Settings ........................................................................................................................... 158
Manually Specifying Scale Levels ................................................................................................................. 159
Publishing Services ....................................................................................................................................... 160
Building Caches .............................................................................................................................................160
Exporting Caches .......................................................................................................................................... 161
Importing Caches ...........................................................................................................................................163
Overwriting Existing Mapping Services ......................................................................................................... 165
16
MN007396A01-D
List of Procedures
Restarting Services on a PremierOne GIS Virtual Machine .......................................................................... 167

Adding Mapping Service Layers .................................................................................................................... 168
Exporting Enterprise GIS Data ...................................................................................................................... 170
Disabling Automatic Address Verification ...................................................................................................... 176
17
MN007396A01-D
About PremierOne GIS Configuration Guide
About PremierOne GIS Configuration

Guide
This document is intended for use by personnel who are responsible for the system administration of the
PremierOne applications. System administration requires an understanding of both current agency system
administration rules and procedures, and how PremierOne functions.
A Geographic Information System (GIS) is a collection of hardware and software components that collect,
manage, analyze, and display information associated with a specific location.
GIS collects four categories of geospatial data in PremierOne:
● Services data – Services data is accessed using PremierOne application services. This data is in a
schema that is optimized for use such as address verification, geocoding, and response determination.
This data is not intended to be displayed on a map for visualization by dispatchers or mobile users
because it is in a specialized schema.
● Routing data – Access Routing data through an ArcGIS Server Routing Service to calculate driving
directions and calculate estimated travel times of emergency responders.
● Premise/Hazards data – Access Premise/Hazards data using PremierOne application services. When a
PremierOne user creates a Premise Hazard record, related information is stored in spatially aware tables.
● Map data – Map data is any data that exists specifically to be displayed on a map.
Your GIS system may vary from the system depicted in this document. Because PremierOne systems are
highly configurable, many factors can cause them to vary, such as licensing, state and local requirements,
agency preferences, and system configuration and customization.
Related Information
For the latest version of this guide and all guides, go to: https://learning.motorolasolutions.com/.
For associated information, refer to the following table:
Related Information Purpose

PremierOne CAD User Guide Explains how to initiate and dispatch incidents and manage
agency resources and information using PremierOne CAD.
PremierOne Mobile Windows User Describes features include messaging, dispatch integration, in-
Guide vehicle reporting, emergency notification, unit status monitors,
database queries, and incident initiation with the PremierOne
Mobile Windows tool.
PremierOne CAD and Mobile Provi- Provides information on PremierOne CAD and Mobile Provi-
sioning Guide sioning (a tool used to properly configure all of the aspects
of PremierOne CAD and Mobile, including agencies, the com-
mand line, mapping, messaging, queries, units, and more).
Technical Support
You can obtain 24/7 support by phone from Technical Support at 1-800-MSI-HELP. International customers,
call 1-302-444-9800.
Have the following information ready:
● Product name and version number
18
MN007396A01-D
About PremierOne GIS Configuration Guide
● Description of the problem (Exact wording of any messages appearing on your screen)
● What you were doing when the problem occurred
● Steps you took to try to solve the problem
● Hardware description
19
MN007396A01-D
Chapter 1: Geospatial Data in PremierOne
Chapter 1
Geospatial Data in PremierOne

PremierOne geospatial data includes Services data, Routing data, and Premise/Hazards data. Production
and staging databases are used for GIS data.
1.1
Services Data
Services data is accessed through the PremierOne application services. This data is in a schema that is
optimized for use such as address verification, geocoding, and response determination. This data is not
intended to be displayed on a map for visualization by dispatchers or mobile users because it is in a
specialized schema.
1.1.1
Services Data Import
Services data is imported into a staging geodatabase through the use of the PremierOne Data Import tools
– custom geoprocessing tools that integrate with the ESRI ArcGIS Desktop application. After PremierOne
Data Import tools generate the data, it gets copied into an SQL server enterprise database. For more detailed
information about importing services data, see GIS Data Import into PremierOne on page 44.
1.1.2
Services Data for Mobile Client
A subset of the services data generated by PremierOne Data Import tools must be deployed to PremierOne
Mobile Clients so that certain GIS functions can be performed when the mobile client is offline. After deployed
to a Mobile client, the data resides in SQL Express databases.
1.2
Routing Data and Map Data
Routing data is accessed using PremierOne application services. This data is used to calculate driving
directions and calculate estimated travel times of emergency responders. It consists of a Geodatabase
network dataset and its data sources. Map data is used for displaying geographic features on the CAD and
Mobile Mapping Clients.
1.2.1
Routing Data Generation
Routing data is imported into a file geodatabase through the use of the PremierOne Data Import tools. After
PremierOne Data Import tools generate the data, the GIS administrator creates a routing service map using
the file geodatabase as its data source and then publishes/updates a routing service to the ArcGIS Server.
For additional information about importing routing data, see Travel Costs Calculation Overview on page 90.
20
MN007396A01-D
1.2.2
Client Data Maps
The CAD and Mobile Mapping Clients consume ArcMap Map Documents (*.mxd files) to display a map. It is
recommended that maps used by the CAD Clients be sourced from ArcGIS Server Mapping Services and/or
File Geodatabases. Maps used by Mobile Clients should be sourced from File Geodatabases only.
1.2.3
Routing and Map Data for Mobile Client
The routing data generated by PremierOne Data Import tools and the source data used in the Map
Documents (*.mxd files) must be deployed to PremierOne Mobile clients so that mapping and routing
functions can be performed when the mobile client is offline. After the data is deployed to a mobile client, it
resides in a file geodatabase.
1.3
Premise/Hazards Data
Premise/Hazards data is accessed using PremierOne application services. When a PremierOne user creates
a Premise/Hazard record, related information is stored in spatially-aware tables.
1.3.1
Premise/Hazards Data Importation
Premise/Hazards data (with the exception of Premise/Hazard Areas) is not imported from offline sources
like services and routing data. It is only created, updated, and deleted through the use of the PremierOne
Provisioning Console and clients.
1.3.2
Premise/Hazards Data for Mobile Client
The request to calculate Premise/Hazards hits takes place on the PremierOne application server. However, to
support the client map and to support calculating hits and displaying attachments when offline, the Premise/
Hazards data must be deployed to PremierOne Mobile clients. After the data is deployed to a Mobile client,
the data resides in SQL Express. For more information, see Exporting Enterprise GIS Data on page 170.
1.3.3
Production and Staging Databases
Performing GIS updates for PremierOne requires the existence of two enterprise (SQL) GIS databases:
a production database and a staging database. At any given time, one GIS database is in production –
meaning the GIS services are using that database as the data source. The other database is considered the
staging database where the next set of GIS is imported and staged for quality assurance purposes. After the
quality assurance process is complete on the staging database, a Provisioning Console user can perform a
database switch in which the staging database becomes the production database and the former production
database becomes the staging database to be used to stage the next set of GIS data. These databases are
commonly referred to as the A and B databases. At any given time, either the A database is the production
(active) database and the B database is the staging (inactive) database, or the B database is the production
(active) database and the A database is the staging (inactive) database.
21
MN007396A01-D
The GIS services have access to connection settings for both databases. These settings are specified in
the PremierOne Server Configuration tool. The GIS services determine which database is active when each
service request is received and performs database actions against that database.
1.4
Establishing a General Workflow for GIS Data
The following list describes a general workflow for importing GIS data, preparing data for deployment and
service publishing, and deployment of GIS data and map document files:
Procedure:
1. Create a staging file geodatabase.
For details, see Creating Staging Geodatabases on page 57.
2. Import GIS data into the staging file geodatabase using PremierOne Data Import Tools.
For details, see Support Geodatabase Data Import Overview on page 49.
3. Copy data from the staged geodatabase to the enterprise SQL server using PremierOne Data Import
Tools.
For details, see Copying GIS Data to the Enterprise Database on page 85.
4. Create a file geodatabase (version 10.8.1) for service publishing and Mobile client use.
For details, see Creating File Geodatabases on page 44.
5. Publish the ArcGIS Server Network Analysis service for CAD.
For details, see Publishing Network Analyst Services on page 117.
6. Publish the ArcGIS Server Map Services for CAD, if desired.
For details, see ArcGIS Server Services on page 148.
7. Create the CAD and Mobile map documents.
For details, see Map Authoring Requirements for PremierOne CAD and Mobile Clients on page 132.
8. Export the GIS data for Mobile clients using PremierOne Data Import tools.
For details, see Exporting Enterprise GIS Data on page 170.
9. Deploy the CAD maps.
For details, see CAD Client Maps on page 148.
10. Deploy the Mobile maps, file geodatabase (containing ROUTING and MAP_LAYERS feature
datasets), and exported data.
For details, see Mobile Client Maps and Data Overview on page 170.
22
MN007396A01-D
Chapter 2: PremierOne Data Import Tools Installation
Chapter 2
PremierOne Data Import Tools

Installation
The Data Import tools installer must be run and the tools added to ArcGIS desktop before GIS data can be
imported into PremierOne.
NOTE: Data Import tools should be installed/upgraded with each CAD upgrade. Contact Motorola for
the new Data Import tools installer appropriate for the CAD build. New GIS-related functionality may not
be available until data is imported using the version of Data Import tools appropriate for the CAD build.
2.1
Uninstalling Previous Versions of PremierOne
Data Import Tools
The current PremierOne system requires ArcGIS v10.8.1 and an updated version of ArcGIS Import Tools.
NOTE: Any previous versions of PremierOne Data Import tools must be uninstalled before uninstalling
a previous version of ArcGIS Desktop. Failure to do so will prevent the previous version of PremierOne
Data Import Tools from being uninstalled.
Procedure:
1. From the Start menu, in the Search programs and files field, type Uninstall.
2. Select Uninstall a Program.
3. Select PremierOne Import Tools.
4. Click Uninstall.
NOTE: You must uninstall the PremierOne Import tool prior to upgrading the ArcGIS software.
2.2
Installing PremierOne Data Import Tools
Prerequisites: The PremierOne All-In-One Installer (AIO) requires the latest .NET Framework. It is
necessary to update .NET on Windows 10 by using the Windows Update.
Procedure:
1. To launch the Data Import Tools installer, go to the installation media drive/folder and double-click
GISDataImportTool_<build_number>.msi.
2. From the Welcome dialog box of the setup wizard, click Next.
3. To accept the defaults, in the Select Destination dialog box, click Next.
4. In the Confirmation dialog box, click Install.
5. In the Installation Complete dialog box, click Finish.
23
MN007396A01-D
2.3
Adding PremierOne Data Import Tools to
ArcToolbox
To use the PremierOne Data Import Tools, they must be added to an Arc Toolbox.
Procedure:
1. Open the ESRI ArcCatalog application.
2. In the Catalog Tree, expand the Toolboxes item.
3. Right-click the My Toolboxes item, and then select New → Toolbox.
The new toolbox appears in the Contents tab of the main ArcCatalog dialog box and highlights the
toolset default name, allowing a new name to be entered.
4. Type a name for the new toolbox. For example, PremierOne Data Import Tool.
5. In the Catalog Tree, select Toolboxes → My Toolboxes.
6. Right-click the toolbox created in the previous step and select Add → Tool.
The Add Tool dialog box appears.
24
MN007396A01-D
Figure 1: ArcCatalog – Add Tool Dialog Box
7. Select the check box next to Motorola Tools to expand the tool options, and then click OK.
The PremierOne Import tools are added to your new toolbox.

NOTE: Some organizations may not use all of the Data Import Tools (such as Motorway
Junction Import, which was developed for use specifically in the United Kingdom, and the
PremierCAD Migration Tools). Rather than adding all of the tools, individual tools may be
selected. If the tools are not needed, the tools can be removed from a toolbox at any time.
2.4
Disabling Background Geoprocessing
A new feature called Background Geoprocessing was introduced in ArcGIS Desktop 10.0. Some ArcGIS
users have reported instability issues when running geoprocessing tools in a background process. This
feature also requires a larger memory allocation to run geoprocessing tools in the background. For these
reasons, Motorola recommends disabling this feature.
25
MN007396A01-D
Procedure:
1. From the Main Menu, select Geoprocessing → Geoprocessing Options.
2. Below Background Processing, clear the Enable checkbox.
26
MN007396A01-D
Chapter 3: GIS Validator Tools
Chapter 3
GIS Validator Tools

Geo-Processing tools assist GIS Administrators in identifying and eliminating duplicate Address Points,
Common Places, and overlapping Street Centerlines/Segments from the source GIS data that is imported
into PremierOne. The tools described in this chapter look and operate similarly to the PremierOne Data
Import Tools.
These tools do not change any source GIS data. These tools create comma separated value (.csv) files that
contain references to records within your GIS source data with the purpose of aiding the GIS Administrator in
eliminating, correcting, or adding distinguishing attribute information to the problem records.
The Validator tools need to be run on the source data prior to importing the data into the PremierOne Staging
Geodatabase. Any corrections/additions/deletions must be made in the source data prior to creating the
Staging Geodatabase.
3.1
Adding GIS-Validator Tools to the PremierOne
Toolbox
Before using GIS-Validator Tools, the tools must be added to the PremierOne toolbox.
Procedure:
1. Launch the ESRI ArcCatalog application.
If the Catalog Tree window is not displayed, navigate to the ArcCatalog main menu and select
Windows → Catalog Tree.
2. In the Catalog Tree window, expand the branch labeled Toolboxes, then expand the My Toolboxes
branch.
3. Right-click on the PremierOne toolbox.
NOTE: The PremierOne toolbox may have been renamed by a GIS Administrator. The
PremierOne toolbox can be identified as the one containing the existing GIS import tools.
4. From the right-click menu on the PremierOne toolbox:
a. Select Add, and then select Tool.
b. Expand the Motorola Tools branch and then expand the PremierOne Import Tools branch.
c. Select the following tools:
Address Point Validator
Common Place Validator
Street Centerline Validator
d. Click OK and verify that the new tools exist within the PremierOne toolbox.
3.2
Address Point Validator
To identify duplicate Address Points imported into PremierOne within GIS data, the GIS Administrator runs
the Address Point Validator tool. The Address Point Validator outputs a comma separated values (.csv) and
27
MN007396A01-D
the formatted file named AddressPointValidation.csv within the My Documents\Data Import Tools
folder on the GIS editing workstation.
3.2.1
Executing the Address Point Validator
Running the Address Point Validator will identify duplicate or invalid Address Points,
NOTE: When filling out the Address Point Validator dialog box it is essential to use the exact same
fields as are used when importing Address Point data into the Staging Geodatabase.
Procedure:
2. From the PremierOne toolbox, double-click the Address Point Validator.
Figure 2: Address Point Validator Dialog Box
3. Complete the following entries:
28
MN007396A01-D
a. Input Address Point Features: drag and drop the address point layer or using the folder button
on the right navigate to the Address Point layer
b. Street Alias Table (optional): drag and drop the Street Alias Table or using the folder button on
the right to navigate to the Street alias table
c. Address Part Fields: using the dropdown select the field(s) that make up the full address. The
feature class may contain one single field for the address or the address may be contained in
more than one field such as house number, street prefix, street name, street type, street suffix.
Identify each field in the order in which they would read the full address.
d. Subdivision Field (optional): using the dropdown select the subdivision field name
e. City Field: using the dropdown select the city field name
f. Subhouse Field (optional): using the dropdown select the Subhouse field
g. Building Field (optional): using the dropdown select the Building field
h. Zip Code Field (optional): using the dropdown select the Zip Code field
i. State Field (optional): using the dropdown select the State field
4. When the fields are set to their appropriate values, click OK.
The Address Point Validator tool executes. Depending on the size/amount of the source GIS data,
this execution may take seconds or minutes.
When finished, the system shows the message Addresses with duplicate addresses: xxx
(where xxx is the number of duplicate Address Point records found). This message is followed
by the fully qualified output filename noted in the message Check the log at: <drive
letter>:\<folder names>\AddressPointValidation.csv.
29
MN007396A01-D
Figure 3: Address Point Validator Report Dialog Box
NOTE: Each time the Address Point Validator tool is executed, the system overwrites any
previously created AddressPointValidation.csv file that exists at the target location.
Because the intention of executing the Address Point Validator tool is to identify duplicate
address points within source GIS data, there is no need to retain previously created
AddressPointValidation.csv files.
To view the log, open the AddressPointValidation.csv file in your preferred .csv file
reader/editor such as MS Excel or Google Sheets. Refer to the contents of this file when
correcting duplicate Address Points.
3.2.2
Correcting Duplicate Address Points
Before correcting duplicate Address Points, make sure you have a recent AddressPointValidation.csv file
available for reference. Refer to the Geodatabase assigned row IDs associated to the duplicate Address
Points identified.
NOTE: The Geodatabase assigned row ID being referred to is often known as the OBJECTID.
Procedure:
1. Launch the ESRI ArcMap application.
2. Add an Address Point layer to the map.
3. Add any map layers, such as Street Centerlines or Parcel Data, to the map to aid in identifying the
location of the points that are now displayed on the map.
4. From the main menu, select Editor → Start Editing.
5. From the Table of Contents view, right-click on the Address Point → Open Attribute Layer.
6. Click Select by Attributes.
The Select by Attributes dialog appears.
30
MN007396A01-D
7. In the SELECT * FROM field, create the query necessary to display the duplicate Address Points to
work with.
NOTE:
Motorola recommends copying and pasting from the OBJECTID column in the
AddressPointsValidation.csv file to ensure that the correct duplicate Address Points are used
in the query.
Sample Query:
Create a ‘Select By Attributes’ statement to find the duplicate records. This can be done many
ways, however, one way is by creating a query to look for all numbers in the OBJECTID field of
a record – OBJECTID IN (#,#,#.…. (where OBJECTID is the name of the unique ID column
in your data).
For instance, in the example below there are 4 duplicates for DOVER DR, the query is:
SELECT * FROM
OBJECTID” IN (939,943,944,945)
Figure 4: Address Point Validator Dialog Box
8. Click Apply → Close.

9. From the main menu, select Selection → Zoom to Selected Features.
The working map zooms to show the selected Address Points
10. Perform one of the following to correct the duplicated Address Points:
a. Delete the extraneous or incorrectly placed Address Points from the map.
b. Add additional attribute information to the duplicate Address Points to make them unique from one
another, such as adding an Apartment or Unit number (sub house number), or Building number/ID.
31
MN007396A01-D
11. Repeats steps step 5 – step 10 until all of the duplicate Address Points referenced in the
AddressPointValidation.csv file are removed or corrected.
12. From the Editor toolbar, click Editor → Save Edits.
13. When the editing is finished, on the Editor toolbar, click Editor → Stop Editing.
3.3
Common Place Validator
To identify duplicate Common Places within GIS data that is imported into PremierOne, the GIS Administrator
may run the Common Place Validator tool. The Common Place Validator outputs a comma separated values
(.csv) formatted file titled CommonPlaceValidation.csv within the My Documents\Data Import Tools
folder on the GIS editing workstation.
NOTE: When filling out the Common Place Validator dialog box it is essential that to use the exact
same fields as are used when Importing Common Place data into the Staging Geodatabase.
3.3.1
Executing the Common Place Validator
To identify duplicate or invalid Common Places, run the Common Place Validator.
Procedure:
2. From your PremierOne toolbox, double-click the Common Place Validator tool.
32
MN007396A01-D
Figure 5: Common Place Validator Dialog Box

a. Input Common Place Features (required): Browse or drag the feature class containing your
Common Places to populate the Input Common Place Features field.
b. Place Name Field (required): Identify the field within your Common Place feature class that
contains the Common Place Name associated with your Common Places.
c. Place Name Alias Table (optional): If using the Common Place Name Alias Table, browse to or
drag the Common Place Alias table to populate the Place Name Alias Table (optional) field.
d. Place Name Alias Fields (optional): If you maintain Common Place Alias names as attributes
within the same table identified in step 3a, identify the fields within the Common Place Features
that contain all of the possible alias names.
NOTE: Common Places may have multiple aliases identified in an Alias1, Alias2,
Alias3, etc. format. Make sure you identify all of the possible alias names.
33
MN007396A01-D
e. Address Part Fields (optional) – From the top down, select the fields (in reading order)
responsible for containing the entire address associated with Common Places for your system.
The fields that you select here are the same that you would select for importing Common Places
into PremierOne.
Example:
You may have one field in your Common Places feature class that contains the entire/unique
address associated with the common place used within your GIS data. If this is the case, you can
identify this single field.
OR
You may have multiple fields within your Common Places feature class that collectively describe
the entire/unique address for a Common Place. If this is the case, you need to identify each field
responsible in the order in which they would be read. For example, the fields for house number,
street prefix direction, street name, street type, and street suffix direction may all need to be
identified.
f. City Field: Identify the city field from the drop-down.
g. Using the drop-downs, identify the other optional fields, such as Subdivision, Sub House,
Building, Zip Code, or State.
The fields that you select here are the same that you would select for importing Common Places
into PremierOne.
h. Street Alias Table (optional): Browse for or drag the appropriate table containing your Street
Aliases if you use them.
4. Once you have set the fields on this form to their appropriate values, click OK.
The Common Place Validator tool executes. Depending on the size/amount of the source GIS data,
When finished, the system shows the message Common Places with duplicate name and
address attributes: xxx (where xxx is the number of duplicate Common Place records found).
This message is followed by the fully qualified output filename noted in the message Check the
log at: <drive letter>:\<folder names>\CommonPlaceValidation.csv.
NOTE: Each time the Common Place Validator tool is executed, the system overwrites any
previously created CommonPlaceValidation.csv file that exists at the target location. The
intention of executing the Common Place Validator tool is to identify duplicate common places
within source GIS data, so there is no need to retain previously created
CommonPlaceValidation.csv files.
To view the log, open the CommonPlaceValidation.csv file in your preferred .csv file reader/
editor such as MS Excel or Google Sheets. Refer to the contents of this file when correcting
duplicate Common Places.
34
MN007396A01-D
3.3.2
Correcting Duplicate Common Places
Before correcting duplicate Common Places, make sure there is a recent CommonPlaceValidation.csv file
available for reference. Refer to the Geodatabase assigned row IDs associated to the duplicate Common
Places identified.
NOTE: The Geodatabase assigned row ID being referred to is often known as the OBJECTID.
Procedure:
2. Add your Common Places layer to the map.
3. To aid in identifying the location of the points that are now displayed on the map, add any map layers,
such as Street Centerlines or Parcel Data, to the map.
4. From the main menu, select Editor → Start Editing.
5. From the Table of Contents view, right-click on the Common Places layer, and select Open
Attribute Layer.
6. Click Select by Attributes.
Figure 6: Common Place Select By Attribute Dialog Box
35
MN007396A01-D
7. In the SELECT * FROM field, create the query necessary to display the duplicate Common Places
that you wish to work with.
NOTE:
Motorola recommends copying and pasting from the OBJECTID column in the
CommonPlaceValidation.csv file to ensure that the correct duplicate Common Places are
used in the query.
Sample Query:
The contents of the SELECT * FROM field could be stated as OBJECTID = xxxxx OR
OBJECTID = yyyyy OR OBJECTID = zzzzz (where xxxxx, yyyyy, zzzzz represent the
OBJECTIDs assigned to the duplicate Common Places that all refer to the same address).
OR
The contents of the SELECT * FROM field can be stated as OBJECTID IN (xxxxx, yyyyy,
zzzzz) (where xxxxx, yyyyy, zzzzz represent the OBJECTIDs assigned to the duplicate
Common Places that all refer to the same address).
These two examples produce the same results.
8. Select Apply and click Close.
9. From the main menu, select Selection → Zoom to Selected Features.
The working map zooms to show the selected Common Places
10. To correct the duplicated Common Places, perform one of the following actions:
● Delete the extraneous or incorrectly placed Common Places from the map.
● Add attribute information to the duplicate Common Places to make them unique from one
another, such as adding an Apartment or Unit number (sub house number), or Building number/ID.
11. Repeats steps step 5 – step 10 until all of the duplicate Common Places referenced in the
AddressPointValidation.csv file are removed or corrected.
13. When the editing is finished, on the Editor toolbar click Editor → Stop Editing.
3.4
Street Centerline Validator
Identify Street Centerlines that contain overlapping addresses within GIS data that is imported into
PremierOne, the GIS Administrator may run the Street Centerline Validator tool. The Street Centerline
Validator outputs a comma separated values (.csv) formatted file titled StreetCenterlineValidation.csv
within the My Documents\Data Import Tools folder on the GIS editing workstation.
When filling out the Street Centerline dialog box it is essential that you use the exact same fields as are
used when importing Street Centerline data into the Staging Geodatabase.
3.4.1
Executing the Street Centerline Validator
To identify Street Centerlines that contain overlapping addresses, run the Street Centerline Validator.
Procedure:
2. From the PremierOne toolbox, execute the Street Centerline Validator tool.
36
MN007396A01-D
Figure 7: Street Centerline Validator

a. Input Street Centerline Features (required entry): Browse for or drag the feature class containing
the Street Centerlines to populate the Input Street Centerline Features field.
b. Street Alias Table (optional): Browse for or drag the appropriate table containing the Street
Aliases if they are used. If Street Aliases are used, then the table name should be
StreetNameAliases.
c. Street Name Parts Fields: Enter, in reading order, all of the fields that comprise the entire street
name.
If the entire street name is contained within one field, only enter that single field.
OR
If the entire street name is a series of multiple fields, then those fields must be selected in the
order in which they would be read, such as prefix, street name, street type, suffix.
d. Left Low House Field: From the dropdown select the field containing the left low house number
37
MN007396A01-D
e. Left High House Field: From the dropdown select the field containing the left high house number
f. Right Low House Field: From the dropdown select the field containing the right low house
number
g. Right High House Field: From the dropdown select the field containing the right high house
number
h. Street Name Parts Fields: Enter, in reading order, all of the fields that comprise the entire street
name.
If the entire street name is contained within one field, only enter that single field.
OR
If the entire street name is a series of multiple fields, then those fields must be selected in the
order in which they would be read, such as prefix, street name, street type, suffix.
4. Select these fields as they would be selected when importing GIS source data into PremierOne:
● Left Subdivision Field (optional): From the dropdown select the field containing the left
subdivision field.
● Right Subdivision Field (optional): From the dropdown select the field containing the right
subdivision field.
● Left City Field (required): From the dropdown select the left city field.
● Right City Field (required): From the dropdown select the right city field.
● Left Zip Code Field (optional): From the dropdown select the left Zip Code field.
● Right Zip Code Field (optional): From the dropdown select the right Zip Code field.
● State Field (optional): From the dropdown select the state field.
5. When the fields on this form are set to their appropriate values, click OK.
The Street Centerline Validator tool executes. Depending on the size/amount of the source GIS data,
6. When done, the system shows the message Street Centerlines with overlapping
addresses: xxx (where xxx is the number of overlapping Street Centerline records found). This
message is followed by the fully qualified output filename noted in the message Check the log
at: <drive letter>:\<folder names>\StreetCenterlineValidation.csv.
NOTE: Each time the Street Centerline Validator tool is executed, the system overwrites any
previously created StreetCenterlineValidation.csv file that exists at the target location.
Because the intention of executing the Street Centerline Validator tool is to identify overlapping
street centerlines within source GIS data, there is no need to retain previously created
StreetCenterlineValidation.csv files.
To view the log, open the StreetCenterlineValidation.csv file in your preferred .csv file reader/
editor such as MS Excel or Google Sheets. Refer to the contents of this file when correcting
overlapping street segments.
3.4.2
Overlapping Street Centerlines Correction Overview
Before correcting overlapping street centerlines, make sure you have a recent
StreetCenterlineValidation.csv file available for reference. Refer to the Geodatabase assigned row IDs
associated to the overlapping street centerlines identified. The Geodatabase assigned row ID being referred
to is commonly known as the OBJECTID. Within the StreetCenterlineValidation.csv file, various error
38
MN007396A01-D
messages are presented. Most of these messages are the same messages that you would experience when
importing the source GIS data into PremierOne.
The specific message being discussed in this section is Features have overlapping addresses. The
steps below describe how you may correct street centerline segments that contain overlapping house
numbers referred to by the ObjectIDs with overlapping addresses error message. The other errors
you may see within the StreetCenterlineValidation.csv file are briefly referred to in Street Centerline
Validator Errors on page 40.
3.4.2.1
Correcting Overlapping Street Centerlines
Procedure:
2. Add the Street Centerline layer to the map.
3. From the Table of Contents view, right-click on the Street Centerline layer.
4. Select Open Attribute Layer, and then click Select by Attributes.
5. In the SELECT * FROM field within the Select by Attributes dialog, create the statement necessary
to display the overlapping street centerlines to be worked with. Motorola recommends copying the
information directly from the OBJECTID column in the StreetCenterlineValidation.csv file that lists
the overlapping street centerlines’ unique IDs.
Sample Query:
The contents of the SELECT * FROM field could be stated as OBJECTID = xxxxx OR OBJECTID =
yyyyy OR OBJECTID = zzzzz (where xxxxx, yyyyy, zzzzz represent the OBJECTIDs assigned
to the overlapping street centerline records that all refer to the same house numbers upon that street).
OR
The contents of the SELECT * FROM field can be stated as OBJECTID IN (xxxxx, yyyyy,
zzzzz) (where xxxxx, yyyyy, zzzzz represent the OBJECTIDs assigned to the overlapping
street centerlines that refer to the same house numbers upon that street).
These two examples produce the same results.
39
MN007396A01-D
Figure 8: Street Centerline Query Dialog Box
6. Select Apply → Close, and then click.

7. From the main menu bar, click Selection → Zoom to Selected Features.
The working map area zooms to show the selected Street Centerline segments.
8. To correct the overlapping Street Centerline segments, check the Left and Right Low and High
(or Start and End) House Numbers. Look for the overlapping house numbers within these ranges
and correct them accordingly. Consider that when correcting overlapping house numbers on street
centerline segments, all of the same rules apply as if creating Street Centerline segments. No two (or
more) street segments should reference the same house number value.
9. Repeat step 5-step 8 until all of the overlapping Street Centerlines referenced in the
StreetCenterlineValidation.csv file have been corrected.
11. When you are finished editing, on the Editor toolbar click Editor → Stop Editing.
3.4.3
Street Centerline Validator Errors
The StreetCenterlineValidation.csv file contains seven errors in the Street Centerline layer and
those segments will not import into the Staging Geodatabase when using the PremierOne Street Centerline
Import tool. It is important to correct all the errors in the error report.
The following are the errors that are written to the StreetCenterlineValidation.csv report:
● Features have overlapping addresses
● Street name is blank
40
MN007396A01-D
● Right Segment has the same house number parity as the left segment
● House number mixed parity on left side of segment
● House number mixed parity on right side of segment
● Grid (Alpha) Mismatch on left side of Segment
● Grid (Alpha) Mismatch on right side of Segment
Any street segments that are referred to by the above errors are not being imported into PremierOne for
location verification use. The worst case scenario of ignoring these errors is that the user will enter an
address they believe should be valid in PremierOne but PremierOne will not validate the address if it falls
on a street segment that is listed in the error report and that street segment is the only resource available
for the validation. In addition the street will display on the visual map display, again it will not address
validate for the dispatcher.
For example, a user enters the address 123 MAIN ST as a location in PremierOne. If the address 123
MAIN ST is referred to by an Address Point, then the Address Point will match and the user receives
confirmation of a valid location, the point is displayed on the map based on the location of the point and
the jurisdictional information is obtained, again, based on the location of the point. If no Address Point
exists for this location, PremierOne searches for street centerline data to find a match. If there is no
street centerline data for 123 MAIN ST the system is unable to verify the location and the system will
require the user to bypass the address verification. When address verification is bypassed the user must
manually enter jurisdictional information. If the user verifies the location as an Address Point and uses the
In Front Of option PremierOne must be able to locate a street centerline containing the address of the
Address Point.
3.5
Tools Assignment
The PremierOne GIS import tools include tools used to assign city name (zip code and subdivision if
applicable) to the Street Centerline, Address Point and Common Place data layers.
3.5.1
Assigning City Names to Streets
Procedure:
1. Select Assign City Names to Streets from PremierOne Import Tools.
41
MN007396A01-D
Figure 9: Assign City Names to Streets
2. Complete the following fields:

● City Feature Class: Select the polygon feature class that is to be used to assign attributes to the
street centerline.
● City Name Field: Browse for the attribute that contains the polygon name associated with the
layer to assign.
● Street Centerline Feature Class: Identify the street centerline feature class that will be assigned.
● Output Left City Field: Manually type the name of the L_* field, if this name does not exist, a new
attribute field will be created. The column name is limited to 10 char length.
● Output Right City Field: Manually type the name of the R_* field, if this name does not exist, a
new attribute field will be created. The column name is limited to 10 char length.
● Offset Length (in feet): Assign distance to look for the left and right assign. 40ft is the
recommended distance (default).
A results dialog box shows the results of the assign process.
3.5.2
Assigning City Names to Points
Procedure:
1. Select the Assign City Names to Points utility from the PremierOne GIS import tools.
42
MN007396A01-D
Figure 10: Assign City Names to Points
2. Complete the following fields:

● City Feature Class: Select the polygon feature class that is to be used to assign attributes to the
point layer.
● City Name Field: Browse for the attribute that contains the polygon name associated with the
layer to assign.
● Address Point or Common Place Feature Class: Identify the point layer feature class that will
be assigned.
● Output City Field: Manually type the name of the attribute field. If this name does not exist, a new
attribute field will be created. The column name length is limited to 10 characters.
A results dialog box shows the results of the assign process.
43
MN007396A01-D
Chapter 4: GIS Data Import into PremierOne
Chapter 4
GIS Data Import into PremierOne

4.1
Supplemental Tables Creation
The Supplemental Tables are used for aliases and standard exceptions. There are four Supplemental Tables
that are created: Common Place Aliases, Standardization Exceptions, Street Name Alias and Street Types.
The Street Types table is used for European Customers; this table is not applicable to U.S. customers and
can be deleted. The Alias tables are used to define additional familiar names commonly used for streets and
common places. The Standardization Exception Table is used to model exceptions for anomalies where the
real Street Name is the same as a street Directional (E, W, S, N).
The Supplemental tables are created one time and then maintained. They will be used during the source data
import into the Staging Geodatabase. The Supplemental Tables are created in a file geodatabase using the
PremierOne Import Tools.
4.1.1
Creating File Geodatabases
Creating the supplemental geodatabase is a task that should only need to be performed once; after which
regular maintenance on the tables within the supplemental geodatabase occurs as the information stored
within them changes.
Procedure:
1. In the ArcCatalog Catalog Tree, right-click a Folder Connection item, and then select New → File
Geodatabase.
A new File Geodatabase appears in the right window pane in the Contents tab. The name of the new
geodatabase is highlighted.
44
MN007396A01-D
Figure 11: ArcCatalog – Create File Geodatabase
2. Select the name and type a name for the geodatabase (such as AliasTables.gdb,
SuppplementalTables).
Figure 12: ArcCatalog – Naming Database
45
MN007396A01-D
4.1.2
Importing the Support Geodatabase Schema
Before the Supplemental Tables can be edited, the geodatabase schema must be imported. Import the
schema using the Create PremierOne Geodatabase tool.
Procedure:
1. In the Catalog Tree, expand the toolbox containing the PremierOne Data Import Tools and double-
click the Create PremierOne Geodatabase tool.
The Create PremierOne Geodatabase dialog box appears.
Figure 13: ArcCatalog – Create PremierOne Geodatabase
2. Click the Folder Browse icon, then browse to the Support Geodatabase folder, and select the .gdb
folder. Alternatively, use the mouse to drag the support geodatabase from the Catalog Tree to the
PremierOne Workspace text box.
The PremierOne Workspace should be the file path of the Supplemental Tables geodatabase.
3. Click the Folder Browse icon and browse to the PremierOne Data Import Tools installation folder
(C:\Program Files (x86)\Motorola\PremierOne Data Import Tools), and select the file
called GISSupportGDBSchema.xml.
The input geodatabase schema XML file should be the file path of an XML definition file containing the
geodatabase schema information.
4. Click OK.
46
MN007396A01-D
5. After the tool finishes, click Close.

6. Right-click the Supplemental Tables geodatabase in the Catalog Tree, and then click Refresh.
The tables imported from the schema definition file display below the Supplemental Tables
geodatabase.
47
MN007396A01-D
Figure 15: ArcCatalog – PremierOne Geodatabase Contents
NOTE: The Street Types table may be deleted for all U.S. customers.
Four tables are created in the support geodatabase:

● CommonPlaceAliases – Used to specify alias place names for common places with a specific
name/address combination or all common places with a specific name. This method is not the only
way to import alias names for common places. See Importing Common Place Points on page 68.
● StandardizationExceptions – Used to parse known street direction abbreviations. When a street
name is imported, the Data Import Tools attempt to parse out known street direction abbreviations.
For example, 123 W MAIN ST is parsed as:
○ House Number: 123
○ Prefix Direction: W
○ Street Name: MAIN ST
This is because W is recognized internally as a valid prefix direction value. An address of 123
W ST (where W is actually the street name) is parsed incorrectly as it is imported. Therefore,
an entry in the StandardizationExceptions table notifies the Data Import Tools how to correctly
standardize this address.
● StreetNameAliases – Used to specify street name aliases for a specific address range and city.
● StreetTypes – Used to specify valid street type abbreviations for address standardization
purposes. This is only necessary for systems deployed in the Latin America Caribbean region.
Like prefix directions in the United States, street type abbreviations appear before the street name
in the Latin America Caribbean region.
48
MN007396A01-D
4.1.3
Adding Support Data Using ArcMap
Support data can be added to the geodatabase using ArcMap or other tables.
ArcMap is used to maintain information in the Supplemental Tables geodatabase. This same workflow applies
for all tables in the support geodatabase.
Procedure:
1. From the Main Menu of ArcMap, select File → Add Data → Add Data.
This process adds the table to the map.
2. Navigate to the folder containing the Supplemental Tables geodatabase from the Look in list.
3. Click the Supplemental Tables geodatabase object to expand it and select the table you want to edit.
4. Click OK.
5. Right-click the table in ArcMap’s table of contents, and then select Open.
6. From the Editor toolbar, select Start Editing.
If the Editor toolbar is not displayed in the tools area, right-click anywhere in the tools area and select
Editor.
7. Perform any of the following:
● To add a record, scroll to the bottom of the table and type values into the empty fields.
● To modify a record, locate the record to modify, click the value to change, and type a new value.
● To delete a record, locate the record to delete, right-click any field in one of the record rows and
8. When finished editing, from the Editor toolbar, select Stop Editing.
If any changes were made, a prompt appears to verify whether any edits should be saved.
9. Click Yes to save the edits.
4.1.4
Support Geodatabase Data Import Overview
Alias data can also be maintained in one of the following file types and loaded into the Support Geodatabase:
● dBase (*.dbf)
● Comma Separated Value (*.csv)
● Tab delimited text (*.txt)
● Microsoft Excel (*.xls or *.xlsx)
● INFO
● VPF
● OLE database
● Geodatabase table
The field names should appear in the first row of the input table. Field names cannot contain spaces or
special characters (such as $ or *); otherwise an error appears when using the Simple Data Loader.
49
MN007396A01-D
4.1.4.1
Importing Data into Support Geodatabases
Procedure:
1. In the ArcGIS Catalog Tree, right-click the table for the data.
2. Select Load → Load Data.
The Simple Data Loader wizard appears.
Figure 16: ArcCatalog – Simple Data Loader Wizard Dialog Box
3. Click Next.
The Simple Data Loader Input Data dialog appears.
50
MN007396A01-D
Figure 17: ArcCatalog – Simple Data Loader Input Data Dialog Box
4. Click the Browse icon and browse to and select the input file.
5. Click Add to add the input data file to the List of source data to load.
6. Click Next.
The Simple Data Loader Subtypes dialog box appears.
51
MN007396A01-D
Figure 18: ArcCatalog – Simple Data Loader Subtypes Dialog Box
7. Do not change any values in this dialog box. Click Next.

The Simple Data Loader Field Mappings dialog box appears.
52
MN007396A01-D
Figure 19: ArcCatalog – Simple Data Loader Field Mappings Dialog Box
8. Specify the field name mappings between the source table and the target table.
Every Target Field value must be matched to a Matching Source field. Click Next.
The Simple Data Loader Query dialog box appears.
53
MN007396A01-D
Figure 20: ArcCatalog – Simple Data Loader Query Dialog Box
9. Perform one of the following:

● To load all of the data from the source, make sure the Load all of the source data option is
selected.
● To only load data that satisfies an attribute query, select Load only the rows that satisfy a query
and click Query Build to specify the load conditions.
10. Click Next.
A summary dialog box displays.
11. Click Finish.
The data is loaded from the input data source to the target table.
4.1.5
Common Place Name Aliases
If dispatchers expect to be able to refer to the same common place using different place names, those alias
names can be maintained in the CommonPlaceAliases table. For example, assume dispatchers want to
be able to enter MCD instead of MCDONALDS. CommonPlaceAliases can also be stored as fields within the
commonplace feature class.
The CommonPlaceAliases table expects the following values:
● ALIAS_PLACE_NAME – An alternate name for a common place. For the previous example, the
ALIAS_PLACE_NAME is MCD.
● REAL_PLACE_NAME – The real name of the common place exactly as it appears in a Common Place
source file imported into PremierOne using the Common Place Import tool. For the previous example,
the real name is MCDONALDS.
54
MN007396A01-D
● REAL_PLACE_ADDRESS and REAL_PLACE_CITY– If the alias name is only applied to a business at a

specific address (including city), place the address and city values exactly as they appear in a Common
Place source file imported into PremierOne using the Common Place Import tool. If these values are left
blank, the alias is applied to any common place containing the real name specified in the CITY specified,
regardless of address. A common place alias must include a CITY name that matches the CITY in the
source data. If the Common Place Alias applies to multiple common places in multiple cities a record for
each CITY must be made in the alias table.
4.1.6
Standardization Exceptions
The PremierOne Import Tools parse the prefix direction from addresses.
The supported prefix directions are:
● N (North)
● S (South)
● W (West)
● E (East)
● NW (Northwest)
● NE (Northeast)
● SW (Southwest)
● SE (Southeast)
● NB (Northbound)
● SB (Southbound)
● EB (Eastbound)
● WB (Westbound)
If there are any street names in the source data that begin with any of these abbreviations (followed
immediately by a space character) and those abbreviations do not represent a prefix direction, those street
names must be maintained in the StandardizationExceptions table. For example, W ST.
The StandardizationExceptions table expects the following values:
● FULL_STREET – The full street name including prefix and suffix abbreviations. For the previous
example, the FULL_STREET is W ST.
● PRE_DIR – The prefix direction abbreviation for the street name entered into FULL_STREET. For the
previous example, since W is the street name and not a prefix direction, the value of PRE_DIR is left
blank.
● PRE_TYPE – The prefix street type abbreviation for the street name entered into FULL_STREET. Prefix
types are only supported for systems deployed in the Latin America Caribbean Region. For the previous
example, the value of PRE_TYPE is left blank.
● STREET_NAME – The name part (minus prefixes and suffixes) for the street name entered into
FULL_STREET. For the previous example, the value of STREET_NAME is W.
● SUF_TYPE – The street type abbreviation for the street name entered into FULL_STREET. For the
previous example, the value of SUF_TYPE is ST.
● SUF_DIR – The suffix direction abbreviation for the street name entered into FULL_STREET. For the
previous example, the value of SUF_DIR is left blank.
NOTE: CITY is not required in the Standardization Exception Table; therefore each record will
apply to all matching records in the source data regardless of the city name.
55
MN007396A01-D
4.1.7
Street Name Aliases
If dispatchers expect to be able to refer to the streets using names other than those that appear in the street
centerline sources, those alias names can be maintained in the StreetNameAliases table. Street Name
aliases are applied to a specific address range within a city. If the same alias applies to a same street name
that runs through multiple cities, a record must be maintained for each of those cities.
For example, assume dispatchers want to be able to enter BASELINE RD for streets that exist in the source
GIS as US-285. Additionally, the alias is only recognized between the 1000 and 6000 blocks within the city of
LAFAYETTE.
The StreetNameAliases table expects the following values:
● GRID – If the addresses on the street are alphanumeric, the GRID value represents all of the characters
to the left of the ranging part of the address. For example, the GRID value for house number 123N100
is 123N. If the grid values change throughout the length of the street, additional StreetNameAliases
records must be maintained for each grid value. For the previous example, the GRID value is left blank.
● LOW_HOUSE – The low house number (not including the GRID value, if applicable) for which the alias
is applied. If the alias should be applied to all street segments matching the full street name within a
particular city, the LOW_HOUSE value should be 0. For the previous example, the LOW_HOUSE value
is 100.
● HIGH_HOUSE – The high house number (not including the GRID value, if applicable) for which the alias
is applied. If the alias should be applied to all street segments matching the full street name within a
particular city, the HIGH_HOUSE value should be 999999999 (or any value above the highest house
number for that street within the particular city). For the previous example, the HIGH_HOUSE value is
6999.
● REAL_PRE_DIR – The prefix direction abbreviation for the real street name as it appears in the Street
Centerline source. For the previous example, the value of REAL_PRE_DIR is left blank.
● REAL_PRE_TYPE – The prefix street type abbreviation for the “real” street name as it appears in the
Street Centerline source. Prefix types are only supported for systems deployed in the Latin America
Caribbean region. For the previous example, the value of REAL_PRE_TYPE is left blank.
● REAL_STREET_NAME – The name part (minus prefixes and suffixes) for the “real” street name as it
appears in the Street Centerline source. For the previous example, the value of REAL_STREET_NAME
is US-285.
● REAL_SUF_TYPE – The street type abbreviation for the real street name as it appears in the Street
Centerline source. For the previous example, the value of REAL_SUF_TYPE is left blank.
● REAL_SUF_DIR – The suffix direction abbreviation for the real street name as it appears in the Street
Centerline source. For the previous example, the value of REAL_SUF_DIR is left blank.
● ALIAS_PRE_DIR – The prefix direction abbreviation for the alias street name. For the previous example,
the value of ALIAS_PRE_DIR is left blank.
● ALIAS_PRE_TYPE – The prefix street type abbreviation for the alias street name. Prefix types are only
supported for systems deployed in the Latin America Caribbean region. For the previous example, the
value of ALIAS_PRE_TYPE is left blank.
● ALIAS_STREET_NAME – The name part (minus prefixes and suffixes) for the alias street name. For the
previous example, the value of ALIAS_STREET_NAME is BASELINE.
● ALIAS_SUF_TYPE – The street type abbreviation for the alias street. For the previous example, the
value of ALIAS_SUF_TYPE is RD.
● REAL_SUF_DIR – The suffix direction abbreviation for the “real” street name as it appears in the Street
Centerline source. For the previous example, the value of SUF_DIR is left blank.
56
MN007396A01-D
● CITY – The name of the City in which the street to be aliased exists as it appears in the Street Centerline
source. For the previous example, the value of CITY is LAFAYETTE.
4.1.8
Street Types
Maintaining a list of valid street type abbreviations is only necessary for systems deployed in the Latin
America Caribbean Region. Every street type abbreviation that appears in any address/street imported into
PremierOne must be maintained in this table. A valid STREET_TYPE abbreviation appears in any source
table that contains addresses/street names.
4.1.9
Creating Staging Geodatabases
The first step to using the PremierOne Data Import Tools to import a new version of GIS data is to create a
staging geodatabase. A new Staging Geodatabase is required each time new data is imported.
Procedure:
1. In the ArcCatalog Catalog Tree, right-click a Folder Connection and select New → File
Geodatabase.
Figure 21: ArcCatalog – New File Geodatabase
A new file geodatabase appears in the Contents tab. The name of the new geodatabase is
highlighted.
2. Enter a name for the geodatabase (such as StagingGDB.gdb, P1Staging.gdb).
57
MN007396A01-D
Figure 22: ArcCatalog – Naming New File Geodatabase
4.1.10
Importing Staging Geodatabase Schema
Before data can be imported into the staging geodatabase, the geodatabase schema must be imported. This
is done using the Create PremierOne Geodatabase tool.
Procedure:
click the Create PremierOne Geodatabase tool.
2. Click the Browse icon, browse to the folder containing the staging geodatabase folder, and select
the .gdb folder.
Alternatively, use the mouse to drag the staging geodatabase from the Catalog Tree to the
PremierOne Workspace text box.
The PremierOne Workspace should be the file path of the staging geodatabase.
3. Click the Browse icon, browse to the PremierOne Data Import Tools installation folder (C:\Program
Files (x86)\Motorola\PremierOne Data Import Tools), and select the file
P1GDBSchema.xml.
58
MN007396A01-D
The Input Geodatabase Schema XML File should be the file path of an XML definition file containing
the geodatabase schema information.
4. Click OK.
The Create PremierOne Geodatabase Execution dialog box appears.
Figure 24: ArcCatalog – Create PremierOne Geodatabase Execution Dialog Box
5. After the tool finishes running, click Close.

6. Right-click the staging geodatabase in the Catalog Tree and select Refresh.
The feature datasets, feature classes, and tables imported from the schema definition file appear
below the staging geodatabase.
59
MN007396A01-D
Figure 25: ArcCatalog – Refreshed PremierOne Geodatabase
4.1.11
GIS Data Import
The following sections describe how to execute each tool that imports data from a source GIS into the staging
Geodatabase.
Every Data Import Tool has certain inputs required to execute the tool. A green dot displays next to fields in
the Import dialog box that are required and must be populated before the tool can be executed. The green
dot disappears after a value is entered for that field.
Most Data Import Tools log data errors and warnings in a comma-separated (*.csv) file. After the tool
finishes running, check the screen for a message in green text specifying the file location of the error file
(usually My Documents\Data Import Tools). Review the information in the error file. Some errors may
prevent a certain feature from being imported. The Street Centerline Import tool in particular may contain
warnings that do not prevent the feature from being imported, such as “zero house number” errors (for
example, it is common for centerlines representing freeways to not contain house numbers).
Some Data Import Tools require that the source data contain a field whose value specifies the owning agency
of each geographic feature being imported. The values of the Agency IDs must match the Agency ID values
used in PremierOne Agency Provisioning application.
NOTE: If a mistake was made when running any of the tools, start the process over from the Creating
File Geodatabases on page 44. Do not try to fix the problem by manually deleting data from specific
tables in the staging Geodatabase.
60
MN007396A01-D
4.1.12
Floor-Specific Layer Additions to a PremierOne Map
The Floor attribute can be selected for Address Points, Common Places, Responses, and Reporting
Districts. Specific naming conventions must be used in order for floor specific layers to be utilized within
the PremierOne map.
Create a group layer called Floor Specific. Under that group layer, add one group layer for each floor
number (may be alphanumeric) for which you have floor-specific layers. The group layer must be named
F:<floor>.
For example:
● F:B2
● F:B1
● F:P3
● F:P2
● F:P1
● F:5
● F:4
● F:3
● F:2
● F:1
Add one or more floor-specific layers to their appropriate group layer. Motorola Solutions recommends
that the visibility of all floor-specific group layers and layers be “unchecked.” PremierOne will automatically
enable/disable floor-specific layers based on user actions.
These conventions must be followed both for maps that are sourced from a file geodatabase and maps that
are published to ArcGIS Server.
4.1.13
Importing Street Centerlines
The Street Centerline Import Tool imports street centerline features into the staging geodatabase. Importing
Street Centerlines is required. Street Centerlines are features that are geometrically represented as lines.
Street segments are typically portions of a street that are bound on either end by an intersection, with another
street segment, or a dead end (cul-de-sac).
The tool can be executed multiple times to import street centerlines from multiple, non-overlapping source
feature classes.
Procedure:
click the Street Centerline Import tool.
The Street Centerline Import dialog box appears.
61
MN007396A01-D
Figure 26: ArcCatalog – Street Centerline Import Tool
2. Type or select the information in the required fields.

Fields with a Browse button next to them can be populated by clicking Browse and navigating to the
folder/file location, or by using the mouse to drag an item from the Catalog Tree and drop it to the
appropriate field.
A description of each field is as follows:
● PremierOne Workspace – Fully qualified path of the staging geodatabase (for example,
Z:\Staging\PremierOneStaging.gdb).
● Input Street Centerline Features - Fully qualified path of the street centerline source being
imported (for example, Z:\Data\MasterGIS.gdb\Streets).
● Standardization Exceptions Table - Fully qualified path of the standardization exceptions table
in the PremierOne Support geodatabase (for example,
Z:\Data\PremierOneSupport.gdb\StandardizationExceptions).
62
MN007396A01-D
● Street Alias Table - Fully qualified path of the street name alias table in the PremierOne Support
geodatabase (for example, Z:\Data\PremierOneSupport.gdb\StreetNameAliases).
● Left Low House Field - The field in the street centerline source containing the low house number
values for the left side of the street segment.
● Left High House Field - The field in the street centerline source containing the high house
number values for the left side of the street segment.
● Right Low House Field - The field in the street centerline source containing the low house
number values for the right side of the street segment.
● Right High House Field - The field in the street centerline source containing the high house
number values for the right side of the street segment.
● Street Name Part Fields - A list, in logical order, of the fields in the source Feature Class
that make up the street name. In some sources, this may include separate fields containing the
prefixes, suffixes, and/or name. For U.S. customers, the order is typically Prefix Direction, Street
Name, Street Type, and finally Suffix Direction. In other sources, the street name may be stored
entirely in a single field. Select the first street name part field and it is automatically added to
the list. Continue selecting street name part fields in order until the list is complete. Buttons on
the side of the list can be used to change the order of the fields or remove fields that were
inadvertently added to the list.
● Street Types Table - Fully qualified path of the street types table in the PremierOne Support
geodatabase (for example, Z:\Data\PremierOneSupport.gdb\StreetTypes). The Street
Types table was designed for use with Latin America Caribbean Region (LACR) addressing styles.
It should not be used for U.S. customers.
● Left Subdivision Field - The street centerline source field name containing the subdivision name
for the left side of the street segment. This is an optional field.
● Right Subdivision Field - The street centerline source field name containing the subdivision
name for the right side of the street segment. This is an optional field.
● Left City Field - The street centerline source field name containing the city name for the left side
of the street segment.
● Right City Field - The street centerline source field name containing the city name for the right
side of the street segment. This field is used for address validation on the CAD workstations.
● Left Postal City Field – The street centerline source field containing the postal city name for
the left side of the street segment. Postal City field is used in PremierOne Records for address
validation.
● Right Postal City Field – The street centerline source field containing the postal city name for
the right side of the street segment. Postal City Field is used in PremierOne Records for address
validation.
● Low Cross Street Override Field – The street centerline source field name containing the low
cross street override data. The PremierOne Street Centerline Import automatically determines the
cross streets at the vertices of a segment. If street segments originate/terminate at less significant
street features (such as alleyways), the cross streets calculated for a particular segment may
contain less useful information. If PremierOne is calculating an undesirable Low Cross Street for
a particular segment, select the field in the street centerline source containing the desired Low
Cross street name. If the value in this field is empty for a particular street segment, PremierOne
automatically determines the Low Cross Street. Data entered into this field will override the
automatically defined cross street.
● High Cross Street Override Field – The PremierOne Street Centerline Import automatically
determines the cross streets at the vertices of the segment. If street segments originate/terminate
at less significant street features (such as alleyways), the cross streets calculated for a particular
segment may contain less useful information. If PremierOne is calculating an undesirable High
63
MN007396A01-D
Cross Street for a particular segment, select the field in the street centerline source containing the
desired High Cross street name. If the value in this field is empty for a particular street segment,
PremierOne automatically determines the High Cross Street.
● Cross Streets Bypass Field – The street centerline source field name containing the cross
streets bypass data. This field is used to prevent PremierOne Import from automatically entering a
street name. The PremierOne Street Centerline Import automatically generates Street Intersection
features unless there is any alpha non-empty value in this field. If street segments originate/
terminate at less significant street features (such as alleyways), PremierOne may generate an
intersection called “MAIN ST & ALLEY”, for example. If there are several alleys that share
beginning/ending vertices with street segments of “MAIN ST”, several “MAIN ST & ALLEY”
intersection features generate. To prevent this, select the field in the street centerline source
containing values to specify whether the street segment should be used to generate intersection
features. Any non-empty, non-null value in this field prevents the street segment from being
used to generate an intersection feature. In this example, populate any non-empty value in a
“CrossStreetBypass” field in the street centerline source for all of the “alleys”. If the value in this
field is empty for a particular street segment, PremierOne automatically generates intersection
features using that street segment.
● Description – The field name in the street centerline source containing a user-defined description
for the street segment. This description appears on CAD/Mobile Client forms supporting address
verification when an address on this segment is verified and selected. Having the description can
be useful in some unusual cases (for example, two same-named or similar-named streets in the
same city, or streets that intersect each other in more than one location). This is an optional field.
● Left Zip Code Field - The street centerline source field name containing the zip code for the left
side of the street segment. This field is required for PremierOne Records address validation
● Right Zip Code Field - The street centerline source field name containing the zip code for the
right side of the street segment. This field is required for PremierOne Records address validation
● State field - The street centerline source field name containing the state name for the street
segment. This field is required for PremierOne Records address validation.
3. Click OK.
The Street Centerline Import Tool Progress dialog box appears.
Figure 27: ArcCatalog – Street Centerline Import Tool Progress Dialog Box
64
MN007396A01-D
4.1.14
Address Point Import Tool Overview
The Address Point Import Tool imports Address Point features into the staging geodatabase. This data is
used for address verification and geocoding purposes. The tool can be executed multiple times to import
address points from multiple, non-overlapping source feature classes.
Address points provide exact map locations for a particular address. If a location is associated with a
business that is commonly referred to with a name, a Common Place should be used instead.
Importing address points is optional. The main benefits for using address points include:
● Addresses that do not geocode accurately using street centerline-based geocoding because they do
not respect standard addressing rules. For example, some cul-de-sacs may not honor the requirement
for addresses to be even on one side and odd on the other side. Instead, addresses may be
assigned sequentially in clockwise or counter-clockwise order. Street Centerline geocoding would likely
be inaccurate in this scenario. Accurate geocoding is important – particularly for the impact it has on
calculating Premise/Hazard hits.
● Rural addresses in which the property is offset a long distance from the street indicated in its address.
● Residential/business properties that share a main address and are differentiated by a building and/or unit
(apartment) number. Without the use of address points, addresses with building and/or unit numbers all
geocode to the main address using street centerline-based geocoding.
There are potential downsides to using address points:
● The Network routing engine attempts to snap an address map location to the nearest street centerline
to generate a route. With address points, the closest street may not be the street associated with the
address point address. This can result in routing to a location that does not provide vehicle access to the
address. This is much less likely to occur with street centerline-based geocoded locations. However,
improper routing to an address point can be alleviated by including private and/or non-municipally
maintained access roads in the street network used as the source to build the Network Dataset.
● Proximity searches are only supported in two dimensions. Address Points do not work well if the intention
is to model the apartment numbers of multi-floor buildings. A Premise Hazard direct hit may be generated
for an apartment that is located several floors directly above the intended location.
● While the address point data source may support Z-levels (altitude), PremierOne does not currently
support map display or spatial calculations in 3D. In other words, there is virtually no value in importing
distinct address points for apartment numbers in multi-level buildings.
If the decision is made to import address points, you do not need to import address points for every address.
If a matching address point for a particular address does not exist, the address is geocoded using a matching
street centerline. Additionally, importing address points with apartment/building numbers does not prevent
a call taker from initiating an incident using an imported apartment/building number. If desired, a subset of
address points that alleviate these geocoding issues may be imported instead of all address points.
PremierOne also supports attributes for Sub-House (apartment/unit), Buildings, Subdivision Name, Zip Code,
State and Description. If the Sub-House (apartment/unit), Buildings, Subdivision Name, Zip Code, State and
Description are used in the Address Point layer they MUST be populated (and match) across all validation
layers (Common Place, Street, Address Point).
When using Address Points the naming convention for the address point(s) MUST MATCH the naming
convention of the street centerline file AND must match the city name in the street centerline data.
65
MN007396A01-D
4.1.14.1
Importing Address Points
Procedure:
click the Address Point Import tool.
The Address Point Import Tool dialog box appears.
Figure 28: ArcCatalog – Address Point Import Tool
2. Type or select the information in the required fields.

Fields with a Browse button next to them can be populated by clicking Browse and navigating to the
appropriate field.
66
MN007396A01-D
● Input Address Point Features – Fully qualified path of the address point source being imported
(for example, Z:\Data\MasterGIS.gdb\Addresses).
● Standardization Exceptions Table – Fully qualified path of the standardization exceptions table
● Street Alias Table – Fully qualified path of the street name alias table in the PremierOne Support
● Address Part Fields – A list, in logical order, of the fields in the source Feature Class that make
up the main part of the address (house number and street name information – not including
building or apartment numbers). In some sources, this list may include separate fields containing
the house number, prefixes, suffixes, and/or name. For U.S. customers, the order is typically
Prefix Direction, Street Name, Street Type, and finally Suffix Direction. In other sources,
the address may be stored entirely in a single field. Select the first address part field and it is
automatically added to the list. Continue selecting address part fields in order until the list is
complete. Buttons on the side of the list can be used to change the order of the fields or remove
fields that were inadvertently added to the list.
● Street Types Table – Fully qualified path of the street types table in the PremierOne Support
geodatabase (for example, Z:\Data\PremierOneSupport.gdb\StreetTypes.
NOTE: The Street Types table was designed for use with Latin America Caribbean region
(LACR) addressing styles. It should not be used for U.S. customers
● Subdivision Field – The address point source field name containing the subdivision name for the
address point.
● City Field – The address point source field name containing the city name for the address point.
● Postal City Field (optional) – The postal city, or suburb, associated with an incident location
“City” address point.
● Subhouse Field (for example, Apartment, Unit) – The field in the address point source containing
the subhouse (for example, apartment/unit number) value for the address point.
● Building Field – The address point field name source containing the building value for the
address point.
● Description – The address point source field name containing a user-defined description for
the address point. This description appears on CAD/Mobile Client forms supporting address
verification when an address point is verified and selected.
● Zip Code Field – The address point source field name containing the zip code for the address
point.
● State Field – The address point source field name containing the state name for the address
point.
3. Click OK.
The Address Point Import Tool Progress dialog box appears.
67
MN007396A01-D
Figure 29: ArcCatalog – Address Point Import Tool Progress Dialog Box
4.1.15
Importing Common Place Points
The Common Place Import Tool imports common place point features into the staging geodatabase.
Importing common places is optional. This data is used for address verification and geocoding purposes.
The tool can be executed multiple times to import common places from multiple, non-overlapping source
feature classes.
Common Places are used to provide an exact location for named places. Common places can include
businesses, schools, mile markers, landmarks, and so on. A common place may or may not be associated
with a street address.
Procedure:
click the Common Place Import tool.
The Common Place Import dialog box appears.
68
MN007396A01-D
Figure 30: ArcCatalog – Common Place Import Tool
2. Type or select the values in the required fields.

Fields with a browse button next to them can be populated by clicking Browse and navigating to the
appropriate field.

● Input Common Place Features – Fully qualified path of the address point source being imported
(for example,. Z:\Data\MasterGIS.gdb\Common).
● Place Name Field – The common place source containing the name of the common place.
● Place Name Alias Table – Fully qualified path of the place name alias table in the PremierOne
Support geodatabase (for example,
Z:\Data\PremierOneSupport.gdb\CommonPlaceAliases).
69
MN007396A01-D
● Place Name Alias Fields – The common place source containing the alias name of the common
place.
NOTE: Common Place Alias names can be specified in two ways. The Place Name Alias
table allows alias names to be maintained in a table externally from the common place
source. The benefit of this method is that it allows an alias name to be applied to a particular
business with several distinct locations (such as STARBUCKS. An alias can also be applied
only to a common place at a specific address. The other method is to store the alias names
within the common place source. The disadvantages to this is that it is not efficient from a
storage standpoint – particularly if some common places have several aliases while most
common places have no aliases.
● Address Part Fields – A list, in logical order, of the fields in the source Feature Class that
make up the main part of the common place address (house number and street name information
– not including building or apartment numbers). In some lists, this may include separate fields
containing the house number, prefixes, suffixes, and/or name. For U.S. customers, the order
is typically Prefix Direction, Street Name, Street Type, and finally Suffix Direction. In other
sources, the address may be stored entirely in a single field. Select the first address part field and
it is automatically added to the list. Continue selecting address part fields in order until the list is
complete. Buttons on the side of the list can be used to change the order of the fields or remove
fields that were inadvertently added to the list.
● Street Types Table – Fully qualified path of the street types table in the PremierOne Support
geodatabase (for example, Z:\Data\PremierOneSupport.gdb\StreetTypes.
NOTE: The Street Types table was designed for use with Latin America Caribbean region
(LACR) addressing styles. It should not be used for U.S. customers.
● Standardization Exceptions Table – Fully qualified path of the standardization exceptions table
● Street Alias Table – Fully qualified path of the street name alias table in the PremierOne Support
● Subdivision Field – The common place source containing the subdivision name for the common
place.
● City Field – The common place source containing the city name for the common place.
● Postal City Field (optional) – The postal city, or suburb, associated with an incident location
“City” address point.
● Subhouse Field (for example, Apartment, Unit) - The common place source containing the
subhouse (for example, apartment/unit number) value for the common place.
● Building Field – The common place source containing the building value for the common place.
● Place Type Field – The common place source containing the building value for the common
place.
● Description – The common place source containing a user-defined description for the common
place. This description appears on CAD/Mobile Client forms supporting address verification when
a common place is verified and selected.
● Zip Code Field – The common place source containing the zip code for the common place.
● State field – The common place source containing the state name for the common place.
3. Click OK.
The Common Place Import Tool Progress dialog box appears.
70
MN007396A01-D
Figure 31: ArcCatalog – Common Place Import Tool Progress Dialog Box
4.1.16
Response Boundaries Import Tool Overview
The Response Boundaries Import tool imports response boundary polygon features (commonly referred to
as “beats” by law enforcement agencies) into the staging geodatabase. Importing response boundaries is
required. This data is used for determining the response to an incident. The tool can be executed multiple
times to import response boundaries from multiple source feature classes. Typically, each response boundary
source feature class represents the response boundaries for all agencies associated with a particular agency
type (Police, Sheriff, Fire, and so on). However, this is not required. Each agency may maintain their own
feature class. Regardless of how the data is maintained in the source, each imported feature class must have
a unique feature class name.
Response boundaries within a particular agency or agency type may overlap. However, if a location is within
multiple beats for a particular agency type, the calltaker must choose a specific agency/beat from a pick-list
before an incident can be created.
4.1.16.1
Importing Response Boundaries
Procedure:
click the Response Boundary Import tool.
The Response Boundary Import dialog box appears.
71
MN007396A01-D
Figure 32: ArcCatalog – Response Boundary Import Tool

appropriate field.

● Input Boundary Features – Fully qualified path of the response boundary source being imported
(for example, Z:\Data\MasterGIS.gdb\Police).
● Agency ID Field – The response boundary source containing the responsible Agency name for
the response boundary.
● Boundary Name Field – The response boundary source containing the response boundary name
(beat name).
3. Click OK.
The Response Boundary Import Tool Progress dialog box appears.
72
MN007396A01-D
Figure 33: ArcCatalog – Response Boundary Import Tool Progress Dialog Box
4.1.17
Reporting District Import Tool Overview
The Reporting District Import Tool imports reporting district polygon features into the staging geodatabase.
Importing reporting districts is optional. This data is used for statistical reporting. The tool can be executed
multiple times to import reporting districts from multiple source feature classes. Each agency that wants to
have a reporting district associated with incidents must import reporting district boundaries associated with
their Agency ID. Typically, each reporting district source feature class represents the reporting districts for
all agencies associated with a particular agency type (Police, Sheriff, Fire, and so on). However, this is not
required. Each agency may maintain their own feature class. Regardless of how the data is maintained in the
source, each imported feature class must have a unique feature class name.
NOTE: Reporting District boundaries within a particular agency should not overlap. In cases where an
incident is located within two reporting districts, PremierOne only associates one reporting district with
the incident – the calltaker cannot select a reporting district from a pick-list.
4.1.17.1
Importing Reporting Districts
Procedure:
click the Reporting District Import tool.
The Reporting District Import dialog box appears.
73
MN007396A01-D
Figure 34: ArcCatalog – Reporting District Import Tool

appropriate field.
● Input Boundary Features – Fully qualified path of the reporting district source being imported (for
example, Z:\Data\MasterGIS.gdb\Police).
● Agency ID Field – The reporting district source containing the responsible Agency name for the
reporting district.
● Boundary Name Field – The reporting district source containing the name of the reporting district.
3. Click OK.
The Reporting District Import Progress dialog box appears.
74
MN007396A01-D
Figure 35: ArcCatalog – Reporting District Import Tool Progress Dialog Box
4.1.18
Contractor Boundary Import Tool
The Contractor Boundary Import Tool imports contractor boundary polygon features into the staging
geodatabase. If the Contractor Rotation feature is used, you must import the contractor boundaries. This
data is used to provision Contractor Rotations in PremierOne. The tool can be executed multiple times to
import contractor boundaries from multiple source feature classes. Each agency that wants to provision
Contractor Rotations must import contractor boundaries associated with their Agency ID. Typically, each
contractor boundary source feature class represents the contractor boundaries for a specific combination of
agency type and contractor type (for example, Taxi services used by Police calltakers). However, this is not
required. Each agency may maintain their own feature classes for each contractor type required. Regardless
of how the data is maintained in the source, each imported feature class must have a unique feature class
name.
NOTE: Contractor boundaries within a particular agency for a particular contractor type should not
overlap. In cases where the location of an incident is within contractor boundaries, PremierOne only
uses one contractor rotation; A PremierOne user cannot select a contractor boundary from a pick-list
4.1.18.1
Importing Contractor Boundaries
Procedure:
click the Contractor Boundary Import tool.
The Contractor Boundary Import dialog box appears.
75
MN007396A01-D
Figure 36: ArcCatalog – Contractor Boundary Import Tool

appropriate field.
● Input Boundary Features – Fully qualified path of the contractor boundary source being imported
(for example, Z:\Data\MasterGIS.gdb\TaxiContractors_PD).
● Agency ID Field – The contractor boundary source containing the responsible Agency name for
the contractor boundary.
● Boundary Name Field – The contractor boundary source containing the contractor boundary
name.
● Contractor Type – The Contractor Type name with which the imported contractor boundaries
are associated. Contractor Type names entered here are populated in the Contractor Type
Code selection of the Contractor Rotation Provisioning dialog box. Contractor Type allows a 10
character value to be entered.
3. Click OK.
The Contractor Boundary Import Tool Progress dialog box appears.
76
MN007396A01-D
Figure 37: ArcCatalog – Contractor Boundary Import Tool Progress Dialog Box
4.1.19
Importing Warrant Districts
The Warrant District Import Tool imports warrant district polygon features into the staging geodatabase.
Importing Warrant Districts is optional. This data is used to determine the warrant district for a location in
PremierOne. The warrant district is only determined as a result of a request from PremierOne Records.
Warrant district information is not attached to the incidents in CAD. The tool can be executed multiple times to
import warrant districts from multiple source feature classes. Regardless of how the data is maintained in the
source, each imported feature class must have a unique feature class name.
Procedure:
click the Warrant District Import tool.
The Warrant District Import dialog box appears.
77
MN007396A01-D
Figure 38: ArcCatalog – Warrant District Import Tool

appropriate field.
● Input Boundary Features – Fully qualified path of the warrant district source being imported (for
example, Z:\Data\MasterGIS.gdb\SheriffWarrants).
● Agency ID Field – The warrant district source containing the Agency ID used by the Records
system.
● Boundary Name Field – The warrant district source containing the name of the warrant district.
3. Click OK.
The Warrant District Import Tool Progress dialog box appears.
Figure 39: ArcCatalog – Warrant District Import Tool Progress Dialog Box
78
MN007396A01-D
4.1.20
Importing Map Books
The Map Book Import Tool imports map book polygon features into the staging geodatabase. Importing Map
Books is optional. This data is used to determine the map book information for a location in PremierOne. The
tool can be executed multiple times to import map books from multiple source feature classes. Each imported
Map Book feature class must have a unique feature class name.
Procedure:
click the Map Book Import tool.
The Map Book Import dialog box appears.
Figure 40: ArcCatalog – Map Book Import Tool

appropriate field.
● Input Boundary Features – Fully qualified path of the map book source being imported (for
example, Z:\Data\MasterGIS.gdb\RandMcNallyMapBook).
● Map Book Name – Name for the map book source. For example, RandMcNally. Map Book
Name allows a 10 character value to be entered. This value appears with the Page Number and
Grid Reference values on Incident Detail forms.
● Page Number Field – The map book source containing the page number on which the map book
boundary can be found in the physical map book (not usually applicable for maps not produced as
a book).
● Grid Reference Field – The map book source containing the grid reference name with which the
map book boundary can be found in the physical map or map book.
3. Click OK.
79
MN007396A01-D
The Map Book Import Tool Progress dialog box appears.

Figure 41: ArcCatalog – Map Book Import Tool Progress Dialog Box
4.1.21
Importing Cellular Towers
The Cell Tower Import Tool imports cellular tower sector coverage polygon features into the staging
geodatabase. Importing Cell Towers is optional. This data is used to display the cell tower sector coverage
area of an incoming Phase II wireless call on the map. The tool can be executed multiple times to import
cell towers from multiple source feature classes. Each imported Cell Tower feature class must have a unique
feature class name.
Procedure:
click the Cell Tower Import tool.
The Cell Tower Import dialog box appears.
80
MN007396A01-D
Figure 42: ArcCatalog – Cell Tower Import Tool

Fields with a browse button next to them can be populated be clicking Browse and navigating to the
appropriate field.
● Input Cell Tower Features – Fully qualified path of the cell tower source being imported (for
example, Z:\Data\MasterGIS.gdb\VerizonCell).
● Cell Tower ID – Cell tower source containing the tower IDs of the cell tower features.
● Cell Tower Sector ID – Cell tower source containing the sector IDs of the cell tower features.
3. Click OK.
The Cell Tower Import Tool Progress dialog box appears.
Figure 43: ArcCatalog – Cell Tower Import Tool Progress Dialog Box
81
MN007396A01-D
4.1.22
Importing Motorway Junctions
The Motorway Junction Import Tool imports motorway junction point features into the staging geodatabase.
Importing Motorway Junctions is optional. Motorway Junctions are used commonly in the United Kingdom
to describe sections of major roadways. For example, M25 J6 J7 S refers to a section of M25 Southbound
between Junction 6 (Westerham A25) and Junction 7 (Brighton M23). They are not commonly used in
the United States. They are imported into PremierOne as Common Places with a specific Place Type
that designates them as Motorway Junctions. The tool can be executed multiple times to import motorway
junctions from multiple source feature classes. Each imported motorway junction feature class must have a
unique feature class name.
Procedure:
click the Motorway Junction Import tool.
The Motorway Junction Import dialog box appears.
Figure 44: ArcCatalog – Motorway Junction Import Tool

appropriate field.
● Input Motorway Junction Features – Fully qualified path of the motorway junction source being
imported (for example, Z:\Data\MasterGIS.gdb\LondonMwayJcts).
● Motorway Name – Motorway junction source containing the motorway name.
● Junction 1 Name – Motorway junction source containing the name of the from junction.
● Junction 2 Name – Motorway junction source containing the name of the to junction.
● Direction – Motorway junction source containing the direction traveled between the two junctions.
3. Click OK.
82
MN007396A01-D
The Motorway Junction Import Tool Progress dialog box appears.

Figure 45: ArcCatalog – Motorway Junction Import Tool Progress Dialog Box
4.1.23
Creating PremierOne Mobile Client Data Packages
The Create Mobile Client Data Package Import Tool creates export files from the Enterprise GIS and SQL
Server databases for subsequent import into the SQL Express databases of PremierOne Mobile clients.
Procedure:
click the Create Mobile Client Data Package Import tool.
The Create Mobile Client Data Package dialog box appears.
83
MN007396A01-D
Figure 46: ArcCatalog – Create Mobile Client Data Package Dialog Box

appropriate field.

● Source SQL Instance – The name of the PremierOne SQL instance from which to extract the
GIS data. This may include server name (or IP address), SQL instance name, and Port (i.e.
10.54.252.46\PremierOne,7300).
● Mobile Database to Update – The Mobile database to update. Select GeoDB_A to update
Geodatabase A or GeoDB_B to update Geodatabase B.
● Source SQL GIS Database Name – The name of the SQL GIS database to export the GIS
data from (typically GISSQL_DATASET_A or GISSQL_DATASET_B). In most cases, this should
correspond to the Mobile Database to Update setting above.
● Source SQL GIS Reader User Name (optional) – The user name of the GIS Reader SQL
Authentication account (typically S-P1-GISSQL-Reader).
● Source SQL GIS Password (optional) – The password for the GIS Reader SQL Authentication
account.
● Source SQL PremiseHazard Database Name – The name of the SQL PremiseHazard database
(typically GISSQL_PremiseHazards).
● Source SQL PremiseHazard Reader User Name (optional) – The user name of the Premise
Hazard Reader SQL Authentication account (typically S-P1-PremiseHazardSQL).
● Source SQL PremiseHazard Password (optional) – The password for the Premise Hazard
Reader SQL Authentication account.
● Include Premise Hazard Attachments – Import Premise Hazard attachment records for local
and offline viewing. Premise Hazard Attachments are configured within provisioning
● Depending on the number and size of premise hazard attachments provisioned in the system, this
can make the size of the Mobile Client GIS data deployment package very large.
84
MN007396A01-D
● Output folder – Browse to the destination folder for the created export package.
3. Click OK.
The Create Mobile Client Data Package Import Tool Progress dialog box appears.
4.1.24
Copying GIS Data to the Enterprise Database
After all of the tools are executed to import all of the source GIS data, the data must be copied to the staging
(inactive) enterprise database. To determine which database (A or B) is active, go into the Provisioning
Console and view the GIS Data dialog box below the Mapping category:
When and where to use:
Figure 47: PremierOne Provisioning Console – GIS Data
In the screen shot, Geodatabase_A is active. Therefore, the staging data must be copied into
Geodatabase_B (whose associated enterprise database is named GISSQL_DATASET_B).
NOTE: The Copy Geodatabase To SQL Server tool supports connecting to the SQL enterprise
database using either Windows Authentication or SQL Authentication. To use Windows Authentication,
a database administrator must add your Windows account as a database login and grant the
db_datawriter privilege to your account for the GISSQL_DATASET_A and GISSQL_DATASET_B
databases. To use SQL Authentication, Motorola creates an SQL login and user called S-P1-GISSQL-
Admin. Motorola provides the password for this login to the GIS administrators.
Procedure:
click the Copy Geodatabase To SQL Server tool.
The Copy Geodatabase to SQL Server dialog box appears.
85
MN007396A01-D
Figure 48: Copy Geodatabase to SQL Server Import Tool

appropriate field.
● Source Geodatabase Workspace – Fully qualified path of the staging geodatabase (for example,
● Target SQL Instance – Name of the PremierOne SQL Server Instance on the SQL Always On
Listener Database Server (for example, P1-SQL-Listen\PremierOne).
● Target SQL Database Name – Name of the inactive PremierOne GIS database (for example,
GISSQL_DATASET_A). Verify which database is inactive by checking the GIS Data provisioning
dialog box.
● Target SQL Admin User Name – Target SQL Admin User Name – Login name for an SQL user
that has db_datawriter or db_owner privileges for the target SQL database. If an SQL login and
password is not specified, Windows authentication is used.
● Target SQL Password – Password for an SQL Admin User.
NOTE: If the user name and/or password contains a space, dash, or double quote
characters, the tool fails to run. Either create a user name/password without these
characters or use Windows authentication.
3. Click OK.
The Step5 CopyStagingToSql dialog box appears.
86
MN007396A01-D
Figure 49: Copy CopyStagingToSql Dialog Box

NOTE: The SQL GIS databases are automatically synchronized across the Primary and Failover
database servers. It is no longer necessary to copy the data to both the Primary and Failover
database servers. The Copy Geodatabase to SQL Server Import tool automatically deletes all
data in the Target database before copying data from the staging geodatabase.
4.1.25
Premise Hazard Area Import Tool
Premise Hazard Areas are features represented geometrically by a polygon (area) which represents
geographic areas associated with specific premise/hazard information. The initially intended use case for
Premise Hazard areas was for the purpose of associating gate codes for with incidents created within gated
communities. Premise Hazard records created at a particular address, place, or intersection is associated
with an incident that occurs within a specified radius of the premise hazard location. However, Premise
Hazard Areas provide a way to define precise areas to associate with a particular premise hazard record
when a simple radius search is not sufficient.
NOTE: Unlike the other GIS features mentioned in this chapter, Premise Hazard areas are not
contained within the A/B databases – it is stored in a single database containing only Premise Hazard
spatial data. Rather than importing Premise Hazard Areas into a staging database first, the data is
imported directly into the inactive enterprise database.
The Premise Hazard Area import tool requires a Layer file as input. Layer files consist of a link to data and
how that data is visualized on a map. The Premise Hazard Area Layer file supports single color symbolism
and transparency.
87
MN007396A01-D
4.1.25.1
Creating Premise Hazard Area Feature Classes
Before running the Premise Hazard Area import tool, a Premise Hazard Area feature class must be created,
populated with data, and configured in ArcMap.
Procedure:
1. In the Catalog Tree of ArcCatalog, right-click a geodatabase workspace and select New → Feature
Class.
2. Type the Feature Class name and if it is not already selected, select Polygon Features as the
features type.
3. Click Next.
4. Specify the Coordinate System for the feature class and click Next.
5. Specify the XY Tolerance for the feature class (or accept the default values) and click Next.
6. Specify the Database Configuration Keywords for the feature class (or accept the default values)
and click Next.
7. Add a field called AREA_NAME with a text data type and a maximum length of 50.
8. Optionally, add a field called DESCRIPTION with a text data type and a maximum length of 255.
9. Click Finish.
4.1.25.2
Populating Premise Hazard Area Feature Classes
After the feature class is created, you can populate the feature class.
Procedure:
1. Open ArcMap and select File → Add Data → Add Data.
2. Navigate to the Premise Hazard Area feature class and open it.
3. Use the Editor toolbar in ArcMap to create Premise Hazard Area feature geometries and specify
values for AREA_NAME (and optionally DESCRIPTION) for each Premise Hazard Area feature.
4. Right-click the layer, select Properties, and specify the properties for the layer (namely Symbology
and Labels).
5. After the layer properties are defined for the layer’s desired appearance, right-click the layer and
select Save as Layer File.
4.1.25.3
Importing Premise Hazard Areas Layers
The Premise Hazard Areas Import Tool imports premise hazard areas into the staging geodatabase.
Procedure:
click the Premise Hazard Area Import tool.
The Premise Hazard Area Import dialog box appears.
88
MN007396A01-D
Figure 50: ArcCatalog – Premise Hazard Area Import Tool

appropriate field.
● Target SQL Instance – The name of the PremierOne SQL Server Instance on the SQL Always
On Listener Database Server (for example, P1-SQL-Listen\PremierOne).
● Target SQL Database Name – The name of the PremierOne Premise Hazard database (for
example, GISSQL_PremiseHazards).
● Target SQL Admin User Name – The login name for an SQL user that has db_datawriter
privileges for the target SQL database. If an SQL login and password is not specified, Windows
authentication is used.
● Target SQL Password – The password for SQL Admin User.
● Premise Hazard Area Layer – Fully qualified path of the Premise Hazard Area layer file (for
example, Z:\Data\PremiseHazardAreas.lyr).
● Area Name Field – The Premise Hazard Area layer file source containing the name of the
Premise Hazard area.
● Area Description Field – The Premise Hazard Area layer file source containing a description for
the Premise Hazard area.
3. Click OK.
The Premise Hazard Area Import Tool Progress dialog box appears.
89
MN007396A01-D
Figure 51: ArcCatalog – Premise Hazard Area Import Tool Progress Dialog Box
4.1.26
Network Dataset Creation
This section describes the process for creating the standard PremierOne network dataset. The network
dataset is used for shortest path route solving, including ETA (estimated time of arrival) calculations and
driving directions. The most common source for creating a Network Dataset is a street centerline feature
class.
NOTE: The street centerline feature class used as the Network Dataset source does not need to be the
same street centerline feature class used as a source to the Street Centerline Import Tool. Motorola
recommends that separate street centerline feature classes be maintained for the specific usages
(address verification and routing). For example, it may be desirable for two crossing street segments to
generate an intersection for address verification purposes, but not for routing (such as highway
overpasses).
To simplify the network dataset creation process, use the Create Network Dataset Import Tool to define and
build a network dataset. The Create Network Dataset Import Tool supports the creation of simple networks
using only one edge source. If multiple edge sources are needed, use the ArcCatalog New Network Dataset
tool. Information about using the ArcCatalog New Network Dataset tool is covered later in this document.
4.1.27
Travel Costs Calculation Overview
The PremierOne Network routing feature dataset requires at least one distance and at least one time cost.
ArcGIS always maintains a shape length value for each feature in a feature class, which is suitable to use
for a distance-based cost attribute. However, a time-based cost is typically something that has to be manually
calculated. A time-based cost can be calculated as a function of distance (linear length) and average speed.
90
MN007396A01-D
4.1.27.1
Creating Average Speed Columns
To prepare for the calculating, ensure that the source street centerline feature classes include a column
containing values that indicate the typical travel speed. The values can often be calculated based on a road
type attribute.
Procedure:
1. In ArcMap, use the Add Data tool to add the source street centerline feature class to the map.
2. Right-click the street centerline layer in the Table of Contents and select Open Attribute Table.
Figure 52: ArcCatalog – ArcMap Open Attribute Table
The attribute table appears at the bottom of ArcMap.
91
MN007396A01-D
Figure 53: ArcCatalog – ArcMap Attribute Table
3. If one does not already exist, add a field to contain the average speed values. From the Table
drop-down list, select Add Field.
Figure 54: ArcCatalog – ArcMap Add Field
The Add Field dialog box appears.
92
MN007396A01-D
Figure 55: ArcCatalog – ArcMap Add Field Properties
4. Type a name for the new field, such as Speed and specify a data type of Long Integer. Click OK.
5. From the Editor tool bar, select Start Editing.
6. For each value in the domain of values representing road types (classes):
a. Click Select By Attributes and enter a query to select all features of a particular road type.
Figure 56: ArcCatalog – ArcMap Select by Attributes
b. Click Apply, then click Close.

c. Click Show Selected Records at the bottom of the attributes table so that only the records
matching the road type query are displayed.
d. Right-click the newly created field in the attributes table and select Field Calculator.
e. Enter the applicable average speed for this road type and click OK.
7. From the Editor tool bar, select Save Edits.
8. From the Editor tool bar, select Stop Editing.
93
MN007396A01-D
4.1.27.2
Creating Cost Columns
When both speed and linear distance values are available in the source street centerline feature class, a
time-based cost attribute can be calculated.
Procedure:
1. If a column in the street centerline source feature class representing the travel time does not exist,
add a field called Cost with a data type of Double. Refer to the Creating Average Speed Columns on
page 91 topic for the steps to add a field.
2. From the Editor tool bar, select Start Editing.
3. Right-click the Cost field in the attributes table and select Field Calculator.
Figure 57: ArcCatalog – ArcMap Field Calculator
4. Enter a formula to calculate the average travel time and click OK.
a. The conversion factor of the formula entered is dependent on the speed and length units of
measure and the desired units of measure for the time value.
b. To calculate a cost value in units of minutes, use the following table to determine the correct
formula to use:
Table 1: Cost Value Calculation Formulas
SPEED in mph SPEED in km/h

[SHAPE_LENGTH] COST = ([SHAPE LENGTH] * COST = ([SHAPE LENGTH] *
in Feet 0.0144) / [SPEED] 0.018288) / [SPEED]
[SHAPE_LENGTH] COST = ([SHAPE LENGTH] * COST = ([SHAPE LENGTH] *

in Meters 0.03728) / [SPEED] 0.06) / [SPEED]
94
MN007396A01-D
4.1.28
Network Dataset Source Data Overview
Network Datasets must reside in a feature dataset. When the Create PremierOne Geodatabase tool is
executed, it creates a feature dataset called ROUTING. Before running the Create PremierOne Network
Dataset tool, the source feature class containing the transportation network street centerlines must be copied
into the ROUTING feature class of the staging geodatabase.
4.1.28.1
Copying Feature Classes
Procedure:
1. Right-click the feature class in the ArcCatalog Catalog Tree and select Copy.
2. Right-click the ROUTING feature class of the staging geodatabase and select Paste.
If the source data is maintained in a coordinate system other than WGS 1984, the feature class must
be imported into the ROUTING feature dataset instead of copied. ArcGIS displays an error when
attempting to copy a feature class into a feature dataset with a coordinate system that does not match
that of the feature class.
4.1.28.2
Importing Feature Classes
Procedure:
1. Right-click the ROUTING feature class of the staging geodatabase and select Import → Feature
class (single).
2. Drag the source feature class from the ArcCatalog Catalog Tree to the Input Features text box.
3. Type a name for the output feature class, then click OK. It is recommended that you name the output
feature class Street_Net
4.1.29
Network Dataset XML Specification Configuration
The Create Network Dataset import tool requires an XML specification file as input. This file contains
information required to define the Network Dataset, including source data field mappings, cost attributes, and
restrictions (such as one-way streets). The Data Import Tools installer includes a sample XML specification
file called NetworkDatasetParams.xml, which can be found in the installation folder (C:\Program
Files (x86)\Motorola\PremierOne Data Import Tools). Create a copy of this file and edit it to
modify the Network Dataset settings as needed. The following sections describe how to modify each element.
NOTE: If you are not comfortable editing XML and/or VBScript code, contact your Motorola Project
Manager to request assistance.
4.1.29.1
Network Dataset Attributes Modification
The Network Dataset element should not be modified. It contains default values for the Network Dataset
name and Coordinate System that other PremierOne components are dependent on.
Example:
95
MN007396A01-D
<NetworkDataset Name="MOT_NET" SupportsTurns="True" spatRefType="G"

spatRefCode="4326"/>
4.1.29.2
EdgeSource Attributes Modification
The EdgeSource element defines the name and the field mappings of the network dataset edge source (the
street centerline feature class representing the routing network).
Example:
<EdgeSource FeatureClassName="Street_Net"
FromElevationFieldName="F_ZLEV" ToElevationFieldName = "T_ZLEV"

StreetNameFieldName="Name"
PrefixDirectionFieldName="Prefix_DIR" PrefixTypeFieldName="Prefix_Typ"
SuffixTypeFieldName="Suffix_Typ" SuffixDirectionFieldName="Suffix_DIR"/>
The FeatureClassName element value must match the name of the edge source (input) feature class. In this
example, the name of the feature class is Street.
The FromElevationFieldName and ToElevationFieldName elements are optional. If the source edge
feature class contains fields to represent the relative elevation of edge endpoints, the names of these fields
is put into these elements. If elevation fields are unavailable in the source, there should be no value between
the double quotes as shown below.
Example:
FromElevationFieldName="" ToElevationFieldName = ""
The remainder of the elements represent the parts of a street name. If the street names are not parsed out
to store prefixes and suffixes in separate fields, then the StreetNameFieldName should be set to the name
of the field that contains the complete street name. Otherwise, provide the field names for each street name
part in the appropriate element. If a particular street part does not have a mapping, there should be no value
between the double quotes.
4.1.29.3
CostAttributes Modification
The sample XML specification includes three example cost attributes: Cost, CostPlusLeftTurnPenalty, and
Distance. PremierOne requires at least one cost attribute that is time-based and at least one cost attribute
that is distance-based. It is recommended that the sample Cost and Distance attributes be modified as
96
MN007396A01-D
needed. The CostPlusLeftTurnPenalty can be removed if having a cost attribute that adds a small time
penalty for making a left turn is not desired.
IMPORTANT:
CostPlusLeftTurnPenalty is a script based evaluator which is not supported in ARC Pro. It is
recommended that you change the script based evaluator to a global turn delay if bringing the routing
network into ARC Pro. For more information, see Defining Global Turn Delays on page 125.
Example:
<Cost Name="Cost" Units="esriNAUMinutes" DataType="esriNADTDouble"

UseByDefault="true">
<SourceValue FeatureClassName="Street_Net" Direction="From-To"

ExpressionType="Field" Value="FT_COST" Expression=""/>
<SourceValue FeatureClassName="Street_Net" Direction="To-From"

ExpressionType="Field" Value="TF_COST" Expression=""/>
<DefaultEvaluator ElementType="esriNETEdge" ExpressionType="Constant"

Value="0" Expression=""/>
<DefaultEvaluator ElementType="esriNETJunction" ExpressionType="Constant"

<DefaultEvaluator ElementType="esriNETTurn" ExpressionType="Constant"

</Cost>
The Name attribute defines the name of the cost attribute. The cost attributes defined here comprise the list
of available costs in Route Settings provisioning. The Units attribute defines the unit of measure that the
source cost data is represented in. The previous example states that the values contained in the FT_COST
and TF_COST fields are expressed in units of minutes.
Possible values for this attribute are:
● esriNAUInches (Inches – Distance)
● esriNAUFeet (Feet – Distance)
● esriNAUYards (Yards – Distance)
● esriNAUMiles (Miles – Distance)
● esriNAUMillimeters (Millimeters – Distance)
● esriNAUCentimeters (Centimeters – Distance)
● esriNAUMeters (Meters – Distance)
● esriNAUKilometers (Kilometers – Distance)
● esriNAUDecimalDegrees (Decimal Degrees – Distance)
● esriNAUDecimeters (Decimeters – Distance)
● esriNAUSeconds (Seconds – Time)
● esriNAUMinutes (Minutes – Time)
● esriNAUHours (Hours – Time)
● esriNAUDays (Days – Time)
97
MN007396A01-D
The DataType attribute specifies the data type of the cost fields in the edge source feature class.
● esriNADTInteger (Source field is defined as Long Integer or Short Integer)
● esriNADTFloat (Source field is defined as Float)
● esriNADTDouble (Source field is defined as Double)
The UseByDefault attribute specifies whether this cost attribute should be used by default when solving
routes in ArcMap. It has no bearing on solving routes in PremierOne.
The FeatureClassName value should be the same as the FeatureClassName value defined in the
EdgeSource element.
There are two SourceValue elements – one specifying the cost of traversing the edge in the From-To
direction and the other specifying the cost of traversing the edge in the To-From direction. The values of
these fields should be the names of the edge source fields containing these respective values. If only one
cost field is maintained in the source which applies to travel in either direction, these attribute values is the
name of that lone cost field.
The DefaultEvaluator elements should not be modified.
4.1.29.4
RestrictionAttributes Modification
The RestrictionAttributes elements define the travel restrictions for individual network edges. The most
common restriction attribute is for network edges that allow for travelling in only one direction (one-way
streets). Other restrictions, such as height and weight restrictions, can be defined. To make proper use of
height/weight restrictions, you need to maintain fields in the edge source that specify whether a particular
vehicle type can travel that segment or not. The sample XML specification contains several sample height/
weight example attributes. It is recommended to delete any RestrictionAttribute attributes that you cannot use
based on the available source data.
Example of the OneWay restriction element:
<Restriction Name="OneWay" UseByDefault="false">
<SourceValue FeatureClassName="Street_Net" Direction="From-To"

ExpressionType="Field" Value="restricted" Expression="restricted =
False;Select Case UCase([One_way]);Case "NT", "TF":
restricted = True;End Select"/>
<SourceValue FeatureClassName="Street_Net" Direction="To-From"

ExpressionType="Field" Value="restricted" Expression="restricted =
False;Select Case UCase([One_way]);Case "NT", "FT":
restricted = True;End Select"/>
<DefaultEvaluator ElementType="esriNETEdge" ExpressionType="Constant"

<DefaultEvaluator ElementType="esriNETJunction" ExpressionType="Constant"

<DefaultEvaluator ElementType="esriNETTurn" ExpressionType="Constant"

</Restriction>
98
MN007396A01-D
Name attribute
Specifies the name of the restriction attribute. After the attribute is built, a list of restriction attributes in the
Network Dataset appears in Route Settings provisioning.
UseByDefault attribute
Specifies whether this cost attribute should be used by default when solving routes in ArcMap. It has no
bearing on solving routes in PremierOne.
FeatureClassName value
This value should be the same as the FeatureClassName value defined in the EdgeSource element.
SourceValue elements
There are two SourceValue elements: one specifying the restriction criteria of traversing the edge in the
From-To direction and the other specifying the restriction criteria of traversing the edge in the To-From
direction. The criteria is defined as a VBScript comparison.
Example:
restricted = False;
Select Case UCase([One_way]);
Case "NT", "TF": restricted = True;
End Select
In this example, taken from the element defined for travel in the From-To direction, the name of the field in
the edge source containing values that define the directions of allowable travel for a particular edge is called
One_way. The field name can be modified if the edge source contains this information in a field having a
different name. The example sets the restricted value to True for a particular edge when traveling in the
From-To direction of the One Way field contains a value of NT (No Travel) or TF (To-From direction). If the
values in the edge source feature are different than the values used in this example (TF, FT, and NT), it is
required to modify the evaluation script accordingly.
4.1.29.5
Directions Attributes Modification
The Directions element defines how turn-by-turn drive directions should be formatted.
Example:
<Directions DisplayLengthUnits="esriNAUMiles" TimeAttributeName="Cost"

LengthAttributeName="Distance"/>
The DisplayLengthUnits attribute specifies the distance unit of measure that is displayed in the turn-by-turn
drive directions.
● esriNAUInches (Inches – Distance)
● esriNAUFeet (Feet – Distance)
● esriNAUYards (Yards – Distance)
● esriNAUMiles (Miles – Distance)
● esriNAUMillimeters (Millimeters – Distance)
● esriNAUCentimeters (Centimeters – Distance)
● esriNAUMeters (Meters – Distance)
99
MN007396A01-D
● esriNAUKilometers (Kilometers – Distance)

● esriNAUDecimalDegrees (Decimal Degrees – Distance)
● esriNAUDecimeters (Decimeters – Distance)
For example, although the distance-based cost attribute may be defined in units of decimal degrees, showing
the number of decimal degrees until the next turn may not be very useful. If the DisplayLengthUnits attribute
is set to esriNAUMiles, the drive directions convert the distance value from its source unit of measure to
Miles when displaying drive directions.
The TimeAttributeName attribute specifies the name of the time-based cost attribute that is used to display
travel time in the turn-by-turn drive directions. This value must match the name of a defined CostAttribute
element.
The LengthAttributeName attribute specifies the name of the distance-based cost attribute that is used to
display travel distance in the turn-by-turn drive directions. This value must match the name of a defined
CostAttribute element.
4.1.29.6
Verifying XML Files
Validate the correctness of the XML syntax by opening the XML file in Internet Explorer.
Procedure:
1. Double-click the file to open the document in the default Internet browser. If the browser displays an
error message, the XML file is not well-formed.
2. Determine what is wrong with the XML and correct the error.
NOTE: Opening the document in an Internet browser only validates the file for XML formatting
correctness. If any of the GIS table/field names are invalid, no error displays. However, an error
is encountered when you execute the Create Network Dataset import tool.
4.1.30
Creating Building Network Datasets
After the XML Specification file is edited as needed, the Create PremierOne Network Dataset Import Tool can
be used to create and build the network dataset.
Procedure:
click the Create PremierOne Network Dataset tool.
The Create PremierOne NetworkDataset dialog box appears.
100
MN007396A01-D
Figure 58: ArcCatalog – Create Network Dataset Import Tool

appropriate field.
● Input Network dataset XML File – Fully qualified path of the XML Specification file that defines
the properties of the Network Dataset to create.
3. Click OK.
The Create PremierOne Network Dataset Import Tool Progress dialog box appears.
Figure 59: ArcCatalog – Create Network Dataset Import Tool Progress Dialog Box
101
MN007396A01-D
4.1.31
ArcCatalog New Network Dataset Wizard Overview
If the source data for the transportation network is stored in multiple feature classes, a custom turn feature
class is needed, or connectivity rules need to be specified, the ArcCatalog New Network Dataset Wizard
cand be used instead of the Create PremierOne Network Dataset Import Tool.
Refer to the ESRI ArcGIS Resources website for comprehensive information about using this tool. The topic
can be found at http://desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/creating-a-network-
dataset.htm.
A PremierOne Network Dataset should be named MOT_NET and needs to contain at least one time-based
cost attribute called Cost and at least one distance-based attribute called Distance.
4.1.32
Verifying Network Datasets Using ArcMap
Before publishing Network Analyst services or deploying a Network Dataset to mobile clients, it is
recommended that the Network Dataset be verified in ArcMap after it is built.
Procedure:
1. In ArcMap, click the Add Data tool button.
The Add Data dialog box appears.
Figure 60: ArcCatalog – ArcMap Add Data
2. Select MOT_NET, and then click Add.

The Adding Network Layer dialog box appears.
102
MN007396A01-D
Figure 61: ArcCatalog – ArcMap Add Data
3. Click No.
4. From the list on the Network Analyst toolbar, select New Route.
103
MN007396A01-D
Figure 62: ArcCatalog – ArcMap New Route
NOTE: If the Network Analyst tool bar is not available, right-click the tool bar area, select
Customize, and select the Network Analyst tool bar.
5. Select the Create Network Location Tool and click two or more road locations.
Figure 63: ArcCatalog – ArcMap Create Network Locations
6. Click the Directions icon.

The Directions dialog box appears.
104
MN007396A01-D
Figure 64: ArcCatalog – ArcMap Network Directions
7. Verify that the route, drive directions, and travel times/distances calculated are as expected.
4.1.33
Model Creation to Import Data
To simplify the import process and provide a consistent process for running the Data Import Tools, the use of
Geoprocessing Models is recommended.
More information about creating models can be found at the ESRI ArcGIS Resources website:http://
desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/creating-a-network-dataset.htm
105
MN007396A01-D
Chapter 5: Introduction to ArcGIS Server
Chapter 5
Introduction to ArcGIS Server

ArcGIS for Server is software that makes the geographic information available to others in your organization
and optionally anyone with an Internet connection via web services. Making this geographic information
available in ArcGIS Server is known as publishing. ArcGIS Server support several types of Map Services, but
PremierOne only uses Mapping and Routing services.
A typical PremierOne production system has two Virtual Machines dedicated for ArcGIS Server. Because
each ArcGIS Server Virtual Machine is an autonomous ArcGIS Server site, all services need to be published
separately to each ArcGIS Server instance.
5.1
ArcGIS Server User Security
ArcGIS Server supports three types of user roles.
Administrator
An Administrator can perform all functions supported by ArcGIS Server. This role should typically be
reserved for users providing technical support. A primary site administrator account is automatically
created when ArcGIS Server is installed to allow the installer to log into ArcGIS Manager and configure
initial security settings. This account remains active for Motorola deployment and customer support
activities.
Publisher
A Publisher can log into ArcGIS Server Manager with access only to the Services and Log Management
features. This role should typically be reserved for members of the GIS department.
User
A user may only consume a published ArcGIS Server service.
When adding an ArcGIS User, a password and role must be specified. Motorola recommends creating user
accounts for each person needing Administrator or Publisher access. For PremierOne use, create a generic
user called CadUser (It is not necessary to create a User-level role and assign the user to that role; new
users are given User-level permissions by default). This user is used when creating GIS Server connections
from within ArcGIS Desktop when authoring maps that consume mapping services.
Since all PremierOne ArcGIS Server installations are autonomous instances, any roles/users added to one of
the instances must also be manually added to the other instances using the same user name and password.
5.2
GIS Server Connections Overview
To perform ArcGIS Server functions from ArcGIS Desktop, GIS Server connections need to be created.
Production systems use a firewall called F5 to separate clients from the PremierOne servers. A PremierOne
system also uses a load balancing mechanism to route client requests evenly across all available servers.
In order to publish an ArcGIS Server to a particular ArcGIS Server VM (Virtual Machine), a specific port
number needs to be specified. F5 uses this port number to route the request to a specific ArcGIS server
virtual machine. However, for client consumption services, requests should be load balanced to either ArcGIS
VM01, or ArcGIS VM02.
ArcGIS Server also supports connections on both unsecured ports and ports secured with Secure Sockets
Layer (SSL). In order to take advantage of the SSL port, an SSL Certificate needs to be installed on client
106
MN007396A01-D
workstations that consume ArcGIS Services. Using SSL is not required, however, if there is any chance that
someone outside your organization could access the PremierOne system, Motorola recommends using SSL.
The following diagram shows how the different ArcGIS Server ports are handled by F5.
Figure 65: ArcGIS Server Ports – F5 Connections
Table 2: ArcGIS Server Ports
Unsecured Port Secured (SSL Port)

Client read-only access (load balanced) 6080 6443
Publish to ArcGIS VM01 6081 6444
Publish to ArcGIS VM02 6082 6445
5.2.1
Creating GIS Server Connections
Procedure:
1. In the Catalog Tree of ArcMap or ArcCatalog, navigate to the GIS Servers folder.
2. Double-click Add ArcGIS Server.
The Add ArcGIS Server wizard appears
107
MN007396A01-D
Figure 66: ArcGIS Desktop – Add ArcGIS Server Role Select
3. Specify how this connection is used.

● Select Publish GIS services if this connection is used to publish services.
● Select Use GIS services if this connection is used to add mapping services as layers to end-user
map documents.
4. Click Next.
The ArcGIS Server User Connection Properties dialog appears.
108
MN007396A01-D
Figure 67: ArcGIS Desktop – Server User Connection Properties
5. Enter the requested information according to the descriptions in the following table:
Table 3: ArcGIS Server Connection Information
Use Case URL UserName
Administer services and http://local► The user name of a mem-

build mapping cache tiles host:6080/arcgis ber of the administrator or
on GIS department ArcGIS publisher role.
Server (choose Publish This assumes that the ArcGIS Serv-
GIS Services) er is installed on the same machine
as the ArcGIS Desktop from which
the connection is being created.
Otherwise, replace localhost with
the IP Address or Host Name of the
ArcGIS Server.
Publish services to an Arc- http://<host>:<port> The user name of a mem-

GIS Server instance that is ber of the Publisher role.
installed on a PremierOne Where <host> is an IP Address or
Application Server (choose Host Name.
Publish GIS Services) In deployments where an F5 firewall
is in place, either a secured or unse-
cured connection can be used. If us-
109
MN007396A01-D
Use Case URL UserName

ing a secured port, you must use a
host name and that host name must
be resolvable by a Domain Name
Service or must manually be entered
in the Windows HOSTS file. Specify
a Publish to port number from
the table in the GIS Server Connec-
tions Overview on page 106 section.
If a F5 is not in place, create a con-
nection using the IP Address of the
specific ArcGIS Server VM and use
port 6080.
Use ArcGIS Services pub- http://<host>:<port>/arc► The user name of a mem-

lished on the PremierOne gis ber of the User role.
Application Servers (choose
Use GIS Mapping Serv- Where <host> is an IP Address or
ices) Host Name.
For User connections, it is required
that a secured port be used and the
host name of the F5 and port 6443.
If F5 is not in place, use the IP Ad-
dress of the single ArcGIS Server
and port 6080.
The Save Username/Password checkbox must be checked for the Use GIS services connection.
Otherwise, CAD Client map users are prompted for a password when attempting to load a map using
mapping services. For Administer/Publisher connections, unchecking Save Username/Password
prevents unauthorized access to GIS Server by anyone who gains unauthorized access to the ArcGIS
Desktop workstation. Each time a connection attempt is made, the ArcGIS Server password must be
entered. If security is not a concern, the Save Username/Password box may remain unchecked for
administer/publisher connections.
NOTE: ArcGIS Server utilizes port 6080 for unsecure (unencrypted) access to ArcGIS Server. If
requested, Motorola may block this port on the firewall to prevent users from connecting to
ArcGIS Server on the unsecure port. Port 6443 is used for secure (SSL encrypted) connections
to ArcGIS Servers and should be specified in the Server URL whenever connecting to a
PremierOne Application Server. This requires an SSL certificate to be installed on the ArcGIS
Administrator workstation. Motorola provides this certificate file (which must also be installed on
any CAD Client workstations that use maps consuming mapping services).
110
MN007396A01-D
5.3
Accessing Server Managers
ArcGIS Server Manager (Manager) is used to administer an ArcGIS Server site, including managing users,
roles, and services. The most user-friendly way to access Manager is from an Administer/Publisher GIS
Server Connection object.
Procedure:
1. Right-click the connection and select ArcGIS Server Manager.
This action launches the browser and automatically specifies the URL for the Manager service for the
ArcGIS Server associated with the specific GIS Server Connection object.
Figure 68: ArcGIS Server Manager – Login
2. Type your credentials and click Login.

NOTE: Usernames and passwords are case-sensitive.
111
MN007396A01-D
Figure 69: ArcGIS Server Manager – Services
The Manager dialog box displays following options:

Services
Administer, configure, and publish ArcGIS Server services.
Site
Configure options for the ArcGIS Server site.
Security
Manage security options, roles, and users.
Logs
Review errors, warnings, and information reported by ArcGIS Server.
The Services tab is selected by default upon logging into Manager. A list of folders appears on the left
side of the dialog box. The System and Utilities folders are added by default when ArcGIS Server is
installed. An additional folder called PremierOne should be created. All of the services published for
use with PremierOne should be published inside the PremierOne folder.
112
MN007396A01-D
Chapter 6: Network Analyst Service Publication
Chapter 6
Network Analyst Service Publication

Publishing network analyst services is required. The network analyst service is used to calculate driving
directions and Estimated Times of Arrival (ETAs). An A service is published for use when Geodatabase_A
is the provisioned Active Geodatabase, and a B service is published for use when Geodatabase_B is the
provisioned Active Geodatabase.
6.1
Publishing a Network Analyst Service
Procedure:
1. Create a map using ArcMap.
The Network Analyst map only needs to contain a Network Dataset and at least one Network
Analyst solver layer. Only the underlying data is used for routing and it is never visualized as a map.
2. Add the Routing and Closest Facility Layer to the map.
3. From the ArcMap Network Analyst list, select New Route.
A route solver layer is added to the map.
4. From the ArcMap Network Analyst list, select New Closest Facility.
A closest facility solver layer is added to the map.
Figure 70: ArcMap – Network Analyst Toolbar
The new map with the additional layers should look like the following illustration:
113
MN007396A01-D
Figure 71: ArcMap – Network Analyst Map
6.2
Modifying Layer Connectivity Properties
Procedure:
1. From the Network Analyst toolbar, click Show/Hide Network Analyst Window.
2. Select the Closest Facility layer from the menu.
Figure 72: Network Analyst Layers
NOTE: The connectivity properties need to be set for both layers
3. Click Properties.
The route Layer Properties window displays.
114
MN007396A01-D
Figure 73: ArcMap Layer Properties – Network Locations
4. Select the Network Locations tab.

5. Select the MOT_NET_Junctions layer and click the Up arrow until it appears at the top of the Snap
To list.
6. Select the checkbox in the Shape column.
NOTE: Ensure that the Snap To option is set to Closest.
7. Select File, and then click Save to save the map file.
It can be used to overwrite the routing service when needed.
8. Repeat steps step 2 – step 7, this time selecting the Route layer in step step 2.
115
MN007396A01-D
6.3
Changing the Route To Settings
The default Route To setting is to route from the Incident to Facility. You can change this setting in the
Analysis Settings tab.
Procedure:
1. From the Layer Properties window, click the Analysis Settings tab.
Figure 74: Layer Properties Window - Analysis Settings Tab
2. In the Travel From section, select the Facility to Incident option.

3. Optional: Apply any necessary restrictions by selecting them within the Restrictions panel. For
example, select the One Way checkbox to indicate a one way road.
116
MN007396A01-D
4. Click OK.
The Route To setting is changed. The map routes you from your facility to the incident location.
6.4
Publishing Network Analyst Services
The Network Analyst Service must be published on all PremierOne ArcGIS Server Virtual Machines for the
specific PremierOne environment. For example, Production, Training, or Staging.
Procedure:
1. After the map is created, select File → Share As → Service... from the ArcMap main menu.
Figure 75: ArcMap – Share As Service
The Share as Service dialog box appears.
117
MN007396A01-D
Figure 76: ArcMap – Share as Service Dialog Box
IMPORTANT: Saving as a service definition file is only recommended when a direct connection
to the GIS server is not available. Overriding a service maintains the originally applied service
settings, whereas the Service Definition requires all the service settings to be rebuilt.
2. Select Overwrite an existing service and then click Next.
The Overwrite an Existing Service dialog displays.
118
MN007396A01-D
Figure 77: Overwrite An Existing Service Dialog
3. Select a Publisher or Admin GIS Server connection from the Choose a connection menu.
The Service list is populated with services on that Server.
4. Select the service to overwrite and click Continue.
The service is overwritten and the Service Editor dialog box appears. The Service Editor dialog box
allows the configuration of the following service options:
● Parameters – Click the Parameters tab and then click Advanced. Set the
setSchemaLockingEnabled option to false (case-sensitive). A false setting prevents schema
lock files from being created in the cache folder and subsequently replicated to the other
Application Servers.
● Capabilities – An ArcGIS Service exposes a Mapping capability by default. The KML capability is
also added by default and can be unchecked. Check the Network Analysis capability.
● Pooling Tab – Set Minimum number of instances per machine to 2, and the Maximum
number of instances per machine to 4. Motorola provides guidance for the Maximum number
of instances per machine based on the number of CAD Clients and the estimated frequency of
service requests. Motorola may change the defaults at any time if it is determined that the default
settings cannot adequately handle user requests.
● Processes Tab – Accept the defaults. If it is determined that the default settings cannot
adequately handle user requests, Motorola may change the defaults at any time.
● Item Description Tab – The GIS Administrator may optionally provide any metadata information
applicable to the service.
5. After all of the service settings are specified, click Stage. The service has now been staged as a
service definition file in the specified folder location.
119
MN007396A01-D
6. To publish a service from a service definition file to an ArcGIS Server, use the Catalog Tree in ArcMap
to navigate to the folder location of the service definition file. Right-click on the service definition file
and select Publish as a service…
NOTE: When overwriting a service that already exists on the destination ArcGIS Server with the
same service name, the existing service must be deleted before publishing.
Figure 78: Publish Service from Service Definition File
The Publishing a Service dialog appears.
120
MN007396A01-D
Figure 79: Publishing a Service Dialog
7. In the Connection drop-down, select a previously created Publisher or Admin ArcGIS Server
connection for a specific PremierOne ArcGIS Server Virtual Machine.
8. Under Publish service to folder:, select the Use an existing folder → PremierOne.
9. Click Finish.
The service is now published to ArcGIS Server.
10. Repeat this step until the service has been published to all PremierOne ArcGIS Server Virtual
Machines on the specific PremierOne Environment.
121
MN007396A01-D
Chapter 7: Mobile Map Packages for Mobile Map
Chapter 7
Mobile Map Packages for Mobile Map

A Mobile Map Package (.mmpk file) can be created for the Mobile map by using ArcGIS Pro.
7.1
Installing ArcGIS Pro
Licensees of ArcGIS Desktop may download, install, and license ArcGIS Pro at no additional cost. ArcGIS
Pro is most commonly downloaded from the http://my.esri.com website. If you do not have a personal account
for this website linked to your site’s ESRI Organization, or do not have permission to download product
components, check with your organization’s ESRI administrative contact. ArcGIS Desktop is not an OEM
component of PremierOne, so customers are expected to maintain their own relationship with ESRI for the
purpose of purchasing and licensing ArcGIS Desktop and ArcGIS Pro.
Procedure:
1. Log into My Esri: http://my.esri.com.
2. From the main menu, select the My Organizations → Downloads.
3. The Downloads page appears, with the Products sub-menu on the left side of the screen selected.
Figure 80: My Esri Downloads Page
4. Download the latest release of ArcGIS Pro unless otherwise directed by Motorola Solutions.
PremierOne Mobile supports ArcGIS Pro 2.8 and 2.9.
5. Run the installer file.
7.2
ArcGIS Pro Licensing Overview
By default, ArcGIS Pro utilizes Named Users. The use of Named Users requires authentication against an
ArcGIS Online site specific to an organization or an organization’s ArcGIS Enterprise Portal.
Refer to the following topic on ESRI’s website:
122
MN007396A01-D
● Named User Licensing with ArcGIS Enterprise: https://pro.arcgis.com/en/pro-app/get-started/overview-of-

named-user-licensing-in-arcgis-enterprise.htm.
Converting a Named User license to a Single Use or Concurrent Use license is also an option, depending
on how the ArcGIS Desktop is licensed. This process involves making a request through My Esri for
conversion of the license.
For more information, refer to the following topics on ESRI’s website:
Single Use Licensing: https://pro.arcgis.com/en/pro-app/get-started/single-use-licenses.htm
Concurrent Use Licensing: https://pro.arcgis.com/en/pro-app/get-started/concurrent-use-licenses.htm.
7.3
Initializing ArcGIS Pro Projects
Procedure:
1. Launch ArcGIS Pro.
2. Select Start without a template.
Figure 81: ArcGIS Pro – Start Without A Template
3. When the project opens, select Insert → Import Map.

4. Browse to the ArcMap document to import. A new map tab opens, displaying the imported map.
Motorola Solutions recommends that at this point a shortcut is added to the folder containing the
ArcMap’s source File Geodatabase for easy access.
5. Select Catalog Pane from the View tab. Right-click the Folders item and select Add Folder
Connection.
123
MN007396A01-D
Figure 82: ArcGIS Pro – Add Folder Connection
6. Browse to the folder containing the File Geodatabase (*.gdb) folder and click OK.
7. Navigate around the map after importing to make sure that everything appears as expected at
different map scales.
7.4
SQL Queries Overview
It is common to use SQL Queries for things like label classes and layer query definitions. Sometimes when
importing a map with SQL Queries and then subsequently creating a Mobile Map Package, those queries
do not perform as expected in applications using ArcGIS Runtime. This is due to slight variations in SQL
specifications. Mobile Map Packages store data in a SQLLite format. Queries that behave as expected in
ArcGIS Pro against a file geodatabase may not behave exactly the same when applied to a Mobile Map
124
MN007396A01-D
Package against a SQLLite database. After creating a Mobile Map Package, navigate around the Mobile Map
to make sure that everything (especially labels) appear as expected at different map scales.
7.5
Basemaps
Basemaps serve as a reference map on which data is overlayed from operational layers, perform analysis,
and visualize geographic information. ArcGIS Pro provides several predefined basemap layers to use in the
maps and will typically add one by default when a new map is created in a project. However, basemap
layers cannot be exported to a Mobile Map Package. They must be removed before creating the Mobile Map
Package.
7.6
Network Analyst Support Additions
ArcGIS Pro does not yet support creating a Network Dataset (as of v2.4). The PremierOne Create Network
Dataset import tool or ArcMap/ArcCatalog’s own Network Analysis toolset can be used instead.
7.6.1
Defining Global Turn Delays
Currently, Mobile Map Packages do not support script-based default values for attribute evaluators. Many
PremierOne users have a CostPlusLeftTurnPenalty attribute which uses a script-based evaluator as a
default on Turn elements. The use of such evaluators will need to be replaced by defining a Global Turn
Delay. For more information on CostPlusLeftTurnPenalty, see CostAttributes Modification on page 96.
Procedure:
1. Open the Network Dataset Properties dialog box:
a. On the Standard tool bar, click the Catalog window button.
The dockable Catalog window appears.
b. Navigate to the location of the network dataset, right-click and select Properties.
The Network Dataset Properties dialog box appears.
2. Select the CostPlusLeftTurnPenalty attribute, and then click the Evaluators button.
3. For the Turn element, under Type, select Global Turn Delay.
125
MN007396A01-D
Figure 83: ArcGIS Pro – Select Global Turn Delay
4. Press the Evaluator Properties button (highlighted in red in Figure 83: ArcGIS Pro – Select Global
Turn Delay on page 126) to define the properties of the Global Turn Delay.
Figure 84: ArcGIS Pro – Define Global Turn Delay
5. Refer to the following ESRI link to learn more on how to define Global Turn Delay evaluators:
http://desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/global-turns-establishing-
global-turns.htm
126
MN007396A01-D
The PremierOne Create Network Dataset Import Tool does not currently support defining Global Turn
Delays, so GIS Administrators will need to define them manually after creating the network and then
re-build the network dataset.
7.6.2
Creating Network Dataset Layers
To support offline routing using a Mobile Map Package, a Network Dataset Layer must be added to the map.
Procedure:
1. Display the Geoprocessing Tools window by selecting the Analysis tab and clicking the Tools
button.
Figure 85: Geoprocessing Tools – Analysis – Tools
2. In the Geoprocessing Tools window, select the Make Network Dataset Layer tool.
This tool can be added to Favorites by right-clicking and selecting Add To Favorites.
Figure 86: Geoprocessing Tools – Make Network
The Make Network Dataset Layer wizard displays.
Figure 87: Make Network Dataset Layer Wizard
127
MN007396A01-D
3. Next to the Input Network Dataset entry box, click the Folder icon to browse for an existing Network
Dataset.
Upon selecting a Network Dataset, the Output Layer is automatically populated with the name of the
Network Dataset. This layer name can be changed. After clicking Run, the network dataset layer is
added to the map. It is recommended that the network dataset layer be unchecked (not visible) in the
table of contents.
7.7
Creating Address Locators
Procedure:
1. Search for the Create Address Locator geoprocessing tool (see Creating Network Dataset Layers on
page 127).
Consider adding the tool to Favorites by right-clicking and selecting Add To Favorites.
Figure 88: Search For Create Address Locator Tool
2. Select the Create Locator Tool.

The Create Locator Wizard appears.
128
MN007396A01-D
Figure 89: Create Locator Wizard
3. Select U.S Address – Dual Ranges, which supports low and high addresses on each side of the
street. This is the most common Address style for the U.S. Select the tables that will participate in the
Locator.
At a minimum, add a Street Address layer and specify a Role of Street Address.
If users will want to search for Common Places, add one or more Common Place layers and specify
a role of POI (Point of Interest).
At this time, Motorola Solutions does not recommend adding an Address Point layer because it
dramatically increases the size of the map package. Depending on your operational needs, Street
Address locating should be sufficient in most cases.
4. Under Reference Data, select the layer that contains the addressing data. After specifying the locator
layers and roles, map the Field Names to the appropriate attribute names in the source data. Field
names preceded by an asterisk are required.
5. Map the address attributes to the field names in the reference data layer.
129
MN007396A01-D
6. Specify the name and location to create the locator. Motorola Solutions recommends saving the file
under the project’s ArcGIS Pro project folder.
7. To allow the Mobile Map to show match suggestions as an address is being typed in, check Enable
Suggestions. Select the Language Code (typically English).
8. Press the Run button.
If the tool finishes successfully, the Locator file is written to the location specified.
7.8
Creating Mobile Map Packages
A Mobile Map Package is represented by a single file on disk having a file extension of mmpk. A Mobile Map
Package is the only local data store supported by ArcGIS Runtime – the software library upon which Mobile
Map is built. The mmpk files are a replacement to ArcMap documents (*.mxd) and file geodatabases
(*.gdb). An mmpk file is actually multiple files compressed into one. Such files can include map definitions, a
SQLite database, locators, geoprocessing tools, and so on. The mmpks will be used to support offline
mapping. ArcGIS Pro is used to create mmpks – ArcMap does not provide this functionality.
The mobile map package is supported by the ESRI ArcPro software. It supports multiple maps within a single
mmpk file.
Procedure:
1. Search for the Create Mobile Map Package geoprocessing tool (see Creating Network Dataset
Layers on page 127).
Consider adding the tool to your Favorites by right-clicking and selecting Add To Favorites.
Figure 90: Search For Create Mobile Map Package Tool
The Create Mobile Map Package wizard appears.
130
MN007396A01-D
Figure 91: Create Mobile Map Package Tool
The Input Map should automatically populate with the active map in your ArcGIS Pro project. Change
the map or add additional maps if necessary using the drop-down button.
2. Select a location and name of the output mmpk file to create.
3. Specify a Locator.
Mobile Map utilizes a Locator for address search functions within the Mobile Map only.
4. Select the Area of Interest.
Typically, this will be a union of the map data. However, if you only want to generate a subset (clip) of
the map, select a different option (such as Current Display Extent or by specifying a polygon layer).
5. Give the map package a Title.
6. Press the Run button.
If the tool finishes successfully, the mmpk file is written to the location specified.
7.9
Mobile Map Package Deployment
When Mobile Map is installed, there is a folder called mmpk in the installation directory. The mmpk file(s)
need to be copied to that location. The PremierOne All-In-One tool will soon be enhanced to add mmpk files
to a deployment package and the files will automatically be copied to the expected location.
131
MN007396A01-D
Chapter 8: Map Authoring Requirements for PremierOne CAD and Mobile Clients
Chapter 8
Map Authoring Requirements for

PremierOne CAD and Mobile Clients
The CAD and Mobile clients require ArcGIS version 10.8.1.
8.1
Relative File Paths Overview
Motorola recommends that Mobile Client maps be configured to use relative file paths when storing paths to
data sources in the map document. When relative file paths are enabled, paths to data sources are stored
in a format that describes the location of the data source relative to the location which the map document is
saved.
If relative file paths are not used, the fully-qualified path to the data source is stored in the map document file.
This file path can be problematic if the source data on the GIS Administrator is stored on a drive letter that
does not exist on the Mobile Client laptops. It can also be a problem when there is a mix of 32-bit and 64-bit
Windows Operating Systems across the Mobile Client laptop inventory, as the Mobile Client Deployment
package is installed by default to a folder in C:\Program Files on 32-bit systems and a folder in C:\Program
Files (x86) on 64-bit systems. Using relative file paths allows the map document and file geodatabases to
be stored in any folder, as long as the relative location of the two entities is maintained as it is on the GIS
administrator workstation.
For example, assume the GIS administrator configures the map properties to use relative file paths and
saves a map document in the same folder that contains the source File Geodatabase folder (*.gdb folder)
containing the data for all of the map layers. The map document file and File Geodatabase folder can then be
copied to any other folder or personal computer and, as long as they are both copied to the same folder, the
map can successfully read from the file geodatabase data source. For example, using relative file paths do
not require that items be stored in the same folder.
For more information about relative file paths, visit the
following Microsoft web page: http://msdn.microsoft.com/en-us/library/windows/desktop/
aa365247(v=vs.85).aspx#fully_qualified_vs._relative_paths
If the inventory of the GIS administrator and the Mobile Client personal computers have similar drive
configurations, and the map documents can access sources that are deployed to multiple folder locations
(such as File Geodatabases for feature classes and Raster files for images), it may be more straightforward
to use absolute file paths.
8.1.1
Enabling Relative Paths
Procedure:
1. On the ArcMap main menu, click File → Map Document Properties.
2. At the bottom of the dialog box, select the check box next to Store relative pathnames to data
sources.
3. Click OK.
132
MN007396A01-D
Figure 92: ArcMap – Map Document Properties
NOTE: These steps only affect the map document currently being edited in ArcMap. For all new
maps to be stored with relative paths, specify relative paths as the default. Click Customize
→ ArcMap Options to open the ArcMap Options dialog box, then click the General tab. Check
the option to Make relative paths the default for new map documents.
8.1.2
Relative File Path Data Sourcing Examples
Example 1:
ArcMap creates a map whose layers use a file geodatabase with the path C:\MapData\CAD\CAD.gdb as
their data source. The Map Properties specify that the relative file paths should be used, and the map
document is saved. If the .mxd file is saved in the Mapdata folder, the file path of the file geodatabase
relative to the folder, in which the .mxd file is saved, is .\CAD\CAD.gdb. The dot at the beginning of the
relative file path refers to the working folder, or the folder in which the .mxd file is opened. This file path
signifies that in the folder containing the .mxd file should include MobileA folder with that folder is the
MobileA.gdb folder inside.
133
MN007396A01-D
Figure 93: ArcCatalog – Relative File Path Example
When the map file and file geodatabase is deployed, it does not matter which folder the .mxd file is copied to
as long as that folder also contains CAD folder. The CAD.gdb folder is copied into the CAD folder. Therefore,
if the .mxd file is copied to C:\Motorola\PremierOne\MobileClient\Mapdata, there must also be a
C:\Motorola\PremierOne\MobileClient\Mapdata\MobileA folder, with the MobileA.gdb folder
inside.
Example 2:
Using ArcMap, instead of saving the map into the MapData folder, the map is saved into a folder called
C:\Users\Administrator\Documents. The relative file path to the gdb
is ..\..\..\MapData\CAD\CAD.gdb. The .. represents the parent folder of the current folder. In this
example, the first set of .. translates to the C:\Users\Administator folder. The second set of .. refers
to the C:\Users folder. The third set of .. refers to the C:\ folder. From there, the rest of the relative file
paths are applied resulting in C:\MapData\CAD\CAD.gdb. If the .mxd file is deployed to
C:\Motorola\PremierOne\MobileClient\Mapdata, the CAD.gdb file must be copied into the C:\
\Motorola\MapData\CAD folder (three folders up from the .mxd file and then down to MapData\CAD\
from there). If you copy the .mxd file into a folder that was less than 3 levels deep, such as MapData,
the..\..\..\MapData\CAD\CAD.gdb relative path is invalid.
Example 3:
ArcMap stores the file geodatabase as C:\MapData\CAD\CAD.gdb and saves the .mxd file on a disk drive
other than the C:\ drive. All of the file paths are stored as absolute instead of a relative path because it
cannot span different disk drives. If the .mxd file is saved to Z:\MapData, it does not matter which folder
the .mxd file is deployed to; the CAD.gdb folder must be copied to C:\MapData\CAD, as it exists on the
ArcGIS workstation on which the map file is saved.
134
MN007396A01-D
8.2
Raster Data Overview
Raster data may be brought into the .mxd document. Motorola recommends that raster data be stored in a
different database than the core PremierOne map data. This is because raster data changes much less
frequently due to the cost of acquiring new images. Since raster files need to be deployed less frequently
than other data, storing them separately reduces database build size and deployment time. It is
recommended that raster data be stored locally as raster files or in a file geodatabase raster catalog. If the
map document references a raster file that was not copied to the client computer, the map comes up blank.
8.3
Efficient Maps Overview
The most important guideline to consider when authoring maps is to design a map that is highly functional for
the target user above all else. Include only the map layers that are integral for the target user. Map drawing
performance and clarity of information should be prioritized over aesthetic and access to unnecessary
information. For example, there may be no benefit to including a Fire Hydrants layer in a map used by
highway patrol users.
8.3.1
Setting Scale Levels at Which Layers Should be Drawn
With the exception of basemap layers, like city/beat boundaries and large bodies of water, most map layers
should not draw at all scale levels.
Procedure:
1. Right-click the layer in the ArcMap Table of Contents and select Properties.
The Layer Properties dialog box appears.
135
MN007396A01-D
Figure 94: ArcMap – Layer Properties
2. Click the General tab.

3. Select Don’t show layer when zoomed.
For layers that should only be displayed when zoomed in close, set a minimum scale. For layers
that should only be displayed when zoomed out, set a maximum scale. Both values can be set for
layers that should only be displayed when zoomed to a scale somewhere in the middle, such as
Major Roads which may not be appropriate to display when zoomed to the map full extent, but whose
features are represented by another layer (such as Streets) when zoomed in close.
4. Click OK.
8.3.2
Specifying Definition Queries
Definition Queries allow the GIS Administrator to display a subset of information within a feature class as a
map layer. As an example, assume there is a Fire Hydrants feature class and the feature class contains
an attribute that specifies whether the hydrant is in service. Using a Definition Query, the map user can see
hydrants that are in service.
Procedure:
1. Right-click the layer in the ArcMap Table of Contents, and select Properties.
136
MN007396A01-D
Figure 95: ArcMap – Layer Properties (Definition Query Tab)
2. Click the Definition Query tab.

3. Type the condition when a feature should be displayed.
The Query Builder is useful in helping define the condition, because clicking the builder provides a
list of available fields in the feature class and the domain values appropriate for any given field.
4. Click OK.
NOTE: When you want to display a subset of features, using a Definition Query properly is much
more efficient that not using a Definition Query and using a “blank symbol” for unique feature
values instead.
8.3.3
Creating Attribute Indexes
When using Definition Queries, defining an attribute index on the field used in the Definition Query condition
can be important. In the previous above, you could create an attribute index on the InService field.
Procedure:
1. Display the Catalog dialog box in either ArcMap or ArcCatalog.
2. Navigate to the System Toolboxes → Data Management Tools toolbox.
3. Double-click the Add Attribute Index tool.
The Add Attribute Index dialog box appears.
137
MN007396A01-D
Figure 96: ArcToolbox – Add Attribute Index
4. Type the values in the required fields.

Fields with a browse button next to them can be populated be clicking browse and navigating to
the folder/file location, or by using the mouse to drag-and-drop an item from the Catalog Tree to the
appropriate field.
● Input Table – Create a new Index in this fully-qualified table/feature class. After the table is
specified, a list of available fields is displayed in the Fields to index list.
● Fields to Index – Field to be indexed.
● Index Name – Name for the index. A suggested name would be IX_<fieldname> (for example,
IX_InService).
● Unique – Not applicable to File Geodatabases. Leave this option unchecked.
● Ascending – Not applicable to File Geodatabases. Leave this option unchecked.
5. Click OK.
8.3.4
Feature Classes Reuse Example
Assume the Streets feature class contains all navigable street features (residential streets, major roads,
highways, and so on) and there is an attribute to describe the road type (class). That same Streets feature
class can be used as a source for several map layers.
For example, assume a user wants to only see the highways when zoomed out past a map scale of 1:24,000;
highways and major roads when zoomed between map scales of 1:2,000 and 1:24,000; and all streets when
zoomed in closer than 1:2,000. Add a layer to the map using the Streets feature class as the data source
and name the layer Highways. Define a Query Definition such that only the Streets features with a road type
matching the domain value for highways are displayed (see Specifying Definition Queries on page 136). Set
138
MN007396A01-D
the Maximum Scale to 1:2,000. This scale causes the Highways layer to display only when the map is
zoomed out past the 1:2,000 map scale (another layer is added later to handle map scales zoomed in beyond
1:2,000). Add another new layer to the map using the Streets feature class as the data source and name the
layer Major Roads.
Define a Query Definition such that only the Streets features with a road type the domain value for major
roads are displayed (see Specifying Definition Queries on page 136 topic). Set the Minimum Scale to
1:24,000 and the Maximum Scale to 1:2,000. Add a third new layer to the map using the Streets feature
class as the data source and name the layer Streets. Since all street features should be displayed when
zoomed in closer than the 1:2000 map scale, do not configure a Query Definition. Set the Minimum Scale to
1:2,000.
8.3.5
Simple Symbols Usage
The following excerpt is from the Improving Symbol Drawing Performance topic on ESRI ArcGIS
Resources website (http://desktop.arcgis.com/en/arcmap/latest/map/styles-and-symbols/improving-symbol-
drawing-performance.htm):
Optimize the speed at which symbols draw in the maps with these options:
● Consider simplifying symbols. Complex symbols or multilayered symbols draw slower than simply
constructed ones. Symbols that contain PNG (*.png), JPEG (*.jpg,*.jpeg), or Windows bitmap
(*.bmp) picture files and halos usually draw slower.
● Consider using symbols from the ESRI_Optimized style. It contains both line and fill symbols that are
designed to perform better while still maintaining a close visual appearance to their counterparts in the
ESRI style. The line and fill symbols in the ESRI_Optimized style draw almost 60 percent faster than
those in the ESRI style.
● Beginning with ArcGIS 9.2, fill symbols with outlines in the ESRI style and a number of other styles use
simple line symbols instead of cartographic line symbols for their outlines. This improvement yields a
drawing performance improvement when working with polygon data of up to 65 percent in many cases,
with an average improvement of almost 25 percent. Map documents and layer files constructed with
symbols from these styles prior to ArcGIS 9.2 still uses the old symbols. You may want to update the
symbols in these maps if drawing performance is an issue.
● The drawing performance of marker symbols, whether used to symbolize points or as a component
of one of the other types of symbols, can be improved greatly by using simple marker symbols and
single-layer character marker symbols; these are the best choices for symbolizing large point-feature
datasets.
● Masks can greatly increase draw times. A good alternative to adding a mask to a character or simple
marker is to create an .emf file that represents the symbol and uses a picture marker symbol that
displays the contents of the .emf file. In addition, .bmp, .png, .gif, and .jpg/.jpeg-based picture
marker symbols can be replaced with .emf markers to improve performance with those symbols.
● The more complexity in line symbols, the more potential for compromised drawing and export
performance. Of course, this needs to be balanced with the need for the degree of detail necessary
for proper cartographic depiction and communication. Simple line symbols are the fastest to draw but
offer limited display options. Cartographic line symbols may draw slowly if they are constructed with a lot
of complexity. Multiple layers, pattern templates, offsets, and excessive line widths increase draw time, for
example.
● In addition, combining symbol types into a multilayer symbol can slow down performance. This is
because the rendering of the dataset must be cycled through once for each layer type. For example,
if you combine a cartographic and hash line symbol, as is done in a basic railroad-style line symbol, the
data is drawn once for the cartographic symbol and again for the hash symbol.
139
MN007396A01-D
● Picture line symbols can dramatically increase draw and export time and generally do not produce
aesthetically pleasing results. It is recommended that you use one of the other line symbol types instead.
● To maximize drawing speed, use simple line symbols for polygon outlines wherever possible. Only use
cartographic line symbols for fill outlines if you need the enhanced properties they provide. For picture fill
symbols, .emf pictures draw faster than .png, .jpg/.jpeg, and .bmp pictures.
8.3.6
Features Labels
Maps convey information about geographic features, yet displaying only features on a map—even with
symbols that convey their meaning—is not always enough for the map viewer to orient themselves. Adding
text to the map improves the visualization of geographic information.
8.3.6.1
Dynamic Labels vs. Annotation
ArcGIS supports two main ways to label features: Dynamic Labels and Annotation. Annotation is an
extremely powerful and fast method of labeling. Annotation can be placed at specific locations on the map.
When there are a lot of features that can be annotated, the GIS Administrator has total control over how to
prioritize the labels of specific features. However, maintaining annotation takes a lot of effort and additional
disk space. To read more about Annotation, refer to this topic on the ESRI ArcGIS Resources website:
http://desktop.arcgis.com/en/arcmap/latest/map/working-with-text/essential-annotation-concepts.htm
Because of the effort involved in maintaining annotation, most GIS administrators use Dynamic Labeling
in their maps – even though it negatively impacts the performance of map drawing. The ArcGIS Dynamic
Labeling feature uses a complex “conflict detection” method to minimize labels being drawn on top of
each other, and this feature is resource-intensive. Dynamic Labeling should be used sparingly and/or with
well-configured labeling options.
8.3.6.2
Enabling Dynamic Labels for Map Layers
Dynamic labels in map layers can be turned on in the ArcMap Table of Contents.
Procedure:
1. Right-click the layer in the ArcMap Table of Contents, and then select Properties.
140
MN007396A01-D
Figure 97: ArcMap – Layer Properties (Labels Tab)
2. Select the Labels tab.

3. Check Label features in this layer.
4. Click OK.
8.3.6.3
Setting Placement Properties
By default, a label is drawn for each feature type. This may not seem apparent at first glance, because
ArcMap does not draw dynamic labels on top of other dynamic labels. However, it should be immediately
apparent that a label for a street does not need to be displayed for each street block. One label for a
particular street in the map view is often enough. A GIS Administrator may also want to prioritize the dynamic
labels of one layer over those of another layer.
Procedure:
1. On the Labels tab of the Layer Properties dialog box, click Placement Properties.
The Placement Properties dialog box appears.
141
MN007396A01-D
Figure 98: ArcMap – Placement Properties
2. Select Duplicate Labels → Remove duplicate labels.

This is the recommended setting.
3. To prioritize the labeling of layers, select the Conflict Detection tab.
142
MN007396A01-D
Figure 99: ArcMap – Label Placement Properties (Conflict Detection)
A description of each option is as follows:

● The Label Weight option determines whether the labels in this layer can be overlapped by labels
in other layers. The higher the weight, the less likely the labels in this layer are to be overlapped
by labels in other layers with a lower label weight.
● The Feature Weight option determines whether the features in this layer can be overlapped
by labels in other layers. Labels are only placed over features with a lower weight. For fastest
performance, it is recommended that Feature Weight be set to None.
● The Buffer value prevents adjacent labels from being drawn too closely to each other by defining
a buffer around the labels within which no other labels is displayed.
● The Place overlapping labels checkbox forces all labels for the layer to display, regardless of
whether they overlap each other. This is generally not recommended for map readability.
4. Select your options and click OK.
143
MN007396A01-D
8.3.6.4
Label Scale Levels
By default, dynamic labels display at the same scale level as the layer itself. By clicking Scale Range, a
scale level can be set which applies to the labels themselves.
8.3.6.5
Label Classes
Using label classes draws specific labels at certain scale levels and uses different font styles/sizes for
different features based on feature class attribute values.
This is an example of a city layer for Cook County Illinois with the Remove duplicate labels and Place
overlapping labels options enabled:
Figure 100: ArcMap – Place Overlapping Labels
This is what the map looks like with the Place overlapping labels option disabled:
144
MN007396A01-D
Figure 101: ArcMap – Remove Duplicate Labels (No Overlapping)
To increase legibility, the map should only display labels for the cities of Chicago, Palos Township, and
Schaumburg.
8.3.6.5.1
Defining Label Classes
Procedure:
1. In the Layer Properties dialog box, select the Labels tab then select Method → Define classes of
features and label each class differently.
A class called Default is automatically created.
2. Clear the Label features in this class option.
3. Click Add and name the new label class Big Cities.
4. Specify the name of the field that contains the values to display as labels and the font characteristics.
145
MN007396A01-D
Figure 102: ArcMap – Label Class
5. Click the SQL Query button.

The SQL Query dialog box appears.
6. Enter a query that sets the condition specifying which features should be labeled for this label class.
Figure 103: ArcMap – Label Class SQL Query
7. Click OK.
146
MN007396A01-D
The new map appears with only the specified labels. More individual city names can be added to the
SQL Query as desired.
Figure 104: ArcMap – Label Class SQL Query
Label classes can also be configured to draw only at specific map scales.
8.3.6.5.2
Configuring Label Classes for Specific Map Scales
Procedure:
1. With the Big Cities class selected, click Scale Range and specify a minimum scale of 1:240,000.
2. Select the Default label class, and check the Label features in this class option.
3. Click Scale Range and specify a maximum scale of 1:240,000.
With this configuration, the Big Cities label class only displays when zoomed out past a map scale
of 1:240,000, and the Default label class only displays when zoomed in closer than a map scale of
1:240,000.
147
MN007396A01-D
Chapter 9: CAD Client Maps
Chapter 9
CAD Client Maps

This chapter describes the process for preparing and deploying CAD Client maps. The CAD Client supports
an A and B map which allows the inactive map, mapping service, and/or source data to be updated while the
active map, service, and/or data are in use.
9.1
CAD Client Map Data Sources
ArcMap documents (.mxd files) support a variety of data sources.
For PremierOne CAD Clients, who typically operate over local and hard-wired networks, GIS Administrators
have several options:
ArcGIS Mapping Service
A Mapping Service is a way to expose a map as a web service using ArcGIS Server.
Local File Geodatabases
Using local file geodatabases as a map data source offers the highest map drawing performance.
However, using these geodatabases comes at an added cost of maintenance as changes to map data
must be pushed out to more locations as compared to using SDE.
Local Files
Using local shapefiles is supported. Also, if the map contains any large raster files, Motorola strongly
recommends that they are stored locally on each client.
External Online Services
Using web services outside of the PremierOne client/server infrastructure is not recommended, as there
is no guarantee that they are highly available or that they will not negatively impact map drawing
performance.
A CAD Client map can use any combination of the data sources listed previously. For example, a CAD map
could consist of basemap layers implemented as a map service, layers with frequently changing data stored
in SDE, and an aerial image stored locally on each workstation.
9.2
ArcGIS Server Services
Each PremierOne GIS Virtual Machine acts as an autonomous ArcGIS server site. The F5 Traffic Manager
balances the request load across all available GIS Virtual Machines. Additionally, an instance of ArcGIS
Server will be installed on the Training System ArcGIS Server VM. This allows map data repositories and
148
MN007396A01-D
caches to be published on the ArcGIS administrator workstation so that the GIS Virtual Machine resources
are not used for the intensive process of building map cache.
9.2.1
Mapping Services
ArcGIS Server mapping services host map data in cached (tiled) or non-cached (dynamic) format. In a map
service, sets of raster (imagery) and vector (feature) data are consolidated into layers and made available as
a web service.
9.2.1.1
Advantages of Cached Map Services
Cached map services in ArcGIS are similar to the cached map capabilities used in web-mapping services
such as Google Maps and Microsoft Bing Maps. As you zoom in on these map services, they are drawn at
the appropriate resolution. Each of these digital maps is generated across the study area (for example, the
country or the whole world) for a range of map scales—essentially one map view for each map scale. Since
the map is cached ahead of time, mapping requests do not require any database server resources to process
and considerably less network bandwidth than maps using SDE data sources.
9.2.1.2
Disadvantages of Cached Map Services
Since cached map services are designed for use on the World Wide Web, they provide excellent
performance. However, this increased performance comes at a cost of disk storage requirements and the
time required to build the cache. Since ArcGIS Server is being deployed on the PremierOne Application
Servers, and these servers are not configured with as much storage as PremierOne Database Servers, the
storage requirements of the cache files may prohibit the use of cached services. It is possible to use cache
for specific areas and/or scale levels of the map, by that reducing the storage requirements of cache files.
Motorola does not recommend using areas and/or scale levels that are not cached. These areas and/or scale
levels are served dynamically, which is a much slower process.
Another disadvantage is that individual layers published within a cached map service cannot be turned on or
off by the user. The map service displays in the map as a group of layers and the user can only turn the entire
group on or off. A GIS Administrator could group layers together (such as a group each for basemap, critical,
and non-critical layers) and publish multiple map services. The user map could then add each service as a
service layer and each group could be turned on or off independently of the other map service layers.
NOTE: Displaying the map in Night Mode is not supported for map service layers.
9.2.2
Provisioning CAD Map Auto Zoom Levels
To provide the best appearance of the map on the CAD Client, these scale levels should match the scale
levels that the CAD Mapping Client typically uses, namely, the scale for the map’s full extent.
Procedure:
1. Select Mapping → Agency → Agency Settings → Map Zoom Behavior.
2. Locate the default ScaleDrawdownValues defined in the CAD mapping client configuration file.
149
MN007396A01-D
These are located in the C:\Program Files

(x86)\Motorola\PremierOne\CADClient\mappingconfig\MappingConfig.xml file.
NOTE: Not all of the scale levels provisioned and configured need to be represented in the
cache. Motorola recommends that between 6 and 10 scale levels be cached depending on the
extent of the map geography.
9.2.3
Creating Cache Tiling Scheme Files
After the scale levels for caching is determined, Motorola recommends creating a tiling scheme. A tiling
scheme file can be reused any time a mapping service is published, saving the GIS administrator time and
effort and ensuring cache scale level settings are being defined consistently.
Procedure:
1. Use ArcToolbox to navigate to the System Toolboxes → Service Tools → Caching Toolbox and
double-click the Generate Map Server Cache Tiling Scheme tool.
Figure 105: ArcToolbox – Generate Map Server Cache Tiling Scheme
2. Specify the Map Document, Data Frame, and Tiling origin units (X and Y).
3. Type scale levels in the Scales text box (for example, enter 24000 to indicate a scale of 1:24,000)
4. Click Plus and continue until all of the desired scales have been entered.
5. Click OK.
150
MN007396A01-D
The cache tiling scheme is created in the Output Tiling Scheme folder.
6. On the Caching tab of the Service Editor dialog box, select the A tiling scheme file option in the
Tiling Scheme list.
The cache scale levels are now defined.
9.2.4
Publishing the Dynamic Mapping Service
The Dynamic Mapping Service must be published on all PremierOne ArcGIS Server Virtual Machines for the
specific PremierOne environment. For example, Production, Training, or Staging.
Procedure:
1. After the map is created, select File → Share as Service from the ArcMap main menu.
Figure 106: ArcMap – Share as Service
151
MN007396A01-D
Figure 107: ArcMap – Share as Service Dialog Box
152
MN007396A01-D
allows the configuration of the following service options:
● Parameters – Click the Parameters tab and then click Advanced. Set the
setSchemaLockingEnabled option to false (case-sensitive). A false setting prevents schema
lock files from being created in the cache folder and subsequently replicated to the other
Application Servers.
● Capabilities – An ArcGIS Service exposes a Mapping capability by default. The KML capability is
also added by default and can be unchecked.
● Processes Tab – Accept the defaults. If it is determined that the default settings cannot
adequately handle user requests, Motorola may change the defaults at any time.
● Item Description Tab - The GIS Administrator may optionally provide any metadata information
153
MN007396A01-D
5. After all of the service settings are specified, click Publish. The service has now been staged as a
service definition file in the specified folder location.
9.2.5
Creating Cached Mapping Services
Procedure:
1. Create a map using ArcMap which contains raster and/or vector data from a geodatabase source.
2. Share the map as a service to the GIS Administrator’s ArcGIS Server instance using ArcMap. This
includes defining the cache settings.
3. Build the cache for the service using ArcGIS Desktop.
4. Export the cache to a cache dataset.
5. Share the map as a service to all PremierOne GIS Virtual Machines for the particular PremierOne
Environment.
Import the cache dataset from the GIS Administrator’s workstation to the map service on all
PremierOne GIS Virtual Machines.
9.2.5.1
Publishing Mapping Services
Procedure:
1. After the map is created, from the ArcMap main menu, select File → Share as a Service.
Figure 109: ArcMap – Share as Service Dialog
154
MN007396A01-D
Figure 110: Share as Service Dialog Box
155
MN007396A01-D
4. Select Publish a Service and click Next.
The Publish a Service dialog appears.
156
MN007396A01-D
Figure 112: Publish a Service Dialog
allows the configuration of several service options. Before setting these options, it is a good idea to
have ArcGIS analyze the map document to ensure that it is ready to be published.
9.2.5.2
Analyzing Map Documents
Procedure:
1. Click Analyze at the top of the dialog box to perform this task.
2. Review the results of the analysis and fix any errors in the Prepare dialog box so the map can be
published as a service.
Optionally, review the warning and informational messages and fix any of those issues that may affect
map drawing performance and appearance.
An exhaustive list of service settings can be found on the ESRI ArcGIS Resources website at http://
desktop.arcgis.com/en/arcmap/latest/map/publish-map-services/setting-map-service-properties.htm.
Motorola recommends the following service settings.
● Parameters – Click the Parameters tab. Motorola recommends that the Anti-Aliasing option
be set to Fast. Click Advanced. Set the setSchemaLockingEnabled option to false (case-
sensitive).
157
MN007396A01-D
● Capabilities – An ArcGIS Service exposes a Mapping Service by default. The KML capability is
also added by default and can be unchecked.
● Processes Tab – Accept the defaults. Motorola may change the defaults at any time if it is
determined that the default settings cannot adequately handle user requests.
● Caching Tab – ArcGIS map services can be precomputed and cached as a series of small tiles
covering the map extent and for multiple map scales. Retrieving these precomputed map tiles,
called cached map services, can be much faster and more scalable than dynamically computing
the map display each time a map is requested from the service. For more information, see
Configuring Cache Settings on page 158.
● Item Description Tab – The GIS administrator may optionally provide any metadata information
● Staging the Service – After all of the service settings are specified, click Stage. The Service
Definition file is created.
9.2.5.3
Configuring Cache Settings
Procedure:
1. Select the Caching item on the left-hand side of the Service Editor.
2. Select the Using tiles from a cache option.
3. Select the Build cache manually after the service is published option at the bottom of the dialog
box.
The map scale levels at which cached tiles shall be created can be entered manually or by loading
a previously created tiling scheme file (see the Creating a Cache Tiling Scheme topic which appears
earlier in this chapter.
4. If using a tiling scheme file, select the A Tiling Scheme File option from the Tiling Scheme drop-
down list.
A Load Tiling Scheme dialog box will display prompting for the location of the tiling scheme file.
If a tiling scheme file is not available, the tiling scale levels must be specified manually. Refer to
Manually Specifying Scale Levels on page 159 for more information.
5. Click the Advanced Settings item on the left side of the Service Editor.
6. Ensure that the Tile Format is PNG. If you will be using multiple mapping services as layers in a client
map, and one service layer will overlap another, choose PNG32 for the overlapping service. This will
provide transparency so that the overlapped service layer may still be seen.
7. Check the Create Tiles on Demand option. If the cache is only built for common areas of interest, this
will allow tiles to be create on demand for areas outside of the cached areas as they are requested by
a client.
8. Click Advanced.
9. Set the Storage Format option to Compact. This will make copying/exporting the cache to the
PremierOne GIS Virtual Machines more efficient.
158
MN007396A01-D
Instead of specifying each setting manually, a tiling scheme file can be used to determine the cache
scale levels.
9.2.5.3.1
Manually Specifying Scale Levels
Instead of using a tiling scheme file, the cache scale levels can be specified manually.
Procedure:
1. Select the Suggest option from the Tiling Scheme list.
2. When prompted, type the number of scale levels to define and click OK.
3. Click the Caching tab, then select the Advanced Settings tab.
Figure 113: ArcMap – Service Editor Caching Advanced Settings Tab
Suggested scale levels are shown. If a scale level does not meet the needs of the map, it can be
deleted and additional scale levels can be added. The Disk Space calculation is an estimate and is
typically a “worst case scenario”.
9.2.5.3.2
Tiles on Demand Creation
In Caching → Advanced Settings, there is a check box called Create tiles on demand. When checked,
tiles for a un-cached extent are created dynamically when requested by a client. Subsequent client requests
for this extent are able to utilize these tiles. As mentioned, dynamic map requests are much slower than
cached map requests and should be avoided whenever possible. But, if cache is not created for all extents
159
MN007396A01-D
and/or scale levels, creating tiles on demand minimizes this loss of performance after the tiles are created.
The on-demand creation of tiles results in reduced performance for the initial request.
9.2.6
Publishing Services
After the service has been configured to the correct specifications, it must be published.
Procedure:
On the Service Editor dialog, click Publish.
9.2.7
Building Caches
After the mapping service is published, the cache files can be built on the Training server's ArcGIS Server
instance. Before this can occur, there must be a GIS Server connection configured to connect to the ArcGIS
Server on the Training system's ArcGIS Server VM as an Administrator or Publisher.Building the cache is a
lengthy, CPU-intensive process. Motorola recommends executing this tool at the end of the work day when
the GIS administrator is no longer actively using the workstation.
Procedure:
1. Right-click the appropriate ArcGIS Server connection.
If the Connect option is available, select it to connect to the server. If it is grayed out, the connection
is already established.
2. Navigate the tree structure below the connection to locate the mapping service under the PremierOne
folder.
3. Right-click the service, and then select Manage Cache → Manage Tiles.
The Manage Tiles dialog box appears.
Figure 114: ArcGIS Desktop – Manage Tiles
160
MN007396A01-D
All of the scale levels are checked by default. The cache can be built for specific scale levels in
batches by clearing the scale levels to ignore and running the tool multiple times for sets of scale
levels.
The Area of Interest is used to build cache a specific polygon are instead of the full extent of the
map. The area of interest may be the extents of an existing feature class in the map or a rectangular
envelope whose coordinates are entered manually. Motorola recommends maintaining and adding a
“cache extent” feature class to cached maps. The cache extent should cover the areas of the map
that are most frequently viewed. Using an area of interest decreases the time required to build the
cache. If he Build tiles on demand option was unchecked, any areas outside the area of interest are
rendered dynamically as a result of a client request. If the Build tile on demand option was selected
tiles for map extents outside the area of interest is built upon an initial client request for that extent.
4. Click OK.
This is a lengthy, CPU-intensive process. Motorola recommends that this tool be executed at the end
of the work day when the GIS administrator no longer actively needs to use the workstation.
The tiles are stored in a folder under the cache folder having the name
PremierOne_<map_service_name>.
Figure 115: Windows Explorer – Cache Folder
9.2.8
Exporting Caches
Exporting a cache is performed by using the Export Map Server Cache tool.
Procedure:
1. Open the ArcGIS Desktop Toolbox from ArcMap or ArcCatalog.
2. Expand the System Toolboxes item.
3. Expand the Server Tools item.
4. Expand the Caching item.
5. Double-click the Export Map Server Cache tool.
The Export Map Server Cache dialog displays.
161
MN007396A01-D
Figure 116: Export Map Server Cache dialog
6. Populate the options in the dialog as follows:

● Input Service – Select the service from a Publisher or Admin GIS Server connection for the
PremierOne GIS Virtual Machine that the cache will be exported from.
● Target Cache Path – Specify the drive or folder location that the cache should be exported to. It
is a good practice to give the folder the same name as the service so that you can identify which
service the cache belongs to.
● Export cache – Select CACHE_DATASET.
● Copy data from server – The Export Cache tool uses a built-in ArcGIS Server user account
to perform the export request. This user may not have access to the target cache path drive or
folder. If you are certain that the user has access to the output folder, leave this option unchecked.
Otherwise, check this option. Enabling this option will make the export process take longer.
● Storage Format Type – Select COMPACT.
● Scales – Select all available map cache scales.
● Overwrite Tiles – Check this option.
● Number of caching service instances (optional) – This specifies how many instances of the cache
tools services will be used to export the cache. The number of instances displayed by default is
the recommended number in order to ensure the process is completed as efficiently as possible.
However, if you need to use the workstation to complete other tasks while the export is taking
place, you may decrease the recommended value.
162
MN007396A01-D
● Area of Interest (Polygon) (optional) – Accept the default value to allow all of the available cache
to be exported.
7. Click OK.
The cache is exported from the service to a cache dataset on the local drive.
9.2.9
Mapping Service Publication on PremierOne GIS Virtual
Machines
After the service has been published on the GIS Administrator’s ArcGIS Server instance and the cache has
been built, the service must be published on the PremierOne GIS Virtual Machines and the cache copied
from the Training system's ArcGIS Server VM to the PremierOne GIS Virtual Machines.
Follow the same steps as documented in Publishing Mapping Services on page 154 and select the
same service name, settings, and options that were chosen when the service was published to the GIS
Administrator’s ArcGIS Server instance. The only change to the steps will be the ArcGIS Server connection
that the service will be published to. This publishing process should be performed for all PremierOne GIS
Virtual Machines on the specific PremierOne environment.
9.2.9.1
Importing Caches
Importing cache is performed by using the Import Map Server Cache tool.
NOTE:
Importing the cache should only be performed on the inactive map (A or B, as currently specified on the
GIS Data page of the PremierOne Provisioning Console). The map service will need to be restarted in
order for the cache to be identified, which is not desirable for a mapping service that is currently “active”
in PremierOne.
Importing cache is performed by using the Import Map Server Cache tool. The cache should be
imported to all PremierOne GIS Virtual Machines for the particular environment being updated.
Procedure:
1. Open the ArcGIS Desktop Toolbox from ArcMap or ArcCatalog.
2. Expand the System Toolboxes item.
3. Expand the Server Tools item.
4. Expand the Caching item.
5. Double-click the Import Map Server Cache tool.
The Import Map Server Cache dialog displays.
163
MN007396A01-D
Figure 117: Import Map Server Cache Dialog
6. Populate the options in the dialog as follows:

● Input Service – Select the service from a Publisher or Admin GIS Server connection for the
PremierOne GIS Virtual Machine that the cache will be imported to.
● Source cache type – Select CACHE_DATASET.
● Source Cache Dataset – Specify the drive or folder location that the cache was exported to in
Importing the Cache. Once the folder is selected, select a cache dataset.
● Upload data from server – Since the cache is copied across machines, this option must be
checked. The Import Cache tool uses a built-in ArcGIS Server user account on the target virtual
machine to perform the import request. This user may not have access to the target cache path
drive or folder. If you are certain that the user has access to the output folder, leave this option
unchecked. Otherwise, check this option. Enabling this option will make the export process take
longer.
● Storage Format Type – Select COMPACT.
● Scales – Select all available map cache scales.
● Overwrite Tiles – Check this option.
● Number of caching service instances (optional) – This specifies how many instances of the
cache tools services will be used to import the cache. The number of instances displayed by
default is the recommended number in order to ensure the process is completed as efficiently as
possible. However, if you need to use the workstation to complete other tasks while the import is
taking place, you may decrease the recommended value.
164
MN007396A01-D
● Area of Interest (Polygon) (optional) – Accept the default value to allow all of the available cache
to be imported.
7. Click OK.
The cache is imported to the service.
9.2.10
Overwriting Existing Mapping Services
When the data and/or map properties have changed substantially enough that an existing inactive (A or B)
map service needs to be updated, the existing service can be overwritten.
Procedure:
1. Overwrite the service on the ArcGIS Administrator’s ArcGIS Server instance.
2. Build the cache for the service.
See Building Caches on page 160 for more information.
3. Export the cache from the service.
See Importing the Cache for more information.
4. Stop the existing service on all PremierOne GIS Virtual Machines.
5. Overwrite the service on all PremierOne GIS Virtual Machines.
6. Import the cache to the particular service on all PremierOne GIS Virtual Machines.
See Importing the Cache for more information.
7. Restart the particular service on all PremierOne GIS Virtual Machines.
8. With the map document open in ArcMap, select File and then click Share as Service from the
ArcMap main menu.
Figure 118: Share As Service Menu
The Share as Service dialog appears.
165
MN007396A01-D
Figure 119: Share as Service Dialog – Overwrite An Existing Service
9. Select Overwrite an existing service and click Next.

166
MN007396A01-D
The service is overwritten.
9.2.11
Restarting Services on a PremierOne GIS Virtual
Machine
Procedure:
1. From the Catalog window in ArcMap or ArcCatalog, open the GIS Server connections.
2. Double-click a Publisher or Admin connection to the ArcGIS Server instance.
3. Navigate through the tree to find the service to restart.
4. Right-click on the service name and select Restart.
167
MN007396A01-D
Figure 121: Restarting A Service From The Catalog Window
9.2.12
Adding Mapping Service Layers
Prerequisites:
After the service is published, the service can be used in a CAD Map. If a GIS Server User connection was
not yet created, this must be done first.
After you have a GIS connection, you can add the mapping service layer.
Procedure:
1. From the ArcMap main menu, select File → Add Data → Add Data.
2. Use the Look In: list to navigate to the GIS Server User connection and double-click the connection.
3. Double-click the PremierOne folder.
4. Select the mapping service, and then click Add.
The mapping service layer is added to the map.
168
MN007396A01-D
Figure 122: ArcMap – Add Service Layer
The map can now be supplemented with any additional data from other sources if needed.
NOTE: After the mapping service is published, you cannot modify most layer properties on
individual layers contained in the mapping service, or hide/view individual layers contained in the
mapping service.
169
MN007396A01-D
Chapter 10: Mobile Client Maps and Data Overview
Chapter 10
Mobile Client Maps and Data Overview

This chapter describes the process for preparing and deploying Mobile Client maps and data. Like CAD
maps, the Mobile Client supports an A and B map, allowing the inactive map and data to be updated while the
active map and data are in use.
10.1
Mobile Clients Map Data Sources
Mobile Map Packages (.mmpk) support a variety of ESRI supported data sources. For more information,
please see ESRI .mmpk reference for more information. This file is used to support PremierOne Mobile
Clients, who typically operate over a wireless network and may be disconnected from the network at any
given time. Multiple .mmpk files can be supported within the PremierOne Mobile Clients. It is recommended
that the .mmpk file be created to include visual map(s), a routing network and a locator.
10.2
Stage Map Data
In order to publish the ArcGIS Network Analysis Service for CAD, a file Geodatabase containing at least the
ROUTING feature dataset should exists. The next step is to use ArcGIS Desktop to copy/paste the feature
classes that is used as the data sources for map layers into the same File Geodatabase.
10.3
Author Mobile Client Maps
ArcPro is used to create maps for the PremierOne Mobile Client. Please refer to the ESRI Maps Resources
for more information.
10.4
Exporting Enterprise GIS Data
In addition to the File Geodatabase that contains the Network Dataset and feature classes utilized as
map layer data sources, GIS data stored in the enterprise SQL databases must also be deployed to the
PremierOne Mobile Client. The Create Mobile Client Data Package Data Import tool is used to export the
required GIS data from the enterprise SQL databases. The files created by this tool are deployed along with
the map files and File Geodatabases to the PremierOne Mobile Client.
Procedure:
click the Create Mobile Client Data Package tool.
170
MN007396A01-D
Figure 123: ArcCatalog – Create Mobile Client Deployment Package
2. Type the values in the required fields. Fields with a browse button next to them can be populated be
clicking browse and navigating to the folder/file location, or by using the mouse to drag-and-drop an
item from the Catalog Tree to the appropriate field.
Descriptions of each field are as follows:
● Source SQL Instance – The name of the PremierOne SQL Server Instance on the SQL Always
On Listener Database Server (e.g., P1-SQL-Listen\PremierOne).
● Mobile Database to Update – Specify which GIS Database on the Mobile Client to update (for
example,. Database A or Database B). In most cases, the database to update corresponds to
the database the data is being exported from (GISSQL_DATASET_A or GISSQL_DATASET_B,
respectively).
● Source SQL GIS Database Name – the name of the PremierOne GIS database containing the
data to export (such as GISSQL_DATASET_A).
● Source SQL GIS Reader User Name – the login name for a SQL user that has db_datareader
privileges for the source SQL GIS database. If a SQL login and password is not specified,
Windows authentication is used.
● Source SQL GIS Password – the password for the SQL GIS Reader User.
● Source SQL PremiseHazard Database Name – the name of the PremierOne Premise Hazard
database containing the data to export (such as , GISSQL_PremiseHazards).
● Source SQL PremiseHazard Reader User Name – the login name for a SQL user that has
db_datareader privileges for the source SQL Premise Hazard database. If a SQL login and
password is not specified, Windows authentication is used.
● Source SQL PremiseHazard Password – the password for the SQL PremiseHazard Reader
User.
3. Click OK.
171
MN007396A01-D
Figure 124: ArcCatalog – Create Mobile Client Data Package

After running the tool, a set of files was created in the output folder:
● *.bin – One binary file exists for each table exported from the SQL enterprise database.
● LoadGisData.sql – This file contains SQL statements to load the *.bin files to SQL Express on
the Mobile client.
● ExecuteLoadScript.bat – The All-In-One tool executes this file to import the data on the Mobile
client. It calls the sqlcmd utility using the LoadGisData.sql script as an input.
172
MN007396A01-D
Chapter 11: Address Verification Basics
Chapter 11
Address Verification Basics

The PremierOne geodatabase, built according to best practices and specifications, forms the solid foundation
which provides a superior level of location-based features and functions, including increased situational
awareness, more accurate responses, and stronger location-based data analysis.
The accuracy of the geodatabase in terms of matching the Master Street Address Guide (MSAG) is a
cornerstone to enabling the best location-based features and functions in PremierOne, and has a direct
impact on the usability of the system.
For example, if the MSAG data does not match what is built into the geodatabase, operators may struggle to
validate addresses during the creation of incidents, which may delay incident entry, creating a negative user
experience and, more importantly, a negative impact on the safety of first responders and the citizens they
protect.
In addition to GIS administrators working to ensure the accurate matching of MSAG data with the
PremierOne geodatabase, it is imperative that end users fully understand how the data is entered into the
geodatabase, and what the system behavior is in terms of how the data is used to create calls, manage
unit locations, and display certain location-based data for increased situational awareness, such as Previous
Incidents and Premise/Hazard locations.
Therefore, operators should be thoroughly trained on the following concepts and processes, which describe
how each type of address and its correlating fields behave during the address validation process.
11.1
Address Validation in PremierOne
When validating a street address (no Location Name is entered), PremierOne performs a hierarchical search:
Address Points first, followed by Street Centerlines. For example, if the user only enters 123 MAIN ST,
PremierOne first looks for an Address Point with a street address of 123 MAIN ST and blank apartment/
building values. If a matching Address Point record cannot be found, PremierOne then attempts to locate a
street centerline having a name that begins with MAIN ST regardless of its prefix direction, a Low House
value that is less than 123, and a High House value that is greater than 123.
If the user enters 123 MAIN ST in the Location field and 2A in the Apt/Unit field, PremierOne first looks
for an Address Point with a street address of 123 MAIN ST, an apartment value of 2A, and a blank building
value. If a matching Address Point cannot be found, PremierOne attempts to locate a street centerline match
as described previously and retains the 2A value in the Apt/Unit field even though there was no matching
Address Point for that apartment number. This hierarchy is the reason why it is critical for every address to
be represented in the street centerline data. Additionally, street centerline data is used to populate the Cross
Street field for Address Point and Common Place (with address) matches. Even if an address returns an
Address Point match, if the address is not also represented by a street centerline record, no cross street
information is provided.
Subdivision, City, and Zip Code do not need to be entered prior to validation. If the match candidate selected
by the user contains this information, it automatically populates the appropriate fields. If the user does enter
a value in any of these fields, the values entered must exactly match the values in the GIS. If it is important
for Subdivision, City, Postal City, and/or Zip Codes values to be associated with incident locations, the values
must be imported universally for Street Centerlines, Address Points, and Common Places. If an Address
Point at 123 MAIN ST has a Zip Code value of 80621, but the Street Centerline record containing 123 MAIN
ST does not have a Zip Code value, the user sees two separate choices for 123 MAIN ST in the pick list,
one for the Address Point and one for the Street Centerline, and the system is unable to determine the cross
streets for the Address Point since the Zip Code values do not match between the two location types.
173
MN007396A01-D
11.2
Default Behavior of Location Fields
The CAD and Mobile clients support several forms on which location information can be entered and/or
displayed. The following information describes these location-related fields and their default behaviors.
11.2.1
Location Field
The location field supports a street address, common place name, street intersection, alarm number, or
Latitude/Longitude coordinate. When entering a street address, entering the prefix direction (such as N, S,
E, or W) of the street name is optional. If a prefix direction is not entered, PremierOne ignores the prefix
direction value of matching streets/addresses. If the user does enter a prefix direction, PremierOne only
returns matches having that prefix direction. Additionally, PremierOne uses a “begins with” search for street
names and common place names by default.
For example, entering the street address 123 MAIN may return the following results:
● 123 MAIN AVE
● 123 N MAIN ST
● 123 MAINLAND RD
Entering the street intersection MAIN & BROAD may return the following results:
● W MAIN ST & BROADWAY AVE
● MAINLAND RD & BROAD ST
● MAIN ST & BROADWAY PL
Entering the common place name STAR may return the following results:
● STARBUCKS
● STARLAND BALLROOM
● STAR PLUMBING
Wildcards can be used with a street name or common place name. The wildcard character expected is
configured in the Provisioning Console under Mapping → Location Verification → Wildcard Character.
If a wildcard character is entered in a street name or common place name, the search no longer applies
an implied wildcard character at the end of the name (“begins with” search) Therefore, when using a
wildcard at the beginning or within a street name, the remainder of the street name including suffixes
must be entered in order to correctly validate.
For example, if the wildcard character is a percent sign (%) and 123 B%TREE RD is entered in the
Location field, the following results may be returned:
● 123 BLUEBERRY TREE RD
● 123 BLACKTREE RD
● 123 BIG ELM TREE RD
11.2.2
Subdivision and City Field
Entering subdivision and/or city values is optional. If values are not entered in this field, all match candidates
that match the other entered location values is returned regardless of their city/subdivision value. If values
are entered into one or both of these fields, the match candidates must have city/subdivision values matching
the respective values provided by the user. The Subdivision and City values may be used interchangeably.
174
MN007396A01-D
If the user is unsure whether the information given by a caller is a subdivision name or a city name, they can
enter it in either field and still get a match even if they enter the value in the field opposite to where it is stored
in the GIS.
11.2.3
Apartment and Building Field
Entering an apartment and/or building value is optional. However, the presence of an apartment/building
value may change the map coordinate of a location if a matching Address Point is found (and subsequently,
hits on Premise Hazards and Duplicate Incidents). A blank value in the Apartment/Building fields is treated
as a unique value – just like a non-blank value. If a user enters 123 MAIN ST without specifying an
apartment or building value, and an Address Point does not exist for 123 MAIN ST with a blank apartment
and building value, the location only geocodes to an Address Point at 123 MAIN ST that also does have an
apartment or building value. If such an Address Point does not exist in the data, the address is geocoded to a
street centerline.
Similarly, if the user enters 123 MAIN ST in the Location field and 47 in the Apartment field and an
Address Point does not exist in the data with that address and apartment number, the location does not
geocode to any other Address Point at 123 MAIN ST and instead geocodes to a street centerline.
11.2.4
Location Name Field
Entering a Location Name value is optional. However, if a value is entered, there must be a Common Place
record having that name in order for the location to be verified. Since the Location field allows a common
place name to be typed in it, there is no need to enter a value in the Location Name field unless the user
wants to verify a location using both a street address (in the Location field) and a common place name (in
the Location Name field).
11.2.5
Description
The Description field is meant to provide descriptive and non-verifiable information about the location, such
as behind the residence. PremierOne may also automatically populate the Description field in other
situations, such as when verifying a latitude/longitude coordinate or if the GIS data contains Description
values. Therefore, any information manually typed into this field can potentially be overwritten.
175
MN007396A01-D
11.2.6
Floor
Floor values are currently not supported by the GIS. Users can enter anything in this field for informational
purposes and it does not affect validation.
11.2.7
Zip Code
Entering a Zip Code value is optional. If a value is not entered in this field, all match candidates that match
the other entered location fields is returned regardless of their Zip Code value. If a value is entered into this
field, the match candidates must have a Zip Code value matching the value provided by the user.
11.3
Default Behavior Modification of Address
Verification
Provisioning/Configuration changes can be made to modify the default behaviors of Address Verification.
11.3.1
Disabling Automatic Address Verification
When a user tabs out of the City field, Address Verification is automatically triggered using any location
values that have were entered. Upon selecting a location from the address verification results pick list, or if
PremierOne returns only one match, the location is considered verified. Changing any location values after a
location is verified forces the location to be re-verified. If users make heavy use of the Subdivision, Location
Name, Apartment, Building, or Zip Code fields, it may not be suitable to trigger address verification when
tabbing out of the City field since these other fields are further down the dialog box.
Procedure:
1. Use the Provisioning Console and navigate to the Incident Management → Service Setting dialog
box.
2. Click the Service Defaults tab.
3. Check the Disable automatic address verification setting.
4. Enter all location information and click Verify on the CAD/Mobile dialog box.
11.3.2
Verification by Location and City Only
The VerifyByLocationAndCity setting in the PremierOne Configuration Tool has been deprecated. If a user
makes a selection for this setting in the configuration tool it will not be effective. This setting has been moved
176
MN007396A01-D
to Provisioning as of the 4.6.13 release and is now available at the Agency level. See the PremierOne CAD
and Mobile Provisioning Guide for more information.
11.3.3
Base Address Point Use When Apartment/Building
Match is not Found
Agencies typically have address points for most (if not all) buildings, but do not always have address points
for apartments or units within the building.
When a user enters a street address with an apartment number, PremierOne address verification behaves as
follows:
● Assume a call-taker enters an address of 123 MAIN ST and apartment number 2A. PremierOne first
looks for an address point with a street address of 123 MAIN ST, an Apt/Unit value of 2A, and no
Building value. If an address point for the entered address and apartment number exists, the system
uses its coordinates.
● If an address point for the street address exists, but not for the specific apartment number, the system
uses the base address point coordinates. A “base address point” is an address point with a street
address and blank Apartment and Building values.
NOTE: This step is only performed if the GeocodeByNonExactAddressPointEnabled setting is
true. This setting is found in the Addressing configuraton file. Configuration files are displayed/
modified in the Configuration utility of the PremierOne Administrator Console.
● If no base address point exists, the system uses the street centerline coordinates.
To provide a clear indication to the user of whether GIS uses an address point or street centerline to
geocode a location, a rectangular blue label appears, showing Premise Lvl for address points and
Centerline Lvl for locations geoverified to a street centerline.
In CAD, this label appears next to the Zip Code field. In Mobile, the blue label appears next to the Loc.
Name field.
11.3.4
Base Address Point Use as the Endpoint When Routing
Units to Incidents or Destinations
When generating a route, the Network routing engine attempts to snap an address map location to the
nearest street centerline. This could result in a route endpoint that is located on a street that does not provide
vehicle access to the address. If routing to a street centerline results in a route to an unreachable endpoint
you can add an address point for that address to be used as the endpoint for route calculation.
By default, this method causes route calculation to snap to the street segment closest to the address point
rather than the street centerline. If no base address point exists, the system uses the street centerline
coordinates.
In some instances, the default behavior of snapping the route endpoint to the street segment closest to an
address point is not desired because it might not have road access to the address point, such as the case
when a highway is the closest street segment to an address point. In such a case, it could be desired to
always use the street centerline as the endpoint for the route calculations even if address points exist in the
system. If this is so desired, the RoutePremiseLocationsToCenterline can be modified, from the default
value of false, to true. For CAD Clients, this setting can be modified under the Addressing configuration
section of the PremierOne Administrator Console Configuration utility. For a Mobile Client, this setting can be
modified on the Mobile Data Computer under C:\Program Files
(x86)\Motorola\PremierOne\MobileClient\config\offlinegisserver.
177
MN007396A01-D
Both the settings on the server and the Mobile Client Configuration file must be set to true for the Mobile
Client to utilize this feature.
For more information on creating address points see Address Point Import Tool Overview on page 65.
11.3.5
Other Address Verification Settings
There are several other ways to modify the default Address Verification behavior through Provisioning
settings. Refer to the Configuring Mapping chapter of the PremierOne CAD and Mobile Provisioning Guide
Version 4.6.11 for additional Address Verification settings.
178

MN007396A01 D Enus PremierOne GIS Configuration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MN007396A01 D Enus PremierOne GIS Configuration Guide

Uploaded by

Copyright:

Available Formats

PremierOne™

GIS Configuration Guide

NOVEMBER 2023 *MN007396A01*

Intellectual Property and Regulatory

Open Source Content

Version Description Date

MN007396A01-003 Initial release of the PremierOne GIS Configuration April 2023

MN007396A01-D Initial release of the PremierOne GIS Configuration November 2023

3.4.1 Executing the Street Centerline Validator...........................................................................36

4.1.25.1 Creating Premise Hazard Area Feature Classes............................................... 88

7.6.1 Defining Global Turn Delays............................................................................................ 125

9.2.9.1 Importing Caches............................................................................................... 163

Figure 76: ArcMap – Share as Service Dialog Box.........................................................................................118

Figure 115: Windows Explorer – Cache Folder.............................................................................................. 161

Creating Cost Columns ....................................................................................................................................94

Restarting Services on a PremierOne GIS Virtual Machine .......................................................................... 167

About PremierOne GIS Configuration

Related Information Purpose

Geospatial Data in PremierOne

PremierOne Data Import Tools

The Add Tool dialog box appears.

Figure 1: ArcCatalog – Add Tool Dialog Box

The PremierOne Import tools are added to your new toolbox.

GIS Validator Tools

3. Complete the following entries:

Figure 3: Address Point Validator Report Dialog Box

8. Click Apply → Close.

Figure 5: Common Place Validator Dialog Box

3. Complete the following entries:

Figure 7: Street Centerline Validator

3. Complete the following entries:

Figure 8: Street Centerline Query Dialog Box

6. Select Apply → Close, and then click.

Figure 9: Assign City Names to Streets

2. Complete the following fields:

Figure 10: Assign City Names to Points

2. Complete the following fields:

GIS Data Import into PremierOne

Figure 11: ArcCatalog – Create File Geodatabase

Figure 14: ArcCatalog – Create PremierOne Geodatabase

5. After the tool finishes, click Close.

Figure 15: ArcCatalog – PremierOne Geodatabase Contents

Four tables are created in the support geodatabase:

Figure 18: ArcCatalog – Simple Data Loader Subtypes Dialog Box

7. Do not change any values in this dialog box. Click Next.

Figure 20: ArcCatalog – Simple Data Loader Query Dialog Box

9. Perform one of the following:

● REAL_PLACE_ADDRESS and REAL_PLACE_CITY– If the alias name is only applied to a business at a

Figure 22: ArcCatalog – Naming New File Geodatabase

5. After the tool finishes running, click Close.

Figure 25: ArcCatalog – Refreshed PremierOne Geodatabase

Figure 26: ArcCatalog – Street Centerline Import Tool

2. Type or select the information in the required fields.

4. After the tool finishes running, click Close.

2. Type or select the information in the required fields.

4. After the tool finishes running, click Close.

Figure 30: ArcCatalog – Common Place Import Tool

2. Type or select the values in the required fields.

A description of each field is as follows:

4. After the tool finishes running, click Close.

Figure 32: ArcCatalog – Response Boundary Import Tool

2. Type or select the values in the required fields.

A description of each field is as follows:

NOVEMBER 2023 MN007396A01

Case "NT", "TF": restricted = True;