PremierOne™ GIS Setup for CAD and Mobilegis3.oit.ohio.gov/ZIPARCHIVES/marcs/map_updates/P1...GIS collects two categories of geospatial data in PremierOne: Services data – Services

PremierOne™GIS Setup for CAD and Mobile

User Guidefor Version 3.2.1

August 2012© 2012 Motorola Solutions, Inc. All rights reserved. BN 0601-90139

Copyrights

The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.

Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola 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, except for the rights that arise by operation of law in the sale of a product.

Restrictions

The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.

Trademarks

Motorola, Moto, Motorola Solutions, PremierOne, and the stylized M logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license.

Microsoft, Windows, Windows XP, Windows Vista, Windows 7, and Windows Server are registered trademarks of Microsoft Corporation. All other product or service names are the property of their respective owners.

Build date: July 25, 2012

TABLE

OF

CONTENTS

August 2012 i

. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents

Chapter 1: Introduction

What Is In This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2About the Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Keyboard Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3Notes and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Chapter 2: Importing GIS Data For Use Within PremierOne

Installing the PremierOne Data Import Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1Adding the PremierOne Data Import Tools to the ArcToolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

Production and Staging Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6The PremierOne Geodatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7Creating the PremierOne Geodatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8Creating and Connecting to the Premise Hazard Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-19

Creating and Connecting to the Premise Hazard Database for CAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-19Creating and Connecting to the Premise Hazard Database for Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-22

Creating the PremierOne Support Geodatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27Importing Common Place Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-39Importing Street Alias Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43Loading Alias Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45Importing Street Centerline Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-49Importing Address Point Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-55Importing Response Boundary Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-59Importing Reporting District Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-62Importing Map Book Features (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-65 Boundaries (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-68Creating a Model to Import All Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-71The PremierOne Network Dataset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-76

Creating the Network Dataset Using the PremierOneImport Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-77Configuring the Network Routing Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-79Building a Network Dataset Using the ArcCatalog Network Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-82Verifying Routing and Drive Directions in ArcMap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-89Configuring the Network Dataset Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-93

NetworkDataset Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-93EdgeSource Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-93Cost Element and CostAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-94Restriction Element and Restriction Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-95Directions Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-97

ii August 2012

Contents

Example of an Edited NetworkParams.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97Testing the XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99

Building a Statewide Network Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100Calculating the Time Cost for Route Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-106

Using the PremierOne Migration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-109Maintaining a Standardization Exceptions Table (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-113Map Layers Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-115Map Properties for .mxd Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-115Creating Map Layer Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-117Creating Symbology for the Map Layers Dataset Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-124Incorporating Raster Images into the Map Layers Dataset Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-125Road Closures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-133Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-134

Chapter 3: Creating SQL Users

SQL Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter 4: Backing Up Your PremierOne GIS Data

Index

August 2012 1-1

CHAPTER

1

. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Introduction 1

The Geographic Information System (GIS) is the software mapping application that collects, manages, analyzes, and displays information associated with a specific location.

GIS collects two categories of geospatial data in PremierOne:

Services data – Services data is accessed by PremierOne’s application services. This data is in a schema that is optimized for use such as address verification, geocoding, routing, and response determination. Because this data is in a specialized schema, it is not intended to be displayed on a map for visualization by dispatchers or mobile users.

Map data – Map data is data that is displayed on a map. Map data is schema-agnostic. Schema-agnostic data is displayed as map layers defined with a set of attributes, such as streets, boundaries, or beats.

The primary respository for GIS data in an ArcGIS-based system, such as PremierOne, is the geodatabase. A geodatabase is an object-oriented database that provides services for managing geographic data. A geodatabase contains feature datasets and is hosted inside of a relational database management system (RDBMS).

A geodatabase extends the functionality of a commercial RDBMS, such as Microsoft SQL Server, to support spatial data and relationships. A geodatabase that uses Microsoft SQL Server as a repository is known as an Enterprise geodatabase (formerly SDE geodatabase). Geodatabases can also be stored in Microsoft SQL Express (Workgroup geodatabase), Microsoft Access (File Geodatabase), or in a format proprietary to ESRI (File-based geodatabase). Enterprise geodatabases are designed to serve multiple users, while all other geodatabases are designed to serve a single user.

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. For more information about specific applications, see the PremierOne CAD User Guide, the PremierOne Mobile User Guide, and the PremierOne Provisioning Guide.

1-2 August 2012

What Is In This Book Chapter 1: Introduction

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Is In This Book

The GIS Configuration Guide has the following chapters:

Chapter 1: “Introduction.” Describes the contents of this guide and explains the conventions and acronyms used. Common GIS terms are described.

Chapter 2: “Importing GIS Data For Use Within PremierOne.” Describes how to prepare and use the map and services data within PremierOne.

Chapter 3: “Creating SQL Users.” Describes how to create SQL users.

Chapter 4: “Backing Up Your PremierOne GIS Data.” Describes backup procedures.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Documents

PremierOne Provisioning Guide

About the Conventions Used in This

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Guide

There are several conventions used in this guide:

“Keyboard Conventions” on page 1-3

“Typographic Conventions” on page 1-3

“Notes and Cautions” on page 1-4

August 2012 1-3

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide About the Conventions Used in This Guide

Keyboard Conventions

Using the keyboard to carry out commands often involves pressing keys together or in sequence.

Typographic Conventions

These typographic conventions are used throughout this guide.

Table 1-1 Keyboard Conventions

Convention Description

Shift+F1 (Or any two keys joined by a plus sign) Press and hold down the Shift key while pressing the F1 key.

Example: Press Shift+F1 to open the online help.

Table 1-2 Typographic Conventions

Convention Description

Courier New Font

Information that the user needs to enter is in Courier New font.

Example: Enter BO90001 in the text box.

Information that the system displays is in Courier New font.

Example: The Undefined Field error message appears.

Bold Labeled buttons, menu commands, and menu options are in bold.

Example: Click OK to close the dialog box.

<variable> Information the user must substitute appears in italics surrounded by angled brackets.

Example: <agency ID> means the user must supply the appropriate agency identification.

field name Field names appear in the Trebuchet MS font.

Example: In the Password field, type the user’s password.

https://secure.logmein.com/home.asp?lang=en

1-4 August 2012

Definitions Chapter 1: Introduction

Notes and Cautions

Throughout this guide, notes and cautions are used to emphasize text. Notes indicate information that is of high importance. Cautions contain information that must be observed or loss of data could result.

NOTEInformation listed in notes is of high importance.

CAUTIONCautions contain information that must be observed or loss of data could result.

Hardware description

Exact wording of any messages appearing on your screen

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Definitions

You may find the following definitions helpful.

Data View – A data view is an all-purpose view in ArcMap for exploring, displaying and querying geographic data. This view hides all map elements such as titles, North arrows, and scale bars.

ESRI – Environmental Systems Research Institute.

Feature – A feature is a representation of a real-world object on a map. Features can be represented in a GIS as points (for example, common place locations), lines (for example, streets), and polygons (for example, city boundaries).

Feature class – A feature class is a collection of geographic features with the same geometry type (such as point, line, or polygon), the same attributes, and the same spatial reference. Feature classes allow homogeneous features to be grouped into a single unit for data storage purposes. For example, highways, primary roads, and secondary roads can be grouped into a line feature class named roads. Streets would not be grouped on the city polygon class.

August 2012 1-5

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Definitions

Separate feature classes are also usually created for different types of entities. For example, although streets and rivers are both line features that essentially could be contained in the same feature class, separate classes are created for the street features and river features because different information is recorded for these different line features.

NOTENOTEThe feature class is the same as a layer.

A feature name is the name of the column containing the name of the feature class. This is usually NAME; you have the flexibility of using any column name.

Feature dataset – A feature dataset is a collection of feature classes that share the same spatial reference frame. The feature dataset can be a single feature class or it can be a group of similar classes.

Geodatabase – A geodatabase is an object-oriented database that provides services for managing geographic data. A geodatabase contains feature datasets and is hosted inside of a relational database management system (RDBMS).

Layout View – A layout view shows the virtual page upon which you place and arrange geographic data and map elements, such as titles, legends, and scale bars. You use the layout view for printing.

Shapefile – A shapefile is a digital vector (non-topological) format for storing geometric location and associated attribute information. The format is created by ArcView and can be used widely by GIS software. Each shapefile has a minimum of three required component files: .dbf, .shp, and .shx.

Examples of common shapefiles are city, common place, EMS, fire, map page, police, and streets. A shapefile is considered a type of feature class. You import shapefiles to create feature classes.

Figure 1-1 Feature Dataset

Feature Classes (also called layers)

Feature Dataset group of Feature

Classes

Shapefiles

each class has the same geometry type (point, line, or polygon)

1-6 August 2012

Definitions Chapter 1: Introduction

August 2012 2-1

CHAPTER

2Importing GIS Data For Use

. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Within PremierOne 2

This chapter describes how to prepare and then use the map and services data within PremierOne. Some of these steps and processes must be completed before other steps can be initiated, so it is important to follow the steps in the order presented.

NOTESThe GIS system administrator will make data changes and updates to the SDE ADMIN geodatabases and make the source of the .mxd map documents the SDE READER connections.

CAUTIONFor version 3.2 and beyond:A new feature called “Background Geoprocessing” has been 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 that this feature be disabled.

To disable background geoprocessing in ArcCatalog, select Geoprocessing > Geoprocessing Options from the Main Menu, and then uncheck the Enable checkbox under Background Processing.

Installing the PremierOne Data Import

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tools

Installing the PremierOne Import Tools application is a prerequisite to creating the PremierOne geodatabase. The application uses an installation wizard that guides you through the installation.

NOTEA new GIS Import tool should be installed with each CAD upgrade. Contact Motorola for the new GIS Import tool. Use this tool to create the Geodatabases with new schema to be used with the CAD upgrade.

2-2 August 2012

Installing the PremierOne Data Import Tools Chapter 2: Importing GIS Data For Use Within PremierOne

PREREQUISITESYou must have ESRI ArcEditor and .NET Framework 2.5 and 3.0 installed to run the PremierOne Data Import Tools wizard.

To install the PremierOne Data Import Tools:

1. On your installation media, navigate to the Deployment/Source folder and double-click the GISDataImportTool.msi file to launch the PremierOne Data Import Tools Setup wizard.

2. From the Welcome page of the setup wizard, click Next.

The Select Installation Folder wizard page appears.

3. Click Next to accept the defaults.

Figure 2-1 Data Import Tool Wizard – Welcome Page

Figure 2-2 Data Import Tool Wizard – Select Installation Folder

August 2012 2-3

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Installing the PremierOne Data Import Tools

The Confirm Installation wizard page appears.

4. Click Next.

The Installing PremierOne Data Import Tools wizard page appears showing the progress of the installation.

5. When the installation is complete, click Next.

The Installation Complete wizard page appears.

6. Click Close.

7. Complete the steps in “Adding the PremierOne Data Import Tools to the ArcToolbox” on page 2-3.

Adding the PremierOne Data Import Tools to the ArcToolbox

Adding the PremierOne Data Import Tools to the ArcToolbox makes the import tools available where you need them.

Figure 2-3 Data Import Tool Wizard – Confirm Installation

2-4 August 2012

Installing the PremierOne Data Import Tools Chapter 2: Importing GIS Data For Use Within PremierOne

PREREQUISITEBefore you can add the PremierOne Data Import Tools to the ArcToolbox, you must complete the following prerequisite:

Complete the steps in “Installing the PremierOne Data Import Tools” on page 2-1.

To add the PremierOne Data Import Tools to the ArcToolbox:

1. Right-click on the ArcToolbox, and then select New Toolbox.

2. Name the new toolbox; for example, PremierOneImportTools.

3. Right-click the new toolbox.

Figure 2-4 Naming New Toolbox to PremierOneImportTools

August 2012 2-5

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Installing the PremierOne Data Import Tools

4. From the menu that appears, select Add, and then select Tool.

The Add Tool dialog box appears.

Figure 2-5 Adding New Tools to a Toolbox

Figure 2-6 Add Tool Dialog Box

2-6 August 2012

Production and Staging Databases Chapter 2: Importing GIS Data For Use Within PremierOne

5. Select PremierOne Import Tools, and then click OK.

The PremierOne Import tools are added to your new toolbox.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Production and Staging Databases

The PremierOne Data Import tools are used to transform your GIS data into the proper schema for the PremierOne GIS Services database. Part of the transformation process projects feature geometries so that they are in the WGS 1984 spatial reference. This is the spatial reference that is used internally by PremierOne.

Figure 2-7 New Toolbox Showing Motorola Tools

August 2012 2-7

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide The PremierOne Geodatabase

Performing GIS updates for PremierOne requires the existence of two Enterprise (SDE) GIS geodatabases: a production database and a staging database. At any given time, one GIS geodatabase is in production—meaning the GIS services are using that geodatabase as the data source. The other geodatabase is considered the staging geodatabase where the next set of GIS is imported and staged for quality assurance purposes. After the quality assurance process is complete on the staging geodatabase, a geodatabase switch occurs in which the staging geodatabase becomes the production geodatabase and the former production geodatabase becomes the staging geodatabase to be used to stage the next set of GIS data.

This requires the GIS services to have access to connection parameters for both geodatabases. Settings are stored in the PremierOne provisioning subsystem to specify which geodatabase is currently the production geodatabase for each agency. Based on the setting in provisioning, the GIS services executes queries against the appropriate geodatabase for each service call, depending on whether the user’s current login identifies them as a production or staging user.

You should also store your map layer data sources in the PremierOne geodatabase. This ensures that the data for use by both PremierOne services and mapping clients are imported and quality assured at the same time.

NOTEFor Mobile users, the GIS administrator must create a file-based geodatabase replica of the production GIS geodatabase and deploy it to all mobile users in order to support offline functionality.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The PremierOne Geodatabase

Use the PremierOneImport Tool to create the CAD geodatabase and import data into the PremierOne geodatabase. Use the standard ArcCatalog Import Feature Class tool to import layers into the geodatabase for use in map documents.

NOTEThe GIS administrator may import data directly into the enterprise (SDE) staging geodatabase. The GIS administrator can create a personal or file-based geodatabase for importing the data, and then copy/paste/import the geodatabase files to the enterprise geodatabase.

2-8 August 2012

Creating the PremierOne Geodatabase Chapter 2: Importing GIS Data For Use Within PremierOne

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating the PremierOne Geodatabase

Use the ArcEditor to create the PremierOne geodatabase.

PREREQUISITESBefore you can create the PremierOne geodatabase, you must complete the following prerequisites.

Install the PremierOne Data Import Tools. The PremierOne Import Tools application is used to capture the GIS data in the proper schema for use with PremierOne.

For more information, see “Installing the PremierOne Data Import Tools” on page 2-1.

Add the PremierOne Data Import Tools to ArcCatalog.

For more information, see “Adding the PremierOne Data Import Tools to the ArcToolbox” on page 2-3.

Have access to the ArcGIS Desktop at the ArcEditor or higher licensing level.

Create a PremierOne GIS folder to use for storing your PremierOne GIS data and information files.

August 2012 2-9

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Creating the PremierOne Geodatabase

To create the PremierOne geodatabase:

1. On the desktop, click the ArcCatalog icon.

The ArcCatalog displays. A PremierOneImportTools folder appears in the ArcToolbox window pane on the Favorites Tab.

NOTENOTEYou may have given this toolbox a different name when you created it. For more information, see “Installing the PremierOne Data Import Tools” on page 2-1.

Figure 2-8 Arc Catalog Main Window

2-10 August 2012


2. Click the plus sign next to PremierOne ImportTool to expand the toolbox.

Figure 2-9 PremierOneImportTool Toolbox Expanded

August 2012 2-11


3. In the left window, right-click the PremierOne GIS folder that you previously created, select New, and then select File Geodatabase.

Figure 2-10 Creating a New File Geodatabase

2-12 August 2012


A New File Geodatabase appears in the right window pane on the contents tab.

4. Rename this file to a name that is appropriate for your system, for example, PremierOneGIS.gdb. To rename the database, click the *.gdb file in the right window pane on the contents tab and type the new name in the box that appears.

Figure 2-11 Renaming the File Geodatabase

August 2012 2-13


When you expand the folder in the directory tree in the left window pane, the new database that you created and its new name appear.

5. Under the PremierOneImportTool in ArcToolbox, double-click Create PremierOne Geodatabase.

Figure 2-12 Confirming the File Geodatabase Name Change

2-14 August 2012


The Create PremierOne Geodatabase dialog box appears.

NOTENOTEBy leaving the help area open during the use of the PremierOne Import Tool, additional information such as a field or form description and required file formats is displayed. This helps you understand the process and steps necessary to prepare the PremierOne GIS data and map sets.

6. Drag the File Geodatabase that you just created from the ArcCatalog and drop it onto the Target Workspace field in the Create PremierOne Geodatabase dialog box.

Figure 2-13 Create PremierOne Geodatabase Dialog Box

August 2012 2-15


7. From the Input Geodatabase Schema XML File field, click the folder to the right of the field and navigate to the folder where you installed the PremierOne GIS Import Tool.

8. Locate and select the P1GDBSchema.xml file.

Figure 2-14 Populating the Create PremierOne Geodatabase Form (Step 7)

2-16 August 2012


9. Click Open.

The fields in the Create PremierOne Geodatabase form are now complete.


Figure 2-16 Create PremierOne Geodatabase Form Completed

August 2012 2-17


10. Click OK.

The process of creating the PremierOne geodatabase with the proper schema necessary for PremierOne operations begins.

The Create PremierOne Geodatabase Processing dialog box shows the progress as each item is being processed.

11. When processing is complete, click Close.

The ArcCatalog redisplays.

12. Use the Refresh command under the View menu or click F5 to refresh the screen.

Figure 2-17 Create PremierOne Geodatabase Processing Dialog Box

2-18 August 2012


The feature datasets and tables required for the PremierOne data display where you previously saw the File Geodatabase.gdb title. The datasets include Boundaries, Geocoding, Map_Layers, Routing, Place_Name, Street_Intersection, and Street_Range.

NOTENOTEYou can also view the same datasets by expanding the PremierOne-related folder in the left navigation pane that was created during the installation process.

Your PremierOne geodatabase is now ready for you to import other GIS-related data.

Figure 2-18 PremierOne Feature Datasets

August 2012 2-19

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Creating and Connecting to the Premise Hazard Databases

Creating and Connecting to the Premise

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hazard Databases

There are two premise hazard databases: one for CAD and one for Mobile.

Creating and Connecting to the Premise Hazard Database for CAD

The Premise/Hazard database is used for provisioning the CAD premise/hazard locations. You populate and maintain the Premise/Hazard database through the CAD provisioning tool. Your GIS database administrator will create the geodatabase connection in SDE then point to this connection in the *.mxd document.

The Database Connection tool creates the database as well as the connection and the import tool imports the database and the schema.

2-20 August 2012

Creating and Connecting to the Premise Hazard Databases Chapter 2: Importing GIS Data For Use Within PremierOne

To create and connect to the premise/hazard database SDE connection:

1. From the left navigation area of ArcCatalog, click the plus sign next to Database Connections.

2. Double click Add Spatial Database Connection.

Figure 2-19 Adding a Spatial Database Connection

August 2012 2-21


The Spatial Database Connection dialog box appears.

3. Use the SDE connection values you received from your PremierOne System Administrator. Figure 2-20 shows a sample configuration.

4. Click OK.

The CAD premise hazard database is created and connected.

5. From the ArcToolbox, double-click PremierOne Geodatabase.

Figure 2-20 Completing the Spatial Database Connection Dialog Box

2-22 August 2012



6. Drag the premise hazard database from the ArcCatalog and drop it onto the Target Workspace field in the Create PremierOne Geodatabase dialog box.

7. From the Input Geodatabase Schema XML File field, click the folder to the right of the field and navigate to the PremHazGDBSchema.xml file.

Locate the schema file with the PremierOne Data Import Tools in your installation folder.

8. Use the Provisioning tools to complete the premise/hazard information. For more information, see the PremierOne Provisioning Guide.

Creating and Connecting to the Premise Hazard Database for Mobile

The premise hazard database for Mobile needs to reside locally on each laptop along with the Mobile file geodatabase.

PREREQUISITESBefore you connect to the premise hazard database, you must complete the following

Figure 2-21 Create PremierOne Geodatabase Dialog Box)

August 2012 2-23


prerequisites.

u Create your map layer dataset. For more information, see “Creating Map Layer Datasets” on page 2-117.

u Create the symbology for your map layers dataset. For more information, see “Creating Symbology for the Map Layers Dataset Documents” on page 2-124.

u Incorporate raster images into your map layer dataset. For more information, see “Incorporating Raster Images into the Map Layers Dataset Display” on page 2-125

Before you can connect to the premise hazard database for Mobile, you need to create a local file geodatabase. Motorola recommends that you create the premise hazard file geodatabase in the DATA folder where your Mobile file geodatabase resides.

To create a new local file geodatabase:

1. From the left navigation area of ArcCatalog, right-click and select New, and then select File Geodatabase.


2-24 August 2012



2. Name the geodatabase file a name that is appropriate for your system. To rename the database, click the *.gdb file in the right window pane on the contents tab and type the new name in the box that appears.


August 2012 2-25



3. In the Target Workspace field, navigate to the location of your newly created geodatabase.

4. In the Input Geodatabase Schema XML File field, navigate to the PremHazGDBSchema.xml file.

Locate the schema file with the PremierOne Data Import Tools in your installation folder.

5. Click OK.


2-26 August 2012


The process of creating the geodatabase with the designated schema begins.




7. Delete the existing feature class “PREMISE HAZARD” from the PREMISE feature dataset of the newly created file geodatabase.

8. Copy the PREMISE HAZARD FeatureClass from the SDE Premise database to the PREMISE feature dataset of the new file geodatabase.

Figure 2-25 Create PremierOne Geodatabase Processing Dialog Box

August 2012 2-27

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Creating the PremierOne Support Geodatabase

Creating the PremierOne Support

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Geodatabase

Use the ArcEditor to create the PremierOne Support geodatabase. The Support geodatabase contains three tables:

CommonPlaceAliases

StandardizationExceptions

StreetNameAliases

PREREQUISITESBefore you can create a PremierOne Support geodatabase, you must complete the following prerequisites.

Install the PremierOne Data Import Tools. The PremierOne Import Tools application is used to capture the GIS data in the proper schema for use with PremierOne.

For more information, see “Installing the PremierOne Data Import Tools” on page 2-1.

Add the tool to ArcCatalog.

For more information, see “Adding the PremierOne Data Import Tools to the ArcToolbox” on page 2-3.

Have access to the ArcGIS Desktop at the ArcEditor or higher licensing level.

Create a PremierOne GIS folder to use for storing your PremierOne GIS data and information files.

Create the PremierOne geodatabase.

For more information, see “Creating the PremierOne Geodatabase” on page 2-8

2-28 August 2012

Creating the PremierOne Support Geodatabase Chapter 2: Importing GIS Data For Use Within PremierOne

To create the PremierOne Support geodatabase:

1. On the desktop, click the ArcCatalog icon.

The ArcCatalog displays. A PremierOneImportTools folder appears in the ArcToolbox window pane on the Favorites Tab.

NOTENOTEYou may have given this toolbox a different name when you created it. For more information, see “Installing the PremierOne Data Import Tools” on page 2-1.

Figure 2-26 Arc Catalog Main Window

August 2012 2-29


2. Click the plus sign next to PremierOne ImportTool to expand the toolbox.

Figure 2-27 PremierOneImportTool Toolbox Expanded

2-30 August 2012


3. In the left window, click the PremierOne folder, select New, and then select File Geodatabase.


August 2012 2-31



4. Rename this file to a name that is appropriate for your system, for example, PremierOneSupport.gdb. To rename the database, click the *.gdb file in the right window pane on the contents tab and type the new name in the box that appears.


2-32 August 2012


When you expand the folder in the directory tree in the left window pane, the new database that you created and its new name appear.

5. Under the PremierOneImportTool in ArcToolbox, double-click Create PremierOne Geodatabase.

Figure 2-30 Confirming the File Geodatabase Name Change

August 2012 2-33



NOTENOTEBy leaving the help area open during the use of the PremierOne Import Tool, additional information such as a field or form description and required file formats is displayed. This helps you understand the process and steps necessary to prepare the PremierOne GIS data and map sets.

6. Locate the PremierOneSupport geodatabase that you just created and drop it onto the Target Workspace field in the Create PremierOne Geodatabase dialog box.


2-34 August 2012


7. From the Input Geodatabase Schema XML File field, click the folder to the right of the field and navigate to the folder where you installed the PremierOne GIS Import Tool.

8. Locate and select the GISSupportGDBSchema file.


August 2012 2-35


9. Click Open.


2-36 August 2012


The fields in the Create PremierOne Geodatabase form are now complete.

10. Click OK.

The process of creating the PremierOne Support geodatabase with the proper schema necessary for PremierOne operations begins.

Figure 2-34 Create PremierOne Geodatabase Form Completed

Figure 2-35 Create PremierOne Support Geodatabase Processing Dialog Box

August 2012 2-37





12. Use the Refresh command under the View menu or click F5 to refresh the screen.

2-38 August 2012


The common place aliases, street aliases, and standardization exceptions now display where you previously saw the new .gdb title.

NOTENOTEYou can also view the same datasets by expanding the PremierOne-related folder in the left navigation pane that was created during the installation process.

NOTEThe following sections describe the various ways of importing feature sets into the PremierOne geodatabase. It is important to note that you can use a model format to import all of the feature sets using a single batch process. For more information on using a model format to import a feature set, see “Creating a Model to Import All Data” on page 2-71.

Figure 2-36 ArcCatalog Aliases and Exceptions

August 2012 2-39

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Common Place Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Common Place Data

A common place is the name of a commonly-known place or feature, such as a business, church, school, landmark, or topographic feature. PremierOne accepts defined common place names during incident initiation.

PREREQUISITEBefore you import common place data, you must complete the following prerequisite:

Create a Standardization Exceptions table if your jurisdiction has street names that include a street name that is a direction, such as North St., South Ave, East Blvd., or West Pkwy. For more information, see “Maintaining a Standardization Exceptions Table (optional)” on page 2-113.

To import common place data:

1. In the ArcToolbox window, double-click the Common Place Import toolbox.

Figure 2-37 Common Place Import Toolbox

2-40 August 2012

Importing Common Place Data Chapter 2: Importing GIS Data For Use Within PremierOne

The Common Place Import dialog box appears.

2. Populate each of the required fields in the dialog box. To do this you can use either the navigate/browse button (represented by the folder icon to the right of the field) or use a drag and drop operation from your GIS data warehouse to the form.

For this dialog box, you populate the following fields:

PremierOne Workspace – Identify the location of the PremierOne geodatabase.

Input Common Place Features – Identify the common place data to import from either a geodatabase or shape file format.

Standardization Exceptions Table (Optional) – Identify the location of the Standardization Exceptions table.

Street Alias Table (Optional) – Identify the location of the Street Alias table.

Place Name Field – Identify the Name field.

Alias Name Fields (optional) – Identify the common place alias name.

Figure 2-38 Common Place Import Dialog Box

August 2012 2-41

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Common Place Data

Address Part Fields (optional) – Identify the address associated with a common place.

Address part fields are a list, in order, of the fields in the source Feature Class that make up the address. In some sources, this may include multiple fields. In other sources, the street name may be stored entirely in a single field.

City Field – Identify the city_name associated with the common place.

An example of a completed Common Place Import dialog box is shown in Figure 2-39 on page 2-41.

Figure 2-39 Completed Common Place Import Dialog Box

2-42 August 2012

Importing Common Place Data Chapter 2: Importing GIS Data For Use Within PremierOne

3. Click OK to begin processing the information and adding it to the PremierOne geodatabase.

The Common Place Processing dialog box shows the progress as each item is processed.

NOTENOTEIf there were errors during the processing, an error log will be written to the Common Place log file. The path to the file will be shown in the Processing dialog box. Work with your GIS system administrator to resolve the errors.



The PremierOne geodatabase now contains your Common Place information.

Figure 2-40 Common Place Import Processing Dialog Box – Process Completed

August 2012 2-43

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Street Alias Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Street Alias Data

You maintain all of your PremierOne street alias data in a geodatabase table.

NOTECreate alias and street standardization tables in their own file databased, not in the PremierOne staging geodatabase.

PREREQUISITESBefore you import the street aliases, you must complete the following prerequisites:

u Create a Standardization Exceptions table if your jurisdiction has street names that include a street name that is a direction, such as North St., South Ave, East Blvd., or West Pkwy. For more information, see “Maintaining a Standardization Exceptions Table (optional)” on page 2-113.

u Create a street alias table. For more information, see “To create the street alias table:” on page 2-43.

u Import the Common Place data. For more information, see “Importing Common Place Data” on page 2-39

u Run the Common Place Migration Tool. For more information, see “Using the PremierOne Migration Tools” on page 2-109

u Delete the PremierOne schema.

u Import the Common Place data again using the newly populated CommonPlaceAliases table as an input parameter.

To create the street alias table:

Do one of the following:

If you are already a Premier CAD or Motorola CAD user, Motorola will extract the current street aliases from your existing application to a .dbf file. You will need to rename the column headings shown as field names in the schema below, and then import the .dbf file into this ArcGIS table. Both existing Premier CAD and Motorola CAD users are required to create a table using the following schema.

Use an xml file that creates the street alias table, the street standardization table, and the common place alias table.

To create the Street Alias, Street Standardization, and Common Place Alias tables using xml:

1) Create a new file database and name it appropriately, i.e., P1 Tables.

2) Run the Create PremierOne Geodatabase tool from the P1 import tools.

2-44 August 2012

Importing Street Alias Data Chapter 2: Importing GIS Data For Use Within PremierOne

3) Select GISSupportGDBSchema.xml.

This will create the three tables that you can now populate either by importing directly into the table or manually populating.

To import an existing Excel spreadsheet of aliases:

1) Save the Excel file as a comma separated (.cvs) file.

2) Use the Load wizard and map the appropriate fields. (See “Loading Alias Table Data” on page 2-45.)

Create a table yourself using the following schema:

<Table name=“StreetNameAliases”>

<Field name=“GRID” dataType=“text” dataLength=“8”></Field>

<Field name=“LOW_HOUSE” dataType=“long integer”></Field>

<Field name=“HIGH_HOUSE” dataType=“long integer”></Field>

<Field name=“REAL_PRE_DIR” dataType=“text” dataLength=“4”></Field>

<Field name=“REAL_PRE_TYPE” dataType=“text” dataLength=“8”></Field>

<Field name=“REAL_STREET_NAME” dataType=“text” dataLength=“76”></Field>

<Field name=“REAL_SUF_TYPE” dataType=“text” dataLength=“8”></Field>

<Field name=“REAL_SUF_DIR” dataType=“text” dataLength=“4”></Field>

<Field name=“ALIAS_PRE_DIR” dataType=“text” dataLength=“4”></Field>

<Field name=“ALIAS_PRE_TYPE” dataType=“text” dataLength=“8”></Field>

<Field name=“ALIAS_STREET_NAME” dataType=“text” dataLength=“76”></Field>

<Field name=“ALIAS_SUF_TYPE” dataType=“text” dataLength=“8”></Field>

<Field name=“ALIAS_SUF_DIR” dataType=“text” dataLength=“4”></Field>

<Field name=“CITY” dataType=“text” dataLength=“150”></Field>

</Table>

August 2012 2-45

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Loading Alias Table Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loading Alias Table Data

To load the alias table data:

1. From the left navigation pane of the ArcCatalog window, right-click StreetNameAliases, select Load, and then select Load Data.

Figure 2-41 Load Street Name Alias Data

2-46 August 2012

Loading Alias Table Data Chapter 2: Importing GIS Data For Use Within PremierOne

The Simple Data Loader dialog box appears.

2. Click Next.

The first Simple Data Loader dialog box appears with the source data in the Input data field.

3. Ensure the path to Database4AliasTable.gdb\Alias_table appears in the Input data field, and then click Add.

Figure 2-42 Simple Data Loader Dialog Box

Figure 2-43 First Simple Data Loader Dialog Box With Source Data in Input data Field

August 2012 2-47

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Loading Alias Table Data

The first Simple Data Loader dialog box appears with the source data in the List of source data to load box.

4. Click Next.

The second Simple Data Loader dialog box appears.

5. Ensure the I do not want to load all rows into a subtype field is selected, and then click Next.

Figure 2-44 First Simple Data Loader Dialog Box With Source Data in List

Figure 2-45 Second Simple Data Loader Dialog Box

2-48 August 2012

Loading Alias Table Data Chapter 2: Importing GIS Data For Use Within PremierOne

The third Simple Data Loader dialog box appears.

6. Click Next.

The fourth Simple Data Loader dialog box appears.

7. Ensure the Load all of the source data option is selected.

8. Click Next.

Figure 2-46 Third Simple Data Loader Dialog Box

Figure 2-47 Fourth Simple Data Loader Dialog Box

August 2012 2-49

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Street Centerline Data

The last Simple Data Loader dialog box appears.

9. Click Finish.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Street Centerline Data

The import tool imports street centerline features into the PremierOne geodatabase for address verification and geocoding purposes. You can run the tool multiple times to import multiple source feature classes.

PREREQUISITEBefore you import the street centerline data, you must complete the following prerequisite:

Create a Standardization Exceptions table if your jurisdiction has street names that include a street name that is a direction, such as North St., South Ave, East Blvd., or West Pkwy.

Figure 2-48 Last Simple Data Loader Dialog Box

2-50 August 2012

Importing Street Centerline Data Chapter 2: Importing GIS Data For Use Within PremierOne

For more information, see “Maintaining a Standardization Exceptions Table (optional)” on page 2-113.

To import street centerline data:

1. In the ArcToolbox window, double-click the Street Centerline Import toolbox.

Figure 2-49 Street Centerline Import Toolbox

August 2012 2-51


The Street Centerline Import dialog box appears.

NOTESThe green dot displayed next to a field in the Street Centerline Import dialog box indicates that the field is required and must be populated before the next step in the process can be completed.

The green dot disappears as each field is populated.

Figure 2-50 Street Centerline Import Dialog Box

2-52 August 2012


The Street Alias table you previously imported loads data into the Street Centerline Import dialog boxes if available.

NOTENOTEThe data used for the Street Centerline Import dialog box can be in shape file format, geodatabase format, or any other ESRI-supported data format.

2. Populate each of the required fields in the Street Centerline Import dialog box. To do this you can use either the navigate/browse button (represented by the folder icon to the right of the field) or use a drag and drop operation from your GIS data warehouse to the form.



Input Street Centerline Features – Identify the Street Centerline data to import from either a geodatabase or shape file format.



Left Low House Field – Identify the left low house field.

This can be as low as 0.

Left High House Field – Identify the left high house field.

For segments that have the same alias withing the same city, the high house field should be something extremely high, such as 999,999,999 but no higher then 2,147,483,647.

Right Low House Field – Identify the right low house field.

This can be as low as 0.

Right High House Field – Identify the right high house field.

For segments that have the same alias withing the same city, the high house field should be something extremely high, such as 999,999,999 but no higher then 2,147,483,647.

NOTEAll segments must have the lowest low and highest high for the address range of the street segments.

Street Name Part Fields – Identify the street name part fields.

August 2012 2-53


Street name part fields are a list, in 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. In other sources, the street name may be stored entirely in a single field.

NOTEIf the Street Name Part Fields are separate fields, you must select each field in the proper order. If you need assistance, contact your GIS System Administrator.

Field – Provide any additional comments.

Left City Field – Identify the left city field.

Right City Field – Identify the right city field.

NOTEThe left and right city fields should match the city name from the ANI/ALI feed.

Low Cross Street Override Field (optional) – If a value exists in this field for a particular street segment input record, that value is used as the LOW_CROSS_STREET value in the STREET_RANGE tabe row(s) associated with that particular street segment. In addition, the Street Centerline Import Tool checks each input segment to see if it contains a value in this field.

If no value is present, the low cross street is calculated normally using connecting street segments. In addition, all low cross streets are calculated normally using connecting street segments.

High Cross Street Override Field (optional) – If a value exists in this field for a particular street segment input record, that value is used as the HIGH_CROSS_STREET value in the STREET_RANGE table row associated with that particular street segment. In addition, the Street Centerline Import Tool checks each input segment to see if it contains a value in this field.

If no value is present, the high cross street is calculated normally using connecting street segments. In addition, all high cross streets are calculated normally using connecting street segments.

Cross Street Bypass Field (optional) – If any non-empty, non-null value exists in this field for a particular street segment input record, that street segment is not used to generate a STREET_INTERSECTION record with any segment that it is connected to on either end. In addition, the Street Centerline Input Tool checks each segment to see if it contains a value in this field.

If no value is present, STREET_INTERSECTION records are generated normally using connecting segments. In addition, all STREET_INTERSECTION records are generated normally using connecting segments.

Description Field (optional) – Provide a description.

2-54 August 2012


Left and Right Zip Code Fields (optional) – Provides Zip code information for use in RMS.

State Field (optional) – Provide state information for use in RMS.

An example of a completed Street Centerline Import dialog box is shown in Figure 2-51 on page 2-54.


Figure 2-51 Completed Street Centerline Import Dialog Box

August 2012 2-55

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Address Point Data

The Street Centerline Import Processing dialog box shows the progress as each item is processed.

NOTENOTEIf there were errors during the processing, an error log will be written to the Street Centerline log file. The path to the file will be shown in the Processing dialog box. Work with your GIS system administrator to resolve the errors.



The PremierOne geodatabase now contains your Street Centerline information.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Address Point Data

Use the import tool to import address point features into the PremierOne geodatabase if your GIS system uses address point data.

Figure 2-52 Street Centerline Import Processing Dialog Box – Process Completed with Errors

2-56 August 2012

Importing Address Point Data Chapter 2: Importing GIS Data For Use Within PremierOne

PREREQUISITEBefore you import address point data, you must complete the following prerequisite:

Create a Standardization Exceptions table if your jurisdiction has street names that include a street name that is a direction, such as North St., South Ave, East Blvd., or West Pkwy. For more information, see “Maintaining a Standardization Exceptions Table (optional)” on page 2-113.

To import address point data:

1. In the ArcToolbox window, double-click the Address Point Import toolbox.

Figure 2-53 Address Point Import Toolbox

August 2012 2-57

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Address Point Data

The Address Point Import dialog box appears.

2. Populate each of the fields in the dialog box. To do this you can use either the navigate/browse button (represented by the folder icon to the right of the field) or use a drag and drop operation from your GIS data warehouse to the form.



Input Address Point Features – Identify the address point data to import from either a geodatabase or shape file format.



Address Part Fields – Identify the address associated with the Address Point.

City Field – Identify the field containing the city for which the address is valid.

Sub House Field (Optional) – Identity the field that contains a sub-house value, such as an apartment number, a unit/suite number, and so on.

Figure 2-54 Address Point Import Dialog Box

2-58 August 2012

Importing Address Point Data Chapter 2: Importing GIS Data For Use Within PremierOne

Building Field (Optional) – Identity the field that contains the building number.

Description Field (Optional) – Identify the field that contains the description.

Zip Code Field (Optional) – Identify the field that contains the Zip code for the address.

State Field (Optional) – Identify the field that contains the state information.


The Address Point Processing dialog box shows the progress as each item is processed.

Figure 2-55 Address Point Import Processing Dialog Box – Processing Complete

August 2012 2-59

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Response Boundary Features

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Response Boundary Features

Use the Response Boundary Import Tool to import response boundary features into the PremierOne geodatabase.

To import the response boundary features into the PremierOne geodatabase:

1. From the ArcToolbox in the ArcCatalog window, double-click the Response Boundary Import toolbox.

Figure 2-56 Response Boundary Import Toolbox

2-60 August 2012

Importing Response Boundary Features Chapter 2: Importing GIS Data For Use Within PremierOne

The Response Boundary Import dialog box appears.


For this dialog box you populate the following fields:


Input Boundary Features – Identify the response boundary to import from either a geodatabase or shape file format and identifies the column with agency attribute.

Boundary Name field – Identify the column with the boundary name attribute.

Agency ID Field – Identify the Agency ID attribute.

3. When you finish populating the fields in the Response Boundary Import dialog box, click OK to begin processing the response boundary features and adding them to the PremierOne geodatabase.

Figure 2-57 Response Boundary Import Dialog Box – Completed

August 2012 2-61

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Response Boundary Features

The Response Boundary Import Processing dialog box shows the progress as each item is being processed.

NOTENOTEIf there were errors during the processing, an error log will be written to the Response Boundary log file. The path to the file will be shown in the Processing dialog box. Work with your GIS system administrator to resolve the errors.


The ArcCatalog returns to focus.

The Response Boundary features are now imported into the PremierOne geodatabase.

NOTENOTERun the Response Boundary Import Tool for each boundary layer necessary to support each of the agencies that you are using with PremierOne. For example, if you are supporting both police and fire, you need to run this tool twice.

Figure 2-58 Response Boundary Import Processing Dialog Box – Processing Completed

2-62 August 2012

Importing Reporting District Features Chapter 2: Importing GIS Data For Use Within PremierOne

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Reporting District Features

Use the Reporting District Import Tool to import reporting district features into the PremierOne geodatabase.

NOTEThe Agency ID in the Reporting District Import Tool must match the Agency ID of the responding agency. This may require fire and police to create thier own sets of nearly identical layers (identical expect for agency ID).

To import reporting district features into the PremierOne geodatabase:

1. From the ArcToolbox in the ArcCatalog window, double-click the Reporting District Import toolbox.

Figure 2-59 Reporting District Import Toolbox

August 2012 2-63

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Reporting District Features

The Reporting District Import dialog box appears.




Input Boundary Features – Identify the response boundary to import from either a geodatabase or shape file format and identify the column with the agency attribute.

Agency ID Field – Identify the Agency ID attribute.

Boundary Name Field – Identify the column with the boundary name attribute.

3. When you finish populating the fields in the Reporting District Import dialog box, click OK to begin processing the response boundary features and adding it to the PremierOne geodatabase.

Figure 2-60 Reporting District Import Dialog Box – Completed

2-64 August 2012

Importing Reporting District Features Chapter 2: Importing GIS Data For Use Within PremierOne

The Reporting District Import Processing dialog box shows the progress as each item is being processed.

NOTENOTEIf there were errors during the processing, an error log will be written to the Reporting District log file. The path to the file will be shown in the Processing dialog box. Work with your GIS system administrator to resolve the errors.



The Reporting District features are now imported into the PremierOne geodatabase.

Figure 2-61 Reporting District Import Processing Dialog Box – Processing Completed

August 2012 2-65

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Map Book Features (Optional)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing Map Book Features (Optional)

Use the Map Book Import tool to import map book features into the PremierOne geodatabase. This is an optional step.

To import the map book features into the PremierOne geodatabase:

1. From the ArcToolbox in the ArcCatalog window, double-click the Map Book Import toobox.

Figure 2-62 Map Book Import Tool

2-66 August 2012

Importing Map Book Features (Optional) Chapter 2: Importing GIS Data For Use Within PremierOne

The Map Book Import dialog box appears. Required fields are identified by a green dot next to the field name.




Input Boundary Features – Identify the response boundary to import from either a geodatabase or shape file format and identify the column with the agency attribute.

Map Book Name – Identify the Map Book Name attribute.

Grid Reference Field – Identify the column with the grid reference attribute.

3. When you finish populating the fields in the Map Book Import Tool dialog box, click OK to begin processing information and adding it to the PremierOne geodatabase.

Figure 2-63 Map Book Import Tool Dialog Box

August 2012 2-67

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Importing Map Book Features (Optional)

The Map Book Import Tool Processing dialog box shows the progress as each item is being processed.

NOTENOTEIf there were errors during the processing, an error log will be written to the Map Book log file. The path to the file will be shown in the Processing dialog box. Work with your GIS system administrator to resolve the errors.



The Map Book features are now imported into the PremierOne geodatabase.

Figure 2-64 Map Book Import Processing Dialog Box

2-68 August 2012

Boundaries (Optional) Chapter 2: Importing GIS Data For Use Within PremierOne

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Boundaries (Optional)

The Contractor Boundary Import Tool imports contractor rotation boundary features into the PremierOne geodatabase for boundary determination purposes. You can import multiple source feature classes into the PremierOne geodatabase by using this tool multiple times.

NOTEThe Agency ID in the Contractor Boundary Import Tool must match the Agency ID of the responding agency. This may require fire and police to create thier own sets of nearly identical layers (identical expect for agency ID).

To import the contractor rotation boundary features into the PremierOne geodatabase:

1. From the ArcToolbox in the ArcCatalog window, double-click Contractor Boundary Import.

Figure 2-65 Contractor Boundary Import in ArcToolbox

August 2012 2-69

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Boundaries (Optional)

The Contractor Boundary Import dialog box appears. The required field is identified by a green dot next to the field name.

2. Populate each of the required fields in the dialog box.

For this dialog box, you populate the Contractor Type field.

3. When you finish populating the fields in the Contractor Boundary Import Tool dialog box, click OK to begin processing information and adding it to the PremierOne geodatabase.

Figure 2-66 Contractor Boundary Import Dialog Box

2-70 August 2012

Boundaries (Optional) Chapter 2: Importing GIS Data For Use Within PremierOne

The Contractor Boundary Import Tool Processing dialog box shows the progress as each item is being processed.

4. When Processing is complete, click Close.


The Contractor Boundary features are now imported into the PremierOne geodatabase.

Figure 2-67 Contractor Boundary Import Tool Processing Dialog Box

August 2012 2-71

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Creating a Model to Import All Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Model to Import All Data

As mentioned earlier in this chapter, you can create an import model to import all of the feature set data in a single batch file. You can use Windows Scheduler to schedule a time for the batch file to fun. For more information, see Windows documentation.

To create a model to import all feature set data in a batch file:

1. From the ArcCatalog window, right-click ArcToolbox, and then select New Toolbox.

A new toolbox is created.

2. Name the toolbox.

Figure 2-68 Creating a New Toolbox

2-72 August 2012

Creating a Model to Import All Data Chapter 2: Importing GIS Data For Use Within PremierOne

3. Create a new model by right-clicking on the newly created toolbox and selecting Model.

4. Drag the PremierOne Import Tools onto the newly created model.

Figure 2-69 Creating a New Model

August 2012 2-73


5. Double-click the tool that was placed in the model, and type Geodatabase in the target workspace.

6. Drag the next import tool.

7. Add a connector from Geodatabase to the import tool.

8. Double-click the tool that was placed in the model and populate the import tool for each layer following the same procedures used for each individual import tool.

Figure 2-70 Adding PremierOne Import Tools to the New Model

2-74 August 2012

Creating a Model to Import All Data Chapter 2: Importing GIS Data For Use Within PremierOne

9. If there will be multiple data import tools, as in the Response layer, copy the first tool, and then paste additional tools. Configure each import tool.

Figure 2-71 Populating Each Import Tool Dialog Box

August 2012 2-75


Figure 2-71 shows the Street Centerline Import dialog box. Click OK and continue populating the rest of the import tool forms as previously described in this chapter.

10. After the import model is created and saved, select Model > Run from the menu in the Data Model window to run the batch file.

11. Set a parameter on the geodatabase to be prompted to enter the name and location of the geodatabase to import into.

Figure 2-72 Feature Set Import Model – Completed

2-76 August 2012

The PremierOne Network Dataset Chapter 2: Importing GIS Data For Use Within PremierOne

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The PremierOne Network Dataset

This section describes the process for creating the standard PremierOne network dataset. The purpose of this dataset is to create the ability to support routing and driving directions using the GIS system for PremierOne. To build a statewide network dataset, see “Building a Statewide Network Dataset” on page 2-100.

NOTEThis is a standard GIS database administrator function. If you are trained in the maintenance and management of the GIS database and are familiar with GIS database administration, specifically how to build and work with network datasets, then this should already be familiar to you. If not, contact your GIS database administrator before creating a network dataset on your own.

The network dataset is used for shortest path route solving, including ETA (estimated time of arrival) calculations and driving directions. To calculate the time cost for route solving, see “Building a Statewide Network Dataset” on page 2-100.

Network datasets are created using ArcCatalog. The network dataset is extremely rich in features compared to the NetEngine Software Developer Kit used in legacy CAD products. This section will not attempt to provide an exhaustive overview of building a network dataset. Rather, it will cover configurations most likely to be utilized by customers using PremierOne. For more information regarding building network datasets, refer to ArcGIS Desktop Online help at the following location:

http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=An_overview_of_Network_Analyst

NOTEA network dataset does not automatically update whenever its source feature classes change. If streets are added or deleted or the values used to define attributes are modified, the network dataset must be rebuilt. You cannot rebuild a network dataset while other users are connected to the geodatabase.

Network datasets may be copied, but only if all of their source feature classes are also copied. ArcCatalog will notify you of the associated feature classes if necessary. Additionally, copied network datasets must be built before they can be used. Right-click the Network Dataset and select Build to complete the process.



August 2012 2-77

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide The PremierOne Network Dataset

Creating the Network Dataset Using the PremierOneImport Tool

To simplify the network dataset creation process, use the PremierOneImport Tool to develop the network dataset for your geodatabase.

PREREQUISITEBefore you create the network dataset, you must complete the following prerequisite:

The Street layer must reside in the Routing feature dataset before you run the PremierOneImportTool.

To create the network dataset using the PremierOneImportTool:

1. Copy the Street feature class into the Routing feature dataset.

2. From the navigation area on the left, click the plus sign next to PremierOne to expand the PremierOne options.

3. Right-click the Routing feature dataset, select Import, and then select Feature Class (single).

Figure 2-73 Importing a Feature Class (Single)

2-78 August 2012


The Feature Class to Feature Class dialog box appears.

4. Drag and drop or browse for the required values for the Input Features and Output Location fields.

5. In the Output Feature Class field, type a unique name; for example, Street_net.

NOTESThe Output Feature Class field must to be named uniquely. For this example, we used “_net” after street to ensure it is unique.

This must be configured in the routing.xml file using the same name.

6. Click OK to begin the import process.

Figure 2-74 Feature Class to Feature Class Dialog Box

August 2012 2-79


The Feature Class to Feature Class Processing dialog box shows the progress as each item is processed.



Configuring the Network Routing Dataset

Use the ArcToolbox to configure the network routing database.

PREREQUISITESBefore you configure the network routing database, you must complete the following prerequisites.

u Create the network dataset. For more information, see “Creating the Network Dataset Using the PremierOneImport Tool” on page 2-77.

u Make sure that the NetworkDatabaseParams.xml file has been edited by your GIS system administrator to ensure the proper feature class name and attributes. (See “Configuring the Network Dataset Parameters” on page 2-93.)

u If all fields are not present in the NetworkDatabaseParams.xml, you must run the ArcCatalog network wizard. (See “Building a Network Dataset Using the ArcCatalog Network Wizard” on page 2-82).

Figure 2-75 Feature Class to Feature Class Processing Complete

2-80 August 2012


To configure the PremierOne network routing dataset:

1. From the ArcToolbox in the ArcCatalog window, double-click Create PremierOne Network Database to launch the tool.

Figure 2-76 Create PremierOne Network Database Toolbox

August 2012 2-81


The Create PremierOne NetworkDataset dialog box appears. Required fields are identified by a green dot next to the field name.

2. Drag the PremierOne geodatabase from the ArcCatalog and drop it onto the Target Workspace field in the Create PremierOne NetworkDataset dialog box.

3. Select the NetworkDatabaseParams.xml file that was modified for your organization and this project to match your feature class names and attributes.


Figure 2-77 Create PremierOne NetworkDataset Dialog Box

2-82 August 2012


The Create PremierOne NetworkDataset Processing dialog box shows the progress as each item is being processed.



You have now created the Network Routing Dataset.

Building a Network Dataset Using the ArcCatalog Network Wizard

PREREQUISITE:If all fields for a dataset are not present in the NetworkDatabaseParams.xml, run the ArcCatalog network wizard.

To run the ArcCatalog network wizard:

1. In ArcCatalog, right-click the selected feature dataset and select New > Network Dataset.

2. Type the name for the network dataset, MOT_NET, and click Next.

Figure 2-78 Create PremierOne NetworkDataset Dialog Box – Process Complete

August 2012 2-83


The feature classes dialog box appears.

3. Select the Street layer feature class to participate in the network and click Next.

The Connectivity dialog box appears.

4. Click Next to use connectivity defaults.

Figure 2-79 ArcCatalog Network Wizard – Feature Classes

Figure 2-80 ArcCatalog Network Wizard – Connectivity

2-84 August 2012


The elevation field data dialog box appears.

5. Unless you have valid F_ZLEV and T_ZLEV data, select No, and then click Next.

The model turns dialog box appears.

6. Select Yes, and then click Next.

Figure 2-81 ArcCatalog Network Wizard – Elevation Field Data

Figure 2-82 ArcCatalog Network Wizard – Model Turns

August 2012 2-85


The specify attributes dialog box appears.

7. Select Oneway, and then click Evaluators.

The Evaluators dialog box appears.

8. For each direction, click in the Values dropdown list, and select the value that matches your Oneway attributes, then click OK.

The specify attributes dialog box redisplays.

9. Click Add.

Figure 2-83 ArcCatalog Network Wizard – Select Attributes

Figure 2-84 ArcCatalog Network Wizard – Evaluators

2-86 August 2012


The Add New Attribute dialog box appears.

10. Complete the fields as follows:

Name: Distance

Usage Type: Cost

Units: Decimal Degrees

11. Click OK.

The new attribute appears on the attributes dialog box.

12. Click Evaluators.

Figure 2-85 ArcCatalog Network Wizard – Add New Attribute

Figure 2-86 ArcCatalog Network Wizard – New Attribute

August 2012 2-87



13. For both directions, change the Type to “Field.” Change the Value to “Shape_length,” and then click OK.

The attributes dialog box redisplays.

14. Click Next.

The driving directions settings dialog box appears.

15. Select Yes to establish driving directions.

If the data has the street name parsed, click the Directions button.

Figure 2-87 ArcCatalog Network Wizard – Evaluators

Figure 2-88 ArcCatalog Network Wizard – Driving Directions

2-88 August 2012


The Network Directions Properties window appears.

16. Populate the correct fields for the Street Name Fields.

17. Click OK.

18. If your data has the name in one concatenated field, click Next.

The Summary window appears.

19. Click Finish.

Figure 2-89 ArcCatalog Network Wizard – Network Directions Properties

Figure 2-90 ArcCatalog Network Wizard – Summary

August 2012 2-89


The build network prompt appears.

20. Click Yes to build the dataset.

Verifying Routing and Drive Directions in ArcMap

NOTESIf multiple street files are used, as in large state-wide sites, the ArcCatalog network wizard must be run.

If the data has at least time cost attributes and distance attributes, the networkparams.xml file may be edited and used. See “Configuring the Network Dataset Parameters” on page 2-93.

The routing attributes must be created on the state plane street file.

If the customer is creating cost ZLEV attributes, the fields must either be short or long data types.

For directions on creating cost attributes, see “Building a Statewide Network Dataset” on page 2-100.

For directions on building the network dataset using ArcCatalog’s wizard, see “Building a Statewide Network Dataset” on page 2-100.

After configuring routing and drive directions in ArcMap, verify them as follows.

Figure 2-91 ArcCatalog Network Wizard – Build Network Prompt

2-90 August 2012


To verify routing and drive directions in ArcMap:

1. In ArcMap, select Add Data.

The Add Data dialog box appears.

2. Select MOT_NET and Street_Net, and then click Add.

The Adding Network Layer dialog box appears, asking if you want to add all feature classes that participate in MOT_NET.

3. Click Yes.

Figure 2-92 ArcMap – Add Data Dialog Box

Figure 2-93 ArcMap – Add Feature Classes Dialog Box

August 2012 2-91


4. On the toolbar, from the Network Analyst drop-down list, select New Route.

5. From the toolbar, select the Create Network Location Tool icon.

The route information appears on the Display tab.

6. Click on the beginning and ending points of the route.

Figure 2-94 ArcMap – Network Analyst New Route

Figure 2-95 ArcMap – Network Location Tool

2-92 August 2012


7. From the toolbar, click the Solve Route icon.

8. From the toolbar, select the Directions Window icon to verify drive directions.

Figure 2-96 ArcMap – Solve Route

Figure 2-97 ArcMap – Directions Window

August 2012 2-93


Configuring the Network Dataset Parameters

When you install the PremierOne Data Import Tools, a configuration file called NetworkDatasetParams.xml is copied to the target installation folder. This file contains values that are used in the Create PremierOne Network Dataset tool. However, you must customize the file according to the schema of your Street Centerline source feature class before the tool can use it. You can use any text editing application, such as Notepad, to edit the XML file. If you would like an introduction to XML syntax, review the information found here: http://www.w3schools.com/xml/default.asp.

NetworkDataset Element

The NetworkDataset element contains an attribute called Name. The Name attribute is the name of the Network Dataset. The preference is to call it MOT_NET, as this name is used as a default network dataset name in the PremierOne server and Mobile client configurations tools.

<NetworkDataset Name=”MOT_NET” SupportsTurns=”True” spatRefType=”G” spatRefCode=”4326” />

The values for the spatRefType and spatRefCode attributes do not need to be changed as long as the Routing feature Dataset is using a WGS 1984 spatial reference.

EdgeSource Element

The EdgeSource element contains parameters or attributes specifying the street name parts and segment connectivity (elevation) fields of the input street centerline feature class.

1. Specify the FeatureClassName.

This is the name of the street centerline feature class that you have already created/imported in the Routing feature dataset.

2. Define the FromElevationFieldName and ToElevationFieldName parameters.

In data brought over from MGU or ATM, these fields were typically called F_ZLEV and T_ZLEV respectively. Unfortunately, these fields were frequently defined in MGU using the “double” data type. This caused the PremierOne Create PremierOne Network Dataset to fail, as these fields had to be an “integer” data type. To solve the problem, create two new integer fields in the source feature class and copy the values from the original fields to the new fields.

If the source feature class does not contain elevation fields, set the two parameters to an empty value (“ ”).

3. Configure the parameters that specify the input field names containing the street name parts.

http://www.w3schools.com/xml/default.asp

http://www.w3schools.com/xml/default.asp

2-94 August 2012


If the street name is concatenated, set the StreetNameFieldName parameter to that field’s name, and the prefix and suffix parameters to empty strings. Otherwise, set the parameters based on the available fields in the source street centerline feature class.

Cost Element and CostAttributes

The Cost element is used to describe the relative effort to traverse a network edge (street segment). This attributes for this element are typically defined in units of time or distance. For Drive Directions to display properly in PremierOne, there needs to be at least one attribute based on distance, and at least one attribute based on time.

The Cost element and its related attributes looks like this:

<Cost Name=”Cost” Units=”esriNAUMinutes” DataType=”esriNADTDouble” UseByDefault=”true”>

<SourceValue FeatureClassName=”Street” Direction=”From-To” ExpressionType=”Field” Value=”FT_COST” Expression=”” />

<SourceValue FeatureClassName=”Street” Direction=”To-From” ExpressionType=”Field” Value=”TF_COST” Expression=”” />

<DefaultEvaluator ElementType=”esriNETEdge” ExpressionType=”Constant” Value=”0” Expression=”” />

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

<DefaultEvaluator ElementType=”esriNETTurn” ExpressionType=”Constant” Value=”0” Expression=”” />

</Cost>

The Name attribute specifies the name of the newly created Cost element. A list of all Cost elements is displayed in the Cost drop-down list box of the Mapping > Route Solving page of the Provisioning console.

The Units attribute specifies the unit of measure represented by values in the source feature class’s cost field(s). For example, if the source feature class is being brought over from MGU and contains fields called FT_COST and TF_COST, the values in those two fields were probably calculated in minutes. The following is a list of valid values for the Units attribute:

esriNAUUnknown

esriNAUInches

esriNAUFeet

esriNAUYards

esriNAUMiles

August 2012 2-95


esriNAUNauticalMiles

esriNAUMillimeters

esriNAUCentimeters

esriNAUMeters

esriNAUKilometers

esriNAUDedimalDegrees

esriNAUDecimeters

esriNAUSeconds

esriNAUMinutes

esriNAUHours

esriNAUDays

Within the Cost element are two child SourceValue elements. One of the SourceValue elements represents travel between the street segment’s From and To nodes (Direction=”From-To”), and the other SourceValue element represents travel between the street segment’s To and From nodes (Direction=”To-From”). In both elements, you need to specify the FeatureClassName. This is the name of the street centerline feature class that you have already created/imported in the Routing feature dataset. Each SourceValue element also contains a Value attribute which is the name of the field in the street centerline feature class containing the respective cost value, such as FT_COST or TF_COST using the MGU example.

The NetworkDatasetParams.xml file also includes an example of creating a cost that adds a turn penalty if the angle of turn exceeds some minimum value.

Restriction Element and Restriction Attributes

The Restriction element determines if a network edge (street segment) is traversable in a specific direction. Restrictions can be set based on clearance, weight, or one-way travel requirements. The Restriction element looks like the following:

2-96 August 2012


<Restriction Name=”OneWay” UseByDefault=”false”>

<SourceValue FeatureClassName=”Street” Direction=”From-To” ExpressionType=”Field” Value=”restricted” Expression=”False”; Select Case UCase{[One_way]}; Case= ”NT”, ”TF”: restricted=True; End Select” />

<SourceValue FeatureClassName=”Street” Direction=”To-From” ExpressionType=”Field” Value=”restricted” Expression=”False”; Select Case UCase{[One_way]}; Case ”NT”, ”FT”: restricted=True; End Select” />

<DefaultEvaluator ElementType=”esriNETEdge” ExpressionType=”Constant” Value=”0” Expression=”” />

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

<DefaultEvaluator ElementType=”esriNETTurn” ExpressionType=”Constant” Value=”0” Expression=”” />

</Restriction>

If you were using data brought over from MGU, the street centerline might contain a field called ONE_WAY containing a value that only allowed travel between the segment’s From and To nodes (FT), To and From nodes (TF), or restricted travel in either direction - no travel (NT). Any other value, including blanks, would permit travel in both directions.

To use the same field in a PremierOne Network Dataset, do the following:

1. Set the Name attribute of the Restriction element.

A list of all defined Restriction attributes is displayed in the Default Restrictions field of the Mapping > Route Solving page in the Provisioning console.

2. In each SourceValue element, specify the FeatureClassName attribute value.

The first SourceValue element represents travel between the street segment’s From and To nodes (Direction=”From-To”). The second SourceValue element represents travel between the street segment’s From and To nodes (Direction=”To-From”).

The FeatureClassName attribute is the name of the street centerline feature class that you have already created/imported in the Routing feature dataset.

3. In each SourceValue element, determine the Value attribute value.

The value of the Value attribute is a variable, in this case “restricted”, which is defined in the Expression attribute. Following is the Expression value for the Direction=”From-To” SourceValue element:

restricted = False;Select Case UCase{[One_way]};

Case “NT”, “TF”: restricted = True;End Select

August 2012 2-97


This code block initializes the Value variable to false. The code block then checks whether the value of the One_way field in the source street centerline record contains the value of NT (no travel) or TF (to-from). If either is true, then restricted = true and you will not be able to create a route using this segment.

The Expression value for the Direction=”To-From” SourceValue element is similar, except the value of FT restricts travel in that direction.

If the field containing the “one way” values is not called One_way, or if the set of expected values is different from NT, FT, and TF, you must reflect this in the Select Case statements of both SourceValue elements.

The VBScript looks different in the context of the XML file because the quote characters cannot be embedded inside an XML value and are therefore replaced by ".

Directions Element

The Directions element specifies the PremierOne system-wide configuration for driving directions. The DisplayLengthUnits attribute specifies the unit of distance measure to be used in drive directions. For example, if the attribute is set to esriNAUMiles, you will see instructions similar to Drive 1.25 miles. The TimeAttributeName attribute should be set to one of the time-based cost attributes defined in the Cost element. The Distance attribute should be set to one of the distance-based cost attributes defined in the Cost element.

Example of an Edited NetworkParams.xml File

This section includes an example of an edited NetworkParams.xml file with these assumptions:

The data has ZLEV attributes as follows:

The street centerline is named STREET_NET.

If the street name is not parsed, leave the parsed fields with empty strings (” ”).

F_ZLEV2 and T_ZLEV2 are ZLEV attributes.

The speed field is named POSTED_SPE.

The network creation is going to be done on a file database, not the SDE geodatabase. The file database will retain the name of SHAPE_LENGTH; the SDE geodatabase will rename this field to SHAPE_LEN.

The one way attributes are in a field called TRAFFIC_AL with values of + and -.

The extra Cost field was deleted.

There is no need for an FT_COST and TF_COST; the one COST field can be used for both.

The additional Restricted sections have been removed.

2-98 August 2012


Edited xml file:

<?xml version=”1.0” encoding=”utf-8” ?>

<ROUTING>

<NetworkDataset Name=”MOT_NET” SupportsTurns=”True” spatRefType=”G” spatRefCode=”4326”/>

<EdgeSource FeatureClassName=”STREET_NET” FromElevationFieldName=”F_ZLEV2” ToElevationFieldName = ”T_ZLEV2” StreetNameFieldName=”Street_Nam” PrefixDirectionFieldName=”Prefix_DIR” PrefixTypeFieldName=”” SuffixTypeFieldName=”Street_Suf” SuffixDirectionFieldName=”Suffix_DIR”/>

<CostAttributes>

<Cost Name=”Cost” Units=”esriNAUMinutes” DataType=”esriNADTDouble” UseByDefault=”true”>

<SourceValue FeatureClassName=”STREET_NET” Direction=”From-To” ExpressionType=”Field” Value=”COST” Expression=””/>

<SourceValue FeatureClassName=”STREET_NET” Direction=”To-From” ExpressionType=”Field” Value=”COST” Expression=””/>

<DefaultEvaluator ElementType=”esriNETEdge” ExpressionType=”Constant” Value=”0” Expression=””/>

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

<DefaultEvaluator ElementType=”esriNETTurn” ExpressionType=”Constant” Value=”0” Expression=””/>

</Cost>

<Cost Name=”Distance” Units=”esriNAUDecimalDegrees” DataType=”esriNADTDouble” UseByDefault=”false”>

<SourceValue FeatureClassName=”STREET_NET”Direction=”From-To” ExpressionType=”Field” Value=”Shape_length” Expression=””/>

<SourceValue FeatureClassName=”STREET_NET” Direction=”To-From” ExpressionType=”Field” Value=”Shape_length” Expression=””/>



August 2012 2-99



</Cost>

</CostAttributes>

<RestrictionAttributes>

<Restriction Name=”one_way” UseByDefault=”false”>

<SourceValue FeatureClassName=”STREET_NET” Direction=”From-To” ExpressionType=”Field” Value=”restricted” Expression=”restricted = False;Select Case UCase([TRAFFIC_AL]);Case "-": restricted = True;End Select”/>

<SourceValue FeatureClassName=”STREET_NET” Direction=”To-From” ExpressionType=”Field” Value=”restricted” Expression=”restricted = False;Select Case UCase([TRAFFIC_AL]);Case "+": restricted = True;End Select”/>




</Restriction>

</RestrictionAttributes>

<Directions DisplayLengthUnits=”esriNAUMiles” TimeAttributeName=”Cost” LengthAttributeName=”Distance”/>

<ROUTING>

Testing the XML File

After you have saved the XML file, you need to test it to make sure you have not introduced any syntax errors.

To test the XML file:

1. Double-click the file in Windows Explorer to open the document in Internet Explorer.

If Internet Explorer displays an error message, your XML file is not well-formed.

2. Determine what is wrong and fix the error.

2-100 August 2012

Building a Statewide Network Dataset Chapter 2: Importing GIS Data For Use Within PremierOne

3. Test the file with the Create PremierOne Network Dataset tool by looking for Success/Error messages.

Ensure the target geodatabase does not have a network dataset and junctions feature class in the ROUTING feature dataset. If it does, delete the network dataset.

4. Look for Success/Error messages.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Building a Statewide Network Dataset

If you have a large network, such as a statewide network, use the network wizard to build the network dataset. Because statewide networks are so large, you separate the street files into multiple sets, such as: STREET_NET1, STREET_NET2, STREET_NET3, STREET_NET4, STREET_NET5, and so on. You then import the street files into the Routing Feature dataset using the Import Feature Class tool.

To build a statewide network dataset:

1. Right-click on the feature dataset, and then select New > Network Dataset.

2. In the Name field, type MOT_NET for the name of the network dataset.

3. Click Next.

The first page of the New Network Dataset wizard appears, showing the street layer feature classes that will partipate in the network.

Figure 2-98 First Page of the New Network Dataset Wizard

August 2012 2-101

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Building a Statewide Network Dataset

4. Click Select All, and then click Next.

The Connectivity Page of the New Network Dataset wizard appears.

5. Click Next.

The Elevation Field Data page of the New Network Dataset wizard appears.

6. If you have valid F_ZLEV and T_ZLEV data, select Yes to modify the connectivity with elevation field data. Otherwise, select No.

Figure 2-99 New Network Dataset Wizard – Connectivity Page

Figure 2-100 New Network Dataset Wizard – Elevation Field Data Page

2-102 August 2012


7. Click Next.

The Model Turns page of the New Network Dataset wizard appears.

8. If you plan to model turns, click Yes, and then click Next.

The Attributes page of the New Network Dataset wizard appears.

9. In the Units column, select Minutes for the Cost attribute.

Figure 2-101 New Network Dataset Wizard – Model Turns Field Data Page

Figure 2-102 New Network Dataset Wizard – Attributes Field Data Page

August 2012 2-103


10. Add a new attribute for distance cost.

a. Click Add.

The Add New Attribute dialog box appears.

b. In the Name field, type Distance.

c. In the Usage Type field, type Cost.

d. In the Units field, type Decimal Degrees.

e. Click OK.

The Attributes page of the New Network Dataset wizard reappears, showing the new Distance attribute.

11. Click Evaluators.

Figure 2-103 Add New Attribute Dialog Box

Figure 2-104 New Network Dataset Wizard – Attributes Field Data Page Showing Distance Attribute

2-104 August 2012



12. For each Source (street layer) and Direction:

a. Change the Type to Field.

b. Change the Value to Shape_Length.

13. Click OK.

The Driving Directions page of the New Network Dataset wizard appears.

Figure 2-105 Evaluators Dialog Box

Figure 2-106 New Network Dataset Wizard – Driving Directions Page

August 2012 2-105


14. Select Yes to establish driving directions settings.

15. If the data has the street name parsed, click Directions. Populate the correct fields for the street names, and then click OK.

16. Click Next.

The Summary page of the New Network Dataset wizard appears.

17. Click Finish.

A message appears asking if you want to build the new network dataset.

Click Yes.

18. If errors are detected, a message appears indicating that the network was built, but with errors.

Figure 2-107 New Network Dataset Wizard – Summary Page

Figure 2-108

2-106 August 2012


19. If you want to show the error log, click Show Build Errors; otherwise, click Close.

Calculating the Time Cost for Route Solving

The PremierOne Network routing feature dataset requires at the very minimum a distance and time cost. If multiple street files are used. as in a large statewide deployment, the ArcCatalog wizard must be used to calculate a Distance cost.

NOTEThe speed calculations must be done on a shape file or geodatabase that is in a projected format.

Figure 2-109 Sample Build Errors Report

August 2012 2-107


To calculate the time cost:

1. In ArcMap, create a Cost field.

From the Attribute table, select Options > Add field.

2. In the Name field, type COST.

3. From the Type list, select Double.

4. Click OK.

If the data does not contain speed attributes, you can create speed attributes based on a class type field; for example, assign a speed of 30 for local roads, 45 for major roads, and 65 for highways. There can be no null or 0 values in the speed attribute field; populate any null or zeros with 1. After you have these attributes created, you can continue to populate the Cost field.

Figure 2-110 Add Field Dialog Box

2-108 August 2012


To populate the cost field:

1. Right-click the new COST field, and then select Field Calculator.

The Field Calculator dialog box appears.

2. In the COST = box, enter the statement or click Load to access a saved statement.

Ensure that the shape length and speed values match the attribute names.

3. Click OK to run the script.

If the customer is creating ZLEV attributes, the fields must be either short or long integer types.

Figure 2-111 Field Calculator Dialog Box

August 2012 2-109

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Using the PremierOne Migration Tools

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the PremierOne Migration Tools

The PremierOne Migration tools are primarily meant for Motorola system integrators to use to import PREMIER CAD common place and street aliases into PremierOne. A short description is included here for informational purposes.

To use the PremierOne Migration tools:

1. Access the Migration Tools:

a. From the ArcToolbox, right-click PremierOneImportTools.

b. From the menu that appears, select Add, and then select Tool.

Figure 2-112 Adding New Tools to a Toolbox

2-110 August 2012

Using the PremierOne Migration Tools Chapter 2: Importing GIS Data For Use Within PremierOne

The Add Tool dialog box appears.

c. Select PremierOne Migration Tools, and then click OK.

2. To migrate common place aliases:

Figure 2-113 Adding Migration Tools

August 2012 2-111

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Using the PremierOne Migration Tools

a. Double-click the database containing the common places.

The PremierCAD Common Place Alias Migration dialog box opens with the URL to that database in the PremierOne Workspace field.

b. In the PCAD Common Place Alias File field, point to the file containing the PREMIER CAD common place aliases.

c. In the Common Place Alias Table field, point to the CommonPlaceAliases created in “Creating the PremierOne Support Geodatabase” on page 2-27.

d. Click OK.

Figure 2-114 PremierCAD Common Place Alias Migration Dialog Box

2-112 August 2012

Using the PremierOne Migration Tools Chapter 2: Importing GIS Data For Use Within PremierOne

3. To migrate street aliases:

a. Double-click the database containing the street.

The PremierCAD Street Alias Migration dialog box opens with the URL to that database in the PremierOne Workspace field.

b. In the PCAD Street Alias File field, point to the file containing the PREMIER CAD street aliases.

c. In the Street Alias Table field, point to the StreetNameAliases created in “Creating the PremierOne Support Geodatabase” on page 2-27.

d. Click OK.

Figure 2-115 Premier CAD Street Alias Migration

August 2012 2-113

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Maintaining a Standardization Exceptions Table (optional)

Maintaining a Standardization

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Exceptions Table (optional)

PremierOne creates the Standardization Exceptions table when it creates the Support geodatabase. (See “Creating the PremierOne Support Geodatabase” on page 2-27.)

NOTECreate alias and street standardization tables in their own file databases , not in the PremierOne staging geodatabase.

PremierOne parses the direction of the street name using an internal algorithm. Use the Standardization Exceptions table to model exceptions for anomalies where the name of the street includes a directional item, such as North St., South Ave, East Blvd., or West Pkwy. The street name parser identifies these directional items as a direction and not part of the name unless they are specifically identified as part of the name using the Standardization Exceptions table.

NOTEAlthough this table is optional, if your jurisdiction has street names that include a directional item, then you should build this table after creating your PremierOne geodatabase. The table should be created prior to importing any of the feature data sets so you do not have to redo the import.

2-114 August 2012

Maintaining a Standardization Exceptions Table (optional) Chapter 2: Importing GIS Data For Use Within PremierOne

Following is an example of a table created for handling exceptions. The required column names and lengths for this table are shown after the table.

The following items were used to create the table columns in ArcMap for Figure 2-116.

Contact your GIS database administrator if you have questions or issues with this section.

Figure 2-116 Street Standardizer Table

FULL_STREET Char 100

PRE_DIR Char 4

PRE_TYPE Char 8

STREET_NAME Char 76

SUF_TYPE Char 8

SUF_DIR Char 4

August 2012 2-115

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Map Layers Datasets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Map Layers Datasets

ArcMap documents (*.mxd files) will be created after building a map layers dataset. Information about the creation and building of an *.mxd file can be found in your ESRI application documentation. Contact your GIS database administrator for further information, if needed.

The map layers dataset is the map used by each of the PremierOne clients to provide a visual display of the CAD data. This data is stored on the server for PremierOne CAD clients, but requires a copy placed on each of the PremierOne Mobile clients to reduce wireless bandwidth use.

For the PremierOne mobile clients, data is stored in a file-based system instead of using the SDE data source, to simplify system access. This file-based system is an exact replica of the SDE geodatase. Two mobile file geodatabases and two accompanying *.mxd documents (A and B) are required. This allows the deployment of a new version of the geodatabase while the client is still using the old version.

The mobile database can be put in any location as long as it is in the same place for all of the mobiles in order to use the Deployment utilities. Motorola recommends that the mobile database be placed in the MapData folder along with the *.mxd documents. The Deployment tool looks in the MapData folder for the mobile database.

If aerial images are used, store them locally outside of the geodatabase.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Map Properties for .mxd Documents

The map data can be stored in any projection system. However, for optimal CAD performance, Motorola recommends the map data be stored in WGS84. All map data imported into the Map Layers feature dataset will be in WGS84. The .mxd map document should also be in WGS84.

2-116 August 2012

Map Properties for .mxd Documents Chapter 2: Importing GIS Data For Use Within PremierOne

To set the map properties:

1. From ArcMap, right-click on Properties.

The Data Frame Properties dialog box appears.

Figure 2-117 ArcMap – Right-Click Properties

Figure 2-118 Data Frame Properties Dialog Box

August 2012 2-117

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Creating Map Layer Datasets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Map Layer Datasets

The PremierOne mapping client uses ArcMap documents (*.mxd files). ArcMap documents can contain layers. The underlying data for the layers can come from several sources: enterprise geodatabases, local geodatabases, local shapefiles, ArcGIS Online, and so on. The only caveat is that each user of a particular map document must have access to that data. Therefore, if a map is authored using data from an enterprise (SDE) data source, the user opening the map document must have access to the database server. If a map is authored using a File Geodatabase, that File Geodatabase must be deployed along with the map document to the target users.

When using non-enterprise data and data not accessed by a URL, it is strongly recommended that you save ArcMap documents using relative file paths. This allows the map document and local map data to be deployed to a drive/path that is different from that of the ArcMap computer. When you use relative file paths, create a folder called mapdata. This is the folder in which you should save the *.mxd file(s). Create another folder called Data under the mapdata folder. Within the Data folder, copy any shapefiles, File Geodatabase, or file-based geodatabase folders that will be referenced by the map document.

Figure 2-119 Establishing the Map Layer Dataset Folder Structure

2-118 August 2012

Creating Map Layer Datasets Chapter 2: Importing GIS Data For Use Within PremierOne

This folder structure matches the structure created by the PremierOne Mobile client installation. The map document will be deployed to the mapdata folder, and the local data will be deployed to the mapdata\Data folder.

NOTEMotorola recommends that you store map data in the same geodatabase as the PremierOne GIS services data. For maps that use data stored in an enterprise PremierOne geodatabase, this means you will need to maintain two sets of map documents – one for each geodatabase connection (the database connection that is currently active, and the connection that is being staged for future activation). In the PremierOne geodatabase template, there is a Feature Dataset called Map_Layers. Motorola suggests that all of the data imported for display in a map document be stored in this Feature Dataset for simplicity’s sake. The Map_Layers feature dataset is defined using the WGS 1984 Spatial Reference. If you would like to define a different spatial reference, delete the Map_Layers feature dataset and add a new one using the desired spatial reference (simply modifying the spatial reference of an existing feature dataset may cause domain and precision issues, so recreating the feature dataset is recommended). Additionally, the map documents which utilize the map data can be defined using any spatial reference. Motorola strongly recommends storing both the data and the map document in WGS84. (For more information about WGS84, see “Map Properties for .mxd Documents” on page 2-115.)

There are several ways to copy data from one location to another. Motorola recommends using either the Copy/Paste or Import/Export method. These methods are described in the following paragraphs.

To use the Copy/Paste method:

1. ArcCatalog provides a user experience similar to that of Windows Explorer for copying GIS data from one location to another. In ArcCatalog, navigate to the location of the data to be copied. Right-click the Feature Dataset or Feature Class and select Copy. Navigate to the location of the target geodatabase, right-click the target location and select Paste.

2. If you choose Feature Dataset for copying, the Feature Dataset and all of the Feature Classes under it will be copied.

NOTENOTEWhen using the Copy/Paste method, the source and target spatial references must be the same. You may not copy feature classes across feature datasets with different spatial references. If this is necessary, use the Import method instead.

To use the Import method:

Using the Import method is similar to the Copy/Paste method, except Import supports on-the-fly spatial reference projections and allows you to select multiple items from multiple sources.

August 2012 2-119


1. In ArcCatalog, right-click the destination geodatabase, Map_Layers feature dataset and select Import, and then select Feature Class (single) to import one feature class, or Feature Class (multiple) to import many feature classes.

Figure 2-120 Using the Import > Feature Class (Multiple) Method

2-120 August 2012


2. Figure 2-121 shows the results of selecting the Import Feature Class (multiple)… method and the resulting dialog box. Note that the Output geodatabase field value should be automatically filled in based on the geodatabase connection from which you initiated the action. Select the source feature class(es) using the Folder button next to the Input Features field. Alternatively, you can drag and drop a feature class from the ArcCatalog window onto the Input Features field.


Figure 2-121 Feature Class to Geodatabase (multiple) Import Dialog Box

August 2012 2-121


The Feature Class to Geodatabase Processing dialog box shows the progress as each item is being processed.

NOTENOTEIf there were errors during the processing, an error log will be written to the Feature Class to Geodatabase log file. The path to the file will be shown in the Processing dialog box. Work with your GIS system administrator to resolve the errors.

You are now finished creating your map layer dataset. You can now use ArcMap to author map documents using the imported data.

Figure 2-122 Feature Class to Geodatabase (multiple) Process Dialog Box

2-122 August 2012


Access ArcMap to configure the symbology and zoom levels for each of the map layers. Below is an example of a configured map window.

NOTEBe sure to set the Data Source Options default in ArcMap to store relative names to data source.

Figure 2-123 Configured Map Window Example

August 2012 2-123


To set the Data Source Options default:

1. From the Properties dialog box, click Data Source Options.

Figure 2-124 Map Properties Dialog Box

2-124 August 2012

Creating Symbology for the Map Layers Dataset Documents Chapter 2: Importing GIS Data For Use Within PremierOne

The Data Source Options dialog box appears.

2. Select Store relative path names to data sources.

3. Click OK.

Creating Symbology for the Map Layers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dataset Documents

Use standard ESRI database map layers dataset techniques to create the symbology for the map layers datasets.

PREREQUISITEBefore you create the symbology for the map layers dataset, you must complete the following prerequisite.


Figure 2-125 Data Source Options Dialog Box

August 2012 2-125

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Incorporating Raster Images into the Map Layers Dataset Display

To create symbology for PremierOne using the map layers dataset *.mxd documents, you follow standard ESRI procedures and processes. The steps used for this are typical ESRI GIS database administration activities and are not described here, although they are required for operational use of the PremierOne geodatabase.

NOTERefer to your ESRI documentation or ESRI online help for additional information.

Incorporating Raster Images into the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Map Layers Dataset Display

Raster data, such as aerial photos, can be used on the CAD and Mobile maps as long as you give consideration to size and bandwidth limitations. It is recommended that a raster file geodatabase be used to store the raster images because they do not get updated regularly. The raster images should be added to the .mxd document.

Use the left window pane in the ArcEditor to incorporate raster images into the map layers dataset.

PREREQUISITESBefore you incorporate raster images into the map layer dataset, you must complete the following prerequisites.


u Create the symbology for your map layers dataset. For more information, see “Creating Symbology for the Map Layers Dataset Documents” on page 2-124.

You or the GIS system administrator may want to consider creating the Raster Feature dataset outside of the File Geodatabase for the Mobile Map clients. Given the potential size of the Raster Feature Dataset this will enable the you or the GIS administrator to update the File geodatabase without copying over the Raster Feature dataset for every maintenance update.

2-126 August 2012

Incorporating Raster Images into the Map Layers Dataset Display Chapter 2: Importing GIS Data For Use Within PremierOne

To incorporate raster images into the map layer dataset:

1. From the navigation area on the left, right-click the geodatabase to which you want to add the image. Make sure you are outside of the CAD/Mobile geodatabase.

2. From the menu that appears, select New, and then select Raster Dataset.

Figure 2-126 Creating a Raster Dataset Outside of the CAD/Mobile Geodatabase

August 2012 2-127


The Create Raster Dataset dialog box appears. Required fields are identified by a green dot next to the field name.

3. Drag the appropriate geodatabase from the ArcCatalog and drop it onto the OutputLocation field in the Create Raster Dataset dialog box.

4. In the Raster Dataset Name with Extension field, type the name of the raster dataset, including the extension.

5. Click the folder to the right of the Spatial Reference for Raster (Optional) field.

Figure 2-127 Create Raster Dataset Dialog Box

2-128 August 2012


The Spatial Reference Properties dialog box appears.

6. Click Import on the XY Coordinate System tab.

The Browse for Dataset dialog box appears.

7. Select the CAD data needed for this process, and then click Add.

Figure 2-128 Spatial Reference Properties Dialog Box

Figure 2-129 Browse for Dataset Dialog Box

August 2012 2-129


8. From the left navigation area of the ArcCatalog, view the *.tif file to verify the number of bands.

Figure 2-130 Viewing the Number of Bands for the *.TIF Raster Image

2-130 August 2012


9. On the Create Raster Dataset dialog box, in the Number of Bands field, edit the number of bands based on the number of bands you discovered in step 8.

10. Click OK to create the Raster Dataset.

The Create Raster Dataset Processing dialog box shows the progress as each item is being processed.

Figure 2-131 Editing the Number of Bands for the *.TIF Raster Image

Figure 2-132 Create Raster Dataset Processing Dialog Box

August 2012 2-131



12. Load the raster data. From the left navigation area of the ArcCatalog, right-click the Raster Data object that you created.

13. From the menu that appears, select Load, and then select Load Data.

14. Drag and drop the raster images that were created into the Input Rasters field.

Figure 2-133 Loading Raster Data

2-132 August 2012


The Mosaic dialog box appears.

Figure 2-134 Mosaic Dialog Box

August 2012 2-133

PremierOne PremierOne™ GIS Setup for CAD and Mobile User Guide Road Closures

15. Drag and drop the raster images that you created into the Input Rasters field.

16. Click OK to load the raster data.

17. Launch ArcMap to add the raster dataset to your *.mxd document and set the zoom level(s) appropriately.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Road Closures

NOTEFor mobile road closures, you must have two mobile file-based databases (A and B) with two accompanying .mxd documents. The .mxd documents must have the geocoding/street_centerline line that points to the local file-based database for road closure capabilities.

PREREQUISITE:Add the Street_Centerline from the Geocoding feature dataset in the SDE reader geodatabase. This layer should be invisible and at the bottom of the layers z order. By default the name in the Configuration Tool is STREET_CENTERLINE. Rename the CUSTOMER_B.DBO.STREET_CENTERLINE to STREET_CENTERLINE because the name must match the CAD configured name. This street centerline is required to get

Figure 2-135 Mosaic Dialog Box With Raster Images Identified

2-134 August 2012

Provisioning Chapter 2: Importing GIS Data For Use Within PremierOne

names to appear on the map so the user can select streets to close.

To enable road closures in CAD:

See “Showing Road Closures on a Map” in the PremierOne CAD User Guide.

ARL unit recommendations take the closed road segments into account.

Any user can re-open the road segments.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Provisioning

There is a specific order that the provisioning must take place. When updating the database:

1. Activate the database that is not being updated and save.

2. Put the database you want to update in restricted mode and save.

When switching the databases:

1. Put all databases in multi-user mode and save. The database must be in multi-user mode when the .mxd data source is updated.

2. Activate the newly updated database for each agency saving between each activation.

NOTEFor multi-agency sites, login using the Admin Agency. Each agency must be selected and activated one at a time.

August 2012 3-1

CHAPTER

3

. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating SQL Users 3

NOTEThis section will be completed by a Motorola engineer along with the custom SQL manager.

You must have two SQL users, a GIS_ADMIN and a GIS_READER. The GIS_ADMIN creates all feature classes, datasets, and attribute tables. The GIS_READER configures services to gain access to the geodatabase.

Example:When it is time to update Geodatabase A, access is restricted an all existing connections are terminated. Putting the geodatabase in a restricted user mode only allows the GIS_ADMIN to gain access. Once modifications are completed, the geodatabase is reverted back to a multi-user mode which allows GIS_READER to gain access again.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SQL Accounts

The GIS_ADMIN account includes:

Server Role: sys_admin, public

Default database: Master

Database Role: db_ddladmin

Default Schema: GIS_ADMIN

The GIS_READER account includes:

Server Role: public

Database Role: db_datareader

Default Schema: GIS_READER

3-2 August 2012

SQL Accounts Chapter 3: Creating SQL Users

August 2012 4-1

CHAPTER

4Backing Up Your PremierOne

. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .GIS Data 4

Motorola suggests that you back up your PremierOne File Geodatabase according to your regular GIS backup procedures. As a part of the standard PremierOne system administrator backup procedures used to backup all SQL databases, one of the items that this process backs up is the PremierOne SDE. In addition to this activity, you should back up any File Geodatabase files, feature sets, or datasets that were created to alternate media on a periodic basis.

4-2 August 2012

Chapter 4: Backing Up Your PremierOne GIS Data

INDEX

August 2012 IX-1

. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Index

A

alias data, importing . . . . . . . . . . . . . . . . . . . . . . . 2-43ARCcatalog, setting up GIS reader . . . . . . . . . . . . . . 3-1ARCtoolbox, adding the data import tools . . . . . . . . . 2-3

B

backing up, PremierOne GIS data . . . . . . . . . . . . . . . 4-1

C

cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4centerline data, importing . . . . . . . . . . . . . . . . . . . 2-49configuration

network dataset . . . . . . . . . . . . . . . . . . . . . . . 2-79contacting technical support . . . . . . . . . . . . . . . . . . . 1-4conventions

cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4used in this guide . . . . . . . . . . . . . . . . . . . . . . . 1-2

D

dataimporting address point data . . . . . . . . . . . . . . 2-55importing common place data. . . . . . . . . . . . . . 2-39importing GIS data. . . . . . . . . . . . . . . . . . . . . . 2-1

data view, definition . . . . . . . . . . . . . . . . . . . . . . . . 1-4database, backing up. . . . . . . . . . . . . . . . . . . . . . . . 4-1definitions, GIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

F

featureclass, definition . . . . . . . . . . . . . . . . . . . . . . . . 1-4dataset, definition. . . . . . . . . . . . . . . . . . . . . . . 1-5definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4name, definition. . . . . . . . . . . . . . . . . . . . . . . . 1-5

featuresimporting district features . . . . . . . . . . . . . . . . 2-62

importing response boundary features . . . . . . . . . 2-59

G

Geodatabasecreating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

GISdata, backing up . . . . . . . . . . . . . . . . . . . . . . . 4-1definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4importing data . . . . . . . . . . . . . . . . . . . . . . . . 2-1network dataset . . . . . . . . . . . . . . . . . . . . . . . . 2-76setting up GIS reader in ARCcatalog . . . . . . . . . . 3-1shapefile, definition . . . . . . . . . . . . . . . . . . . . . 1-5

I

import tools, installing the PremierOne data . . . . . . . . 2-1importing, map book features. . . . . . . . . . . . . . . . . . 2-65

K

keyboard convention descriptions . . . . . . . . . . . . . . . 1-3

L

layers, definition . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4layout view, definition . . . . . . . . . . . . . . . . . . . . . . 1-5

M

maplayer datasets, creating . . . . . . . . . . . . . . . . . . 2-117layers datasets. . . . . . . . . . . . . . . . . . . 2-114, 2-115

map book features, importing. . . . . . . . . . . . . . . . . . 2-65map layers, incorporating raster images . . . . . . . . . . 2-125model, creating a model to import all data . . . . . . . . . 2-71mxd document, adding the premise hazard database connec-

tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1, 4-1

Index

IX-2 August 2012

N

network dataset, creating using the import tool . . . . . 2-77notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

P

PremierOnegeodatabase, creating . . . . . . . . . . . . . . . . . . . . 2-8

premise hazardcreating and connecting to . . . . . . . . . . . . . . . 2-115database, adding connections to .mxd documents . . 3-1,

4-1database, creating and connecting for CAD. . . . . 2-19database, creating and connecting for mobile. . . . 2-22

production and staging databases . . . . . . . . . . . . . . . 2-6

R

related documents . . . . . . . . . . . . . . . . . . . . . . . . . 1-2reporting district features, importing . . . . . . . . . . . . 2-62response boundary features, importing . . . . . . . . . . . 2-59

S

shapefile, definition . . . . . . . . . . . . . . . . . . . . . . . . 1-5SQL

accounts listing . . . . . . . . . . . . . . . . . . . . . . . . 3-1users, creating . . . . . . . . . . . . . . . . . . . . . . 3-1, 4-1

standardization exceptions table (optional), creating . 2-113street

alias data, importing . . . . . . . . . . . . . . . . . . . . 2-43centerline data, importing . . . . . . . . . . . . . . . . 2-49

symbology for the map layers dataset documents, creating . . 2-124

T

typographic conventions . . . . . . . . . . . . . . . . . . . . . 1-3

W

what is in this book . . . . . . . . . . . . . . . . . . . . . . . . 1-2