IMAGINE Enterprise Editor

Users Guide December 2010

Copyright 2010 ERDAS, Inc.

All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ERDAS, Inc. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ERDAS, Inc. All requests should be sent to the attention of: Manager, Technical Documentation ERDAS, Inc. 5051 Peachtree Corners Circle Suite 100 Norcross, GA 30092-2500 USA. The information contained in this document is subject to change without notice. Government Reserved Rights. MrSID technology incorporated in the Software was developed in part through a project at the Los Alamos National Laboratory, funded by the U.S. Government, managed under contract by the University of California (University), and is under exclusive commercial license to LizardTech, Inc. It is used under license from LizardTech. MrSID is protected by U.S. Patent No. 5,710,835. Foreign patents pending. The U.S. Government and the University have reserved rights in MrSID technology, including without limitation: (a) The U.S. Government has a nonexclusive, nontransferable, irrevocable, paid-up license to practice or have practiced throughout the world, for or on behalf of the United States, inventions covered by U.S. Patent No. 5,710,835 and has other rights under 35 U.S.C. 200-212 and applicable implementing regulations; (b) If LizardTech's rights in the MrSID Technology terminate during the term of this Agreement, you may continue to use the Software. Any provisions of this license which could reasonably be deemed to do so would then protect the University and/or the U.S. Government; and (c) The University has no obligation to furnish any know-how, technical assistance, or technical data to users of MrSID software and makes no warranty or representation as to the validity of U.S. Patent 5,710,835 nor that the MrSID Software will not infringe any patent or other proprietary right. For further information about these provisions, contact LizardTech, 1008 Western Ave., Suite 200, Seattle, WA 98104. ERDAS, ERDAS IMAGINE, Stereo Analyst, IMAGINE Essentials, IMAGINE Advantage, IMAGINE, Professional, IMAGINE VirtualGIS, Mapcomposer, Viewfinder, and Imagizer are registered trademarks of ERDAS, Inc. Other companies and products mentioned herein are trademarks or registered trademarks of their respective owners.

Table of Contents
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About This Manual . . . . . . . . . . Example Data . . . . . . . . . . . . . . Documentation . . . . . . . . . . . . . Conventions Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii vii vii vii

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Overview of IEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Oracle Spatial Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Spatial Data Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Spatial Data Model Oracle Spatial Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Supported Geometric Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Geometries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Metadata, Tolerance, and Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Data Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Indexing Spatial Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Application Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Topological Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Topology elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Topology related tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Display Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Styling Rules in Predefined Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Metadata Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Tour Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Connecting to Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 IEE Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Table of Contents Table of Contents iii iii

Connection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Map Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Discover Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Search and Locate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 IEE Layer Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Transaction Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Understanding IEE Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Snapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Data Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Release Locks on Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Draw Handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 IEE Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 IEE Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Locking & Grid Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Snapping Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Topology and Precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Hilite and Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 IEE Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Understanding IEE Digitizing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Polygon Topo Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Segmentation Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Dangle Lock (Start) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Dangle Lock (End) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Rubber Band Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Theme Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Axis Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Grid Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Snap Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Theme Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Digitizing with IEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Place Point Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Place Line Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Place Polygon Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Place Rectangle Polygon Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Place Circular Arc Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

iv

Table of Contents

Place Topology Isolated Node Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Place Topology Edge Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Place Point Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Place Line Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Place Polygon Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Place Polygon Interact Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Saving Data to Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Exporting Spatial Data to Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Workspace Manager and Measurement Tool . . . . . . . . . . . . . . . . . . . 59

Workspace Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Select Workspace Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Create Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Remove Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Synchronize Active Workspace with Parent Workspace . . . . . . . . . . . . . . . . . . . . . 61 Roll Back Changes to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Merge Active Workspace into Parent Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Refresh Active Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Configure Workspace Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Preparing the Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Primary Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 USER_SDO_GEOM_METADATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Spatial Indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Key Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Triggers and Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Workspace-Enabled Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Measurement Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Length, Area, Perimeter Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Print to PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Starting the Printing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Creating Print Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Print Template Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 <print-component> Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 <provider> Element Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 <properties> Element Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 <subcomponents> Element Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Table of Contents

Properties Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Page Sizes Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Predefined Page Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Keyin Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

vi

Table of Contents

Preface
About This Manual
The IMAGINE Enterprise Editor (IEE) Users Guide is both a theoretical and a practical guide that will help you learn how to use IMAGINE Enterprise Editor software. The IMAGINE Enterprise Editor Guide manual serves primarily as a tutorial. It also includes a comprehensive index so that you can reference particular information while using IMAGINE Enterprise Editor for your own projects. Introduction is designed to give you an overview of the concepts and technology involved with creating and maintaining data with IEE. Tour Guides is designed to provide more detailed information about the components of IEE and how to use them. This user guide is not intended to tell you everything there is to know about any one topic, but to show you how to use some of the basic tools you will need to get started.

Example Data

Sample data sets are provided with the software. This data is separately installed from the data DVD. For the purposes of documentation, <ERDAS_Data_Home> represents the name of the directory where sample data is installed. The Tour Guides refer to specific data which are stored in <ERDAS_Data_Home>/examples.

Documentation

This manual is part of a suite of on-line documentation that you receive with ERDAS IMAGINE software. There are two basic types of documents, digital hardcopy documents which are delivered as PDF files suitable for printing or on-line viewing, and On-Line Help Documentation, delivered as HTML files. The PDF documents are found in <IMAGINE_HOME>\help\hardcopy where <IMAGINE_HOME> represents the name of the directory in which ERDAS IMAGINE is installed. Many of these documents are available from the ERDAS Start menu. The on-line help system is accessed by clicking on the Help button in a dialog or by selecting an item from a Help menu.

Conventions Used in This Book

In ERDAS IMAGINE, the names of menus, menu options, buttons, and other components of the interface are shown in bold type. For example: In the Select Layer To Add dialog, click the Fit to Frame option. When asked to use the mouse, you are directed to click, double-click, Shift-click, middle-click, right-click, hold, drag, etc. click click once with the left mouse button.

Preface Preface

vii vii

double-click click twice with the left mouse button. Shift-click hold down the Shift key on your keyboard and simultaneously click the left mouse button. middle-click click once with the middle mouse button. right-click click once with the right mouse button. hold press and hold the left (or right, as noted) mouse button. drag drag the mouse while holding the left mouse button.

The following paragraphs are used throughout the ERDAS IMAGINE documentation: These paragraphs contain strong warnings or important tips.

These paragraphs give you software version-specific information.

These paragraphs provide information about ERDAS products.

These paragraphs lead you to other areas of this book or other manuals for additional information. NOTE: Notes give additional instruction. Blue text indicates a link that will take you to related information when you click it.

Blue Box These boxes contain supplemental technical information.

viii

Preface

Introduction
Introduction
The purpose of the IMAGINE Enterprise Editor (IEE) Users Guide is to provide background information on the technology used to implement a database-centric enterprise geographic information system (GIS) and how the IEE software can be used to manipulate and maintain the data stored within the enterprise environment. Chapter 2 covers the actual functionality provided with IEE. This guide is aimed at a diverse audience: from those who are new to databases to those savvy users who have been in this industry for years. IMAGINE Enterprise Editor provides a seamless interface between ERDAS IMAGINE and Oracle Spatial geospatial data management platform. IEE enables simultaneous access to Oracle Spatial, Oracle Topology and Oracle GeoRaster formatted data within the IMAGINE Viewer.

Overview of IEE

Oracle Spatial Concepts

Spatial Data Modeling
Traditional RDBMS data model concepts apply when dealing with spatial data. Oracle supports many traditional data types, including VARCHAR2 for characters, DATE type for dates, NUMBER type for numbers, and now an SDO_GEOMETRY data type for storing the coordinates of spatial features. There is no spatial table in Oracle, just ordinary Oracle tables with one or more SDO_GEOMETRY columns. When normalized tables are created, Oracle recommends including SDO_GEOMETRY columns in tables where all the other columns in the table have a one-to-one relationship with the SDO_GEOMETRY column. Consider the following example of modeling road and river spatial features. Road information might include number of lanes, a street address range, and more. River information might include salinity, maximum depth, and more. Even though they are both linear features, since the information for roads is not relevant to rivers, and river information is not relevant to roads, it is not recommended to store their coordinates in the same SDO_GEOMETRY column of a table. A normalized data model would store the road spatial features in a Roads table, along with other columns that have a one to one relationship with the coordinates of a road. A similar normalized data model is recommended for a Rivers table.

Introduction Introduction

1 1

An additional benefit of storing roads apart from rivers becomes more apparent at query time. When you are only searching for roads, there is no need to sift through a table that contains entries for both roads and rivers. Figure 1: Spatial Data Model Comparison
Oracle Spatial All data for a layer is stored in a single table Layers are grouped together as a map Users lock only areas of data so many users can work on layers.

File / Directory Based 2 to 8 files for each layer Layers are added to individually edit environment Only one user can edit an opened layer at a time.

Spatial Data Model Oracle Spatial Example

Table 1: Road Table Example
ROAD NAME ROAD ID ROAD TYPE NUM LANES SURFACE GEOM

HWY-25 I-70 Main St CR-34

32456 32456 345621 234001

Primary Primary City County

4 4 2 1

Concrete Concrete Asphalt Dirt

sdo_geometry sdo_geometry sdo_geometry sdo_geometry

Table 2: sdo_geometry Structure

MDSYS.SDO_GEOMETRY object Name SDO_GTYPE SDO_SRID SDO_POINT NUMBER NUMBER SDO_POINT_TYPE Type Description Defines the kind of geometry Used to identify a coordinate system Optimized storage for point data

Introduction

SDO_ELEM_INFO SDO_ORDINATES

SDO_ELEM_INFO_ARRAY SDO_ORDINATE_ARRAY

Defines how to interpret the ordinate array Storage for ordinates of geometry

Supported Geometric Types

Oracle Spatial supports three multi-dimensional geometric primitive types and geometries composed of collections of these types. The three primitive types are: Points (X1, Y1) Line strings (X1, Y1, Xn, Yn) Polygons (X1, Y1,... Xn, Yn)

Geometric Primitive Types

Line string Arc line string Compound line string SelfSelf-crossing line strings

Valid n Polygon with hole Compound polygon Optimized polygons SelfSelf-crossing polygons

Not valid
Points are elements composed of between two and four ordinates, if only X and Y - often correspond to longitude and latitude. Line strings are composed of two or more pairs of points that define line segments. Self-crossing lines are supported. Lines that cross to form a ring have no implied interior. Coordinates may be stored in clockwise or counterclockwise order.

Introduction

Polygons are composed of line strings that form a closed ring, and the interior of the polygon is implied. Polygons may also contain holes that are constructed by defining inner polygons. Holes represent polygon voids (doughnuts). Self-crossing polygons are not supported although self-crossing line strings are. If a line string crosses itself, it does not become a polygon. A self-crossing line string does not have any implied interior. Polygon can be exterior polygons or interior polygons (also called holes). An exterior polygon has to be followed by its interior polygons. Exterior polygons must be stored in counter clockwise rotation. Interior polygons must be stored in clockwise rotation.

Elements

An element is the basic building block of a geometric feature for Oracle Spatial. The supported spatial element types are point, line string, and polygon. Elements are constructed using ordinates - if 2D they are pairs, called coordinates, and depending on the element type, the element may contain many coordinates. In a GIS example, elements might model historic markers (points), roads (line strings), or political or administrative boundaries (polygons). Each coordinate in an element is stored as an X, Y pair.

Elements

Basic building blocks of a geometry Same as geometric primitive types Element types
Point Line Polygon Compound Linestring Compound Polygon

Element 6 Element 5 Element 4 Element 2 Element 1

Element 7

Constructed using ordinates

Element 3

Hawaii, USA

Point data consists of one or more coordinates (or more than 2 values for > 2D) and resides in one row of the spatial table. Line data consists of two or more sets of ordinate values representing line segments of the geometry. Line strings consisting of many ordinates within the spatial object.

Introduction

Polygon data also consists of coordinate pair values, one vertex pair for each line segment of the polygon. The first coordinate pair represents the first line segment, with coordinates defined in either a clockwise or counterclockwise order around the polygon. You must close the polygon by repeating the first vertex as the last. An example of a geometry that consists of multiple elements is the State of Hawaii. Hawaii consists of seven islands, and when modeled using Oracle Spatial it will consist of seven elements, one for each island.

Geometries

Geometries are the representation of spatial features, modeled as an ordered set of primitive elements.

Geometry
Geometry 1 California Geometry 2 Texas

Represents Represents a a spatial spatial feature feature Consists Consists of of an an ordered ordered set set of of elements elements
Geometry 3 Florida Geometry 4 Hawaii

A complex geometric feature such as a polygon with holes would be stored as a sequence of polygon elements. In a multiple-element polygonal geometry, all sub-elements are wholly contained within the outermost element, thus building a more complex geometry from simpler pieces. A geometry might describe the available land in a town. This could be represented as a polygon with holes where water or zoning prevents construction.

Layers

The graphic below illustrates geometries stored in a polygonal layer representing political boundaries in the United States.

Introduction

Layers

Consist Consist of of geometries geometries that share a that share a common common set set of of attributes attributes Layer Layer is is a a geometry geometry column column in in a a table table

States layer

Table 3: Oracle Spatial Gtypes

SDO_GTYPES
GTYPE - Gtype with Dimensionality 2D 0 1 2 3 4 5 6 7 3D 3000 3001 3002 3003 3004 3005 3006 3007 4D 4000 4001 4002 4003 4004 4005 4006 4007

Unknown Geometry Point Linestring Polygon Collection MultiPoint MultiLinestring MultiPolygon

2000 2001 2002 2003 2004 2005 2006 2007

The main reason for discussing earlier version of Oracle Spatial is because of issues that users will have with migrating data from other data sources or models.

Introduction

As an example we can look at the requirement for polygons to be counter clockwise to describe positive area and clockwise to define negative areas or voids. In 8.1.5 Oracle Spatial did not have this constraint and therefore all polygons had to be pre-processed during indexing and querying to determine the true relationship between positive and negative polygons. This processing could be a big issue to a large data set and was eventually mitigated by applying additional business rules to the Oracle Spatial object model. There are many spatial formats in the world and quite a few of them do not require polygons to have a certain direction. Oracle Spatial now has a function that will re-direct and re-order any polygons that do not follow its current structural rules. This allows a user to migrate spatial data into the 8.1.5 format and then bring the data into compliance with the current release of Oracle Spatial.

Element Types
Number Element Type 0 UNKNOWN_ELEMENT 1 2 POINT LINESTRING Interpretation User defined # of points in collection 1 - Straight lines 2 - Circular arcs 1 - Straight lines 2 - Circular arcs 3 - Optimized rectangle 4 - Circle # of type 2 sub-elements that make up the linestring # of type 2 sub-elements that make up the polygon

3 1003 2003

POLYGON (Outer) (Inner)

COMPOUND LINESTRING

5 1005 2005

COMPOUND POLYGON (Outer) (Inner)

Introduction

Element Example: Line String

Ordinate offset 1 Element type 2 (x2,y2) (x2,y2) Interpretation 1

(x1,y1) (x1,y1)

(x3,y3) (x3,y3)

(x4,y4) (x4,y4)

Each Each line line segment segment is is defined defined by by two two points points Last point from one is the first point of Last point from one is the first point of next next segment segment Line Line segments segments that that close close to to form form a a ring ring have have no no implied implied interior interior Line Line segments segments must must be be contiguous contiguous Line Line segments segments can can cross cross

Element Example: Polygon

Ordinate offset 1 Element type 1003 (x5,y5) Interpretation 1

(x6,y6) (x1,y1)

(x4,y4) (x4,y4)

(x2,y2)

(x3,y3)

Interpretation Interpretation 1 1- All All line line segments segments are are straight straight lines lines Area Area is is implied implied Line Line segments segments cannot cannot cross cross each each other other

Introduction

Element Example: Arc Polygon

Ordinate offset 1 Element type 1003 (x6,y6) (x7,y7) (x7,y7) (x5,y5) Interpretation 2

(x8,y8)

(x4,y4)

(x9,y9) (x1,y1) (x2,y2)

(x3,y3)

Interpretation Interpretation 2 2- All All line line segments segments are are circular circular arcs arcs Area Area is is implied implied Arcs Arcs can can not not cross cross each each other other

Element Example: Arc String

Ordinate offset 1 (x2,y2) Element type 2 (x4,y4) Interpretation 2

(x1,y1) (x3,y3) (x3,y3) (x5,y5) (x6,y6)

(x7,y7)

Each Each arc arc is is defined defined by by three three points points on on the the circumference circumference of of a a
circle circle Last Last point point from from one one arc arc is is the the first first point point of of next next arc arc Arcs Arcs that that close close to to form form a a ring ring have have no no implied implied interior interior Arcs must be contiguous Arcs must be contiguous Arcs Arcs can can cross cross

Introduction

Element Example: Rectangle

Ordinate offset 1 Element type 1003 Interpretation 3

(x2,y2)

(x1,y1)

Optimal Optimal storage storage - Defined Defined by by lower lower left left point, point, upper upper right right point point Area Area is is implied implied

Element Example: Circle

Ordinate Offset 1 Element Type 1003 Interpretation 4

(x2,y2)

(x1,y1) (x1,y1)

(x3,y3)

Defined Defined by by any any three three distinct distinct points points on on the the circumference circumference Area Area is is implied implied

10

Introduction

Element Example: Compound Line String

Ordinate Offset 1 1 5 13 (x4,y4) (x3,y3) (x6,y6) (x2,y2) (x5,y5) (x7,y7) Element Type 4 2 2 2 Interpretation 3 1 2 1

(x9,y9) (x8,y8)

(x1,y1)

First First triplet triplet (header) (header) defines defines the the number number of of sub-elements sub-elements Sub-elements Sub-elements must must be be contiguous contiguous Arcs Arcs and and line line segments segments of of sub-elements sub-elements can can cross cross Element Element type type 4 4 can can ONLY ONLY contain contain sub-elements sub-elements of of type type 2 2

Element Element Example: Example: Compound Compound Polygon Polygon

Ordinate Offset 1 1 5 (x6,y6) (x7,y7) (x1,y1) (x5,y5) (x3,y3) Element Type 1005 2 2 (x4,y4) Interpretation 2 1 2

(x2,y2)

First First triplet triplet (header) (header) defines defines the the number number of of sub-elements sub-elements Sub-elements Sub-elements must must be be contiguous contiguous Arcs Arcs and and line line segments segments of of sub-elements sub-elements cannot cannot cross cross Element Element type type 5 5 can can ONLY ONLY contain contain sub-elements sub-elements of of type type 2 2 Area Area is is implied implied

Introduction

11

Etype Etype 0 0- to to support support interoperability interoperability

Ordinate Offset 1 27 Element Type 2 0 (x5,y5) Interpretation 1 200

(x1,y1) (x13,y13) (x13,y13)

MDSYS.SDO_ELEM_INFO_ARRAY MDSYS.SDO_ELEM_INFO_ARRAY (1,2,1,27,0,200) (1,2,1,27,0,200) MDSYS.SDO_ORDINATE_ARRAY MDSYS.SDO_ORDINATE_ARRAY ( ( x1,y1,....,x13,y13,x1,y1,x5,y5,x13,y13) x1,y1,....,x13,y13,x1,y1,x5,y5,x13,y13)

Element Element Example: Example: Unknown Unknown geometry geometry

Ordinate Offset 1 17 Element Type 0 1 Interpretation 1324 2

Element Element type type 0 0 is is ignored ignored by by Oracle Oracle Spatial Spatial Element type 0 is for modeling unsupported Element type 0 is for modeling unsupported element element types types (i.e. curves, splines etc) (i.e. curves, splines etc) A A geometry geometry with with an an element element type type 0 0 must must contain contain at at least least one one element element of of type type 1,2,3,4 1,2,3,4 or or 5. 5. The The non non 0 0 element element is is an an approximation approximation of of the the unsupported unsupported geometry. geometry. The The approximation approximation is is indexed indexed by by Oracle Oracle Spatial Spatial

12

Introduction

Collection Example: Point cluster

Ordinate Offset 1 Element type 1 Interpretation 5

(x1,y1) (x2,y2)

(x3,y3) (x5,y5) (x4,y4)

Interpretation Interpretation is is the the number number of of points points in in the the cluster cluster

Collection Example: Multi Line String

Ordinate offset 1 7 Element type 2 2 Interpretation 1 2

(x2,y2) (x2,y2)

(x5,y5) (x5,y5)

(x1,y1) (x1,y1)

(x3,y3) (x3,y3)

(x4,y4) (x4,y4)

(x6,y6) (x6,y6)

Elements Elements can can be be line line strings, strings, arc arc strings strings or or compound line strings compound line strings

Introduction

13

Collection Example: Multi Polygon

Ordinate offset 1 13 (x5,y5) Element type 1003 1003 Interpretation 1 4

(x6,y6) (x1,y1)

(x4,y4) (x4,y4)

(x8,y8) (x9,y9)

(x7,y7) (x7,y7)

(x2,y2)

(x3,y3)

Elements Elements can can be be polygons, polygons, arc arc polygons, polygons, or or compound compound polygons polygons

Collection Example: Multi Polygon

Ordinate offset 1 13 Element type 1003 1 (x5,y5) Interpretation 1 1

(x6,y6) (x1,y1)

(x4,y4) (x4,y4) (x7,y7) (x7,y7)

(x2,y2)

(x3,y3)

Elements Elements can can be be polygons, polygons, arc arc polygons, polygons, or or compound compound polygons polygons

14

Introduction

Element example: Polygon with void

Ordinate offset 1 13 Element type 1003 2003 (x5,y5) (x6,y6) (x1,y1) (x7,y7) (x2,y2) (x3,y3) (x8,y8) (x4,y4) (x4,y4) Interpretation 1 3

A A void void can can be be modeled modeled with with any any combination combination of of type type 3 3 and and Area Area is is implied implied as as the the difference difference between between the the outer outer and and inner inner
polygons polygons type type 5 5 elements elements Voids Voids can can contain contain islands islands and and islands islands can can contain contain voids voids

Element example: Compound polygon with void

Ordinate Offset 1 1 7 17 (x7,y7) (x8,y8) (x1,y1) (x6,y6) (x10,y10) (x9,y9) Element Type 1005 2 2 2003 (x5,y5) Interpretation 2 1 2 3

(x4,y4)

(x2,y2)

(x3,y3)

A A void void can can be be modeled modeled with with any any combination combination of of type type 3 3 and and
type type 5 5 elements elements Voids can Voids can contain contain islands islands and and islands islands can can contain contain voids voids Area Area is is implied implied as as the the difference difference between between the the outer outer and and inner inner polygons polygons

Introduction

15

Constructing geometries
SQL> SQL> INSERT INSERT INTO INTO LINES LINES VALUES VALUES ( ( 2> attribute_1, 2> attribute_1, ..., ..., attribute_n, attribute_n, 3> MDSYS.SDO_GEOMETRY 3> MDSYS.SDO_GEOMETRY ( ( 4> 2002, 4> 2002, null, null, null, null, 5> MDSYS.SDO_ELEM_INFO_ARRAY 5> MDSYS.SDO_ELEM_INFO_ARRAY (1,2,1), (1,2,1), 6> MDSYS.SDO_ORDINATE_ARRAY 6> MDSYS.SDO_ORDINATE_ARRAY ( ( 7> 10,10, 7> 10,10, 20,25, 20,25, 30,10, 30,10, 40,10)) 40,10)) 8> ); 8> );

(20,25) (20,25)

(10,10) (10,10)

(30,10) (30,10)

(40,10) (40,10)

Constructing geometries
SQL> SQL> INSERT INSERT INTO INTO PARKS PARKS VALUES( VALUES( 2> attribute_1, 2> attribute_1, ..., ..., attribute_n, attribute_n, 3> MDSYS.SDO_GEOMETRY( 3> MDSYS.SDO_GEOMETRY( 4> 2003, 4> 2003, null, null, null, null, 5> MDSYS.SDO_ELEM_INFO_ARRAY 5> MDSYS.SDO_ELEM_INFO_ARRAY 6> (1,1005,2, 6> (1,1005,2, 1,2,1, 1,2,1, 7,2,2, 7,2,2, 17,2003,3), 17,2003,3), 7> MDSYS.SDO_ORDINATE_ARRAY 7> MDSYS.SDO_ORDINATE_ARRAY 8> (10,50,10,30,50,30,50,50,40,60, 8> (10,50,10,30,50,30,50,50,40,60, 9> 30,50,20,60,10,50,25,35,35,40 9> 30,50,20,60,10,50,25,35,35,40 ) ) 10> ); 10> );
(20,60) (10,50) (10,50) (30,50) (35,40) (25,35) (40,60)

(50,50)

(10,30)

(50,30)

16

Introduction

Ring ordering
In In 8.1.6+: 8.1.6+: External External ring ring must must appear appear before before internal internal ring ring

Outer Outer and and inner inner rings rings identified identified by by element element type type
1003 2003 must be constructed as 1003 must be constructed as + +

2003 +

1003

Metadata, Tolerance, and Coordinate Systems

Every SDO_GEOMETRY column in a table requires an entry in Oracle spatial metadata dictionary, SDO_GEOM_METADATA_TABLE. For each user schema that has spatial data, the metadata is accessed through the view USER_SDO_GEOM_METADATA. The metadata entries includes the following information: Name of the table that contains the column of type SDO_GEOMETRY Name of the column defined with the SDO_GEOMETRY data type Number of axes (dimensions) for the SDO_GEOMETRY column Lower and upper bounds for each axis Tolerance value for each axis, generally the same value for all axes Spatial reference identifier (SRID)

The lower and upper bound of each axis is not necessarily the minimum bounding rectangle (MBR) of the data in the SDO_GEOMETRY column.

Introduction

17

USER_SDO_GEOM_METADATA
SQL> SQL> DESCRIBE DESCRIBE USER_SDO_GEOM_METADATA USER_SDO_GEOM_METADATA Name Null? Type Name Null? Type --------------------------- ------------------- ----------------------------------TABLE_NAME NOT VARCHAR2(32) TABLE_NAME NOT NULL NULL VARCHAR2(32) COLUMN_NAME NOT VARCHAR2(32) COLUMN_NAME NOT NULL NULL VARCHAR2(32) DIMINFO MDSYS.SDO_DIM_ARRAY DIMINFO MDSYS.SDO_DIM_ARRAY SRID NUMBER SRID NUMBER MDSYS.SDO_DIM_ARRAY VARRAY(4) VARRAY(4) OF OF SDO_DIM_ELEMENT SDO_DIM_ELEMENT MDSYS.SDO_DIM_ELEMENT object SDO_DIMNAME VARCHAR2(64) SDO_DIMNAME VARCHAR2(64) SDO_LB SDO_LB SDO_UB SDO_UB NUMBER NUMBER NUMBER NUMBER

SDO_TOLERANCE SDO_TOLERANCE NUMBER NUMBER

The axes bounds should be values that contain all current and future geometries. The first axis defined must always be x, and the second axis y. Optional z and measure axes can also be defined. When dealing with geodetic data (data that is longitude/latitude), the first axis must be defined within a (-180, 180) range, and the second axis within (-90,90). Tolerance is generally the same for all axes. Tolerance is the distance two coordinates must be apart to be considered unique. Oracles geometry validation routines, spatial operators, and spatial functions all use tolerance. It is very important to define a tolerance that reflects the true resolution at which your data was collected. When storing data that is not longitude/latitude, the tolerance unit is the same as the coordinate system unit associated with the spatial data. When storing longitude/latitude (geodetic) data, the tolerance unit is meters.

18

Introduction

All coordinate systems supported by Oracle Spatial and Oracle Locator are defined in a dictionary table called MDSYS.CS_SRS. Custom coordinate systems can also be added to the MDSYS.CS_SRS dictionary, and the process is described in the Oracle Spatial Users Guide and Reference. In the MDSYS.CS_SRS dictionary, a numeric primary key called the SRID identifies each supported coordinate system. The dictionary table also contains the definition of each coordinate system in the well_known_text (WKT) grammar defined by the Open GIS Consortium (OGC). Associating spatial data with a coordinate system is as simple as associating the spatial data with an SRID value. Associating spatial data with an SRID is recommended, especially if your data is geographic, that is, related to the Earth. Geographic data can be divided into two categories, geodetic (longitude/latitude data), and projected (non-longitude/latitude data). Oracle considers Great Circle distances between consecutive coordinates of geometries defined with a geodetic SRID. When associating an SRID with an SDO_GEOMETRY column, it must be specified in the USER_SDO_GEOM_METADATA entry, and also in the SDO_SRID attribute of each SDO_GEOMETRY object loaded.

Data Loading

Bulk loads can be accomplished with traditional Oracle utilities, such as SQL*Loader and Import. Bulk unloading can be accomplished with Oracles Export utility. These utilities require no spatial specific syntax. As recommended with non-spatial data, if you are performing a large bulk load, it is recommended to drop indexes (including spatial indexes if they exist), perform the load, and recreate indexes after the load completes. If indexes are not dropped prior to a bulk load, they are maintained as the load occurs. This can slow the load process considerably. SQL*Loader can load spatial data, but it does not understand Geographic Information System (GIS) vendor exchange formats, such as ESRI shapefiles, MapInfo Tab files, Autodesk DWG files, or Microstation DGN files. Each major GIS vendor has their own tool to export their exchange formats into Oracles SDO_GEOMETRY format.

See Exporting Spatial Data to Oracle on page 58.

Data Validation

Spatial data must be valid to ensure correct results when you perform spatial analysis. If an SDO_GEOMETRY column is spatially indexed, Oracle will perform some validity checks when spatial data is inserted into the column. But complete validation only occurs by running either the SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT or SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT procedure.

Introduction

19

If data is guaranteed to be valid prior to data load, validation is not necessary. Otherwise, validation is highly recommended. Invalid geometries should either be corrected or deleted. SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT and SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT validate geometries in accordance with rules defined by the Open GIS Consortium (OGC) via the Simple Feature Specification for SQL. When invalid geometries are reported (for example, a self-intersecting polygon), additional context information, such as which edges intersected, is also reported. The additional context information is very useful in correcting invalid geometries. Some of the most common validation errors reported include: ORA 13356 Adjacent repeated points in geometry are redundant. Tolerance may be set too coarsely. Making tolerance finer may fix the error.Points may truly be repeated. Remove duplicate vertices. ORA 13349 Polygon boundary crosses itself. Tolerance may be set too coarsely. Making the tolerance finer may fix the error. Polygon truly self intersects. Fix the polygon by ensuring that no edges intersect. ORA 13367 Wrong rotation for interior/exterior rings. Correct the rotation of the polygon ring. Outer rings should be counterclockwise, inner rings clockwise. The additional context information reported by the validation routines can be supplied to the following routines to help fix invalid geometries: SDO_UTIL.REMOVE_DUPLICATE_VERTICIES SDO_UTIL.EXTRACT

Indexing Spatial Data

R-Tree spatial indexes, introduced in Oracle 8.1.7, require no tuning, and are recommended in almost all scenarios. Oracle9i introduced a geodetic R-tree index, which takes into account Great Circle distances, and also geometries that span the poles and the 180 meridian. Oracle9i Release 2 introduced some parallelization when creating R-tree spatial indexes, and also performance enhancements. Oracle Database includes more R-tree performance enhancements, concurrent DML enhancements, and more parallelization. Specifying the LAYER_GTYPE parameter in the CREATE INDEX statement will:

20

Introduction

Help maintain spatial integrity, by only allowing a certain class of spatial features to be inserted in to the SDO_GEOMETRY column. For example, specifying LAYER_GTYPE=POINT at index creation will allow only point data to be inserted into the column. Help query performance. Spatial queries optimizations will be invoked if the class of spatial data for the column is specified at index creation.

R-tree Indexing Concept

R-tree Index Leaf nodes of R-tree store <MBR, geometry pointer>

MBR Geometry

Application Considerations

If visualization is a key component of your application, this section may be very relevant. When the display is zoomed out very far, it is not good practice to turn on very detailed layers. For example, if the display is zoomed out to show the entire United States, turning on detailed streets does not add value to the display. Detailed streets at that zoom level would appear as a solid blob on the screen. It is much more realistic to turn on detailed streets when the display is zoomed in to a one kilometer area east to west.

Introduction

21

Consider a layer with very detailed polygon regions (about 3000 vertices in each polygon). When zoomed out very far, it does not make sense to display these very detailed polygons. The detail of the polygons is lost because the many coordinates in these polygons are being forced to render onto just a few pixels. A more realistic scenario would be to use zoom control to only turn on the detailed polygons when you are reasonably zoomed in. Another realistic approach is to create a generalized layer (generalized version of the detailed polygons). The generalized layer is displayed when zoomed out very far, and the detailed layer is displayed when you are zoomed closer in. Zoom control and the use of generalized layers are very well known concepts for display applications. Correct usage of zoom control and generalized layers will provide much better performance. Unnecessary fetches of detailed geometries from the server can be avoided, especially since most of the coordinates of the detailed geometries will render on just a few pixels.

Topological Data Model

Topology elements
The basic topology elements in an Oracle topology are its nodes, edges and faces. These elements are all two-dimensional.
Node

A node is represented by a point and can be used to model an isolated point feature or to bound edges. Every node has a coordinate pair associated with it to describe the spatial location of the node.
Edge

An edge is bounded by a start and end node and has a coordinate string associated that describes the spatial representation. Each edge can consist of multiple vertices, represented by linear as well as circular arc strings. As each edge is directed, it is possible to determine which faces are located at the left and right hand side of the edge.
Face

A face is represented by a polygon (that can be reconstructed from the several edge strings) and has references to a directed edge on its outer and (if any) inner boundaries. Each topology has a universal face that contains all other nodes, edges and faces in the topology.

22

Introduction

Topology Geometry

Nodes, edges and faces are the building blocks by which every real world object can be constructed. These real world objects are modeled as a feature or topology geometry (topo_geometry). Each topo_geometry is stored as a set of topological elements, for example, a parcel can consist of several faces. Oracle distinguishes these topo_geometry types: point line string polygon or multipolygon heterogeneous collection

Each topo_geometry has a reference to its topo_geometry layer. These layers consist of collections of topo_geometries of a specific type, for instance 'parcels' or 'roads'. Oracle automatically assigns unique IDs to topo_geometries and topo_geometry layers. It is possible to define a hierarchy in topology geometry layers. This hierarchy indicates that a topo_geometry of the type of the topmost hierarchy level consists of topo_geometries at the next level down and so on. On a cadastral data set this could be used to model the relationship between a cadastral municipality, cadastral sections, cadastral sheets and parcel numbers.

Figure above shows relationship between topology geometries and nodes, edges and faces.

Topology related tables

In order to be able to work with the collection of tables, the DBMS creates some extra tables. The relationship table is already mentioned as it stores the relationship between topology geometries at the one side and the nodes, edges and faces on the other side.

Introduction

23

Another automatically generated table is the history table, which holds track of all changes to the topology over time. The metadata tables store the properties of the tables, as well as references to all indexes. The initialize metadata procedure creates these indexes on the topology tables.

Display Metadata

IEE applies specific styles (such as colors and patterns) to specific themes (that is, collections of spatial features, such as cities, rivers, and highways) to render a map (such as a GIF image for display on a Web page). For example, the application might display a map in which state parks appear in green and restaurants are marked by red stars. A map typically has several themes representing political or physical entities, or both. For example, a map might show national and state boundaries, cities, mountain ranges, rivers, and historic sites. When the map is rendered, each theme represents a layer in the complete image. The Oracle Map Definition Tool lets you define styles, themes, and base maps, including the rules for applying one or more styles to each theme. These styles, themes, base maps, and associated rules are stored in the database in map definition tables under the MDSYS schema, and they are visible to you through metadata views. Access to styles belonging to other users is determined by the database privileges granted. The mapping metadata (the set of styles, themes, and base maps) that a user can access is stored in metadata views that are automatically defined when a user is created.

These views are described in Metadata Views on page 30 (for example, USER_SDO_STYLES, USER_SDO_THEMES, and USER_SDO_MAPS). The set of map definition objects that a given user can access is sometimes called that users mapping profile. You can manage styles, themes, and base maps with the Oracle Map Definition Tool (described in the Oracle Map Definition Tool User's Guide).

Styles

A style is a visual attribute that can be used to represent a spatial feature. The basic map symbols and labels for representing point, line, and area features are defined and stored as individual styles. Each style has a unique name and defines one or more graphical elements using XML syntax. Each style is of one of the following types: Color: a color for the fill or the stroke (border), or both.

24

Introduction

Marker: a shape with a specified fill and stroke color, or an image. Markers are often icons for representing point features, such as airports, ski resorts, and historical attractions. When a marker style is specified for a line feature, the rendering engine selects a suitable point on the line and applies the marker style (for example, a shield marker for a U.S. interstate highway) to that point. Line: a line style (width, color, end style, join style) and optionally a centerline, edges, and hash mark. Lines are often used for linear features such as highways, rivers, pipelines, and electrical transmission lines. Area: a color or texture, and optionally a stroke color. Areas are often used for polygonal features such as counties and census tracts. Text: a font specification (size and family) and optionally highlighting (bold, italic) and a foreground color. Text is often used for annotation and labeling (such as names of cities and rivers).

The primary advanced style is BucketStyle, which defines the relationship between a set of simple styles and a set of buckets. For each feature to be plotted, a designated value from that feature is used to determine which bucket it falls into, and then the style associated with that bucket is used to plot the feature. The AdvancedStyle class is extended by BucketStyle, which is in turn extended by ColorSchemeStyle and VariableMarkerStyle. (Additional advanced styles, such as for charts, are planned for a future release.)

Table 4 below lists the Java class for creating style of each type. Table 4: Style Type Java Classes
Style Type Color Marker Line Area Text Advanced

Java Class
oracle.sdovis.style.StyleColor oracle.sdovis.style.StyleMarker oracle.sdovis.style.StyleLine oracle.sdovis.style.StyleArea oracle.sdovis.style.StyleText oracle.sdovis.stylex.Advanced and extension

Geometry Types
(any type) point, line line polygon (any type) (any type)

All styles for a database user are stored in that users USER_SDO_STYLES view, which is described in Metadata Views on page 30.

Introduction

25

Themes

A theme is a visual representation of a particular data layer. Each theme (except for image themes) is associated with a specific spatial geometry layer, that is, with a column of type MDSYS.SDO_GEOMETRY in a table or view. For example, a theme named US_States might be associated with the STATE_SHAPE spatial geometry column in a STATES table. A theme can have its definition, including styling rules, stored permanently in the database (a predefined theme), or a theme can be dynamically defined with a map request (a JDBC theme). All predefined themes for a database user are stored in that users USER_SDO_THEMES view, which is described in Metadata Views on page 30. Each predefined theme is associated with one or more styling rules. The styling rules for each predefined theme are expressed using XML, such as in Example 1 for an Airport theme.

Styling Rules in Predefined Themes

The following naming conventions are used for "prefixes" in style names in the examples in this chapter: v. indicates variable (advanced style), m. indicates marker, c. indicates color, l. indicates line, and t. indicates text. In the content (character data) of an XML document, &lt; and &gt; must be used to represent < and >, respectively. Otherwise, < or >, such as in WHERE CATEGORY > B, will be interpreted by the XML parser as part of an XML tag.
Example 1: Example of XML Definition of Styling Rules for an Airport Theme
<?xml version="1.0" standalone="yes"?> <styling_rules> <rule> <features style="c.black gray"> runway_number &gt; 1 </features> <label column="name" style="t.airport name"> </label> </rule> <rule> <features style="m.airplane"> runway_number = 1 </features> </rule> </styling_rules>

Each styling rule has a required <features> element and an optional <label> element. The <features> element specifies which rows (features) in the table or view will be selected based on its attribute value and the style to be used for those selected features. The <label> element specifies whether or not to annotate the selected feature, and if so, which column in the table or view to use for text labels.

26

Introduction

In the Styling Rules example, there are two styling rules associated with the Airport theme. The first rule specifies that only those rows that satisfy the condition runway_number &gt; 1 (that is, runway number greater than 1) will be selected, and these will be rendered using the style named c.black gray. Any valid SQL WHERE clause conditions can be used as the value of a <features> element.

If no value is supplied, no WHERE clause condition is applied. For example, assume that the definition had been the following (that is, omitting the runway_number &gt; 1 condition):
<?xml version="1.0" standalone="yes"?> <styling_rules> <rule> <features style="c.black gray"/> <label column="name" style="t.airport name"> 1 </label> </rule> </styling_rules>

In this case, all airport features would be selected and would be rendered using the color style named c.black gray. The first rule also has a <label> element, which specifies that the NAME column in the table or view will be used to annotate each airport, using the text style t.airport name. The value of the <label> element, which can be any SQL expression, is used to determine whether or not a feature will be annotated. If the value is greater than zero, the feature will be annotated. In this case, because the value is the constant 1, all features specified by the <features> element will be annotated, using the values in the NAME column. If the value is less than or equal to zero for a feature, that feature will not be annotated. The second rule, which applies to those airports with only one runway, does not have a <label> element, thus, preventing all such airports from being annotated. In addition, the features that satisfy the second rule will be rendered using a different style (m.airplane), as specified in its <features> element.

If two or more rules are specified, a UNION ALL operation is performed on the SQL queries for the rules (from first to last) to fetch the qualified features from the table or view. If an advanced style is specified in a rule, the SELECT list of the query to fetch qualified features contains the spatial column, the attribute column or columns, the name of the feature style, the label information, the WHERE clause, and the feature query. Based on the value of the attribute column or columns and the definition of the specified feature style, each feature is associated with a style.

Introduction

27

Maps

A map can consist of a combination of elements and attributes, such as the following: Background image Title Legend Query window Footnote (such as for a copyright notice) Base map Themes (in addition to any in the base map) JDBC queries JDBC image queries

These elements and attributes, when specified in a map request, define the content and appearance of the generated map. A map can have a base map and a stack of themes rendered on top of each other in a window. A map has an associated coordinate system that all themes in the map must share. For example, if the map coordinate system is 8307 (for Longitude / Latitude [WGS 84], the most common system used for GPS devices), all themes in the map must have geometries defined using that coordinate system. You can add themes to a map by specifying a base map name or by using the programming interface to add themes. The order in which the themes are added determines the order in which they are rendered, with the last specified theme on top, so be sure you know which themes you want in the background and foreground. All base map names and definitions for a database user are stored in that users USER_SDO_MAPS view, which is described in Metadata Views on page 30. The DEFINITION column in the USER_SDO_MAPS view contains an XML description of a base map. Example of XML Definition of a Base Map
<?xml version="1.0" ?> <map_definition> <theme name="theme_us_states" min_scale="10" max_scale="0" /> <theme name="theme_us_parks" min_scale="5" max_scale="0" /> <theme name="theme_us_highways" min_scale="5" max_scale="0" />

28

Introduction

<theme name="theme_us_streets" min_scale="0.05" max_scale="0" /> </map_definition>

Each theme in a base map can be associated with a visible scale range within which it is displayed. In the example above, the theme named theme_us_streets is not displayed unless the map request is for a map scale of 0.05 or less and greater than 0 (in this case, a scale showing a great deal of detail). If the min_scale and max_scale attributes are not specified, the theme is displayed whenever the base map is displayed. The display order of themes in a base map is the same as their order in the base map definition. In the previous example the theme_us_states theme is rendered first, then theme_us_parks, then theme_us_highways, and finally (if the map scale is within all specified ranges) theme_us_streets.

Metadata Views

The mapping metadata describing base maps, themes, and styles is stored in the global tables SDO_MAPS_TABLE, SDO_THEMES_TABLE, and SDO_STYLES_TABLE, which are owned by MDSYS. However, you should never directly update these tables. Each user has the following views available in the schema associated with that user: USER_SDO_MAPS and ALL_SDO_MAPS contain information about base maps. USER_SDO_THEMES and ALL_SDO_THEMES contain information about themes. USER_SDO_STYLES and ALL_SDO_STYLES contain information about styles.

You are encouraged to use the Oracle Map Definition Tool (described in the Oracle Map Definition Tool User's Guide) to manage the mapping metadata. Only advanced users should consider using SQL statements to update the metadata views. The USER_SDO_xxx views contain metadata information about mapping elements (styles, themes, base maps) owned by the user (schema), and the ALL_SDO_xxx views contain metadata information about mapping elements on which the user has SELECT permission. The ALL_SDO_xxx views include an OWNER column that identifies the schema of the owner of the object. The USER_SDO_xxx views do not include an OWNER column.

Introduction

29

All styles defined in the database can be referenced by any user to define that users themes, markers with a text style, or advanced styles. However, themes and base maps are not shared among users; so, for example, you cannot reference another users themes in a base map that you create. The following rules apply for accessing the mapping metadata: If you need to add, delete, or modify any metadata, you must perform the operations using the USER_SDO_xxx views. The ALL_SDO_xxx views are automatically updated to reflect any changes that you make to USER_SDO_xxx views. If you need only read access to the metadata for all styles, you should use the ALL_SDO_STYLES view. Both the OWNER and NAME columns make up the primary key; therefore, when you specify a style, be sure to include both the OWNER and NAME.

30

Introduction

Introduction

31

32

Introduction

Tour Guides
Connecting to Oracle Database
IEE Startup
To start an IMAGINE Enterprise Editor session, follow the steps below.

From the IMAGINE Workspace, click File button > New > 2D View.. > IEE Layer. The Enterprise Editor connection selector dialog opens.

Figure 2: Connection Selector

Click Connect to Oracle to open the Connect to Oracle Database dialog.

Tour Guides Tour Guides

33 33

Connection Dialog

Connection information must then be given to allow a connection to an Oracle instance to be established.

Figure 3: Connection Dialog

Enter the following information:

Server Name of the Oracle Database Server to which you want to connect SID System Identifier - a unique name for an Oracle instance (for example, ORCL) Port Number used by the Oracle Listener (default 1521) Username Name of the Oracle Schema that has the spatial data

Password

Enter the password for the Username (Schema) that was entered.

Figure 4: Password Dialog

34

Tour Guides

Map Selection

This dialog lists all maps defined for the current data source. You must select from the list of maps to continue the connection process.

Figure 5: Map Selection Dialog

To modify or add to the list of available maps use the Oracle Map Definition Tool.

Discover Options

The Discover Options dialog provides a navigation work flow to help in the location and investigation of spatial data within the current database connection.

Tour Guides

35

Figure 6: Discover Options Dialog

Choose a Theme from the <Theme List>. The values that are then displayed represent the center X and Y position and size of the MBR for the entire theme. To use these values click the Next> button or: Click the Calc. Extent button to calculate the MBR (minimum bounding rectangle) for the currently selected theme and populate the XPos, YPos and Map Size with the resulting values. Click the Search button to open the Search and Locate dialog and enter search criteria to locate specific objects in the currently selected theme. Type in values to the Xpos, Ypos and Map Size fields. Click Prev. XYS to set the values for XPos, YPos and Map Size to the last values used. Click View to set the Xpos, YPos and Map Size to the current view window.

After the appropriate choice has been made click the Next> button to initiates the extraction of data from the database using the XPos, YPos and Map Size values. It it important that the metadata that defines each layer of data be as close as possible to the MBR representing the limits of the data and not set to the entire world for example (-180,180,90,90).

36

Tour Guides

Search and Locate

The Search and Locate dialog provides a means to search for and locate a feature based on search criteria. The search criteria can comprise any combination of columns in the underlying table of the active theme. The active theme is indicated in the title bar. The search criteria can use any one of a number of operators and any value to search against. Each search criteria row is separated by a Boolean AND or OR operator.

Figure 7: Search and Locate Dialog

Click the Add button to add a search record to the Search Criteria list and then: Double-click on the Column field and select the column name from the list of available values. Double-click on the Operator field and select the type of operator to apply. Double-click on the Value field and then type in the value to apply.

Tour Guides

37

Click the Next field and choose AND or OR if you are going to add an additional search record. Click the Search button to query the database and return the results. Choose a record from the populated Results list by clicking on the record. Click the Locate button to compute the MBR of the selected geometry and pass the results to the XPos, YPos and Map Size fields on the Discover Options dialog.

After the Locate button is clicked, the Discovery process is complete and the IEE layer will display the vector data in the IEE Layer of the IMAGINE 2D View.

IEE Layer Tab

The IEE Layer Tab provides access to administrative functions as well as for all menus that control digitizing and interface settings. This tab is available when you click IEE Layer in the Workspace menu bar.

Figure 8: IEE Layer Tab

See the IMAGINE Enterprise Editor On-Line Help for more information about the user interface.

Transaction Management Commands

Some of the commands in the IEE menu provide functionality that impacts the list of transactions that are sent to the database. These commands are

Undo - Click to undo a performed operation. It can undo all operations that were performed after the last successful commit, or since you started using the application. Undo All - Click to undo all operations that were performed after the last successful commit, or since you started using the application. Redo - Click to redo a previously undone operation. It can redo all operations that were performed after the last successful commit, or since you started using the application.

38

Tour Guides

Save Settings - Click to save the current IEE environment settings locally. These settings will be used every time you start IEE until the settings are saved again.

Understanding IEE Settings

To take full advantage of the functionality provided by IEE and to ensure that all edits made using the IEE environment, familiarize yourself with the following concepts before making changes in the IEE Settings dialog. When digitizing, IEE will automatically snap to nodes or vertices by default of the IEE Snapping Engine. The snapping engine is always activated. Therefore, new linear features will always be snapped to a node or a vertex within the snapping tolerance. The Snapping Settings section in the IEE Settings dialog gives control over whether to display nodes or vertices to which IEE will snap, and what color they should appear. IEE can also set the diameter of these nodes or vertices (end points and all points). This is the display diameter of the points and also the snapping diameter. IEE can implement pessimistic or optimistic locking. The default is pessimistic locking. When pessimistic locking is enabled, any area extracted will become locked and other users will not be able to edit that area. They will however, be able to view that area. When optimistic locking is enabled, any area extracted is not locked and any user can edit the data in it. When the IEE layer is started and connected to an Enterprise Server or and Oracle database, a session is created. When an area of the map is extracted, this data becomes locked if pessimistic locking is enabled. When IEE is closed, the session for that connection is destroyed. If the Release Locks on Exit option has been deselected, the data you extracted remains locked and no one else can edit that data when IEE is closed. If the Release Locks on Exit option is selected, the lock on the extracted data is released when the session ends and others can then edit the data.

Snapping

Data Locking

Release Locks on Exit

It is recommended that the Release Locks on Exit option be selected if pessimistic locking is enabled.

Grid

A grid consists of evenly spaced points. This can be useful for digitizing schematic maps where accurate and consistent placement of features is necessary. Grid Settings are made up of two grid types: Grid Major and Grid Minor. The Grid Major field defines the distance in real world coordinates between points on the grid. The Grid Minor field defines the number of grid points between each Grid Major point.

Tour Guides

39

Draw Handles

Draw Handles can be useful when selecting placed features. Draw handles appear as small boxes at every node of a selected feature. It helps to identify the line selected. Every table that stores simple geometry, feature, or topology primitive data requires an entry in the Oracle Spatial metadata table, USER_SDO_GEOM_METADATA. Among others, this table defines the tolerance value for each axis. The tolerance is usually the same for the x and y axes. Tolerance defines the minimum distance two coordinates must be apart to be considered unique. When using geodetic data (longitude/latitude) the tolerance unit is meters. When using data that is nonlongitude/latitude, the tolerance unit is the same as the coordinate system unit associated with the spatial data.

IEE Tolerance

IEE Settings Dialog

Locking & Grid Settings

This dialog allows you to set various IMAGINE Enterprise Editor parameters. To open this dialog, click IEE Layer tab > Settings > General.

Figure 9: Locking & Grid Settings Tab

Lock Mechanism Settings: Use Pessimistic Locking Select this option to implement pessimistic locking in the database during data extraction. When the checkbox is not checked, optimistic locking is implemented.
Pessimistic locking locks all feature records in the map that are set to editable for the current extract window. No other user can edit the same feature at the same time.

40

Tour Guides

Optimistic locking is used when this setting is turned off. When optimistic locking is used, edited records are checked for other updates before being written into the database. If another update was performed by another process, then certain procedures are run to resolve this mismatch.

Commit on Save This setting is valid only when Pessimistic Locking is enabled. Commit on Save option performs an explicit commit operation after changes are successfully saved to the database. Release Lock on Exit This setting is valid only when Pessimistic Locking is enabled. Select this option to release all locks held by IMAGINE Enterprise Editor when ending a session. The lock on the extracted data is released when the session ends and others can then edit the data.
When Pessimistic Locking is enabled and Release Lock on Exit is not selected, any data that was extracted remains locked after the session ends, making the data not editable for any user.

Process Settings: Display Progress Bar Select this option to display a progress bar during the extraction of data from the database and when saving data to the database.
data from the database and when saving data to the database.

Grid Settings:
A grid consists of evenly spaced points, used to assist in precise placement of digitized elements. These grid settings are used by Grid Lock to display the grid.

Grid Major Enter a value greater than 0.0 to define the distance in real-world coordinates between points on the grid. Default is 0.0 = no grid. Grid Minor Enter a value greater than 0.0 to define the number of grid points between each grid major point. Default is 0.0 = no grid.

Tour Guides

41

Snapping Settings

Figure 10: Snapping Settings Tab

The Snapping engine allows points to automatically snap to nodes or vertices when being digitized. New linear features are always snapped to a node or a vertex within the snapping tolerance. The Snapping Settings tab has parameters to offer control whether to display nodes or vertices to which points will snap, and a color chooser. You can set the diameter of the point symbol, depending on change in the map scale.

Units: Distance Select this option to set the units of the diameter field to be measured in real-world units, defined by the coordinate system currently in use. Pixels Select this option to set the units of the diameter field to be measured in on-screen pixels.

The Distance and Pixels options are mutually exclusive, that is, only one of them can be selected at any one time.

Max Visible Scale: Enter a value to define the scale below which the End Points and Vertex Points are drawn, when selected for display. If the map is zoomed out beyond this scale setting, the points would be too small to be seen thus they will not be drawn. If this value is set to zero, End Points and Vertex Points are drawn at all scales, when selected for display. End Points:

42

Tour Guides

Visible Select this option to display a circle at the start and end nodes of a line. When the checkbox is not checked, the circle symbols at the start and end nodes are hidden. [color]
Shows the current color for end points circle symbol. Click the chooser icon bottom portion and select a color, or click the top portion to open the Color Chooser to create a custom color.

Diameter Determines the diameter of the end point circle symbol. The Diameter option is measured in either real-world distance or onscreen pixels depending on the setting in the Units section. Vertex Points: Visible Select this option to display a circle at all vertices along a line, including start and end nodes. When the checkbox is not checked, the circle symbols at the vertices are hidden. [color]
Shows the current color for vertex points circle symbol. Click the chooser icon bottom portion and select a color, or click the top portion to open the Color Chooser to create a custom color.

Diameter Determines the diameter of the vertex point circle symbol. The Diameter option is measured in either real-world distance or on-screen pixels depending on the setting in the Units section.

Topology and Precision

Figure 11: Topology and Precision Tab

Tour Guides

43

During mouse interactions, the viewer converts mouse clicks that appear in screen coordinates to map coordinates. This translation normally introduces a level of precision too great for end use. For this reason, the program contains a setting that forces all coordinate inputs to be rounded to a given number of decimal places, the Precision setting. You can set it to any integer value; a value of 6 is recommended. No rounding takes place when the value is set to less than zero.

IEE Tolerancing: Precision Enter a decimal place value in which to round coordinate inputs.
In topology, a node can be isolated or it can be used to bound edges. Two or more edges meet at a non-isolated node. An edge is bounded by a start node and an end node.

Topology: Allow ISO Moves Select this option to modify a topology edge affecting the topology face that any isolated nodes or edges fall in.
When this option is not checked (default), normal Oracle topology rules are applied when modifying topology edges. If an edge is modified that changes the face in which an isolated node or isolated edge fall in, an exception is returned.

Hilite and Display Settings

Figure 12: Hilite and Display Settings Tab

Hilite and Display Settings: [color] Hilite Color selected feature.

Shows the current highlight color for a

44

Tour Guides

Click the chooser icon bottom portion and select a color, or click the top portion to open the Color Chooser to create a custom color.

Draw Handles (Selection) Select this option to display draw handles as small boxes at every node of a selected feature. To hide draw handles when selecting, click the checkbox to remove the check. Display Bounding Boxes Select this option to draw red lines representing each layers minimum bounding rectangle (MBR), the area in which map editing can take place. Explicit Extract Mode Select this option to stop new data from being extracted when zooming in or out or panning in the map view.
When this checkbox is checked, if you zoom out, for example, any new data that would normally be drawn outside the current view to fit the new view will not be drawn. You must select IEE > Extract from the Viewer menu bar to draw (extract) the missing data to fit the view. Select this option to save processing time. When this checkbox is not checked, new data is automatically extracted when zooming or panning.

Implicit Background Mode Select this option to stop new background data from being extracted when zooming in or out or panning in the map view.
An image theme is treated as a background. If a feature theme, for example, Roads theme, is selected for display and not edit, the Roads theme becomes part of the background. When this checkbox is checked, if you zoom out, for example, any new background data that would normally be drawn outside the current view to fit the new view will not be drawn. You must select IEE > Extract from the Viewer menu bar to draw (extract) the missing background data to fit the view. Select this option to save processing time. When this checkbox is not checked, new background data is automatically extracted when zooming or panning.

IEE Locks

The IEE Locks dialog allows you to perform specific editing of layers or elements by locking a specific tool. This dialog opens when you click IEE Layer tab > Lock Controls.

Tour Guides

45

Figure 13: IEE Locks

Understanding IEE Digitizing Locks

To take full advantage of the functionality provided by IEE and to ensure that all edits made using the IEE environment, you should familiarize yourself with the following concepts before making changes in the IEE Digitizing Locks dialog. Key concepts that need to be understood to use the IEE digitizing locks effectively are outlined below.

Polygon Topo Lock

When digitizing areas, one area may be digitized inside another area. When this happens, one might want to punch a hole in the outer polygon. This means the ordinates of the outer polygon will be changed to allow for the existence of an inner polygon. The ordinates of the inner polygon will be added to the ordinate list of the outer polygon, thus punching a hole in the geometry of the outer polygon. The inner polygon geometry will be created separately. For example, a lake is being digitized and the lake is to be associated with the park in which it is located. In this case, use the Polygon Topo Lock to state the preference for associating the geometry of the lake with the geometry of the park.

Segmentation Lock

Select this option to create new nodes where the lines intersect existing edges or faces, splitting the existing edge or face, and creating new lines. When the checkbox is not checked, overlapping features are allowed and new nodes or split existing edges or faces are not created. When digitizing a new linear feature certain topological rules can be implemented. These include: Create new nodes where the line intersects existing edges or faces, splitting the existing edge or face, and creating the new line. Force the start of the edge to end at an existing node delete trailing start dangle.

46

Tour Guides

Force the end of the edge to end at an existing node delete trailing end dangle. Allow the start of the edge to end at a new node do not remove trailing start dangle. Allow the end of the edge to end at a new node do not remove trailing end dangle. Simply allow the overlapping features and do not create new nodes or split existing edges or faces.

Dangle Lock (Start)

This option works in conjunction with the Segmentation Lock option. Select this option to force the start of a new edge to end at an existing node and delete the trailing start dangle. When digitizing a linear feature, it may cross another linear feature, causing a dangle to be created. A dangle is a linear feature whose start or end node is not attached to another linear feature. This option automatically causes all start dangles to be removed when the data is digitized. When the checkbox is unchecked, trailing start dangles will remain when the data is digitized.

Segmentation Lock must also be enabled for Dangle Lock (Start) to take effect.

Dangle Lock (End)

This option works in conjunction with the Segmentation Lock option. Select this option to force the start of a new edge to end at an existing node and delete the trailing end dangle. When digitizing a linear feature, it may cross another linear feature, causing a dangle to be created. A dangle is a linear feature whose start or end node is not attached to another linear feature. This option automatically causes all end dangles to be removed when the data is digitized. When the checkbox is unchecked, trailing end dangles will remain when the data is digitized.

Segmentation Lock must also be enabled for Dangle Lock (End) to take effect.

Rubber Band Lock

Select this option to move an end node of a linear feature and also move the attached linear features. When the checkbox is not checked, attached linear features are not moved when an end node of a linear feature is moved.

Tour Guides

47

This lock can be useful for maintaining topology when you are modifying linear features. When digitizing IEE may move and end node that exists on an edge. If this end node is also an end node on an attached edge, IEE will want to maintain the connection between the two edges. Rubber banding allows this. When rubber banding is selected, the attached edge is also moved when you move an end node and thus ensures that the current topology is not violated.

Theme Lock

Select this option to allow only objects in the theme currently being modified to be affected. When the checkbox is not checked, all objects that intersect or fall within edit tolerance of the object that is being modified will be affected as well. Select this option to digitize only along the x (horizontal) or y (vertical) axis. Select this option to force each mouse click to snap to a defined grid. This grid point spacing is defined in the IEE Settings dialog. IEE can define a grid to be displayed in the map view. This grid can be particularly useful when digitizing network data as it defines a set distance between each grid point.

Axis Lock Grid Lock

Snap Lock

Select this option to automatically snap a new, intersecting linear feature to nodes of an existing feature. In this way, you can ensure that each node on your new line will snap to a node on an existing line, thus maintaining topology.

48

Tour Guides

Theme Control

The Theme Control dialog provides the ability to manipulate the themes associated with the map. Once a theme is selected, the styles defined for this theme become visible in the Styles section. To open this dialog:

Click this icon

on the IEE Tools palette

Select IEE Layer tab > Theme Control

Figure 14: Theme Control Dialog

Header This column displays the names of specific themes available for the map.
Visible When the checkbox is checked, this column indicates that the corresponding theme is visible.

Tour Guides

49

Editable When the checkbox is checked, this column indicates that editing tools can be used on the corresponding theme. Labelled If the corresponding style has a label, the label is visible when the checkbox is checked. Attributed Applies only to topology features. When the checkbox is checked, the attributes for the topology feature theme are extracted from the database.

Prev. In the Styles section, a preview icon of the corresponding style is shown if available.
If a theme is selected for edit and not for display, the data for that theme will still be retrieved from the database when the extract button is clicked.

Digitizing with IEE

The IMAGINE Enterprise Editor Tools palette provides various tools to interact with Oracle database maps and data sets. There are Miscellaneous tools to select objects and open frequently used dialogs. Geometry tools are used to place and edit primitive elements and geometries, defined as an ordered set of primitive elements. Topology tools are used in Topology data models. A map must have a existing theme based on the <TOPO>_EDGES$ table to use the topology tools. This theme must have three styles defined: one marker style, one linear style, and one polygonal style for nodes, edges, and faces respectively. The Feature tools are used to edit Topology features associated to Topology primitives. A Topology feature is stored as a set of topological primitives (nodes, edges, and faces). There are four types of topology features: Point, Line, Polygon, and Collection. To open the IEE Tools palette, click IEE Layer tab > Show Tools.

Place Point Geometry

To place a point geometry with IEE:

1. Select a theme from the Themes section of the Active Theme dialog that has a point/Marker style. 2. Select a point/Marker style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click geometry mode. to initiate the place point

4. Click the left button to place a point geometry. 5. Fill in the attributes in the Feature Attributes dialog.

50

Tour Guides

6. Click OK to accept the point geometry and its attributes, or click Cancel to reject the point geometry and its attributes.

Place Line Geometry

To place a line geometry with IEE:

1. Select a theme from the Themes section of the Active Theme dialog that contains a line style. 2. Select a line style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click geometry mode. to initiate the place line

4. Click the left button to place a starting point for the line geometry. 5. Continue clicking the left button to place additional vertices for the line. 6. Click left when finished with vertex placement. 7. Fill in the attributes in the Feature Attributes dialog. 8. Click OK to accept the line geometry and its attributes or click Cancel to reject the line geometry and its attributes.

Place Polygon Geometry

To place a polygon geometry with IEE:

1. Select a theme from the Themes section of the Active Theme dialog that contains a polygon style. 2. Select a polygon style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click geometry mode. to initiate the place polygon

4. Click the left button to place a starting point for the polygon geometry. 5. Continue clicking the left button to place additional vertices for the polygon. 6. Click left when finished with vertex placement. 7. Fill in the attributes in the Feature Attributes dialog. 8. Click OK to accept the polygon geometry and its attributes or click Cancel to reject the polygon geometry and its attributes.

Place Rectangle Polygon Geometry

To place a rectangle polygon geometry with IEE:

Tour Guides

51

1. Select a theme from the Themes section of the Active Theme dialog that contains a polygon style. 2. Select a polygon style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click polygon geometry mode. to initiate the place rectangle

4. Click a left button to define a corner of the rectangle polygon.

A dynamic rectangle will show as the cursor is moved representing the rectangle defined by the first point and the cursor location as an opposing corner.
5. Click a second point to define the opposite corner of the polygon will be placed. 6. Fill in the attributes in the Feature Attributes dialog. 7. Click OK to accept the rectangle polygon geometry and its attributes or click Cancel to reject the rectangle polygon geometry and its attributes.

Place Circular Arc Geometry

To place a circular arc geometry with IEE:

1. Select a theme from the Themes section of the Active Theme dialog that contains a polygon style. 2. Select a polygon style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click geometry mode. to initiate the place circular arc

4. Click a left button to define the first end point on the arc. 5. Click another left button to define the second end point on the arc.

Move the cursor to begin drawing a dynamic circle, setting the size of the arc.
6. Click a left button at the desired location of the third point on the arc, finishing the arc placement. 7. Fill in the attributes in the Feature Attributes dialog. 8. Click OK to accept the arc geometry and its attributes or click Cancel to reject the arc geometry and its attributes.

52

Tour Guides

Circle polygons are supported by IEE and Oracle Spatial but may not be supported by some third party applications that may need to access the spatial data.

For additional information regarding polygon and line geometry placement see IEE Locks on page 46.

Place Topology Isolated Node Primitive

A map must have a existing theme based on the <TOPO>_EDGES$ table to use the topology tools. This theme must have three styles defined: one marker style, one linear style, and one polygonal style for nodes, edges, and faces respectively. To place an isolated node primitive in a topology:
1. Select a theme from the Themes section of the Active Theme dialog that has been defined for a topology layer. 2. Select the point/marker style from the Styles section of the Active Theme dialog that represents the topology nodes. 3. In the IEE Tools palette, click node primitive mode. to initiate the place isolated

4. Click the left button to place a node.

Place Topology Edge Primitive

A map must have a existing theme based on the <TOPO>_EDGES$ table to use the topology tools. This theme must have three styles defined: one marker style, one linear style, and one polygonal style for nodes, edges, and faces respectively. To place an edge primitive:
1. Select a theme from the Themes section of the Active Theme dialog that has been defined for a topology layer. 2. Select the point/marker style from the Styles section of the Active Theme dialog that represents the topology nodes. 3. In the IEE Tools palette, click primitive mode. to initiate the place edge

4. Click the left button to place a starting point for the edge primitive. 5. Continue clicking the left button to place additional vertices for the edge. 6. Click left when finished with vertex placement.

Tour Guides

53

7. Click Undo from the IEE menu to remove the edges and nodes created as a result of the edge digitizing.

The snapping and segmentation functionality of IEE will be utilized when placing edges. During the Place Edge Primitive operation, if the new edge crosses the topology of itself or other edges, one or more of the following will occur: Split all intersections and create the relevant edges and nodes. Force the ends of the edge (individually) to end at a node delete trailing dangles. Allow the ends of the edge (individually) to end at a new node do not remove trailing dangles.

Place Point Feature

The Feature tools are used to edit Topology features associated to Topology primitives. A Topology feature is stored as a set of topological primitives (nodes, edges, and faces). There are four types of topology features: Point, Line, Polygon, and Collection. To place a point feature:
1. Select a theme from the Themes section of the Active Theme dialog that has a point/Marker style. 2. Select a point/Marker style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click feature mode. to initiate the place point

4. Click the left button to place a point feature. 5. Fill in the attributes when the Feature Attributes dialog appears. 6. Click OK to accept the point feature and its attributes or click Cancel to reject the point feature and its attributes.

Place Line Feature

The Feature tools are used to edit Topology features associated to Topology primitives. A Topology feature is stored as a set of topological primitives (nodes, edges, and faces). There are four types of topology features: Point, Line, Polygon, and Collection. To place a line feature with IEE:
1. Select a theme from the Themes section of the Active Theme dialog that contains a line style. 2. Select a line style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click mode. to initiate the place line feature

54

Tour Guides

4. Click the left button to place a starting point for the line feature. 5. Continue clicking the left button to place additional vertices for the line. 6. Click left when finished with vertex placement. 7. Fill in the attributes when the Feature Attributes dialog appears. 8. Click OK to accept the line feature and its attributes or click Cancel to reject the line feature and its attributes.

The snapping and segmentation functionality of IEE will be utilized when placing line features. During the Place Line Feature operation, if the new feature crosses the topology of itself or other edges, one or more of the following will occur: Split all intersections and create the relevant edges and nodes. Force the ends of the edge (individually) to end at a node delete trailing dangles. Allow the ends of the edge (individually) to end at a new node do not remove trailing dangles.

Place Polygon Feature

The Feature tools are used to edit Topology features associated to Topology primitives. A Topology feature is stored as a set of topological primitives (nodes, edges, and faces). There are four types of topology features: Point, Line, Polygon, and Collection. To place a polygon feature:
1. Select a theme from the Themes section of the Active Theme dialog that contains a polygon style. 2. Select a polygon style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click feature mode. to initiate the place polygon

4. Click the left button to place a starting point for the polygon feature. 5. Continue clicking the left button to place additional vertices for the polygon. 6. Click left when finished with vertex placement. 7. Fill in the attributes when the Feature Attributes dialog appears. 8. Click OK to accept the polygon feature and its attributes or click Cancel to reject the polygon feature and its attributes.

Tour Guides

55

The snapping and segmentation functionality of IEE will be utilized when placing polygon features. During the Place Polygon Feature operation, if the new feature crosses the topology of itself or other edges, one or more of the following will occur: Split all intersections and create the relevant edges and nodes. Associate all new and or modified faces with the polygon feature.

Place Polygon Interact Feature

The Feature tools are used to edit Topology features associated to Topology primitives. A Topology feature is stored as a set of topological primitives (nodes, edges, and faces). There are four types of topology features: Point, Line, Polygon, and Collection. To place a polygon interact feature:
1. Select a theme from the Themes section of the Active Theme dialog that contains a polygon style. 2. Select a polygon style from the Styles section of the Active Theme dialog. 3. In the IEE Tools palette, click interact feature mode. to initiate the place polygon

4. Click the left button to place a starting point for the polygon feature. 5. Continue clicking the left button to place additional vertices for the polygon. 6. Click left when finished with vertex placement. 7. All topology faces that interact with the digitized polygon will then be used to create a new polygon feature. 8. Fill in the attributes when the Feature Attributes dialog appears. 9. Click OK to accept the polygon feature and its attributes or click Cancel to reject the polygon feature and its attributes.

Saving Data to Database

To save changes made during an edit session, click File button > Save. When you click Save, IEE will save any changes to the database based on the Use Pessimistic Locking option of the IEE Settings dialog section of the IEE Settings dialog: If the Use Pessimistic Locking option is not selected, that is, optimistic locking is implemented, IEE performs all pending database DML and performs a database commit. Local undo history will be cleared.

56

Tour Guides

If the Use Pessimistic Locking option is selected, IEE performs all pending database DML, performs a database commit and releases the locks currently held by the session.

If the Save Changes function returns an error, the local undo history will not be cleared.

Tour Guides

57

Exporting Spatial Data to Oracle

Spatial data (points, lines, and polygons) must be exported to the Oracle database in Oracle Spatial format. This section describes the steps required for the export of spatial data.
1. Create a user (schema) in the Oracle database with sufficient privileges.

May require DBA support for user creation and granting of privileges.
2. Start IMAGINE Workspace. 3. Click Manage Data tab > Export Data. 4. Set Format field to Oracle Spatial Feature. 5. In Input File field, navigate to the .shp file. 6. In Output File field, navigate to the desired directory to store the .ogv file, then enter the name of the .ogv file. 7. Click OK button to open the Loading Shapefile to Oracle dialog. 8. Choose the coordinate system. 9. Click the Connect button to choose an existing connection or create a new connection. 10. Click OK button to start conversion of shapefile.

For more information on IMAGINEs conversion process see the ERDAS IMAGINE Import-Export on-line help document Oracle Spatial Shapefile Loader.

Before IEE can be used as an editing environment, you must use the Oracle Map Builder Tool to define styles, themes, and maps for exported spatial data.

58

Tour Guides

Workspace Manager and Measurement Tool

This chapter contains information about the following topics:

Workspace Manager Configure Workspace Manager Measurement Tool Length, Area, Perimeter Engine

Workspace Manager

Workspace Manager is a feature of the Oracle database for application developers and database administrators (DBAs). It manages current, proposed, and historical values for data in the same database using workspaces. A workspace is a virtual environment. It logically groups collections of changes (that is new row versions) that are physically contained in one or more version-enabled tables. You must set your session context to a particular workspace to access new versions created from that workspace. Through the use of workspaces, IMAGINE can do the following: Isolate a collection of changes to production data Keep a history of changes to data Create multiple data scenarios for analysis

The tools in IMAGINE that you can use to implement this Oracle feature are outlined in the next section.

For further information regarding Oracle Workspace Manager, visit the Oracle Web site http://www.oracle.com.

Select Workspace Name

IMAGINE maintains a list of workspaces that you can activate. The default LIVE workspace is automatically created by IMAGINE. To activate a workspace, follow these steps:

1. Click the Select Workspace Name

The Workspace Names dialog opens.

icon.

2. Select the workspace. 3. Click OK to complete the activation.

Workspace Manager and Measurement Tool Workspace Manager and Measurement Tool

59 59

Create Workspace

Workspaces can be created in a hierarchical fashion. By default, when a workspace is created, it is created from the topmost database workspace, which is always called LIVE. A child workspace can have two or more parent workspaces, in which case it becomes a multiparent workspace. A multiparent workspace can see data from all of its parent workspaces and their ancestor workspaces, and it can be merged with and refreshed from its parent workspaces. This is an easy way to see all of the changes made in, or make a change that needs to be visible in, two or more workspaces. IMAGINE assigns the active workspace as the parent of a newly created workspace. To create a workspace, follow these steps:

1. Click the Create Workspace

The Input dialog opens.

icon.

2. Type the name of the workspace in the Enter Name field. Note: The parent of the new workspace is displayed to the right of the Parent WS label. 3. Click OK.
The Message dialog opens, confirming the name.

4. Click OK to create the workspace.

Remove Workspace

IMAGINE can remove the active workspace. To remove a workspace, follow these steps:

1. Ensure the workspace to be removed is the active workspace. 2. Click the Remove Workspace
icon.

The Remove Workspace dialog opens with Yes, No, and Cancel options.

3. Click Yes to remove the workspace.

60

Workspace Manager and Measurement Tool

Synchronize Active Workspace with Parent Workspace

The Synchronize Active Workspace with Parent Workspace option automatically concatenates the workspace merge, refresh, and rollback operations. This ensures that the user workspace is fully up-to-date with its parent, thus allowing it to be in the same state as a newly created workspace. Click icon to use this option.

Roll Back Changes to Workspace

Rolling back a workspace involves deleting changes. You can delete all changes made since the workspace was created. This rollback procedure leaves behind the workspace structure for future use; only the data in the workspace is deleted. IMAGINE rolls back the active workspace. To roll back a workspace, follow these steps:

1. Ensure the workspace to be rolled back is the active workspace. 2. Click the Rollback Changes to Workspace
icon.

The Rollback Workspace dialog opens, with Yes, No, and Cancel options.

3. Click Yes to roll back changes to the workspace.

Merge Active Workspace into Parent Workspace

Merging a workspace involves applying changes made in a child workspace to its parent workspace. To merge a workspace, follow these steps:

1. Ensure the workspace to be merged is the active workspace. 2. Click the Merge Active Workspace into Parent Workspace icon.
The Merge Workspace dialog opens, with Yes, No, and Cancel options.

3. Click Yes to merge the active workspace into the parent workspace.

Refresh Active Workspace

Refreshing a workspace involves applying changes made in the parent workspace to a child workspace.

1. Click the Refresh Active Workspace

icon.

Configure Workspace Manager

The sections that follow discuss how to configure IMAGINE for Oracle Workspace Manager.

Workspace Manager and Measurement Tool

61

Scripts

The information below contains scripts that are designed to be executed in SQLPlus while connected to the Oracle database that owns the data being workspace enabled. IMAGINE supports the use of Oracle Workspace Manager to versioncontrol changes made to the database. There are a number of steps you must execute to prepare the tables for using Oracle Workspace Manager. You MUST execute these steps in the defined order in this document.

Preparing the Table

Primary Key

Workspace-managed database tables must have a primary key defined. This is an Oracle requirement that has an impact on the way in which IMAGINE must use the table as a theme.
create table owm_geom ( id number PRIMARY KEY, geom mdsys.sdo_geometry ) /

USER_SDO_GEOM_MET ADATA

You must register the table in the Oracle view USER_SDO_GEOM_METADATA to allow a spatial index to be created on the table.
insert into user_sdo_geom_metadata values ( 'OWM_GEOM', 'GEOM', mdsys.sdo_dim_array ( sdo_dim_element('X',-180,180,0.05), sdo_dim_element('Y',-90,90,0.05) ),8307 );

Spatial Indexing

The table must also have a spatial index. Spatial indexes are required to allow data to be queried with a spatial operator. For example, query all data that lies inside the bounds of a polygon or rectangle.
create index idx_sp_owm_geom on owm_geom(geom) indextype is mdsys.spatial_index;

Key Column

If you want to successfully set a workspace-enabled theme in IMAGINE, it must be set up with a Key column definition. This is required as the table has a PRIMARY KEY on the ID column and IMAGINE must use this as the unique identifier.

62

Workspace Manager and Measurement Tool

Workspace-enabled tables require a primary key because, internally, an Oracle workspace-enabled table ultimately becomes a view. Views generally do not have a ROWID and, therefore, must have an ID column that can be identified as a PRIMARY KEY.

Figure 15: Oracle Map Builder Dialog

The script below can create styles, themes, and maps for the example table OWM_GEOM.
insert into user_sdo_Styles (name, type, definition) values ('CIRCLE','MARKER', '<?xml version="1.0" standalone="yes"?> <svg width="1in" height="1in"> <desc></desc> <g class="marker" style="stroke:#000000;fill:#FF0000;width:15;height:15; font-family:Dialog;font-size:12;font-fill:#FF0000"> <circle cx="0" cy="0" r="12.0" /> </g> </svg>' ) / insert into user_sdo_Styles (name, type, definition) values ('COLOR','COLOR', '<?xml version="1.0" standalone="yes"?> <svg width="1in" height="1in"> <desc/>

Workspace Manager and Measurement Tool

63

<g class="color" style="stroke:#000000;fill:#3333FF"> <rect width="50" height="50"/> </g> </svg>' ) / insert into user_sdo_Styles (name, type, definition) values ('LINE STYLE','LINE', '<?xml version="1.0" standalone="yes"?> <svg width="1in" height="1in"> <desc></desc> <g class="line" style="fill:#FF0000;stroke-width:1.0"> <line class="base" /></g> </svg>' ) / insert into user_sdo_Styles (name, type, definition) values ('COLLECTION_STYLE','ADVANCED', '<?xml version="1.0" ?> <AdvancedStyle> <CollectionStyle> <style name="CIRCLE" shape="point" /> <style name="LINE STYLE" shape="line" /> <style name="COLOR" shape="polygon" /> </CollectionStyle> </AdvancedStyle>' ) / insert into user_sdo_themes(name, base_table, geometry_column, styling_rules) values ('OWM_GEOM','OWM_GEOM','GEOM', '<?xml version="1.0" standalone="yes"?> <styling_rules key_column ="ID" table_alias="a"> <rule column="A.GEOM.SDO_GTYPE"> <features style="COLLECTION_STYLE"> </features> </rule> </styling_rules>') / insert into user_sdo_maps (name, definition) values ('OWM_MAP', '<?xml version="1.0" standalone="yes"?> <map_definition> <theme name="OWM_GEOM"/>

64

Workspace Manager and Measurement Tool

</map_definition>') /

Triggers and Sequences

With IMAGINE, a table that has a Key column must also have a trigger created on it to automatically assign the ID. This trigger gets the ID from a database sequence whenever a new record is inserted into the database. Once a record is inserted, the ID is used to maintain the record. The use of a sequence is required so that multiple users never obtain the same ID. Below is an example of a database sequence and trigger applied to the database table.
create sequence seq_owm_geom start with 1; create or replace trigger tr_ins_owm_geom before insert on owm_geom for each row declare i number; begin select seq_owm_geom.nextval into i from dual; :new.id:=i; end; /

Workspace-Enabled Tables

For you to utilize Oracle Workspace Manager with IMAGINE, the table must be enabled as a workspace-enabled table. This MUST be the last step in the preparation of a database table for Oracle Workspace Manager. All primary keys, triggers, and indexes must already be created. This is done by using the following procedure:
exec dbms_wm.enableversioning('OWM_GEOM')

Measurement Tool

This tool lets you measure the length or perimeter and area of a feature. A linear feature is measured by its length, while a polygon feature is measured by its perimeter and area. The measurement displays in the bottom-left corner of the IMAGINE window. To measure a feature by selection, follow these steps:

1. Click the Measure Feature by Selection

icon.

2. Click to select a feature on the map to measure. 3. Click again to accept the feature and display the measurement, or rightclick to reject.

Workspace Manager and Measurement Tool

65

Length, Area, Perimeter Engine

IMAGINE provides a listener called AreaPerimeterOpListener to automatically calculate the length/area/perimeter of a geometry and store the calculation as an attribute in the base table for the theme. For this operation to be successful, the base table for a theme must contain specific column names. This engine can only be used for polygonal and linear geometries. The column names for polygon geometries are:

NET_AREA Area minus any holes GROSS_AREA Total area (including holes) PERIMETER_LENGTH Perimeter of polygons

The column name for linear geometries is:

LINEAR_LENGTH Length of linear geometry.

Note: If linear geometry is a multiline geometry, the calculation is the length of all of the multi line geometries.
IMAGINE automatically attempts to find the column names outlined above and maintain these measurement attributes. Any one or all of these attributes can be maintained. The attributes are available for viewing in the User Attributes dialog.

66

Workspace Manager and Measurement Tool

Print to PDF
Support for printing an IEE layer is provided by generating a PDF document that you can send to a printing or storage device. The printed area corresponds to the extent displayed in the Viewer; however, the size corresponds to the one defined in the selected print template. The Printing dialog creates a PDF for the current cache of data from the Viewer when the Printing dialog is launched unless the extract-newmap setting is set in the template to extract fresh data from the database before creating the PDF. Control over the template size and styling options are defined in the template used to generate the PDF.

Information on creating a template and valid settings for the template file are provided in Creating Print Templates. This chapter contains information about the following topics:

Starting the Printing Process Creating Print Templates Print Template Components <print-component> Section Properties Section Page Sizes Template Predefined Page Sizes

Starting the Printing Process

There are several ways to open the Printing dialog:

Ribbon: Click IEE Layer > Print To PDF Classic: Select IEE > Print PDF in the Viewer menu bar
Enter the PRINT MAP keyin command

Print to PDF Print to PDF

67 67

Template File
The Template File dropdown list contains a set of pre-installed printing templates. These template files contain settings that influence the final look of the PDF documents. Paper size, border margin, width, and background color are examples of settings defined in the templates.

For a list of templates supplied by ERDAS, see Creating Print Templates.

For a complete list of supported defaults for printing, see Template Global Properties.

Template Description Area

The area directly below the Template File dropdown list displays a description of the currently selected template file. This description is defined in the selected templates XML file. If no description is defined, this area is blank.

68

Print to PDF

Template Properties Table

The template properties table appears below the description area. It has two column headers named Property and Value. Each row corresponds to a template global property defined in the selected template. The first item in the row is the name of the property and the second item is its corresponding value.

For more information, see Creating Print Templates.

Print
Click the Print button to generate a PDF document. The application launches Adobe Acrobat Reader if using IMAGINE or the Web plug-in for Adobe Acrobat if using ERDAS ADE Enterprise on a server. The naming convention and location for the saved file are:

Naming convention File location

<current time in ms>.pdf

C:\Documents and Settings\[username]\output

If there is an error during the PDF creation process, a Print Error dialog opens. Click the Details button to view more information about the source of the error. Errors during printing can be caused by problems like a loss of a connection with the database, a formatting issue with a template, or a problem with the source data. Click OK to close the Print Error dialog. It may take several minutes to generate the PDF document, especially if the dataset is large. Please wait for the PDF to be created if there seems to be no activity after clicking the Print button.

Cancel
Click the Cancel button to close the Printing dialog.

Help
Click the Help button to open the On-Line Help document for the Printing dialog.

Creating Print Templates

Before you can use a custom defined template, the print template must be available in the following location to populate the Template File dropdown list. The print templates are located in this directory:
<IMAGINE_HOME>\adehome\printing\templates

Print to PDF

69

Changes made to an existing template or the addition of a new template are reflected the next time the Printing dialog is opened. Specific print templates supplied by ERDAS and the template settings are listed in this table:

Table 5: Print Templates Supplied by ERDAS

Template Name Settings

PrintTemplateA3 paper size (11.7 x 16.5 inches) (297 x 420 mm) Geographic-USA_A3.xml landscape layout legend at the bottom of the page PrintTemplateGeographicUSA_Multipage_A3.xml multiple pages A3 paper size (11.7 x 16.5 inches) (297 x 420 mm) landscape layout legend at the bottom of the page barcode on each page PrintTemplate-A0.xml A0 paper size (33.1 x 46.8 inches) ( 841 x 1189 mm) landscape layout legend at the top of the page barcode at the bottom of the page PrintTemplate-A4_1.xml A4 paper size (8.3 x 11.7 inches) (210 x 297 mm) landscape layout legend at the bottom of the page maintains the map scale as currently displayed PrintTemplate-A4_2.xml A4 paper size (8.3 x 11.7 inches) (210 x 297 mm) landscape layout legend at the right side of the page maintains the extents of the view as currently displayed barcode

70

Print to PDF

Table 5: Print Templates Supplied by ERDAS

Template Name PrintTemplate-A4_3_110000.xml Settings A4 paper size (8.3 x 11.7 inches) (210 x 297 mm) landscape layout legend at the right side of the page prints at a scale of 1:10,000 barcode PrintTemplate-Ltr.xml US Letter paper size (8.5 x 11 inches) (216 x 279 mm) landscape layout legend at the bottom of the page maintains the extents of the view as currently displayed PrintTemplateA4 paper size (8.3 x 11.7 inches) (210 x 297 mm) NorthArrowExamples.xml landscape layout legend at the bottom of the page maintains the map scale as currently displayed several examples of North Arrow symbols

Print Template Components

A print template contains the xml representation of the properties needed by the printing process and a list of components to be printed. The root element of the xml is <print-template>. A <print-template> element contains two parts: <print-component> Section This is a sequence of one or more <print-component> xml elements. Properties Section The properties section is made of a <properties> xml element. Properties defined in this section are global properties. They are inherited by all components and subcomponents defined in the template. However, components and subcomponents can overwrite the global properties by defining their own version of the properties.

Print to PDF

71

<printcomponent> Section

This is a sequence of <print-component> xml elements. The <printcomponent> xml element represents components that appear on the generated PDF document. It has three elements: <provider> xml This element defines the Java class responsible for providing the data to be printed on the PDF documents. This element is optional.

For more information, see <provider> Element Syntax. <properties> This element contains a list of properties to be used during the printing process by the Java rendering class. The Java rendering class must be defined here as one of the properties with a key name of class-name and a value set to the fully qualified Java class.

Note: The class-name property must specify a class implementing the PrintPdfComponentRenderer or the sub classing of one of its implementing classes.

For more information, see <properties> Element Syntax. <subcomponents> This element lets you define a hierarchy of print components and is always drawn in the area of it parent component. Subcomponents have the same structure as the print components. This element is potentially an empty list of <subcomponent> elements.

<provider> Element Syntax

The <provider> element defines a data provider class. This class provides the data to render in the PDF document. It consists of a <properties> element. That element must contain one <property> element with a key name of provider-class-name and as a value, the fully qualified name of the provider class.

Note: The provider class you specify must implement the class ProviderIFace or subclass one of its implementing classes.
Example:
<provider> <properties> <property> <key>provider-class-name> <value>com.leica.ade.printing.providers.ADELegend Provider</value> </property> </properties> </provider>

72

Print to PDF

<properties> Element Syntax

This is a potentially empty list of <property> elements. Every <property> defined must have a <key> element and a <value> element. Example:
<properties> <property> <key>class-name</key> <value>com.leica.ade.printing.renderers.ADE DefaultLegendRendrer </property> </properties>

<property> Element Syntax

This is the representation of a property in a print template. A property consists of a <key> element, which represents the name of the setting and the <value> for that setting. Both elements must be present for the <property> element to be considered valid.

For a full list, see Valid Template Properties. Example:

<property> <key>x</key> <value>0</value> </property>

Valid Template Properties

All the print components in the ADE print template file define some of the properties used by the corresponding rendering Java class to plot the given component. The following properties are present in all of the print components:

x X coordinate of the component on the printed PDF document. y Y coordinate of the component on the printed PDF document. width Width of the component as it appears in the generated PDF document. height Height of the component as it appears in the generated PDF document. border-width Width of the border to draw around the component in the generated PDF document.

Print to PDF

73

border-color Color of the border as defined by the property border-width. Map Scale Bar Print Component Renderers the map legend in the PDF document. It uses the following properties:

bar-height Height of one strip. If the Scale Bar mode is set to DUAL_MODES, there are two strips of rectangles, one on top of the other. The top strip represents the US scale, and the bottom strip represents the metric scale. In this case, the height of the scale bar is 2 x bar-height (not including the height of the labels (mi, km)). In a single mode (US_MODE, METRIC_MODE), the height of the scale bar is bar-height because there is only one rectangular strip. mode Mode of the scale bar to use. The values are: DUAL_MODES US and Metric mode combined together. US_MODE US mode only. METRIC_MODE Metric mode only.

width Width of the scale bar.

Note: The height is computed.

color-1 The first color used to fill the first rectangular area of the scale bar. color-2 Color of the second rectangular area for the scale bar. label-color Color of the text labels for the scale bar. label-font Font of the label texts. label-halo-size Size, in pixels, of the halo around the label texts. label-position Position of the label. Possible values are BOTTOM and TOP. transparency Percentage value for transparency. 0 means opaque and 100 means full transparency. font-size Size of the font used to plot label text strings.

Legend Component Prints the map legend on the PDF. The legend is printed as a rectangular area with one or more columns of text description and an image as defined by the theme styles. It uses the following properties:

74

Print to PDF

themes-to-exclude List of themes to exclude from the legend. width Width of the legend. height Height of the legend. border-width Border width of the legend. border-color Color to use when plotting the legend border. legend-entry-width Width of individual entries in the legend (17 pixels by default). legend-entry-height Height of individual entries in the legend (14 pixels by default). font-family Font family name to display legend entry text strings. font-size Size to use for the font defined with the property font-family. fonts-installation-folders Path of the folder containing the definition of the fonts to use.

Map Component The following properties are used by the map component for printing:

border-margin Margin to be left before plotting the border of the map component. border-width Width of the border drawn around the map. width Width of the map component in (pixels). height Height of the map component in pixels extract-new-map Boolean value indicating whether to retrieve fresh copies of the maps before printing. fill-background Boolean value indicating whether to fill the background with a background color defined by the property fillcolor. border-color Color of the border line as it appears around the map component.

Print to PDF

75

map-mbr-precision Number of decimal numbers to use while drawing the map coordinates around the map component (4 digits by default). map-mbr-font-size Size of the font used to draw the map coordinates around the map component (5 by default). map-mbr-format Format to use while plotting the map coordinates around the map component. The values are:

DECIMAL-DEGREES Map coordinates are printed in decimal degrees. NATIVE Map coordinates are printed in the format:
long,lat For example: -120.061, 34.672

DEG_MIN_SEC Map coordinates are printed in the format:

deg:min:sec C where deg is the corresponding decimal degrees, min is the corresponding decimal minutes, sec represents the decimal seconds in the coordinate, and C is one of the characters W, N, E, S. For example: 39:39:35.577 N, 124:24:25.764 W

map-mbr-layout How coordinates are drawn around the map. The values are:

INLINE_LAYOUT Both coordinates are drawn horizontally with x and y separated by a semicolon. STACKED Both coordinates are drawn horizontally with y one below x. CORNERED The x coordinates are drawn horizontally and the y coordinates are drawn vertically.

print-image-blocks Boolean value indicating whether to print the image blocks and WMS images on the map.

Print Text Component Lets you place text blocks in the PDF document. In addition to the positional properties (x, y, width, height, border-width, border-margin), it has the following properties:

76

Print to PDF

font-style Font style to use. Value are PLAIN, BOLD, ITALIC and BOLDITALIC. font-family Font family name. font-size Size of the of the fonts. text-color Color to use while printing the text block. text-align Alignment of the text (left, right, center).

North Arrow Print Component Defines properties used to plot the North arrow on the generated PDF document. It has the following properties:

fill-color Color used to fill the area occupied by the North arrow in the PDF document. transparency Percentage of transparency to apply to the North arrow. 0 means opaque and 100 means full transparency. arrow-type Property that defines the type of arrow to use. The values are 1 (default), 2, or a fully qualified Java class name (for example, com.erdas.ade.printing.component.renderers.northarrow.North ArrowImageType). image-url URL of the image to use as the image of the North arrow.

<subcomponents> Element Syntax

The <subcomponent> has zero or more print components, which become the children of this defining component. Example:
<subcomponents> <subcomponent> <provider> ... </provider> <properties> ... </properties> <!-Print subcomponents can define their own subcomponents that are rendered on their parent's drawing area. These subcomponents should appear here if present. --> <subcomponents> ...

Print to PDF

77

</subcomponents> </subcomponent> </subcomponents>

Properties Section

The properties section is made of a <properties> xml element. Properties defined in this section are global properties. They are inherited by all components and subcomponents defined in the template. However, components and subcomponents can overwrite the global properties by defining their own version of the properties.

Template Global Properties

The global properties is the last section of a print template. It is a <properties> xml element. Any property defined here, as indicated earlier, is inherited by the different components and their subcomponent hierarchies. The properties in use are as follows:

fill-color Background color for the map. Color values are defined in the format:
#rrggbb where rr represents red, gg represents green, and bb represents the blue component of the color. These are hexadecimal values from 00 through ff.

page-size Page size for the template. The page sizes are defined in a separate page size template (page-sizes.xml).

For more information, see Page Sizes Template.

orientation Orientation of the pages in the printed document. Valid values are portrait and landscape. border-margin Border margin of the printed pages. This amount of space is left on all sides of the page. border-width Width/thickness of the border around the printed map. border-color Color of the border line as it appears around the printed map. description User friendly description of this template. This description appears in the Print dialog box.

78

Print to PDF

fill-background Boolean indicating whether to fill the background with of a user-defined color (see also fill-color above). The background is filled when this value is set to True and the property fill-color is defined. maintain-scale Boolean value indicating whether to maintain the same scale on both the printed map and on the map in the current Viewer. document-title Text string that becomes the title of the PDF document to be generated. document-subject Text string that becomes the subject of the PDF document to be generated. document-author Author of the document. This text is the value of the field subject of the PDF document that is generated. document-keywords Text string to fill the keyword field of the PDF document to be generated. print-image-blocks Boolean value indicating whether to print the image blocks and WMS images on the map.

Page Sizes Template

The Page Sizes template is an XML file (page-sizes.xml) containing a definition of the different page sizes you can use when generating the PDF. The file contains a sequence of page size definitions such as:
<page-size name="LETTER"> <width>612</width> <height>792</height> </page-size>

The page size template is located in this directory:

<IMAGINE_HOME>\adehome\printing\resources

The width and height of a page are expressed in user units that correspond by default to the typographic measurement unit known as a dot. There are 72 dots in an inch (dpi). Printing is based on the Adobe Acrobat PDF format and, depending on the version of the PDF, their page size limits. For PDF versions up to 1.3, the minimum page size is 72 x 72 units (1 x 1 in). For later versions of the PDF, the minimum size is 3 x 3 units (approximately 0.04 x 0.04 in), and the maximum size is 14,400 x 14,400 units (approximately 200 x 200 in). A page size definition is composed of the different parts as follows:

Print to PDF

79

name attribute The name to use for this page size. This attribute must be unique within the template file. width element The width of the generated PDF document. It is a string representation of the float value of the width of the page in user units (dots). height element The height of the generated PDF document. It is a string representation of a float value for the height of the page in user units (dots).

Predefined Page Sizes

The predefined page size definitions are listed in this table.

Table 6: Predefined Page Size Definitions

Name LETTER NOTE LEGAL TABLOID EXECUTIVE POSTCARD A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 B0 B1 B2 B3 B4 B5 Width 612 540 612 792 22 283 2384 1684 1191 842 595 420 297 210 148 105 73 2834 2004 1417 1000 708 498 Height 792 720 1008 1224 756 416 3370 2384 1684 1191 842 595 420 297 210 148 105 4008 2834 2004 1417 1000 708

80

Print to PDF

Table 6: Predefined Page Size Definitions

Name B6 B7 B8 B9 B10 ARCH_E ARCH_D ARCH_C ARCH_B ARCH_A FLSA FLSE HALFLETTER _11X17 ID_1 ID_2 ID_3 LEDGER CROWN_QUARTO LARGE_CROWN_QUARTO DEMY_QUARTO ROYAL_QUARTO CROWN_OCTAVO LARGE_CROWN_OCTAVO DEMY_OCTAVO ROYAL_OCTAVO SMALL_PAPERBACK PENGUIN_SMALL_PAPERBA CK PENGUIN_LARGE_PAPERBA CK Width 354 249 175 124 87 2592 1728 1296 864 648 612 648 396 792 242.65 297 354 1224 535 569 620 671 348 365 391 442 314 314 365 Height 498 354 249 175 124 3456 2592 1728 1296 864 936 936 612 1224 153 210 249 792 697 731 782 884 527 561 612 663 504 513 561

Print to PDF

81

82

Print to PDF

Keyin Commands
This table describes all of the keyin commands that are available for IMAGINE Enterprise Editor and ERDAS ADE products. The first four columns reflect the applicability of each command to these products. The commands are arranged alphabetically in the Keyin column.

Keyin Commands

Table 7: Keyin Commands

ADE-M yes yes ACTIVATE GPS ABOUT Open the About dialog. ABOUT Keyin Description Usage

IEE

ADE-E

ADE-R

Activates and connects to the GPS ACTIVATE GPS device using the current COM port and baud rate settings Adds a theme name to the available theme list Adds a dynamically defined theme ADD AVAILABLE THEME=DATASOURCE_NAME, THEME_NAME ADD DYNAMIC THEME=DATASOURCE,THEMEN AME,TABLE,GEOM_COLUMN, KEY_COLUMN,QUERY,SRID,FE ATURE_STYLE_NAME,LABEL_ COLUMN,LABEL_STYLE_NAME ADD FEATURE TO LIVE LAYER ADD FEATURE TO PRIMITIVE Adds a reference project to the current ADD REFERENCE PROJECT or map. ADD REFERENCE PROJECT=FILEPATH Animate all edits since last save Associate a topology primitive with a feature Open a geo-referenced imagery file ANIMATE EDITS ASSOCIATE FEATURE Allows the user to open a georeferenced imagery file for use within the application

yes

yes

yes

yes

ADD AVAILABLE THEME

yes

yes

ADD DYNAMIC THEME

yes yes ADD REFERENCE PROJECT ADD FEATURE TO PRIMITIVE

yes

yes

ADD FEATURE TO LIVE LAYER

Adds a feature to the live feature transient layer for native rendering Add a feature to a topology primitive

yes

yes

yes

yes

yes yes yes

yes

yes

ANIMATE EDITS ASSOCIATE FEATURE ATTACH IMAGE

yes

yes

yes

yes

83

84

Table 7: Keyin Commands (Continued)

ADE-M ATTACH THEME yes yes CAPTURE CONTROL POINTS yes CAPTURE GPS FEATURE Take the current active theme and style settings and starting placing a feature of that type, using the GPS events. Takes the current GPS point and simulates a left click using that point. Any current active drawing tools will receive and process this point. Saves the current map view to the system clipboard BUFFER GEOMETRY Creates a buffered geometry AXIS LOCK Draw geometries only in straight lines along the x and y axis Extracts the active theme ATTACH THEME AXIS LOCK=TRUE/FALSE BUFFER GEOMETRY=BUFFER_ DISTANCE Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

Captures control points and warps the CAPTURE CONTROL POINTS selected imagery to those points CAPTURE GPS FEATURE

yes

CAPTURE GPS POINT

CAPTURE GPS POINT

yes CHANGE FEATURE STYLE

yes

CAPTURE SCREEN

CAPTURE SCREEN

yes

yes

yes

CHANGE FEATURE STYLE, Tool used to change a selected features datasource, theme and style. CHANGE FEATURE STYLE=TRUE/FALSE This tools will attempt to copy any common attributes execpt the KEY column. There are two signatures for this tool, The first, CHANGE FEATURE STYLE will try to copy the attributes, The second CHANGE FEATURE STYLE=TRUE/FALSE can be used to define whether or not to copy the attributes Clears the list of available themes CLEAR AVAILABLE THEME Clears a clipping polygon for an image CLEAR CLIP POLYGON=fileName

yes

yes

yes

yes

CLEAR AVAILABLE THEME CLEAR CLIP POLYGON

Keyin Commands

yes

Table 7: Keyin Commands (Continued)

ADE-M CLEAR GPS MESSAGE yes yes CLEAR IMAGE REGISTRY yes yes yes CLOSE IMAGE BLOCK yes CLOSE IMAGES Closes the specified image block Closes all the currently attached imagery Closes the specified reference map CLEAR TRANSIENTS Clears any transient elements CLEAR MOUSE CROSSHAIR POINT Clears the current mouse crosshair point CLEAR LIVE LAYER Clears the live feature transient layer CLEAR HILITES Clears the current hilite list CLEAR HILITES CLEAR GPS POINT Clears the current GPS point CLEAR GPS POINT Clears the current GPS message CLEAR GPS MESSAGE Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
Clears the current image block registry CLEAR REGISTRY CLEAR LIVE LAYER CLEAR MOUSE CROSSHAIR POINT CLEAR TRANSIENTS CLOSE IMAGE BLOCK=FILEPATH Closes all the currently attached imagery within the the application client. CLOSE REFERENCE MAP=FILEPATH or CLOSE REFERENCE MAP=MAP_ID CLOSE REMOTE PROJECT MAP CLOSE SHAPE FILE=FILEPATH Commit all the saved changes to the datasource Open up the dialog that allows you to configure the primary and secondary filters COMMIT CHANGES CONFIGURE FILTERS CLOSE REFERENCE MAP CLOSE REMOTE PROJECT MAP CLOSE SHAPE FILE yes yes CONFIGURE FILTERS COMMIT CHANGES Close the specified remote project map Closes the specified shapefile yes CONFIGURE GPS Opens the GPS settings dialog to allow CONFIGURE GPS user to modify the current GPS device and collection settings Load map data from a specified file LOAD DIRECTORY=FILEPATH CONNECT DIRECTORY

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

85

86

Table 7: Keyin Commands (Continued)

ADE-M yes CONNECT GPS Opens the Connect to GPS Device dialog or connects directly to the GPS Connect to a GPS device using the last known COM port and baud rate Connects to a specified application server as defined by the passed URL Start the command to copy an SDO_GEOMETRY feature CONNECT ENTERPRISE Opens the enterprise connection wizard CONNECT ENTERPRISE CONNECT GPS or CONNECT_GPS=PORT_NO, BAUDRATE,TRUE/FALSE CONNECT GPS DEFAULT CONNECT SERVER=URL COPY GEOMETRY Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes CONNECT SERVER yes yes CREATE DATASOURCE COPY PARALLEL COPY GEOMETRY

yes

CONNECT GPS DEFAULT

yes

yes

yes

yes

yes

yes

yes

yes

Copies a selected geometry parallel to INCOMPLETE DO NOT USE the original geometry Creates a datasource based on the information specified CREATE DATASOURCE=NAME,HOST,SID ,PORT,USERNAME,PASSWORD, MODE,NO_OF_MAPPERS CREATE REMOTE PROJECT or CREATE REMOTE PROJECT=NAME,DESCRIPTION ,FILEPATH Creates a remote project by opening up the create remote project wizard or using the passed project parameters and the current feature cache Opens a dialog which allows the user to create a TFW grid Create a new (Oracle Workspace manager) Workspace. CREATE TFW GRID CREATE WORKSPACE=dataSourceName, workspaceName or CREATE WORKSPACE=workspaceName The second option used the active datasource

yes

yes

yes

yes

yes

CREATE REMOTE PROJECT

yes CREATE WORKSPACE

CREATE TFW GRID

yes

yes

yes

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M DATABASE DIRECT QUICK CONNECT yes yes DELETE Deletes the currently selected features. If there are no features selected it will initiate a selection tool to pick the features for deletion. Delete the active (Oracle Workspace manager) Workspace. Displays a description of a specified keyin, along with the keyins usage Destroys the current map cache Destroys the server session Destroy the servlet session on exit Starts the difference polygon command that requires the user to select a polygon geometry as a master, and then determine the difference with subsequently selected polygon geometries to the master geometry DELETE DEACTIVATE GPS Disconnect from the GPS device DEACTIVATE GPS Connect directly to the specified Oracle database instance Keyin Description Usage DATABASE DIRECT QUICK CONNECT=HOST,INSTANCE,PO RT,SCHEMA,MAPNAME

IEE

ADE-E

ADE-R

Keyin Commands
DELETE WORKSPACE DESCRIBE KEYIN yes yes yes yes DIFFERENCE POLYGON DESTROY SERVLET SESSION ON EXIT DESTROY SERVER SESSION DESTROY MAP CACHE DELETE WORKSPACE DESCRIBE KEYIN=KEYIN DESTROY MAP CACHE DESTROY SERVER SESSION DESTROY SERVLET SESSION ON EXIT=TRUE/FALSE DIFFERENCE POLYGON yes DISABLE THEME Disable (Turn off) a specified theme for DISABLE a specified datasource THEME=DATASOURCE_NAME, THEMENAME Disassociate a feature from a topology DISASSOCIATE FEATURE primitive Close the connection to the GPS devices DISCONNECT GPS yes DISASSOCIATE FEATURE DISCONNECT GPS

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

87

88

Table 7: Keyin Commands (Continued)

ADE-M DOWNLOAD EDITS yes DRAW CLIP POLYGON DYNAMICALLY SEGMENT LINE Starts the selection command to perform a dynamic segmentation EDIT FEATURE ATTRIBUTES Start a selection command to select geometry and display its attributes for edit Starts a tool to draw the clipping polygon for an image DRAG MAP Start the DragMap command DRAG MAP DRAW CLIP POLYGON=fileName DYNAMICALLY SEGMENT LINE=DistanceAlongLineTo Segment EDIT FEATURE ATTRIBUTES Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

Tool to download an operation list from DOWNLOAD EDITS=file on server the app server

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

ENABLE THEME

Enable (Turn on) a specified theme for ENABLE a specified datasource THEME=DATASOURCE_NAME, THEMENAME Executes all keyins listed in a given file EXECUTE KEYIN SCRIPT=fileNameContaining Keyins Exits the application EXIT

yes

yes

yes

EXECUTE KEYIN SCRIPT

yes yes yes EXPORT MAP AS IMAGE EXPORT KEYINS EXPLICITLY EXTRACT

yes

yes

EXIT

yes

yes

yes

Extract geometries from the current EXPLICITLY EXTRACT datasource for the current extract MBR Exports all known keyins to a tab delimited text file Opens a dialog to allow the user to select a file to which they wish to export the current screen map as a PNG file Opens the remote project export wizard EXPORT KEYINS=fileName EXPORT MAP AS IMAGE

yes

yes

yes

yes

Keyin Commands
yes

EXPORT REMOTE PROJECT

EXPORT REMOTE PROJECT

Table 7: Keyin Commands (Continued)

ADE-M EXPORT SHAPE FILE Opens a dialog box to select a directory name to export the current map data to as shape files. The names of each theme in the map will become the name of the shape files Opens a dialog box to select a file name to export the active theme to a shape file Keyin Description Usage EXPORT SHAPE FILE / EXPORT SHAPE FILE=directoryName / EXPORT SHAPE FILE=directoryName,FALSE (FALSE=do not export attributes to dbf file) EXPORT THEME TO SHAPE FILE / EXPORT THEME TO SHAPE FILE=fileName / EXPORT THEME TO SHAPE FILE=fileName,FALSE (FALSE=do not export attributes to dbf file)

IEE

ADE-E

ADE-R

Keyin Commands
EXPORT THEME TO SHAPE FILE EXPORT TO SERVER DATABASE This command will export the currently EXPORT TO SERVER loaded map to a datasource defined in DATABASE=exportDatasource Name,newMapName the http server. THIS ONLY WORKS FOR SDO_GEOMETRY THEMES to a HTTP server Start the tool that extends two linear SDO_GEOMETRY features to their intersection point Extract geometries only for the currently selected theme for the current extract MBR Zoom to the extent of the extracted geometries Zoom to the extent of the extracted geometries FOR INTERNAL USE ONLY. Tells the application that it has saved data to the database and requires a COMMIT or ROLLBACK FOR INTERNAL USE ONLY EXTEND TO INTERSECTION yes EXTEND TO INTERSECTION EXTRACT ACTIVE THEME EXTRACT ACTIVE THEME yes FIT VIEW yes FLAG COMMIT ROLLBACK FIT VIEW FIT VIEW FIT VIEW

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

89

90

Table 7: Keyin Commands (Continued)

ADE-M yes FLAG SAVE Sets the save status indicating that a save has occurred but no commit/rollback has occurred Forces all the features in the current project to be editable FLAG SAVE Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes yes FORCE TOPOLOGY REBUILD

yes

FORCE EDITABLE DISCONNECTED PROJECT

FORCE EDITABLE DISCONNECTED PROJECT

yes

yes

yes

Rebuild all topology features from their FORCE TOPOLOGY REBUILD primitives in cache

yes

yes

FUNCTION NOT IMPLEMENTED Simple keyin to allow developers to get FUNCTION NOT IMPLEMENTED YET UI complete without having the YET function complete. GARBAGE COLLECT yes yes yes yes GET ACTIVE WORKSPACE NAME yes yes yes yes yes GET ACTIVE Z GET ACTIVE THEME GET ACTIVE STYLE GET ACTIVE MAP GET ACTIVE DATASOURCE Returns the currently active datasource Gets the currently active map name Gets the active style Returns the currently active theme Gets the active workspace (Oracle Workspace Manager). Gets the current z or height value for placing 3D geometies Collect the JVM garbage GARBAGE COLLECT GET ACTIVE DATASOURCE GET ACTIVE MAP GET ACTIVE STYLE GET ACTIVE THEME GET ACTIVE WORKSPACE NAME GET ACTIVE Z GET AGGRESSIVE SELECTION GET ALLOW TOPO ISO MOVES Indicates whether or not antialiasing is GET ANTIALIASED in use Indicates whether or not axis lock is in GET AXIS LOCK use

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

GET AGGRESSIVE SELECTION Indicates whether or not aggressive selection is in use GET ALLOW TOPO ISO MOVES Indicates whether or not moving isolated nodes is allowed GET ANTIALIASED GET AXIS LOCK

yes

yes

yes

yes

yes

Keyin Commands

yes

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes yes yes yes yes yes GET DATABASE CONNECTION GET COORDINATE UNIT FACTOR GET COMMIT ON SAVE GET COLOR VALUE INTERNAL USE ONLY GET CLIENT CONTEXT Returns a handle of the client context object GET CENTER Y Gets the map centre y coordinate GET CENTER Y GET CLIENT CONTEXT INTERNAL USE ONLY GET CENTER X Gets the map centre x coordinate GET CENTER X GET BACKGROUND COLOR Returns the current background color Keyin Description Usage GET BACKGROUND COLOR

IEE

ADE-E

ADE-R

Keyin Commands
Indicates whether or not committing on GET COMMIT ON SAVE every save is in use Gets the coordinate readout unit factor GET COORDINATE UNIT for displaying coordinates FACTOR GET COORDINATE UNIT NAME Gets the coordinate readout unit name GET COORDINATE UNIT NAME for displaying coordinates Gets the current connection for a specified datasource Gets the default directory in which the application is executing. Inquires whether the application is set to paint bounding rectangles for the extract rectangle and the MBR of themes as defined in the USER_SDO_GEOM_METADATA GET DATABASE CONNECTION=DATASOURCE_ NAME GET DEFAULT DIRECTORY GET DISPLAY BOUNDING BOXES GET DEFAULT DIRECTORY yes GET DISPLAY BOUNDING BOXES yes GET DRAW GEOGRAPHIC GRID Gets the current setting for whether the GET DRAW GEOGRAPHIC GRID viewer is to draw a dynamically calculated geographic grid on a projected dataset Inquires whether the application will GET DRAW HANDLES draw square boxes at the vertices of a geometry when selected yes GET DRAW HANDLES

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

91

92

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes yes yes yes yes yes GET FEATURE INFO yes yes GET FLATTEN READONLY THEMES GET FEATURE INFORMATION GET EXPLICIT SIZE GET EXPLICIT EXTRACT GET EXPLICIT CENTER Y GET EXPLICIT CENTER X Gets the center X for the position that will be used to extract data Gets the center Y for the position that will be used to extract data Indicates whether or not the application is explicitly extracting GET ENDPOINT MODE PIXELS Indicates whether or not the current endpoint size mode is in pixels GET ENDPOINT MODE DISTANCE Indicates whether or not the current endpoint size mode is in distance GET ENDPOINT DIAMETER Returns the current diameter of endpoints GET ENDPOINT COLOR Returns the endpoint color as a HEX number eg FFFFFF GET ENDPOINT COLOR GET ENDPOINT DIAMETER GET ENDPOINT MODE DISTANCE GET ENDPOINT MODE PIXELS GET EXPLICIT CENTER X GET EXPLICIT CENTER Y GET EXPLICIT EXTRACT Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

Gets the map size for the position that GET EXPLICIT SIZE the application will use to extract data Prepares the application to select geometry and display its attributes GET FEATURE INFO

yes

yes

yes

Tells the application to select a feature GET FEATURE INFORMATION and display its attributes Asks whether the application is to fetch GET FLATTEN READONLY any readonly themes as one image as THEMES opposed to a separate image per theme Gets the current color for drawing the geographic grid Gets the status of a GPS GET GEOGRAPHIC GRID COLOR GET GPS STATUS returns (0=Not connected, 1=Connected with quality reading, 2=Connected with poor quality)

yes

yes

yes

yes

yes

GET GEOGRAPHIC COLOR GET GPS STATUS

Keyin Commands

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes yes yes GET IMAGERY EDIT MAINTAIN ASPECT RATIO yes yes GET LIVE THEME EXTRACT PERIOD GET IMPLICIT BACKGROUND GET HILITE COLOR Returns the highlight color being used within the application GET GRID VISIBLE Asks the application if it is to draw the grid if grid lock is on GET GRID MINOR Returns the current grid minor being used within the application GET GRID MAJOR Returns the current grid major being used within the application GET GRID MAJOR GET GRID MINOR GET GRID VISIBLE GET HILITE COLOR GET GRID LOCK Indicates whether or not the application is using grid lock GET GRID LOCK Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
Used to ask the application whether an GET IMAGE EDIT MAINTAIN image edit should maintain the aspect ASPECT RATIO ratio of the image Returns the implicit background GET IMPLICIT BACKGROUND Gets the period of time after which the GET LIVE THEME EXTRACT application will automatically extract a PERIOD live theme GET MAX SNAP VISIBLE SCALE GET POLYGON ENGINE MERGE HOLES Used to set if the polygon topology engine should merge holes into an encompassing geometry GET POLYGON ORIGINAL Used to define if original geometries are superior to new ones. If an original GEOMETRIES SUPERIOR geometry is superior, then when a new geometry overlaps an old, the boundaey of the original polygon is maintained. If the original geometry is not superior then the a newly placed overlapping geometry will cut into the original ones. GET POLYGON ORIGINAL GEOMETRIES SUPERIOR yes yes GET POLYGON ENGINE MERGE HOLES GET MAX SNAP VISIBLE SCALE Get the maximum visible scale for vertex points yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

93

94

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes GET RESOLVE DANGLES END GET RELEASE LOCKS ON EXIT Indicates whether the application is releasing database locks on exit GET PRIMARY FILTER Returns the current primary selection filter mode GET PRIMARY FILTER GET RELEASE LOCKS ON EXIT Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

Returns a true or false value indicating GET RESOLVE DANGLES END whether the application is resolving end dangles Returns a true or false value indicating GET RESOLVE DANGLES whether the application is resolving START start dangles Indicates whether or not the application is resolving polygons Indicates whether or not the application is currently resolving splits or not Asks ADEMobile whether it is allowed to rotate text GET RESOLVE POLYGONS GET RESOLVE SPLITS

yes

yes

yes

yes

GET RESOLVE DANGLES START GET RESOLVE POLYGONS GET RESOLVE SPLITS

yes yes

yes

yes

yes

yes

yes

yes

yes yes GET RUBBER BAND LOCK

yes

yes

GET ROTATE TEXT

GET ROTATE TEXT

yes

yes

yes

Returns a true or false value indicating GET RUBBER BAND LOCK the application whether or not the application is to use rubber band lock Get the current view map scale based on the current active theme GET SCALE Returns the the actual DPI value being GET SCREEN DPI used by the application Returns the current DPI mode being used by the application (Default (1) or Custom (0)) Returns the units of measurement used to calulate the custom screen DPI (if any) GET SCREEN DPI MODE

yes yes yes GET SCREEN DPI GET SCREEN DPI MODE

yes

yes

yes

GET SCALE

yes

yes

yes

yes

yes

yes

Keyin Commands
yes

yes

yes

yes

GET SCREEN DPI UNITS

GET SCREEN DPI UNITS

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes yes yes GET SHOW TOOLTIP IN DRAW MODE GET SHOW TOOLTIP IN SELECT MODE GET SHOW TOOLTIP IN VIEW MODE yes yes yes GET SNAP MODE GET SNAP LOCK GET SIZE GET SHOW SCALE BAR Asks the renderer if the scalebar is being rendered GET SHOW ENDPOINTS Indicates whether the application is painting endpoints GET SHOW ALLPOINTS Indicates whether or not the application is painting all endpoints GET SECONDARY FILTER Returns the current secondary selection filter mode GET SCREEN WIDTH Returns the current physical width of the screen to calculate the DPI GET SCREEN WIDTH GET SECONDARY FILTER GET SHOW ALLPOINTS GET SHOW ENDPOINTS GET SHOW SCALE BAR Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
Returns a true or false value indicating GET SHOW TOOLTIP IN DRAW MODE whether or not the editor is currently showing tooltips in draw mode Returns a true or false value indicating GET SHOW TOOLTIP IN SELECT MODE whether or not the editor is currently showing tooltips in select mode Returns a true or false value indicating GET SHOW TOOLTIP IN VIEW MODE whether or not the editor is currently showing tooltips in view mode Gets the current size of the map Indicates whether or not the application is using snap lock or not Gets the current snap mode for the application. (1=Endpoint, 2=MidPoint, 3=Perpendicular) GET SIZE GET SNAP LOCK GET SNAP MODE yes GET SRS GEOGRAPHIC POINT Projects a projected coordinate into the geographic coordinates the active themes SRID GET SRS GEOGRAPHIC POINT=X,Y

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

95

96

Table 7: Keyin Commands (Continued)

ADE-M yes GET SRS PROJECTED POINT Projects a Long/Lat coordinate into the GET SRS PROJECTED local projection based on the active POINT=Long,Lat themes SRID Gets all styles for a theme as a | delimeted String GET STRING STYLE NAMES=DATASOURCE_NAME, THEME_NAME Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

GET STRING STYLE NAMES

yes

yes

yes

yes

GET STROKE TOLERANCE

Gets the current stroke tolerance used GET STROKE TOLERANCE for placing stroked circles and arcs. the application will automatically stroke circles and arcs placed in a GeoDetic dataset Gets all the style names for a theme in GET STYLE the active datasource as a NAMES=THEME_NAME java.lang.String[] Finds out is a style for a datasource and theme is visible Checks whether the application is to label a theme Determines whether theme lock is on or off GET STYLE VISIBLE=DATASOURCE,THEME NAME,STYLENAME GET THEME LABELLED=DATASOURCE, THEMENAME GET THEME LOCK Indicates whether or not the GET USE PESSIMISTIC application is using pessimistic locking LOCKING Gets the username from the JVM Properties (If allowed) Returns the current user ordinate tolerance Returns the current vertex color being used within the application GET USER NAME GET USER PRECISION GET VERTEX COLOR

yes

yes

yes

yes

GET STYLE NAMES

yes

yes

yes

yes

GET STYLE VISIBLE

yes

yes

yes

yes

GET THEME LABELLED

yes yes GET USER NAME yes yes GET USER PRECISION GET VERTEX COLOR GET USE PESSIMISTIC LOCKING

yes

yes

yes

GET THEME LOCK

yes

yes

yes

yes

yes

yes

yes

yes

yes

Keyin Commands

yes

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M GET VERTEX DIAMETER yes GET WORKSPACE NAMES Gets the list of current workspaces (Oracle Workspace Manager) for the application to use. GET VIEWER PANEL Returns a handle of the viewer panel (client context) object GET VIEWER PANEL GET WORKSPACE NAMES Returns the current vertex diameter GET VERTEX DIAMETER Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes yes HAS EDITS Return the number of edits (UndoableOperation) applied in the cache for this session GROUP GEOMETRIES Tells the application to group the selected geometries GET ZOOM RATIO Returns the zoom ratio currently being GET ZOOM RATIO used within the application GROUP GEOMETRIES HAS EDITS yes HAS OPERATION CONTROLLER EDITS IMAGERY EDIT MOVE IMAGE IMAGERY EDIT RESIZE IMAGE HAS OPERATION CONTROLLER Determines whether the application has any edits in cache that have yet to EDITS be saved Click on an image block to move its position IMAGERY EDIT MOVE IMAGE=imageNameToEdit IMAGERY EDIT RESIZE Click on an image block and drag a corner of the image to reset the image IMAGE=imageNameToEdit extents Save the position of the current image IMAGERY EDIT SAVE IMAGE in a TFW file POSITION=imageName Opens a dialog box to select and import a shape file into the current active theme Initializes the the application viewer IMPORT SHAPE FILE IMAGERY EDIT SAVE IMAGE POSITION IMPORT SHAPE FILE INITIALIZE VIEWER INITIALIZE VIEWER

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

97

98

Table 7: Keyin Commands (Continued)

ADE-M yes INSERT VERTEX Starts the insert vertex command. This command will insert a vertex into a SDO_GEOMETRY object, or if the user selects a topology primitive (edge) will perform an update edge Starts the intersect polygon command INTERSECT POLYGON that requires the user to select a polygon geometry as a master, and then determine the intersection with subsequently selected polygon geometries to the master geometry Indicates whether or not the application is using aggressive selection IS AGGRESSIVE SELECTION INSERT VERTEX Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

INTERSECT POLYGON

yes

yes

yes

IS AGGRESSIVE SELECTION

yes yes IS THEME EDITABLE

yes

yes

yes

IS PENDING COMMIT ROLLBACK

Asks the application whether a commit IS PENDING COMMIT or rolback is required after a save ROLLBACK Indicates whether a specified theme is IS THEME set to be extracted in edit mode. This EDITABLE=DATASOURCE_ NAME,THEMENAME does not necessarily mean that the theme is actually editable Indicates whether a specified theme is IS THEME enabled (Turned On) ENABLED=DATASOURCE_ NAME,THEMENAME Indicates whether a specified theme readonly or locked by another user IS THEME READONLY=DATASOURCE_ NAME,THEMENAME LASOO FEATURES Tells the application to draw a shape that will be used to select all feature in the map based on an ANYINTERACT with the shape

yes

yes

yes

yes

yes

yes

yes

IS THEME ENABLED

yes

yes

yes

yes

IS THEME READONLY

yes

yes

yes

yes

LASOO FEATURES

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M yes LASSO CIRCLE LASSO CIRCLE Tells the application to draw a circle that will be used to select all feature in the map based on an ANYINTERACT with the shape Simulates a left click from the mouse Loads the given class name Loads a GeoTiff image into the the application viewer Creates and Attaches an Image Block into the application LEFT CLICK=X,Y LOAD CLASS=full.package.ClassName LOAD GEOTIFF IMAGE=fileName LOAD IMAGE BLOCK=fileName Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes LOAD GEOTIFF IMAGE LOAD IMAGE BLOCK LOAD IMAGE CENTER POINT LOAD IMAGE SCREEN yes LOAD JPG IMAGE LOAD JAR LOAD CLASS LEFT CLICK Opens any registered images that LOAD IMAGE CENTER POINT interact with the center point on screen Opens any registered imagery that LOAD IMAGE SCREEN interact with the current screen extents Loads a jar file (NOT YET SUPPORTED) Loads a JPEG image into the the application viewer. This JPEG image can have a TFW file for its georeference position LOAD JAR=jarFileName (Must be in classpath) LOAD JPEG IMAGE=fileName LOAD SERVER IMAGE Loads an image into the viewer from a LOAD SERVER IMAGE=fileName/LOAD SERVER directory on the server. The directory must be with respect to the server and IMAGE=fileName,true or false not the client. An optional boolean will tell the application to locate the image once opened

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

99

100

Table 7: Keyin Commands (Continued)

ADE-M LOAD SERVER IMAGE THREADED LOAD SERVER IMAGE Starts a thread that load a server image into viewer from a directory on THREADED=fileName the server. This will only download the possible viewable part of the image in the viewer resolution and the entire image. It will also load the image based on user zoom events. The directory must be with respect to the server and not the client Loads user configurable settings Tells the application to explicitly go to the database and extract all attribute information for TOPO_GEOMETRY themes Locates and displays an image block in the viewer and positions auxiliary viewers at the 4 corners if there are 4 auxiliary viewer open Opens the locate/search dialog LOAD SETTINGS DIALOG LOAD USER ATTRIBUTES Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes LOAD USER ATTRIBUTES

LOAD SETTINGS DIALOG

yes

yes

yes

yes

LOCATE IMAGE BLOCK

LOCATE IMAGE BLOCK=blockName

yes yes yes LRS GET MEASURE FACTOR LOCK GPS POINT

yes

yes

yes

LOCATE XYS

LOCATE XYS

yes

yes

yes

Set the current GPS Point location and LOCK GPS POINT=X,Y then centers the map at that point Used to set a unit factor to convert lrs measures to a unit other than that specified by the SRS Used to get the point measure mode for the LRS engine, 0=Reference all points, 1=Reference end points Used to get the precision for the calculation of lengths LRS GET MEASURE FACTOR

yes

LRS GET POINT MODE

LRS GET POINT MODE

yes

LRS GET PRECISION

LRS GET PRECISION

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M yes LRS GET SEGMENT MODE LRS GET SEGMENT MODE Used to get the segment measure mode for the LRS engine, 0=Reference each segment as if it were one, 1=Reference each segment separately Used to set a unit factor to convert lrs measures to a unit other than that specified by the SRS Used to set the point measure mode for the LRS engine, 0=Reference all points, 1=Reference end points Used to set the precision for the calculation of lengths LRS SET MEASURE FACTOR=x Keyin Description Usage

Keyin Commands
yes LRS SET MEASURE FACTOR yes LRS SET POINT MODE LRS SET POINT MODE=0/yes yes yes LRS SET SEGMENT MODE LRS SET PRECISION LRS SET PRECISION=x LRS SET SEGMENT Used to set the segment measure MODE=0/yes mode for the LRS engine, 0=Reference each segment as if it were one, 1=Reference each segment separately Draws a polygon and outputs the area MEASURE AREA and perimeter in the message field Command to select a feature and output the length/area/perimeter of a features geometry Draws a line and outputs the length in the message field Merges the active (Oracle Workspace manager) workspace into the parent workspace. Merges the edges from one node into another node removing the original node if possible MEASURE FEATURE yes yes MEASURE FEATURE MEASURE AREA yes MEASURE LENGTH MERGE ACTIVE WORKSPACE MEASURE LENGTH MERGE ACTIVE WORKSPACE yes MERGE NODE MERGE NODE

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

101

102

Table 7: Keyin Commands (Continued)

ADE-M yes MERGE NODE RESHAPE Merges the edges from one node into another node removing the original node if possible and reshapes the moved edges Starts the Merge Polygon command that requires the user to select a polygon geometry as a master, and then merge subsequently selected polygon geometries to the master geometry, disolving any common boundaries Starts a modify operation on a geometry. For topology primitives (Edge) this will only allow the user to update intermediate vertices on the edge MODIFY MERGE POLYGON MERGE NODE RESHAPE Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

MERGE POLYGON

yes

yes

yes

yes

MODIFY

yes

yes

yes

yes

MODIFY RESHAPE

Starts a modify with reshape operation MODIFY RESHAPE on a geometry. For topology primitives (Edge) this will only allow the user to update intermediate vertices on the edge Starts the command to move a topology edge Starts the command to move a topology edge and reshape the edge with the node Prepares the application to move a user selected geometry MOVE EDGE MOVE EDGE RESHAPE

yes yes MOVE EDGE RESHAPE

yes

yes

yes

MOVE EDGE

yes

yes

yes

yes

yes

yes

yes

MOVE GEOMETRY

MOVE FEATURE

yes

MOVE IMAGE BLOCK BOTTOM Moves an image block to the bottom of MOVE IMAGE BLOCK the display chain BOTTOM=FileName MOVE IMAGE BLOCK DOWN Moves an image block down the display chain MOVE IMAGE BLOCK DOWN=FileName

Keyin Commands

yes

Table 7: Keyin Commands (Continued)

ADE-M MOVE IMAGE BLOCK TOP MOVE IMAGE BLOCK UP yes MOVE ISOLATED NODE Starts the Move Isolated Node command for moving a topology isolated node Moves an image block up the display chain MOVE IMAGE BLOCK UP=FileName MOVE ISOLATED NODE, MOVE ISOLATED NODE=TRUE/FALSE (boolean tells the application to force the move even if it is moved to another face) MOVE NODE MOVE NODE RESHAPE Moves an image block to the top of the MOVE IMAGE BLOCK display chain TOP=FileName Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes MOVE NODE RESHAPE Starts the Move Node for moving a topology node and reshaping connected edges Moves a theme to the bottom in the display list MOVE NODE Starts the Move Node command for moving a topology node MOVE THEME BOTTOM MOVE THEME DOWN MOVE THEME TOP MOVE THEME UP yes OPEN ABOUT BOX NULL MOVE THEME BOTTOM=dsName,themeName Moves a theme down in the display list MOVE THEME DOWN=dsName,themeName Moves a theme to the top in the display MOVE THEME list TOP=dsName,themeName Moves a theme up in the display list Tells the application to go into an idle state. Opens the About dialog, which contains information regarding the current the application release MOVE THEME UP=dsName,themeName NULL OPEN ABOUT BOX yes OPEN ADE FILE Opens an file if the file path parameter OPEN ADE FILE or OPEN ADE is specified. Otherwise it will prompt FILE=FILEPATH the user to select the file

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

103

104

Table 7: Keyin Commands (Continued)

ADE-M OPEN ADE VIEWER DIALOG OPEN CONFIG DIALOG OPEN CONNECT DIALOG OPEN CREATE WORKSPACE DIALOG OPEN CUSTOMIZE DIALOG OPEN DATABASE CONNECT DIALOG OPEN DIALOG OPEN DISCOVER DIALOG yes OPEN DISPLAY SETTINGS Opens the specified dialog Opens the Connection dialog box for the application Opens the display settings dialog to allow the user to change the current viewer display settings Opens a dialog which allows the user to select what the file they want to open Opens the Customization dialog Opens a dialog to enter a Workspace name for the creation of a workspace. Opens the enterprise server connection wizard Opens the Configuration Dialog box OPEN CONFIG DIALOG OPEN CONNECT DIALOG OPEN CREATE WORKSPACE DIALOG OPEN CUSTOMIZE DIALOG Opens a cloned ViewerPanel in a Dialog box Keyin Description Usage OPEN ADE VIEWER DIALOG

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

Opens the oracle database connection OPEN DATABASE CONNECT wizard. DIALOG OPEN DIALOG=DIALOG_NAME OPEN DISCOVERY DIALOG OPEN DISPLAY SETTINGS

yes

yes

yes

yes

yes

yes

yes

OPEN FILE

OPEN FILE

yes

OPEN GPS POSITION WINDOW Opens the GPS position window to allow users to see the current GPS position information OPEN GRID SETTINGS

OPEN GPS POSITION WINDOW

yes

Opens the grid settings dialog to allow OPEN GRID SETTINGS the user to modify the current grid settings OPEN IMAGE MANAGER Opens the image manager which allows the user to edit/remove existing background imagery files within the the application client.

Keyin Commands
yes

OPEN IMAGE MANAGER

Table 7: Keyin Commands (Continued)

ADE-M OPEN IMAGE MANAGER DIALOG yes OPEN KEYIN FIELD Open the keyin field dialog which allows the user to enter and execute keyin commands Opens a dialog to select imagery to load into the application Opens the Locate Point dialog OPEN KEYIN FIELD Opens an Imagery management dialog OPEN IMAGE MANAGER box with a List of Loaded Imaged DIALOG Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
OPEN LOAD IMAGE DIALOG OPEN LOCATE DIALOG yes OPEN LOCKING AND PRECISION SETTINGS OPEN LOCKS DIALOG yes OPEN LOCKS SETTINGS Opens the Locks Dialog Opens the locks dialog that allows the user to configure the locks within the application OPEN LOAD IMAGE DIALOG OPEN LOCATE DIALOG Opens the locking and precision dialog OPEN LOCKING AND to allow user to change the current PRECISION SETTINGS locking and precision settings OPEN LOCKS DIALOG OPEN LOCKS SETTINGS OPEN LRS ENGINE SETTINGS DIALOG OPEN POLYGON ENGINE SETTINGS DIALOG OPEN PROJECT DIALOG yes OPEN REMOTE PROJECT Open the LRS Engine Settinbgs dialog OPEN LRS ENGINE SETTINGS DIALOG Opens the settings dialog box for the Polygon Engine Opens a dialog to load a project file Opens the specified remote project. If no project is specified then the user will be prompted to select a remote project Open the remote project manager Opens a dialog to allow the user to select the how to save the current map. OPEN POLYGON ENGINE SETTINGS DIALOG OPEN PROJECT DIALOG OPEN REMOTE PROJECT or OPEN REMOTE PROJECT=FILEPATH OPEN REMOTE PROJECT MANAGER OPEN SAVE AS DIALOG OPEN REMOTE PROJECT MANAGER OPEN SAVE AS DIALOG

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

105

106

Table 7: Keyin Commands (Continued)

ADE-M OPEN SEARCH DIALOG OPEN SEGMENTATION ENGINE DIALOG OPEN SERVER SHAPE FILE Opens a shape file on the server. The file path MUST be in relative terms to the server drive mounts. A second optional parameter tells whether it is to zoom to the opened file extents (Default=TRUE) Opens the Settings Dialog Opens a shape file and adds it as a new theme Opens the snap settings dialog to allow users to modify the current snapping settings Opens the theme control dialog Opens the Segmentation Engine Dialog Opens the search dialog OPEN SEARCH DIALOG OPEN SEGMENTATION ENGINE DIALOG OPEN SERVER SHAPE FILE=fullyQualifiedServerFilePath. shp, OPEN SERVER SHAPE FILE=fullyQualifiedServerFilePath. shp,TRUE/FALSE OPEN SETTINGS DIALOG OPEN SHAPE FILE=FILEPATH OPEN SNAPPING SETTINGS Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes yes yes OPEN SNAPPING SETTINGS OPEN SHAPE FILE

yes

OPEN SETTINGS DIALOG

yes

yes

yes yes OPEN WMS MANAGER

yes

yes

OPEN THEME CONTROL

OPEN THEME CONTROL

Open the WMS manager which allows OPEN WMS MANAGER the user to configure the WMS services running within the application. Pans the map in a specified direction (North, South, etc) Prepares the application to move the maps current centre x,y coordinate to a user selected point Tells the application to move the map to the east Tells the application to move the map to the north Tells the application to move the map to the south PAN=N/S/E/W/NE/NW/SE/SW PAN ABOUT POINT

yes PAN ABOUT POINT

yes

yes

PAN

yes

yes

yes yes yes PAN NORTH PAN SOUTH

yes

yes

PAN EAST

PAN EAST PAN NORTH PAN SOUTH

yes

yes

Keyin Commands

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes yes PLACE ARC Tells the application to start placing a PLACE ARC SDO_GEOMETRY Arc geometry for the active datasource, theme and style. If the theme is GeoDetic, the application will automatically stroke the arc into a linear geometry PLACE ATOMIC TOPO LINEAR Tell the application to draw a linear FEATURE TOPO_GEOMETRY feature for the active linear topo geometry theme and calculate all topological edits that would occur, and handle these edits in an atomic nature Tell the application to draw a polygonal PLACE ATOMIC POLYGONAL TOPO FEATURE TOPO_GEOMETRY feature for the active topology geometry theme and automatically calculate the topology primitive for the feature Tells the application to start placing a PLACE CIRCLE SDO_GEOMETRY Circle geometry for the active datasource, theme and style. If the theme is GeoDetic, the application will automatically stroke the circle into a linear polygon. The stroke tolerance for the stroking can be set using SET STROKE TOLERANCE=123 PAN WEST Tells the application to move the map to the west PAN WEST Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes PLACE ATOMIC LINEAR TOPO FEATURE yes PLACE ATOMIC POLYGONAL TOPO FEATURE yes PLACE CIRCLE

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

107

108

Table 7: Keyin Commands (Continued)

ADE-M yes PLACE CIRCLE CENTER Tells the application to start placing a SDO_GEOMETRY Circle by the center point for the active datasource, theme and style. If the theme is GeoDetic, the application will automatically stroke the circle into a linear polygon. The stroke tolerance for the stroking can be set using SET STROKE TOLERANCE=123 Tells the application to start placing a topology edge geometry for the active TOPOLOGY PRIMITIVE datasource, theme and style PLACE EDGE Keyin Description Usage PLACE CIRCLE CENTER;PLACE CIRCLE CENTER=radius

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

PLACE EDGE

yes

yes

yes

yes

PLACE INTERACT POLYGONAL Place a polygonal TOPO_FEATURE TOPO FEATURE by using an any interact for the drawn feature to the topology faces PLACE ISOLATED NODE Tells the application to start placing a topology node geometry for the active TOPOLOGY PRIMITIVE datasource, theme and style Tells the application to start placing a SDO_GEOMETRY line for the active datasource, theme and style.

PLACE INTERACT POLYGONAL TOPO FEATURE PLACE ISOLATED NODE

yes

yes

yes

yes

yes

yes

yes

yes

PLACE LINE

PLACE LINE

yes

yes

yes

yes

PLACE OBJECT

PLACE OBJECT Tells the application to place the relevant geometry type based on active theme type (SDO_GEOMETRY, Topology Primitive, TOPO_GEOMETRY etc) and the active style type (Point, Line, Polygon) Tells the application to start placing a SDO_GEOMETRY point geometry, that can be rotated, for the active datasource, theme and style PLACE ORIENTED POINT, PLACE ORIENTED POINT=ANGLE_IN_DEGREES

Keyin Commands
yes

yes

yes

yes

PLACE ORIENTED POINT

Table 7: Keyin Commands (Continued)

ADE-M yes PLACE POINT Tells the application to start placing a PLACE POINT SDO_GEOMETRY point for the active datasource, theme and style. Tell the application to draw a point TOPO_GEOMETRY feature for the active point topo geometry theme and calculate automatically add the isolated node primitive for the topo feature Tells the application to start placing a SDO_GEOMETRY polygon for the active datasource, theme and style. Tells the application to start placing a SDO_GEOMETRY Rectangle geometry for the active datasource, theme and style PLACE POINT TOPO FEATURE Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes PLACE POINT TOPO FEATURE yes PLACE POLYGON PLACE POLYGON yes PLACE RECTANGLE PLACE RECTANGLE, PLACE RETANGLE=width,height, PLACE RECTANGLE=width,height, position For position values use CC:Centre, LL:Lower Left, LR:Lower Right, UL:Upper left, UR:Upper Right,LHS:Centre Left, RHS:Centre Right, TOP:Top Centre, BOT:Bottom Centre yes PLACE STROKED ARC Tells the application to start placing a PLACE STROKED ARC SDO_GEOMETRY stroked Arc geometry for the active datasource, theme and style. If the active theme is GeoDetic. The stroke tolerance for the stroking can be set using SET STROKE TOLERANCE=123 Tells the application to start placing a stroked circle geometry into a linear polygon. The stroke tolerance for the stroking can be set using SET STROKE TOLERANCE=123 PLACE CIRCLE yes PLACE STROKED CIRCLE

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

109

110

Table 7: Keyin Commands (Continued)

ADE-M yes PLACE STROKED CIRCLE CENTER PLACE STROKED CIRCLE Tels the application to start placing a CENTER;PLACE STROKED stroked circle geometry into a linear polygon by chooseing the center point. CIRCLE CENTER=radius The redius of the circle can be set using a paramater. The stroke tolerance for the stroking can be set using SET STROKE TOLERANCE=123 Prints the current JAVA properties to the applciation log Prints the current map Prints out basic statistics for loaded themes Deletes the currently selected feature(s) Returns all datasource names available to Acquis Returns all the available maps for a given datasource Returns all the available themes for a specified datasource and theme Turns off the random styles Changes the styles of features to a randomly set style Tool to select an edge and start redigitizing the intermediate vertex points PRINT JAVA PROPERTIES PRINT MAP PRINT THEME STATS PURGE CHANGES QUERY DATASOURCE NAMES QUERY MAP NAMES=DATASOURCE QUERY THEME NAMES=DATASOURCE,THEME NAME RANDOM STYLES OFF RANDOM STYLES ON REIGITIZE EDGE Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes PRINT MAP yes yes yes yes yes QUERY THEME NAMES QUERY MAP NAMES QUERY DATASOURCE NAMES PURGE CHANGES PRINT THEME STATS

yes

PRINT JAVA PROPERTIES

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes yes yes REDIGITIZE EDGE RANDOM STYLES ON

yes

yes

yes

RANDOM STYLES OFF

yes

yes

yes

yes

yes

yes

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M yes REDIGITIZE GEOMETRY Tool to select a linear or polygonal geometry and start redigitizing from the selection point Redo the last undone edit Redo all undone edits Refreshed the active (Oracle Workspace manager) Workspace. REDO ALL REFRESH ACTIVE WORKSPACE REDO REIGITIZE GEOMETRY Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes REFRESH ACTIVE WORKSPACE REFRESH THEME LIST REGISTER IMAGERY REDO ALL REDO Tell the application to refresh the REFRESH THEME LIST themes in the current theme control list Opens a dialog box for the selection REGISTER IMAGERY of images that have TFW files, that can then be opens by point or range in the application Registers a single imagery file that can REGISTER IMAGERY FILE then be opened by point or range in the application Reloads available styles Reloads available themes Remove a valid backgound map removes a theme from the viewer Starts the remove vertex command. This command will remove a vertex from a SDO_GEOMETRY object, or if the user selects a topology primitive (edge) will perform an update edge Repaints the current view RELOAD STYLES RELOAD THEMES REMOVE BACKGROUND MAP=MAPNAME/MAPID REMOVE THEME=dsName,themeName REMOVE VERTEX REGISTER IMAGERY FILE RELOAD STYLES RELOAD THEMES yes REMOVE THEME yes REMOVE VERTEX REMOVE BACKGROUND MAP yes REPAINT VIEW REPAINT VIEW

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

111

112

Table 7: Keyin Commands (Continued)

ADE-M REPLAY GPS LOG yes RESTART yes yes RIGHT CLICK Simulate right click event. Viewer selection point not retained for processing Tells the application to rollback all the saved changes from the datasource Rolls back the active (Oracle Workspace manager) Workspace. Set the current rotation for the applications Viewer REVERSE GEOMETRY Restart the application RESTART RESET STATE NULL Tells the application to go into an idle state. RESET STATE NULL Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

Replays the GPS positioning based on REPLAY GPS LOG=FILEPATH an NMEA log file

yes

yes

yes

yes

yes

yes

yes

Reverses the points of a geometry of a REVERSE GEOMETRY feature RIGHT CLICK

yes

yes

yes

yes ROLLBACK WORKSPACE yes yes SAVE AS yes yes yes SAVE CHANGES SAVE COMMIT EXTRACT CHANGES SAVE AS ADE FILE SAVE ADE FILE ROTATE VIEW

yes

yes

yes

ROLLBACK CHANGES

ROLLBACK CHANGES ROLLBACK WORKSPACE ROTATE VIEW=ANGLE_IN_DEGREES

yes

yes

yes

yes

yes

Saves the current list of edits out to the SAVE ADE FILE currently opened file Opens a dialog which allows the user to select the file they wish to save to SAVE AS Save the current content of the view as SAVE AS ADE FILE an ADE File Tells the application to save all the edits made since the last save Performs a save, a commit and an extract in one command SAVE CHANGES SAVE COMMIT EXTRACT CHANGES

yes

yes

yes

yes

yes

yes

yes

yes

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M SAVE IMAGE AS JPG Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
Saves a loaded image block as a jpeg SAVE AS image. Useful for saving heavy GeoTiff JPEG=fileNameOfOriginalImage images as Jpeg images for ADEMobile (The saved filename will be the same the given filename but with a jpg extension) Saves the current edits our to currently SAVE REMOTE PROJECT opened remote project Saves all current settings out to disk Saves the application map data to a directory as a ADE file. SAVE SETTINGS SAVE TO DIRECTORY or SAVE TO DIRECTORY=FILEPATH yes yes SAVE TO DIRECTORY SAVE TOOL OPTIONS CONFIGURATIONS yes SEARCH SAVE SETTINGS SAVE REMOTE PROJECT Saves the current configuration for the SAVE TOOL OPTIONS Tool Options dialog CONFIGURATIONS Opens the search dialog which allows users to search and locate maps features SEARCH yes SEG GET CONSIDER SELF INTERSECTIONS SEG GET DANGLE TOLERANCE SEG GET INSERT VERTEX ACTIVE LINEAR Ask the Segmentation listener whether SEG GET CONSIDER SELF it is to consder self intersection in the INTERSECTIONS added geometry. Gets the dangle length tolerance for removing dangling geoemtries. Ask the Segmentation listener whether it is to insert a vertex in the active geometry during an AddSDOGeometryOperation. This is similar to splitting up the active geometry, but the resultant splits are added to the original geometry as a vertex. SEG GET DANGLE TOLERANCE SEG GET INSERT VERTEX ACTIVE LINEAR yes yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

113

114

Table 7: Keyin Commands (Continued)

ADE-M yes SEG GET INSERT VERTEX OTHER LINEAR SEG GET INSERT VERTEX Ask the Segmentation listener OTHER LINEAR whether it is to insert a vertex in the other geometries encountered during an AddSDOGeometryOperation. This is similar to splitting up the other geometries, but the resultant splits are added to the original geometry as a vertex. SEG GET INSERT VERTEX Ask the Segmentation listener OTHER LINEAR whether it is to insert a vertex in the other geometries encountered during an AddSDOGeometryOperation. This is similar to splitting up the other geometries, but the resultant splits are added to the original geometry as a vertex. Gets the segmentation tolerance for segmenting linear geometries. SEG GET SEGMENATION TOLERANCE Keyin Description Usage

IEE

ADE-E

ADE-R

yes

SEG GET INSERT VERTEX OTHER POLYGON

yes yes SEG GET SPLIT ACTIVE LINEAR SEG GET SPLIT ACTIVE LINEAR INTO MULTI

SEG GET SEGMENTATION TOLERANCE

Ask the Segmentation listener whether SEG GET SPLIT ACTIVE LINEAR it is to split the newly added geometry during an AddSDOGeometryOperation Ask the Segmentation listener whether it is to create multi geometry objects from the resultant splits of the added geometry during an AddSDOGeometryOperation. This is similar to splitting up the active geometry, but the resultant splits are combined into one MULTI geometry SEG GET SPLIT ACTIVE LINEAR INTO MULTI

yes

yes

SEG GET SPLIT OTHER LINEAR

Ask the Segmentation listener whether SEG GET SPLIT OTHER LINEAR it is to split other geometries encountered during an AddSDOGeometryOperation

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M yes SEG GET SPLIT OTHER LINEAR INTO MULTI Keyin Description Usage

Keyin Commands
SEG GET SPLIT OTHER LINEAR Ask the Segmentation listener whether it is to create multi geometry INTO MULTI objects from the resultant splits of other geometries during an AddSDOGeometryOperation. This is similar to splitting up the other geometries, but the resultant splits are combined into one MULTI geometry Tell the Segmentation listener to consder self intersection in the added geometry. Sets the dangle length tolerance for removing dangling geoemtries. SEG SET CONSIDER SELF INTERSECTIONS=TRUE/FALSE SEG SET DANGLE TOLERANCE=tolDoubleValue yes SEG SET CONSIDER SELF INTERSECTIONS SEG SET DANGLE TOLERANCE SEG SET INSERT VERTEX ACTIVE LINEAR yes yes Tell the Segmentation listener to insert SEG SET INSERT VERTEX a vertex in the active geometry during ACTIVE=TRUE/FALSE an AddSDOGeometryOperation. This is similar to splitting up the active geometry, but the resultant splits are added to the original geometry as a vertex. Tell the Segmentation listener to insert SEG SET INSERT VERTEX OTHER LINEAR=TRUE/FALSE a vertex in the other geometries encountered during an AddSDOGeometryOperation. This is similar to splitting up the other geometries, but the resultant splits are added to the original geometry as a vertex. In this case others refers to any other geometry encountered. (Theme Lock is supported) yes SEG SET INSERT VERTEX OTHER LINEAR

IEE

ADE-E

ADE-R

115

116

Table 7: Keyin Commands (Continued)

ADE-M yes SEG SET INSERT VERTEX OTHER POLYGON Keyin Description Usage

IEE

ADE-E

ADE-R

Tell the Segmentation listener to insert SEG SET INSERT VERTEX OTHER POLYGON=TRUE/FALSE a vertex in the other polygonal geometries encountered during an Add/UpdateSDOGeometryOperation. This is similar to splitting up the other geometries, but the resultant splits are added to the original geometry as a vertex. In this case others refers to any other geometry encountered. (Theme Lock is supported) Sets the segmentation tolerance for segmenting linear geometries. Tell the Segmentation listener to split the newly added geometry during an AddSDOGeometryOperation SEG SET SEGMENATION TOLERANCE=tolDoubleValue SEG SET SPLIT ACTIVE LINEAR=TRUE/FALSE

yes yes SEG SET SPLIT ACTIVE LINEAR SEG SET SPLIT ACTIVE LINEAR INTO MULTI

SEG SET SEGMENTATION TOLERANCE

yes

SEG SET SPLIT ACTIVE LINEAR Tell the Segmentation listener to create multi geometry objects from the INTO MULTI=TRUE/FALSE resultant splits of the added geometry during an AddSDOGeometryOperation. This is similar to splitting up the active geometry, but the resultant splits are combined into one MULTI geometry. SEG SET SPLIT OTHER LINEAR=TRUE/FALSE

yes

SEG SET SPLIT OTHER LINEAR Tell the Segmentation listener to split other geometries encountered during an AddSDOGeometryOperation. In this case others refers to any other geometry encountered. (Theme Lock is supported)

Keyin Commands

Table 7: Keyin Commands (Continued)

ADE-M yes Keyin Description Usage

Keyin Commands
SEG SET SPLIT OTHER LINEAR SEG SET SPLIT OTHER LINEAR Tell the Segmentation listener to INTO MULTI=TRUE/FALSE INTO MULTI create multi linear geometry objects from the resultant splits of other geometries during an AddSDOGeometryOperation. This is similar to splitting up the other geometries, but the resultant splits are combined into one MULTI geometry. In this case others refers to any other geometry encountered. (Theme Lock is supported) SELECT ACTIVE FEATURE SELECT ACTIVE THEME Prepares the application to set a user selected feature as the active feature SELECT ACTIVE FEATURE yes yes SELECT ACTIVE THEME Prepares the application to set the active theme based on a user selected theme Prepares the application to select multiple features Simulates a left click from the mouse Simulate right click event. Viewer selection point not retained for processing SELECT FEATURES SEND LEFT CLICK=X,Y SEND RESET yes yes yes SEND RESET SEND LEFT CLICK SELECT FEATURES yes yes SET ACTIVE DATASOURCE SEND RIGHT CLICK Simulates a right click from the mouse SEND RIGHT CLICK=X,Y Set the active datasource within the application Sets the specified map as the active map Sets the currently active map by specifying the map ID within the current map cache SET ACTIVE DATASOURCE=DATASOURCEN AME SET ACTIVE MAP=NAME SET ACTIVE MAP ID=yes yes SET ACTIVE MAP SET ACTIVE MAP ID

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

117

118

Table 7: Keyin Commands (Continued)

ADE-M SET ACTIVE MAP INDEX Sets the currently active map by specifying the map index within the current map cache Sets the active style within the application Sets the active text within the application Set the active theme Sets the current workspace (Oracle Workspace Manager) for the application to use. Sets the current z or height value for placing 3D geometies SET ACTIVE STYLE=STYLENAME SET ACTIVE TEXT=TEXT SET ACTIVE THEME=THEMENAME SET ACTIVE WORKSPACE NAME=datasource,workspacena me SET ACTIVE Z=zvalue SET AGGRESSIVE SELECTION=TRUE/FALSE SET ALL FILTERS OFF SET ALLOW TOPO ISO MOVES=TRUE/FALSE Tells the application whether or not to paint using antialiasing This keyin will set a user attribute (column value) on the currently selected features where possible Tells the application whether or not to use axis lock Sets the background color SET ANTIALIASED=TRUE/FALSE SET ATTRIBUTE FOR SELECTION=COLUMN_NAME, VALUE SET AXIS LOCK=TRUE/FALSE SET BACKGROUND COLOR=FFFFFF Keyin Description Usage SET ACTIVE MAP INDEX=yes

IEE

ADE-E

ADE-R

yes

yes

yes SET ACTIVE TEXT yes SET ACTIVE WORKSPACE NAME yes yes yes yes yes SET ATTRIBUTE FOR SELECTION yes yes SET AXIS LOCK SET BACKGROUND COLOR SET ANTIALIASED SET ALL FILTERS OFF SET ACTIVE Z SET ACTIVE THEME

yes

yes

yes

SET ACTIVE STYLE

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

SET AGGRESSIVE SELECTION Tells the application whether to use aggressive selection or not Removes any selection filters

yes

yes

yes

yes

yes

yes

SET ALLOW TOPO ISO MOVES Tells the application whether or not to allow the moving of isolated nodes

yes

yes

yes

yes

yes

yes

yes

yes

yes

Keyin Commands

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes SET BACKGROUND COLOR RGB SET CENTER X SET CENTER Y SET COMMIT ON SAVE SET CONNECT MODE Set the current connection mode Tells the application whether or not to commit automatically after every save Sets the centre y coordinate of the current map Sets the centre x coordinate of the current map Sets the current background color based on RGB values ranging from 0255 Keyin Description Usage SET BACKGROUND COLOR RGB=R,G,B SET CENTER X=XCOORD SET CENTER Y=YCOORD SET COMMIT ON SAVE=TRUE SET CONNECT MODE=0=Not Connected, 1=Connected Via HTTP Connection in ADERemote, 2=Connected to a HTTP Connection with the the application Applet,3=Connected to a local project, 4=Connected directly to Oracle

IEE

ADE-E

ADE-R

Keyin Commands
yes yes yes yes yes SET COORDINATE UNIT FACTOR SET COORDINATE UNIT NAME SET DEBUG LEVEL Sets the coordinate readout unit factor SET COORDINATE UNIT for displaying coordinates FACTOR=0.001 (for meters in a millimeter system) Sets the coordinate readout unit name SET COORDINATE UNIT for displaying coordinates NAME=Meter SET DEBUG LEVEL=LEVEL Sets the level of debugging information the application will return. (DEBUG | FATAL | FINEST) Level can be either DEBUG, FATAL or FINEST Sets the default directory in which the application is executing. Tells the application whether or not to destroy the servlet on exit SET DEFAULT DIRECTORY=DIRECTORY SET DESTROY SERVLET ON EXIT=TRUE/FALSE yes SET DEFAULT DIRECTORY yes SET DESTROY SERVLET ON EXIT

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

119

120

Table 7: Keyin Commands (Continued)

ADE-M yes SET DISPLAY BOUNDING BOXES Tell the application whether to paint bounding rectangles for the extract rectangle and the MBR of themes as defined in the USER_SDO_GEOM_METADATA Sets the current list of themes which SET DISPLAY THEME are to be painted within the application LIST=THEMEyes SET DRAW GEOGRAPHIC GRID=TRUE/FALSE SET DRAW HANDLES=TRUE/FALSE SET EDIT THEME LIST=LIST SET ENDPOINT COLOR=COLOR SET ENDPOINT COLOR RGB=R,G,B SET ENDPOINT DIAMETER=DIAMETER Toggles the current endpoint mode based on the boolean value passed SET ENDPOINT MODE DISTANCE=TRUE/FALSE Turns on or off the current endpoint SET ENDPOINT MODE PIXELS mode based on the boolean parameter Sets the current error message for the SET application ERROR=ERROR_MESSAGE Sets the center X for the position that the application will use to extract data SET EXPLICIT CENTER X=XCOORD SET DISPLAY BOUNDING BOXES=TRUE/FALSE Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes yes SET DRAW GEOGRAPHIC GRID Tells the viewer to draw a dynamically calculated geographic grid on a projected dataset SET DRAW HANDLES Tell the application whether to draw square boxes at the vertices of a geometry when selected Sets the current list of themes which can be edited Set the endpoint color Sets the current end point color for snaps points based on RGB values ranging from 0-255 Sets the diameter of endpoints within the application

yes

yes

yes

SET DISPLAY THEME LIST

yes

yes

yes

yes

yes

yes

yes yes yes SET ENDPOINT COLOR RGB SET ENDPOINT COLOR

yes

yes

yes

SET EDIT THEME LIST

yes

yes

yes

yes

yes

yes

yes yes yes SET ERROR yes SET EXPLICIT CENTER X SET ENDPOINT MODE DISTANCE SET ENDPOINT MODE PIXELS

yes

yes

yes

SET ENDPOINT DIAMETER

yes

yes

yes

yes

yes

yes

yes

yes

yes

Keyin Commands

yes

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes yes yes yes SET FLATTEN READONLY THEMES Tells the application to fetch any readonly themes as one image as opposed to a separate image per theme Sets the current color for drawing the geographic grid Sets the GPS message and color SET FLATTEN EDITS ON SAVE Flattens edits at save time SET FACES VISIBLE Tells the application whether or not to show faces SET EXPLICIT SIZE Sets the map size for the position that the application will use to extract data SET EXPLICIT EXTRACT Tells the application to only extract when prompted by the user SET EXPLICIT CENTER Y Sets the center Y for the position that the application will use to extract data SET EXPLICIT CENTER Y=YCOORD SET EXPLICIT EXTRACT=TRUE/FALSE SET EXPLICIT SIZE=MAPSIZE SET FACES VISIBLE=TRUE/FALSE SET FLATTEN EDITS ON SAVE=TRUE/FALSE SET FLATTEN READONLY THEMES=TRUE/FALSE Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes SET GPS MESSAGE SET GEOGRAPHIC COLOR SET GEOGRAPHIC GRID COLOR=FFFFFF SET GPS MESSAGE=MESSAGE, TRUE/FALSE for red/green SET GPS STATUS=0,1,2 (0=Not connected, 1=Connected with quality reading, 2=Connected with poor quality) Tells the application whether or not to use grid lock Sets the grid major within the application Sets the grid minor within the application SET GRID LOCK=TRUE/FALSE SET GRID MAJOR=GRID_MAJOR SET GRID MINOR=GRID_MINOR SET GPS STATUS Sets the status of a GPS device yes yes yes SET GRID MAJOR SET GRID MINOR SET GRID LOCK

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

121

122

Table 7: Keyin Commands (Continued)

ADE-M yes yes yes SET HILITE COLOR RGB Sets the current hilite color for selection based on RGB values ranging from 0-255 SET HILITE COLOR Sets the highlight color to be used within the application SET GRID VISIBLE Tells the application to draw the grid if grid lock is on SET GRID VISIBLE=TRUE/FALSE SET HILITE COLOR=FFFFFF SET HILITE COLOR RGB=R,G,B Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

SET IMAGE CLIP RECT

SET IMAGE CLIP Sets the clipping rectangle for an image. This rectangle should represent RECT=fileName,llx,lly,lrx,lry,urx, ury,ulx,uly wither an MBR xlo,ylo,xhi,yhi OR 4 points (x1,y1,x2,y2,x3,y3,x4,y4) polygon in anticlockwise order starting with lower left. Tells the imagery that it is to be drawn clipped as defined by the clipping rectangle or polygon SET IMAGE DISPLAY CLIPPED=fileName,true/false

yes

SET IMAGE DISPLAY CLIPPED

yes

SET IMAGERY EDIT MAINTAIN ASPECT RATIO SET IMAGERY TRANSPARENCY

Used to tell the application whether an SET IMAGE EDIT MAINTAIN image edit should maintain the aspect ASPECT RATIO=TRUE/FALSE ratio of the image Set the transparancy of a given image SET IMAGE block TRANSPARENCY=imageName,al hpa (The alpha value ranges from 0-255) Sets the implicit background Inserts updated features into the database in the event they have beendeleted by another user Sets the period of time after which the application will automatically extract a live theme SET IMPLICIT BACKGROUND=TRUE/FALSE SET INSERT DELETED UPDATES=TRUE/FALSE SET LIVE THEME EXTRACT PERIOD=milliseconds

yes

yes SET INSERT DELETED UPDATES yes

yes

yes

SET IMPLICIT BACKGROUND

yes

yes

yes

Keyin Commands

yes

yes

yes

SET LIVE THEME EXTRACT PERIOD

Table 7: Keyin Commands (Continued)

ADE-M yes yes SET MAP VIEWABLE Set the map at a give index viewable/non-viewable Set the master datasource within the application Sets the specified map as the master map Sets the client side max visible scale for viewing a theme based on the active datasource and passed theme SET MAP NAME Sets the specified map as the active map SET ACTIVE MAP=NAME SET MAP VIEWABLE=MAPNAME/MAPID, TRUE/FALSE SET MASTER DATASOURCE= DATASOURCENAME SET MASTER MAP=NAME SET MAX SCALE=THEME_NAME,MAX_ SCALE SET MAX SNAP VISIBLE SCALE Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes yes SET MAX SCALE SET MASTER MAP SET MASTER DATASOURCE yes SET MAX SNAP VISIBLE SCALE Set the maximum scale which vertex (snap) points will be visible on the viewer SET MESSAGE yes SET MIN SCALE Sets the current message to be viewed SET MESSAGE=MESSAGE within the application Sets the client side min visible scale for viewing a theme based on the active datasource and passed theme SET MIN SCALE=THEME_NAME,MIN_ SCALE This keyin sets the crosshair point for SET MOUSE CROSSHAIR POINT=SCREEN_PT_X, the application. If this is set, the SCREEN_PT_Y application will draw a vertical and horizontal line through the point when painting This method sets the minimum size for SET MOUSE VIEW WINDOW a mouse view window when zooming BUFFER SIZE=size in by window Tells the application whether or not to show nodes SET NODES VISIBLE=TRUE/FALSE yes SET MOUSE CROSSHAIR POINT SET MOUSE VIEW WINDOW BUFFER SIZE yes SET NODES VISIBLE

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

123

124

Table 7: Keyin Commands (Continued)

ADE-M yes SET POLYGON ENGINE MERGE HOLES SET POLYGON ORIGINAL GEOMETRIES SUPERIOR Used to set if the polygon topology engine should merge holes into an encompassing geometry Keyin Description Usage SET POLYGON ENGINE MERGE HOLES=TRUE/FALSE

IEE

ADE-E

ADE-R

yes

SET POLYGON ORIGINAL Used to define if original geometries are superior to new ones. If an original GEOMETRIES geometry is superior, then when a new SUPERIOR=TRUE/FALSE geometry overlaps an old, the boundaey of the original polygon is maintained. If the original geometry is not superior then the a newly placed overlapping geometry will cut into the original ones. Sets the primary filter mode (0=None, SET PRIMARY FILTER=0/1/2/3/4/5 1=SDO_GEOMETRY, 2=TOPO_FEATURE, 3=Topology Primitive, 4=LRS Geometry, 5=Active Theme) SET RELEASE LOCKS ON EXIT=TRUE/FALSE SET RESOLVE DANGLES END SET RESOLVE DANGLES START=TRUE/FALSE Tells the application whether or not too SET RESOLVE resolve polygons POLYGONS=TRUE/FALSE Tells the application whether to resolve SET RESOLVE splits or not SPLITS=TRUE/FALSE Tells ADEMobile that Whether it is allowed to rotate text SET ROTATE TEXT=TRUE/FALSE Tells the application whether or not the SET RUBBER BAND application is to use rubber band lock LOCK=TRUE/FALSE

yes

yes

yes

yes

SET PRIMARY FILTER

yes yes yes yes yes yes yes SET ROTATE TEXT SET RUBBER BAND LOCK SET RESOLVE SPLITS SET RESOLVE POLYGONS SET RESOLVE DANGLES START SET RESOLVE DANGLES END

yes

yes

yes

SET RELEASE LOCKS ON EXIT Tells the application whether or not to release database locks on exit Tells the application to resolve end dangles Tells the application to resolve start dangles

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

Keyin Commands

yes

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes yes SET SECONDARY FILTER Sets the secondary filter mode (0=None, 1=Point Type, 2= Linear Type, 3= Polygon Type, 4=Collection Type) Tell the application to paint all endpoints Tells the application to paint the endpoints of all geometries Tells the the application Renderer to display the scale bar Tell the application whether to display the Tool Options dialog boxes for Selection and Placement operations SET SECONDARY FILTER=0/1/2/3/4 SET SCALE Set the current view map scale based on the current active theme SET SCALE=1:1000 or SET SCALE=1000 Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes yes SET SHOW TOOL OPTIONS SET SHOW SCALE BAR SET SHOW ENDPOINTS SET SHOW ALLPOINTS SET SHOW ALLPOINTS=TRUE/FALSE SET SHOW ENDPOINTS=TRUE/FALSE SET SHOW SCALE BAR=TRUE/FALSE SET SHOW TOOL OPTIONS=TRUE/FALSE SET SHOW TOOLTIP IN DRAW MODE SET SHOW TOOLTIP IN SELECT MODE SET SHOW TOOLTIP IN VIEW MODE yes yes yes SET SNAP MODE SET SNAP LOCK SET SIZE Tells the editor whether or not to show SET SHOW TOOLTIP IN DRAW the attribute tooltip in draw mode MODE=TRUE/FALSE Tells the editor whether or not to show SET SHOW TOOLTIP IN SELECT the attribute tooltip in select mode MODE=TRUE/FALSE Tells the editor whether or not to show SET SHOW TOOLTIP IN VIEW the attribute tooltip in view mode MODE=TRUE/FALSE Set the current view map size Tells the application whether or not to use snap lock Sets the current snap mode for the application, The snaps are controlled with the middle mouse button. (1=Endpoint, 2=MidPoint, 3=Perpendicular) SET SIZE=MAPSIZE SET SNAP LOCK=TRUE/FALSE SET SNAP MODE=1/2/3

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

125

126

Table 7: Keyin Commands (Continued)

ADE-M SET STATUS yes SET STROKE TOLERANCE Sets the stroke tolerance for placing stroked circles and arcs. the application will automatically stroke circles and arcs placed in a GeoDetic dataset Sets the current status message for the application SET STATUS=STATUS SET STROKE TOLERANCE to open an entry dialog or SET STROKE TOLERANCE=123 to set it directly Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

SET STYLE VISIBLE

Sets a specified style for a datasource SET STYLE and theme to be visible VISIBLE=DATASOURCE,THEME NAME,STYLENAME, TRUE/FALSE Marker that defines whether a TOPO_GEOMETRY themes has had its attributes extracted from the database SET THEME ATTRIBUTED=DATASOURCE_N AME,THEME_NAME, TRUE/FALSE

yes

yes

yes

yes

SET THEME ATTRIBUTED

yes

yes

yes

SET THEME CENTROIDS

Sets a column in a theme table to be a SET THEME centoid CENTROIDS=dsName,themeNam e,CENTROID_COLUMN_NAME Sets a specified theme to be editable for a given datasource Defines whether to label a theme SET THEME EDITABLE=DATASOURCE, THEMENAME,TRUE/FALSE SET THEME LABELLED=DATASOURCE, THEMENAME,TRUE/FALSE Sets theme lock on/off Sets a specified theme not to be editable Sets a specified theme to be viewable SET THEME LOCK=TRUE/FALSE SET THEME NON EDITABLE=DATASOURCE, THEMENAME SET THEME VIEWABLE=DATASOURCE, THEMENAME,TRUE/FALSE

yes

yes

yes

yes

SET THEME EDITABLE

yes

yes

yes

yes

SET THEME LABELLED

yes yes

yes

yes

SET THEME LOCK SET THEME NON EDITABLE

yes

yes

yes

Keyin Commands
yes

yes

yes

yes

SET THEME VIEWABLE

Table 7: Keyin Commands (Continued)

ADE-M SET TOPO GEOM NULL Sets the geometry of a topo feature to SET TOPO GEOM NULL null, forcing a topo feature geoemtry rebuild in memory. This is really a debugging tool Tells the application whether or not to use pessimistic locking Sets the user ordinate tolerance Sets the color of a vertex within the application Sets the current vertex point color for snaps points based on RGB values ranging from 0-255 Sets the vertex diameter SET USE PESSIMISTIC LOCKING=TRUE/FALSE SET USER PRECISION=PRECISION SET VERTEX COLOR=FFFFFF SET VERTEX COLOR RGB=R,G,B SET VERTEX DIAMETER=DIAMETER Keyin Description Usage

IEE

ADE-E

ADE-R

Keyin Commands
yes yes yes yes SET VERTEX COLOR RGB SET VERTEX COLOR SET USER PRECISION SET USE PESSIMISTIC LOCKING yes SET WAIT TEXT SET VERTEX DIAMETER Sets the message that the application SET WAIT TEXT=TEXT will paint at the center of the map when it is waiting (This will only have effect when the Progress bar is not in use) Sets the zoom ratio to be used within the application Opens a dialog that manages GPS settings and controls Command to launch a context help screen Opens a dilaog box that displays the active projection data for a given map Opens the the application SQLQuery box SET ZOOM RATIO=RATIO SHOW GPS MANAGER SHOW HELP or SHOW HELP=URL SHOW PROJECTION INFO SHOW SQL DIALOG yes SHOW GPS MANAGER yes SHOW HELP SHOW PROJECTION INFO SHOW SQL DIALOG SET ZOOM RATIO

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

127

128

Table 7: Keyin Commands (Continued)

ADE-M SHOW THEME CONTROL DIALOG yes yes yes SPLIT FEATURE Starts the Split command that will break a line into two pieces about the selected point. If a user selects a Topology primitive (Edge) this becomes an Add Node command SLIDE NODE RESHAPE Slides a node along an edge and reshapes the moved edges SLIDE NODE Slides a node along an edge SLIDE NODE SLIDE NODE RESHAPE SPLIT FEATURE Open the theme control dialog to allow SHOW THEME CONTROL users to change the current map view DIALOG settings Keyin Description Usage

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes yes SPLIT NODE RESHAPE

yes

yes

yes

SPLIT NODE

Splits an edge(s) from a node keeping SPLIT NODE the existing node Splits an edge(s) from a node keeping SPLIT NODE RESHAPE the existing node and reshapes the moved edges Starts the command to split a polygon, SPLIT POLYGON The user draws a cutting plane that will split a polygon about the cutting place start wms service thread=http://onearth.jpl.nasa.gov/ wms.cgi?,daily_planet Stops a WMS service to ADE Swipes the raster display left right on the map Swipes the vector display left right on the map stop wms service thread SWIPE RASTER DISPLAY SWIPE VECTOR DISPLAY Change the viewer to another map for SWITCH MAP=MAPNAME the currently active datasource.

yes

yes

yes

yes

yes

yes

yes

SPLIT POLYGON

yes

yes

yes

START WMS SERVICE THREAD Load a WMS service to ADE

yes yes yes SWITCH MAP

yes

yes

STOP WMS SERVICE THREAD SWIPE RASTER DISPLAY SWIPE VECTOR DISPLAY

yes

yes

yes

yes

Keyin Commands

yes

Table 7: Keyin Commands (Continued)

ADE-M SYNCHRONIZE WORKSPACE yes yes TOGGLE ARROWS TEST DPI Returns the the actual DPI value being GET SCREEN DPI used by the application Attaches the PaintListener that makes TOGGLE ARROWS the application paint arrows on geometries and Centroids in polygons Set the current GPS Point location but TRACK GPS POINT=X,Y does center the map Undo the last edit performed Undo all edits since last save UNDO UNDO ALL Synchronizes the current workspace with parent Keyin Description Usage SYNCHRONIZE WORKSPACE

IEE

ADE-E

ADE-R

Keyin Commands
yes yes yes yes yes yes UNION POLYGON UNGROUP GEOMETRIES UNDO ALL SILENTLY UNDO ALL UNDO TRACK GPS POINT Undo all edits since last save without a UNDO ALL SILENTLY warning Tell the application to ungroup the selected geometries Starts the Merge (Union) Polygon command that requires the user to select a polygon geometry as a master, and then merge subsequently selected polygon geometries to the master geometry, disolving any common boundaries Unloads all attached image files Updates the the application view UNGROUP GEOMETRIES UNION POLYGON UNLOAD IMAGE BLOCKS yes UPLOAD EDITS yes USE CUSTOM SCREEN DPI UPDATE VIEW CLEAR IMAGE BLOCKS UPDATE VIEW Tool to upload the current operation list UPLOAD EDITS=file on server to the app server Calculates the actual screen dpi based CALCULATE SCREEN DPI=15.5 on the screen width in inches (as passed to the method)

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

129

130

Table 7: Keyin Commands (Continued)

ADE-M VALIDATE ORACLE TOPOMAP VIEW FEATURE ATTRIBUTES Checks to see if the current Oracle TopoMap is valid Keyin Description Usage VALIDATE ORACLE TOPOMAP

IEE

ADE-E

ADE-R

yes

yes

yes

yes

yes

yes

Tells the application to start a selection VIEW FEATURE ATTRIBUTES command to select geometry and display its attributes in readonly mode Shows the next views if there is any available Shows the previous view that was shown within the application. This creates a next view Gets the capabilities of the WMS VIEW NEXT VIEW PREVIOUS

yes yes VIEW PREVIOUS

yes

yes

VIEW NEXT

yes

yes

yes yes WMS SET ADDITIONAL PARAMS WMS SET EPSG WMS SET FORMAT WMS SET LAYERS WMS SET PASSWORD WMS SET REQUESTED TILE SIZE FACTOR

yes

yes

WMS GET CAPABILITIES

WMS GET CAPABILITIES

yes

yes

WMS SET ADDITIONAL Sets the WMS additional request parameters should they be required or PARAMS=&myparam=myvalue supported Sets the WMS output EPSG Sets the WMS format Sets the WMS LAYERS Sets the WMS service password should authentication be required WMS SET EPSG=EPSG:4326 WMS SET FORMAT=image/jpeg WMS SET LAYERS=daily_planet WMS SET PASSWORD=password WMS SET REQUESTED TILE Sets a scale factor for the width and SIZE FACTOR=2.0 height of a WMS requested image. Required by some WMS servers that are set with a minimum bounds on the image requests in. Default is 1.0 Sets the WMS styles Sets the WMS service username should authentication be required Sets the WMS Version WMS SET STYLES=default WMS SET USERNAME=userName WMS SET VERSION=1.1.yes

yes yes yes yes yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes yes yes

yes

yes

WMS SET STYLES WMS SET USERNAME WMS SET VERSION

yes

yes

Keyin Commands

yes

yes

Table 7: Keyin Commands (Continued)

ADE-M yes WMS SET WMSURL Sets the WMS URL Keyin Description Usage WMS SET WMSURL=http://onearth.jpl.nasa. gov/wms.cgi XOR POLYGON

IEE

ADE-E

ADE-R

Keyin Commands
yes XOR POLYGON Starts the exclusive OR polygon command that requires the user to select a polygon geometry as a master, and then determine the XOR with subsequently selected polygon geometries to the master geometry Tells the application to zoom into the map by ration ZOOM RATIO Prepares to zoom in about a user selected point ZOOM IN ZOOM IN ABOUT POINT yes yes yes ZOOM OUT ZOOM IN ABOUT POINT ZOOM IN Tells the application to zoom out of the ZOOM OUT map by the zoom ratio (GET ZOOM RATIO). Prepares to zoom out about a user selected point Tells the application to start the Zoom out to Window zoom command Tells the application to zoom to the database defined (SDO_GEOM_METADATA) extent of the active theme Tells the application to start the Zoom to Window zoom command ZOOM OUT ABOUT POINT ZOOM OUT TO WINDOW ZOOM TO EXTENT yes ZOOM OUT TO WINDOW yes ZOOM TO EXTENT ZOOM OUT ABOUT POINT ZOOM TO WINDOW ZOOM TO WINDOW

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

131

132

Keyin Commands

Index
Symbols
<features> element 27 <label> element 27

E
edge primitive 53 edge topology element 22 elements 4 end points 43 example data vii exporting spatial data to oracle 58 exterior polygons 4

A
ALL_SDO_MAPS 30 ALL_SDO_STYLES 30 ALL_SDO_THEMES 30 ALL_SDO_xxx 30 allow ISO moves 44 application considerations 21 area style metadata 25 axis lock 48

F
face topology element 22

G
generalized layer 22 geodetic data 18 geometric primitive type lines 3 points 3 polygons 4 geometries 5 Great Circle distances 19 grid 40, 41 grid lock 48 grid major 42 grid minor 42 grid settings 42 Gtypes 6

B
base map 29 BucketStyle 25

C
circular arc geometry 52 color metadata style 25 ColorSchemeStyle 25 commit on save 41 connection 34 CREATE INDEX statement 21

H
hilite and display settings 45 hilite color 45 history table 24

D
dangle lock (end) 48 dangle lock (start) 47 data loading 19 data locking 39 database privileges 24 DATE data type 1 detailed layer 22 diameter end points 43 diameter vertex points 43 dictionary table 19 digitizing 50 digitizing locks 46 discover options 35 display bounding boxes 45 display metadata 24 display progress bar 42 distance units 43 draw handles 40 draw handles (selection) 45

I
IEE Layer tab 38 IEE locks 46 IEE Settings dialog 40 IEE tolerance 40 IEE tolerancing 44 IEE Tools palette 50 Import 19 indexing spatial data 21 interior polygons 4 isolated node primitive 53

J
Java class style types 25 JDBC theme 26

L
LAYER_GTYPE parameter 21 layers 5

Index

133

line element data 4 line feature 54 line geometry 51 line style metadata 25 lock mechanism settings 41 locking 41 longitude/latitude 18

file 68 global properties 78 page sizes 79 properties 73 print to PDF 67 process settings 42

M
map selection 35 maps 28 marker metadata style 25 max visible scale 43 MDSYS.CS_SRS 19 MDSYS.SDO_GEOMETRY 26 metadata table 24 metadata views 30

R
RDBMS data model 1 rectangle polygon geometry 52 redo command 39 relationship table 24 release locks on exit 39, 41 roll back changes 61 R-Tree spatial indexes 21 rubber band lock 48 rules for accessing mapping metadata 30

N
node topology element 22 NUMBER data type 1

S
sample data vii save settings command 39 saving data to database 57 schema 34 SDO_GEOM.VALIDATE_GEOMETRY_WITH_C ONTEXT 20 SDO_GEOM.VALIDATE_LAYER_WITH_CONTE XT 20 SDO_GEOM_METADATA_TABLE 17 SDO_GEOMETRY 17 SDO_GEOMETRY data type 1 SDO_MAPS_TABLE 30 SDO_STYLES_TABLE 30 SDO_THEMES_TABLE 30 SDO_UTIL.EXTRACT routine 20 SDO_UTIL.REMOVE_DUPLICATE_VERTICIES routine 20 search and locate 37 segmentation lock 47 server (connection) 34 SID (connection) 34 snap lock 48 snapping 39 snapping settings 42 spatial data modeling 1 SQL*Loader 19 SRID 17 start IEE 33 styles (metadata) 25 area 25 color 25 line 25 marker 25 text 25

O
OGC 19 Open GIS Consortium 19 optimistic locking 39 ORA 13349 validation error 20 ORA 13356 validation error 20 ORA 13367 validation error 20 Oracle 1 geometric types 3 spatial example 2 Oracle Map Definition Tool 25 Oracle Spatial element types 7

P
password 34 pessimistic locking 39 pixels units 43 point element data 4 point geometry 50 polygon element data 5 polygon feature 55 polygon geometry 51 polygon interact feature 56 polygon topo lock 46 port (connection) 34 precision tolerancing 44 predefined themes 26 styling rules 26 print templates creating 69

134

Index

styling rules 26 styling rules example 26

T
text style metadata 25 theme control 49 theme lock 48 themes 26 Tolerance 18 topo_geometry 23 topological data model 22 topology 44 topology settings 44 topology-related tables 24 transaction management commands 39

U
undo all command 39 undo command 39 UNION ALL operation 28 units 43 use pessimistic locking 41 USER_SDO_GEOM_METADATA 17, 40 USER_SDO_MAPS 25, 30 USER_SDO_STYLES 25, 30 USER_SDO_THEMES 25, 26, 30 USER_SDO_xxx 30 username (connection) 34

V
validation errors 20 VARCHAR2 data type 1 VariableMarkerStyle 25 vertex points 43 visible end points 43 visible vertex points 43 visualization 21

W
well_known_text (WKT) grammar 19 WHERE clause 27 workspace manager 59

Index

135

136

Index