IEE User Guide

IMAGINE Enterprise
Editor
User’s Guide
5 February 2008
Copyright © 2007 Leica Geosystems Geospatial Imaging, LLC
All rights reserved.
Printed in the United States of America.
The information contained in this document is the exclusive property of Leica Geosystems Geospatial Imaging, LLC.
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 Leica Geosystems Geospatial Imaging, LLC. All requests should be sent to the attention of:
Manager, Technical Documentation

Leica Geosystems Geospatial Imaging, LLC.
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 non-exclusive, 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, IMAGINE OrthoBASE, Stereo Analyst and IMAGINE VirtualGIS are registered trademarks;
IMAGINE OrthoBASE Pro is a trademark of Leica Geosystems Geospatial Imaging, LLC.
SOCET SET is a registered trademark of BAE Systems Mission Solutions.
Other companies and products mentioned herein are trademarks or registered trademarks of their respective owners.
Table of Contents
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Conventions Used in This Book . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview of IEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Oracle Spatial Concepts . . . . . . . . . . . . . . . . . . . . . . . .3
Spatial Data Modeling . . . . . . . . . . . . . . . . . ........ . .. 3
Spatial Data Model – Oracle Spatial Example . ........ . .. 4
Supported Geometric Types . . . . . . . . . . . . . ........ . .. 4
Elements . . . . . . . . . . . . . . . . . . . . . . . . . ........ . .. 6
Geometries . . . . . . . . . . . . . . . . . . . . . . . . ........ . .. 7
Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . ........ . .. 7
Metadata, Tolerance, and Coordinate Systems ........ . . 19
Data Loading . . . . . . . . . . . . . . . . . . . . . . . ........ . . 21
Data Validation . . . . . . . . . . . . . . . . . . . . . . ........ . . 21
Indexing Spatial Data . . . . . . . . . . . . . . . . . ........ . . 22
Application Considerations . . . . . . . . . . . . . . ........ . . 23
Topological Data Model . . . . . . . . . . . . . . . . . . . . . . . 24
Topology elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Topology related tables . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Display Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . ........ . . 25
Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . ........ . . 27
Styling Rules in Predefined Themes . . . . . . . ........ . . 27
Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ........ . . 28
Metadata Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Getting Connected . . . . . . . . . . . . . . . . . . . . . . . . . . 33
IEE Startup . . . . . . ........ . ........ . ........ . . 33
Connection Dialog . . ........ . ........ . ........ . . 34
Password . . . . . . . . ........ . ........ . ........ . . 34
Map Selection . . . . . ........ . ........ . ........ . . 35
Discover Options . . ........ . ........ . ........ . . 35
Search and Locate . ........ . ........ . ........ . . 36
IEE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Transaction Management Commands . . . . . . . . . . . . . 39
Understanding IEE Settings . . . . . . . . . . . . . . . . . . . . . . . 39
Snapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
iii
Data Locking ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Release Locks on Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Grid . . . . . . ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Draw Handles ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
IEE Tolerance ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
IEE Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Locking & Grid Settings . . . . . . . ........ . ........ . . 40
Snapping Settings . . . . . . . . . . . ........ . ........ . . 41
Topology and Display Settings . . ........ . ........ . . 43
IEE Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Understanding IEE Digitizing Locks . . . . . . . . ........ . . 44
Dissolve Polygon Lock . . . . . . . . . . . . . . . . . ........ . . 44
Segmentation Lock . . . . . . . . . . . . . . . . . . . ........ . . 44
Dangle Lock (Start) . . . . . . . . . . . . . . . . . . . ........ . . 45
Dangle Lock (End) . . . . . . . . . . . . . . . . . . . ........ . . 45
Rubber Band Lock . . . . . . . . . . . . . . . . . . . . ........ . . 45
Theme Lock . . . . . . . . . . . . . . . . . . . . . . . . ........ . . 45
Axis Lock . . . . . . . . . . . . . . . . . . . . . . . . . . ........ . . 45
Grid Lock . . . . . . . . . . . . . . . . . . . . . . . . . . ........ . . 45
Linear Snap Lock . . . . . . . . . . . . . . . . . . . . ........ . . 45
Theme Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Display Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Edit Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Digitizing with IEE . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Place Point Geometry . . . . . . . . . . . . . . . . . ........ . . 47
Place Line Geometry . . . . . . . . . . . . . . . . . . ........ . . 47
Place Polygon Geometry . . . . . . . . . . . . . . . ........ . . 47
Place Circle Polygon Geometry . . . . . . . . . . . ........ . . 48
Place Circle Polygon Geometry by Center . . . . ........ . . 48
Place Rectangle Polygon Geometry . . . . . . . . ........ . . 49
Place Circular Arc Geometry . . . . . . . . . . . . . ........ . . 49
Place Isolated Node Primitive . . . . . . . . . . . . ........ . . 50
Place Edge Primitive . . . . . . . . . . . . . . . . . . ........ . . 50
Place Point Feature . . . . . . . . . . . . . . . . . . . ........ . . 51
Place Line Feature . . . . . . . . . . . . . . . . . . . ........ . . 51
Place Polygon Feature . . . . . . . . . . . . . . . . . ........ . . 52
Place Polygon Interact Feature . . . . . . . . . . . ........ . . 52
Saving Data to Database . . . . . . . . . . . . . . . . . . . . . . 53
Exporting Spatial Data to Oracle . . . . . . . . . . . . . . . . 54
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
iv
Preface
About This Manual The IMAGINE Enterprise Editor (IEE) User’s 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.
": Tutorial" 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.
Sample Data Sample data sets are provided with the software. The sample data
are installed in the <IMAGINE_HOME>/examples directory.
<IMAGINE_HOME> is the variable name of the directory where
IMAGINE resides. When accessing data files, you need to replace
<IMAGINE_HOME> with the name of the directory where ERDAS
IMAGINE is loaded.
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.
Many of these documents are available from the Leica Geosystems
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 ERDAS IMAGINE, the names of menus, menu options, buttons,
and other components of the interface are shown in bold type. For
in This Book 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.
Preface 1
• click — click once with the left mouse button.
• 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 Leica Geosystems

products.
These paragraphs lead you to other areas of this book or other

manuals for additional information.
NOTE: Notes give additional instruction.
Blue Box
These boxes contain supplemental technical information.
Blue text indicates a link that will take you to related information
when you click it.
2 Preface
Introduction
Introduction The purpose of the IMAGINE Enterprise Editor (IEE) User’s 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.
Overview of IEE The IMAGINE Enterprise Editor provides a seamless interface

between ERDAS IMAGINE 9.0 and Oracle 10g Spatial. IEE enables
simultaneous access to Oracle Spatial, Oracle Topology and Oracle
Georaster formatted data within the IMAGINE Viewer.
Oracle Spatial IMAGINE Enterprise Editor provides a seamless interface between

ERDAS IMAGINE 9.0 and Oracle 10g Spatial. IEE enables
Concepts
simultaneous access to Oracle Spatial, Oracle Topology and Oracle
Georaster formatted data within the IMAGINE Viewer.
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_GEOMETY 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.
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.
Introduction 3
Figure 1: Spatial Data Model Comparison
File / Directory Based Oracle Spatial
2 to 8 files for All data for a layer is

each layer stored in a single table
Layers are added Layers are grouped

to edit together as a map
environment
individually
Users only lock areas of
data so many users can
Spatial Data Model –

Oracle Spatial Example
Table 1: Road Table Example
ROAD ROAD ROAD NUM SURFACE GEOM

NAME ID TYPE LANES
HWY-25 32456 Primary 4 Concrete sdo_geometry
I-70 32456 Primary 4 Concrete sdo_geometry
Main St 345621 City 2 Asphalt sdo_geometry
CR-34 234001 County 1 Dirt sdo_geometry
Table 2: sdo_geometry Structure
MDSYS.SDO_GEOMETRY object
Name Type Description
SDO_GTYPE NUMBER Defines the kind of geometry
SDO_SRID NUMBER Used to identify a coordinate system
SDO_POINT SDO_POINT_TYPE Optimized storage for point data
SDO_ELEM_INFO SDO_ELEM_INFO_ARRAY Defines how to interpret the ordinate array
SDO_ORDINATES SDO_ORDINATE_ARRAY Storage for ordinates of geometry
Supported Geometric Oracle Spatial supports three multi-dimensional geometric primitive

Types types and geometries composed of collections of these types. The
three primitive types are:
• Points (X1, Y1)
4 Introduction
• Line strings (X1, Y1, Xn, Yn)
• Polygons (X1, Y1,... Xn, Yn)
Geometric Primitive Types

Arc line Compound Self-
Self-crossing
Line string string line string line strings
Valid
Polygon Compound Optimized Self-

Self-crossing
n polygons
with hole polygon 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.
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.
Introduction 5
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 Element 6
– Point
– Line Element 5
– Polygon Element 4
– Compound Linestring
Element 7 Element 2
– Compound Polygon
Element 1
• Constructed Element 3
using ordinates
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.
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.
6 Introduction
Geometries Geometries are the representation of spatial features, modeled as an
ordered set of primitive elements.
Geometry
Geometry 1 Geometry 2
California Texas
• Represents
Represents aa
spatial
spatial feature
feature
• Consists
Consists ofof an
an
ordered
ordered set
set of
of
elements
elements
Geometry 3 Geometry 4
Florida 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 7
Layers
• Consist
Consist of of geometries
geometries
that
that share
share aa common
common
set
set of
of attributes
attributes
• Layer
Layer isis aa geometry
geometry
column
column in a table
in a table
States layer
Table 3: Oracle Spatial Gtypes
SDO_GTYPES
GTYPE - Gtype with Dimensionality
2D 3D 4D
0 Unknown 2000 3000 4000

Geometry
1 Point 2001 3001 4001
2 Linestring 2002 3002 4002
3 Polygon 2003 3003 4003
4 Collection 2004 3004 4004
5 MultiPoint 2005 3005 4005
6 MultiLinestring 2006 3006 4006
7 MultiPolygon 2007 3007 4007
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.
8 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 Interpretation
0 UNKNOWN_ELEMENT User defined
1 POINT # of points in collection
2 LINESTRING 1 - Straight lines

2 - Circular arcs
3 POLYGON 1 - Straight lines

1003 (Outer) 2 - Circular arcs
2003 (Inner) 3 - Optimized rectangle
4 - Circle
4 COMPOUND LINESTRING # of type 2 sub-elements that make up

the linestring
5 COMPOUND POLYGON # of type 2 sub-elements that make up

the polygon
1005 (Outer)
2005 (Inner)
Introduction 9
Element Example: Line String
Ordinate offset Element type Interpretation
1 2 1
(x2,y2)
(x2,y2)
(x1,y1)
(x1,y1) (x3,y3)
(x3,y3) (x4,y4)
(x4,y4)
•• Each
Each line
line segment
segment is
is defined
defined byby two
two points
points
•• Last
Last point
point from
from one
one is
is the
the first
first point
point of
of next
next segment
segment
•• Line
Line segments
segments that
that close
close to
to form
form aa ring
ring have
have no
no implied
implied interior
interior
•• Line
Line segments
segments must
must bebe contiguous
contiguous
•• Line
Line segments
segments can
can cross
cross
Element Example: Polygon

1 1003 1
(x5,y5)
(x6,y6)
(x1,y1) (x4,y4)
(x4,y4)
(x2,y2) (x3,y3)
• Interpretation
Interpretation 11 -- 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
10 Introduction
Element Example: Arc Polygon
1 1003 2
(x6,y6)
(x7,y7)
(x7,y7) (x5,y5)
(x8,y8) (x4,y4)
(x9,y9) (x3,y3)
(x1,y1)
(x2,y2)
• Interpretation
Interpretation 22 -- 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

1 2 2
(x2,y2) (x4,y4)
(x1,y1)
(x7,y7)
(x3,y3)
(x3,y3) (x5,y5)
(x6,y6)
•• Each
Each arc
arc is
is defined
defined by
by three
three points
points on
on the
the circumference
circumference of
of aa
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 aa ring
ring have
have no
no implied
implied interior
interior
•• Arcs
Arcs must
must bebe contiguous
contiguous
•• Arcs
Arcs can
can cross
cross
Introduction 11
Element Example: Rectangle
1 1003 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 Element Type Interpretation
1 1003 4
(x1,y1)
(x1,y1)
(x2,y2)
(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
12 Introduction
Element Example: Compound Line
String
1 4 3
1 2 1
5 2 2
13 2 1
(x4,y4)
(x3,y3) (x5,y5)
(x9,y9)
(x7,y7)
(x6,y6)
(x8,y8)
(x2,y2) (x1,y1)
•• First
First triplet
triplet (header)
(header) defines
defines the
the number
number of
of sub-elements
sub-elements
•• Sub-elements must be contiguous
Sub-elements must be contiguous
•• Arcs
Arcs and
and line
line segments
segments of
of sub-elements
sub-elements can
can cross
cross
•• Element
Element type
type 44 can
can ONLY
ONLY contain
contain sub-elements
sub-elements of
of type
type 22
Element
Element Example:
Example: Compound
Compound Polygon
Polygon
1 1005 2
1 2 1
5 2 2
(x6,y6)
(x4,y4)
(x7,y7)
(x1,y1) (x3,y3)
(x5,y5)
(x2,y2)
•• First
First triplet
triplet (header)
(header) defines
defines the
the number
number of
of sub-elements
sub-elements
•• Sub-elements must be contiguous
Sub-elements must be contiguous
•• Arcs
Arcs and
and line
line segments
segments of
of sub-elements
sub-elements cannot
cannot cross
cross
•• Element
Element type
type 55 can
can ONLY
ONLY contain
contain sub-elements
sub-elements of
of type
type 22
•• Area
Area is
is implied
implied
Introduction 13
Etype
Etype 00 -- to
to support
support interoperability
interoperability

1 2 1
27 0 200
(x5,y5)
(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
1 0 1324
17 1 2
•• Element
Element type
type 00 is
is ignored
ignored by
by Oracle
Oracle Spatial
Spatial
•• Element
Element type
type 00 is
is for
for modeling
modeling unsupported
unsupported element
element types
types
(i.e.
(i.e. curves,
curves, splines
splines etc…)
etc…)
•• A
A geometry
geometry with
with an
an element
element type
type 00 must
must contain
contain at
at least
least one
one
element
element ofof type
type 1,2,3,4
1,2,3,4 or
or 5.
5. The
The non
non 00 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
14 Introduction
Collection Example: Point cluster
Ordinate Offset Element type Interpretation
1 1 5
(x1,y1) (x3,y3)
(x5,y5)
(x2,y2)
(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

1 2 1
7 2 2
(x2,y2)
(x2,y2) (x5,y5)
(x5,y5)
(x1,y1) (x3,y3) (x4,y4)

(x4,y4) (x6,y6)
(x6,y6)
(x1,y1) (x3,y3)
• Elements
Elements can
can be
be line
line strings,
strings, arc
arc strings
strings or
or
compound
compound line
line strings
strings
Introduction 15
Collection Example: Multi Polygon
1 1003 1
13 1003 4
(x5,y5)
(x6,y6) (x8,y8) (x7,y7)

(x7,y7)
(x4,y4)
(x4,y4)
(x1,y1)
(x9,y9)
(x2,y2) (x3,y3)
• Elements
Elements can
can be
be polygons,
polygons, arc
arc polygons,
polygons, or
or
compound polygons
compound polygons
Collection Example: Multi Polygon

1 1003 1
13 1 1
(x5,y5)
(x6,y6)
(x4,y4)
(x4,y4)
(x1,y1)
(x7,y7)
(x7,y7)
(x2,y2) (x3,y3)
• Elements
Elements can
can be
be polygons,
polygons, arc
arc polygons,
polygons, or
or
compound polygons
compound polygons
16 Introduction
Element example: Polygon with void
1 1003 1
13 2003 3
(x5,y5)
(x6,y6) (x8,y8)
(x4,y4)
(x4,y4)
(x1,y1)
(x7,y7)
(x2,y2) (x3,y3)
•• AA void
void can
can be
be modeled
modeled with
with any
any combination
combination of
of type
type 33 and
and
type
type 55 elements
elements
•• Voids
Voids can contain
can 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
Element example: Compound polygon

with void
1 1005 2
1 2 1
7 2 2
17 2003 3
(x5,y5)
(x7,y7)
(x8,y8)
(x4,y4)
(x1,y1) (x6,y6)
(x10,y10)
(x9,y9)
(x2,y2) (x3,y3)
•• AA void
void can
can be
be modeled
modeled with
with any
any combination
combination of
of type
type 33 and
and
type
type 55 elements
elements
•• Voids
Voids can
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 17
Constructing geometries
SQL>
SQL> INSERT
INSERT INTO
INTO LINES
LINES VALUES
VALUES ((
2>
2> attribute_1,
attribute_1, ...,
..., attribute_n,
attribute_n,
3>
3> MDSYS.SDO_GEOMETRY
MDSYS.SDO_GEOMETRY ((
4>
4> 2002,
2002, null,
null, null,
null,
5>
5> MDSYS.SDO_ELEM_INFO_ARRAY
MDSYS.SDO_ELEM_INFO_ARRAY (1,2,1),
(1,2,1),
6>
6> MDSYS.SDO_ORDINATE_ARRAY
MDSYS.SDO_ORDINATE_ARRAY ((
7>
7> 10,10,
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>
2> attribute_1,
attribute_1, ...,
..., attribute_n,
attribute_n,
3>
3> MDSYS.SDO_GEOMETRY(
MDSYS.SDO_GEOMETRY(
4>
4> 2003,
2003, null,
null, null,
null,
5>
5> MDSYS.SDO_ELEM_INFO_ARRAY
MDSYS.SDO_ELEM_INFO_ARRAY
6>
6> (1,1005,2,
(1,1005,2, 1,2,1,
1,2,1, 7,2,2,
7,2,2, 17,2003,3),
17,2003,3),
7>
7> MDSYS.SDO_ORDINATE_ARRAY
MDSYS.SDO_ORDINATE_ARRAY
8>
8> (10,50,10,30,50,30,50,50,40,60,
(10,50,10,30,50,30,50,50,40,60,
9>
9> 30,50,20,60,10,50,25,35,35,40
30,50,20,60,10,50,25,35,35,40 ))
10>
10> );
);
(40,60)
(20,60)
(10,50)
(50,50)
(10,50) (30,50)
(35,40)
(25,35)
(10,30) (50,30)
18 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
2003
1003
must be + +
constructed as
Metadata, Tolerance, and Every SDO_GEOMETRY column in a table requires an entry in Oracle
Coordinate Systems 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 19
USER_SDO_GEOM_METADATA
SQL>
SQL> DESCRIBE
DESCRIBE USER_SDO_GEOM_METADATA
USER_SDO_GEOM_METADATA
Name
Name Null?
Null? Type
Type
--------------
-------------- ---------- ------------------
---------- ------------------
TABLE_NAME
TABLE_NAME NOT
NOT NULL
NULL VARCHAR2(32)
VARCHAR2(32)
COLUMN_NAME
COLUMN_NAME NOT
NOT NULL
NULL VARCHAR2(32)
VARCHAR2(32)
DIMINFO
DIMINFO MDSYS.SDO_DIM_ARRAY
MDSYS.SDO_DIM_ARRAY
SRID
SRID NUMBER
NUMBER
MDSYS.SDO_DIM_ARRAY
VARRAY(4)
VARRAY(4) OF
OF SDO_DIM_ELEMENT
SDO_DIM_ELEMENT
MDSYS.SDO_DIM_ELEMENT object
SDO_DIMNAME
SDO_DIMNAME VARCHAR2(64)
VARCHAR2(64)
SDO_LB
SDO_LB NUMBER
NUMBER
SDO_UB
SDO_UB 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. Oracle’s
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.
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.
20 Introduction
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
Oracle’s 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 Oracle’s SDO_GEOMETRY format.
SeeExporting Spatial Data to Oracle on page 54.
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.
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:
Introduction 21
• 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 10g includes more R-tree
performance enhancements, concurrent DML enhancements, and
more parallelization.
Specifying the LAYER_GTYPE parameter in the CREATE INDEX
statement will:
• 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.
22 Introduction
R-tree Indexing Concept
R-tree
Index
Leaf nodes of R-tree store

MBR
<MBR, geometry pointer>
Geometry
Application If visualization is a key component of your application, this section

Considerations 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.
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.
Introduction 23
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. 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. 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. 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.
Nodes, edges and faces are the building blocks by which every real
world object can be constructed. These real world objects are
modeled as features or topo_geometries. Each topo_geometry is
stored as a set of topological elements, e.g. a parcel can consist of
several faces. Oracle distinguishes five different topo_geometry
types: points, line strings, (multi) polygons and (combining the four
previous topology geometry types) a 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.
24 Introduction
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 en faces on the other side.
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 user’s 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.
Introduction 25
• 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 Java Class Geometry Types
Color oracle.sdovis.style.StyleColor (any type)
Marker oracle.sdovis.style.StyleMarker point, line
Line oracle.sdovis.style.StyleLine line
Area oracle.sdovis.style.StyleArea polygon
Text oracle.sdovis.style.StyleText (any type)
Advanced oracle.sdovis.stylex.Advanced and (any type)

extension
All styles for a database user are stored in that user’s

USER_SDO_STYLES view, which is described in Metadata Views on
page 30.
26 Introduction
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 user’s
USER_SDO_THEMES view, which is described in Metadata Views on
page 30.
Styling Rules in Each predefined theme is associated with one or more styling rules.
Predefined Themes The styling rules for each predefined theme are expressed using
XML, such as in Example 1 for an Airport theme.
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, < and > 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 > 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.
Introduction 27
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 > 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 > 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.
Maps A map can consist of a combination of elements and attributes, such

as the following:
• Background image
28 Introduction
• 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 user’s 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" />
<theme name="theme_us_streets" min_scale="0.05"
max_scale="0" />
</map_definition>
Introduction 29
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.
All styles defined in the database can be referenced by any user to
define that user’s 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 user’s themes
in a base map that you create.
The following rules apply for accessing the mapping metadata:
30 Introduction
• 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.
Introduction 31
32 Introduction
Tutorial
Getting To initiate an IMAGINE Enterprise Editor session, follow the steps

below.
Connected
IEE Startup Select File -> New from the Viewer Menu. Then choose the IEE
Layer option.
Figure 2: IEE Startup
The Enterprise Editor connection selector dialog opens.
Figure 3: Connection Selector
Select Connect to Oracle to open the Connect to Oracle Database

dialog.
Tutorial 33
Connection Dialog Connection information must then be given to allow a connection to
an Oracle instance to be established.
Figure 4: Connection Dialog
The following information must be supplied during the connect

process:
• Server – The name of the Oracle Database Server that you

whish to connect to.
• SID – The System Identifier. A unique name for an Oracle

instance (ex. ORCL)
• Port – The number used by the Oracle Listener (default 1521)
• Username – The name of the Oracle Schema that has the spatial
data.
Password The final piece of connection information is the password for the
Username (Schema) that was entered.
Figure 5: Password Panel
34 Tutorial
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 6: Map Selection Panel
To modify or add to the list of available maps use the Oracle Map
Definition Tool.
Discover Options The Discover Options Panel provides a navigation work flow to help
in the location and investigation of spatial data within the current
database connection.
Figure 7: Discover Options Panel
Tutorial 35
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 press the Next> button or:
- Press 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.
- Press the Search button to open the Search and Locate panel
and enter search criteria to locate specific objects in the
currently selected theme.
- Type in values to the Xpos, Ypos and Map Size fields.
- Press Prev. XYS to set the values for XPos, YPos and Map
Size to the last values used.
- Press View to set the Xpos, YPos and Map Size to the current
view window.
After the appropriate choice has been made press 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).
Search and Locate The Search and Locate panel 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.
36 Tutorial
Figure 8: Search and Locate Panel
Press 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.
- Click the Next field and choose AND or OR if you are going
to add an additional search record.
- Press the Search button to query the database and return
the results.
- Choose a record from the populated Results list by clicking on
the record.
- Press 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 panel.
Tutorial 37
Once the Locate button is pressed the Discovery process is complete
and the IEE layer will display the vector data in the IEE Layer of the
IMAGINE Viewer.
IEE Interface The IEE Menu provides access to administrative functions as well as
for all menus that control digitizing and interface settings.
Figure 9: IEE Menu
Please see the IMAGINE Enterprise Editor on-line help for more
information about the user interface.
38 Tutorial
Transaction Some of the commands in the IEE menu provide functionality that
impacts the list of transactions that are sent to the database. These
Management
commands are
Commands Undo - IEE will undo a performed operation each time this button
is clicked. It can undo all operations that were performed after
the last successful commit, or since the user started using the
application.
Undo All - Pressing this command will undo all operations hat
were performed after the last successful commit, or since the
user started using the application.
Redo - Pressing this command will redo a previously undone
operation each time this button is clicked. It can redo all
operations that were performed after the last successful commit,
or since the user started using the application.
Save Settings - Pressing this command will save the current IEE
environment settings locally. These settings will be used very
time the user starts IEE until the settings are saved again.
Understanding IEE To take full advantage of the functionality provided by IEE and to
Settings ensure that all edits made using the IEE environment, users should
familiarize themselves with the following concepts before making
changes in the IEE Settings Dialog.
Snapping When digitizing IEE will automatically snap to nodes or vertices. The
IEE Snapping Engine allows this. 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.
Data Locking 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.
Release Locks on Exit 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.
Tutorial 39
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.
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.
IEE Tolerance 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 non-longitude/latitude, the tolerance unit is the same as the
coordinate system unit associated with the spatial data.
IEE Settings This dialog provides access to the IEE Settings. It opens when you
click the IEE Settings option in IEE menu.
Dialog
Locking & Grid Settings Figure 10: Locking & Grid Settings Tab
40 Tutorial
Lock Mechanism Settings:
Use Pessimistic Locking - When this checkbox is selected,
pessimistic locking is implemented in the database during data
extraction. De-selecting this option implements optimistic
locking.
Release Locks on Exit - When this checkbox is selected, all
locks held by IEE will be released when you close IEE.
Process Settings:
Display Progress Bar - When this checkbox is selected, a
progress bar will display during the extraction of data from the
database and when saving data to the database.
Grid Settings:
Grid Major – A value greater than 0.0 entered in this field
defines the distance in real world coordinates between points on
the grid in the X or horizontal dimension. Default is 0.0 or no grid.
Grid Minor – A value greater than 0.0 entered in this field
defines the distance in real world coordinates between points on
the grid in the Y or vertical dimension. Default is 0.0 or no grid.
Snapping Settings Figure 11: Snapping Settings Tab
The Snapping engine is always enabled.
Units:
Distance - Selecting this option defines the units of the Diameter
field to be measured in real world units, defined by the coordinate
system currently in use.
Pixels - Selecting this option defines the units of the Diameter
field to be measured in on-screen pixels.
Tutorial 41
The Distance and Pixels options are mutually exclusive, that is,
only one of them can be selected at any one time.
Max Visible Scale: - The value entered in this text field defines the
scale below which the End Points and All Points will be displayed, if
selected for display. If this value is set to zero, End Points and All
Points will be displayed at all scales, if selected for display.
End Points:
Visible - Selecting this option displays a circle at the start and
end nodes of a line.The color of the circle is determined by the
value selected in the Color drop down list. The diameter of the
circle is determined by the value in the Diameter field.
Deselecting this option hides the circle at the start and end
nodes. The Diameter field is measured in either real world
distance or on-screen pixels. It is converted to real world
coordinates when snapping occurs. The value in the Diameter
field also determines the snapping tolerance.
A color selection box shows the current color selected for end
points. Click the icon to the left of the color box to choose another
color.
Diameter – Determines the diameter of the end point circle
displayed. The Diameter field is measured in either real world
distance or on-screen pixels depending on the setting in the Units
section.
Vertex Points:
Visible - Selecting this option displays a circle at all vertices of a
line.The color of the circle is determined by the value selected in
the Color drop down list. The diameter of the circle is determined
by the value in the Diameter field. Deselecting this option hides
the circle at the nodes. The Diameter field is measured in either
real world distance or on-screen pixels. It is converted to real
world coordinates when snapping occurs. The value in the
Diameter field also determines the snapping tolerance
A color selection box shows the current color selected for vertex
points. Click the icon to the left of the color box to choose another
color.
Diameter – Determines the diameter of the vertex point circle
displayed. The Diameter field is measured in either real world
distance or on-screen pixels depending on the setting in the Units
section.
42 Tutorial
Topology and Display Figure 12: Topology and Display Tab
Settings
IEE Tolerancing:
Precision - Determines the precision of all edits performed using
IEE. Enter the value of the new precision in the field.
Topology:
Allow ISO Moves - When this option is checked, IEE will allow
the modification of topology edges affecting the topology face
that any isolated nodes or edges fall in.
When this option is not checked (default), IEE will apply normal
Oracle topology rules when modifying topology edges. IEE will
then return an exception if an edge is modified that changes the
face in which an isolated node or isolated edge fall in.
Display Settings:
Hilite Color - Shows the current color selected for the Hilite
Color.
Draw Handles (Selection) - When this option is checked, draw
handles are displayed. To hide draw handles upon a select
operation de-select the Draw Handles option
Display Bounding Boxes - When this option is checked, red
lines will display representing each layers minimum bounding
rectangle or MBR.
Tutorial 43
IEE Locks Figure 13: IEE Locks
Understanding IEE To take full advantage of the functionality provided by IEE and to
Digitizing Locks 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 Panel.
Key concepts that need to be understood to use the IEE digitizing
locks effectively are outlined below.
Dissolve Polygon 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 Dissolve Polygon lock to
state the preference for associating the geometry of the lake with the
geometry of the park.
Segmentation Lock When digitizing one may want to activate the IEE Segmentation
Engine. This engine gives you greater control when digitizing linear
features, especially topological edges. 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.
- 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.
44 Tutorial
- 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) When digitizing linear features the IEE Segmentation Engine will
force the start of a new linear geometry or edge to end at an existing
node and delete the trailing start dangle. When unchecked will not
remove trailing start dangle.
Dangle Lock (End) When digitizing linear features the IEE Segmentation Engine will
force the end of a new linear geometry or edge to end at an existing
node and delete the trailing end dangle. When unchecked will not
remove trailing end dangle.
Rubber Band Lock 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 When this lock is enabled, only objects in the theme currently being
modified are affected. When this checkbox is not selected all objects
that intersect or fall within edit tolerance of the object that is being
modified will be affected as well.
Axis Lock When digitizing, IEE may need to draw a line along the x (horizontal)
or y (vertical) axis. The axis lock allows this.
Grid Lock 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. When grid lock is enabled, each
mouse click will be forced to snap to the nearest grid point.
Linear Snap Lock When digitizing a new linear feature and this lock is enabled, the
linear feature is automatically snapped to nodes of an existing
feature. In this way, can ensure that each node on your new line will
snap to a node on an existing line, thus maintaining topology.
Tutorial 45
Theme Control This panel allows the user to choose which themes/layers they wish
to have display and edit control over.
Figure 14: Theme Control Panel
Display Themes This allows the user to switch on and off for display the themes listed
by selecting or deselecting the options. Themes on the client can
only be switched on/off on the fly if they are in the edit themes list.
Switching on/off the display of background themes warrants a

round trip to the server.
Edit Themes This allows the user to switch on and off for editing the themes listed
by selecting or deselecting the options. A change in the edit warrants
a round trip to the server for a new extract list.
If a user has a theme 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.
46 Tutorial
Digitizing with IEE
Place Point Geometry To place a point geometry with IEE:
1. Select a theme from the Themes section of the Active Theme

Panel that has a point/Marker style.
2. Select a point/Marker style from the Styles section of the Active

Theme Panel.
3. Press to initiate the place point geometry mode.
4. Click the left button to place a point geometry.
5. Fill in the attributes when the Feature Attributes panel appears.
6. Click OK to accept the point geometry and its attributes or,
7. Click Cancel to reject the point geometry and its attributes.
Place Line Geometry To place a line geometry with IEE:

Panel that contains a line style.
2. Select a line style from the Styles section of the Active Theme
Panel.
3. Press to initiate the place line geometry mode.
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.
8. Click OK to accept the line geometry and its attributes or,
9. Click Cancel to reject the line geometry and its attributes.
Place Polygon Geometry To place a polygon geometry with IEE:

Panel that contains a polygon style.
2. Select a polygon style from the Styles section of the Active

Theme Panel.
Tutorial 47
3. Press to initiate the place polygon geometry mode.
4. Click the left button to place a starting point for the polygon
geometry.

the polygon.
8. Click OK to accept the polygon geometry and its attributes or,
9. Click Cancel to reject the polygon geometry and its attributes.
Place Circle Polygon To place a circle polygon geometry with IEE:

Geometry

Theme Panel.
3. Press to initiate the place circle polygon geometry mode.
4. Click a left button to define the first point on the circle.
5. Click another left button to define a second point on the circle.

A dynamic circle will show as the cursor is moved representing
the circle passing through the three points.
6. Click a left button to define the third point on the circle and a
circle polygon will be placed.
8. Click OK to accept the circle polygon geometry and its attributes

or,
9. Click Cancel to reject the circle polygon geometry and its

attributes.
Place Circle Polygon To place a circle polygon geometry by center with IEE:
Geometry by Center

Theme Panel.
3. Press to initiate the place circle polygon geometry mode.
48 Tutorial
4. Click a left button to define the center of the circle polygon.
A dynamic circle will show as the cursor is moved representing
the circle defined by the center point and the cursor location as
radius.
5. Click a second point to define the radius and a circle polygon will
be placed.
7. Click OK to accept the circle polygon geometry and its attributes

or,
8. Click Cancel to reject the circle polygon geometry and its

attributes.
Place Rectangle Polygon To place a rectangle polygon geometry with IEE:

Geometry

Theme Panel.
3. Press to initiate the place rectangle polygon geometry

mode.
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.
7. Click OK to accept the rectangle polygon geometry and its

attributes or,
8. Click Cancel to reject the rectangle polygon geometry and its

attributes.
Place Circular Arc To place a circular arc geometry with IEE:

Geometry
Panel.
3. Press to initiate the place circular arc geometry mode.
Tutorial 49
4. Click a left button to define the first point on the circular arc.
5. Click another left button to define a second point on the curricular

arc.
A dynamic circular arc will show as the cursor is moved
representing the circle passing through three points (the first and
second point and the cursor location).
6. Click a left button to define the third point on the arc and a
circular arc will be placed.
8. Click OK to accept the circular arc geometry and its attributes or,
9. Click Cancel to reject the circular arc geometry and its attributes.
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 44
Place Isolated Node To place an isolated node primitive in a topology with IEE:
Primitive
Panel that has been defined for a topology layer.
2. Select the point/marker style from the Styles section of the

Active Theme Panel that represents the topology nodes.
3. Press to initiate the place isolated node primitive mode.
4. Click the left button to place a node.
Place Edge Primitive To place an edge primitive with IEE:

Panel that has been defined for a topology layer.
2. Select the point/marker style from the Styles section of the

Active Theme Panel that represents the topology nodes.
3. Press to initiate the place edge primitive mode.
4. Click the left button to place a starting point for the edge
primitive.
50 Tutorial
the edge.
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 To place a point feature with IEE:

Panel that has a point/Marker style.
9. Select a point/Marker style from the Styles section of the Active

Theme Panel.
10. Press to initiate the place point feature mode.
11. Click the left button to place a point feature.
13. Click OK to accept the point feature and its attributes or,
14. Click Cancel to reject the point feature and its attributes.
Place Line Feature To place a line feature with IEE:

Panel.
3. Press to initiate the place line feature mode.
4. Click the left button to place a starting point for the line feature.

the line.
Tutorial 51
8. Click OK to accept the line feature and its attributes or,
9. Click Cancel to reject the line feature and its attributes.

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:
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 To place a polygon feature with IEE:


Theme Panel.
3. Press to initiate the place polygon feature mode.
feature.

the polygon.
8. Click OK to accept the polygon feature and its attributes or,
9. Click Cancel to reject the polygon feature and its attributes.

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:
nodes.
- Associate all new and or modified faces with the polygon
feature.
Place Polygon Interact To place a polygon interact feature with IEE:

Feature
52 Tutorial
Theme Panel.
3. Press to initiate the place polygon interact feature mode.
feature.

the polygon.
7. All topology faces that interact with the digitized polygon will
then be used to create a new polygon feature.
9. Click OK to accept the polygon feature and its attributes or,
10. Click Cancel to reject the polygon feature and its attributes.
Saving Data to
Database
To save changes made during an edit session the Save Button in the
Viewer Menu is used. When the save button is clicked 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,
i.e.optimistic locking is implemented, IEE performs all
pending database DML and performs a database commit.
Local undo history will be cleared.
- 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.
Tutorial 53
Exporting Spatial Spatial data (points, lines, and polygons) must be exported to the
Oracle database in Oracle Spatial format. This section describes the
Data to Oracle
steps required for the export of spatial data.
1. Create a user (schema) in the Oracle 10g database with sufficient

privileges.
May require DBA support for user creation and granting of

privileges.
2. Start IMAGINE 9.0.
3. Start the Import/Export tool by clicking this button on the main
icon panel.
4. Click the Export button.
5. Set Type field to Oracle Spatial Feature.
6. Set Media field to File.
7. Use Browse tool to locate .shp file as input file.
8. Choose or type in a name for the .ogv file.
9. Click OK button to open the Loading Shapefile to Oracle panel.
10. Choose the coordinate system.
11. Click the Connect button to choose an existing connection or

create a new connection.
12. Click OK button to start conversion of shapefile.
For more information on IMAGINE’s conversion process see the

ERDAS IMAGINE Import/Export on-line help file “Oracle Spatial
Shapefile Loader“.
Before IEE can be used as an editing environment, you must use

the Oracle Map Definition Tool to define styles, themes, amd
maps for exported spatial data.
54 Tutorial
Index draw handles (selection) 43
E
Symbols edge primitive 50
edge topology element 24
<features> element 27
edit themes 46
<label> element 27
elements 6
end points 42
A exporting spatial data to oracle 54
ALL_SDO_MAPS 30 exterior polygons 5
ALL_SDO_STYLES 30
ALL_SDO_THEMES 30
ALL_SDO_xxx 30
F
face topology element 24
allow ISO moves 43
application considerations 23
area style metadata 26 G
axis lock 45 generalized layer 23
geodetic data 20
B geometric primitive type
lines 5
base map 29
points 5
BucketStyle 26
polygons 5
geometries 7
C Great Circle distances 21
circle polygon geometry 48 grid 40
circle polygon geometry by center 48 grid lock 45
circular arc geometry 49 grid major 41
color metadata style 25 grid minor 41
ColorSchemeStyle 26 grid settings 41
connection 34 Gtypes 8
CREATE INDEX statement 22
H
D hilite color 43
dangle lock (end) 45 history table 25
dangle lock (start) 45
data loading 21
data locking 39
I
database privileges 25 IEE Interface 38
IEE locks 44
DATE data type 3
detailed layer 23 IEE settings 39
diameter end points 42 IEE Settings dialog 40
diameter vertex points 42 IEE tolerance 40
dictionary table 20 IEE tolerancing 43
digitizing 47 Import 21
digitizing locks 44 indexing spatial data 22
discover options 35 interior polygons 5
display bounding boxes 43 isolated node primitive 50
display metadata 25
display progress bar 41 J
display settings 43 Java class style types 26
display themes 46 JDBC theme 27
dissolve polygon lock 44
distance units 41
draw handles 40
Index 55
L styling rules 27
LAYER_GTYPE parameter 22 process settings 41
layers 7
line element data 6 R
line feature 51 RDBMS data model 3
line geometry 47 rectangle polygon geometry 49
line style metadata 26 redo command 39
linear snap lock 45 relationship table 25
lock mechanism settings 41 release locks on exit 39, 41
locking 40 R-Tree spatial indexes 22
longitude/latitude 20 rubber band lock 45
rules for accessing mapping metadata 30
M
map selection 35 S
maps 28 sample data 1
marker metadata style 26 save settings command 39
max visible scale 42 saving data to database 53
MDSYS.CS_SRS 20 schema 34
MDSYS.SDO_GEOMETRY 27 SDO_GEOM.VALIDATE_GEOMETRY_WITH_C
metadata table 25 ONTEXT 21
metadata views 30 SDO_GEOM.VALIDATE_LAYER_WITH_CONTE
XT 21
N SDO_GEOM_METADATA_TABLE 19
node topology element 24 SDO_GEOMETRY 19
NUMBER data type 3 SDO_GEOMETRY data type 3
SDO_MAPS_TABLE 30
SDO_STYLES_TABLE 30
O
SDO_THEMES_TABLE 30
OGC 20
SDO_UTIL.EXTRACT routine 22
Open GIS Consortium 20
SDO_UTIL.REMOVE_DUPLICATE_VERTICIES
optimistic locking 39
routine 22
ORA 13349 validation error 22
search and locate 36
segmentation lock 44
server (connection) 34
Oracle 3
SID (connection) 34
geometric types 4
snapping 39
spatial example 4
snapping settings 41
Oracle Map Definition Tool 25
spatial data modeling 3
Oracle Spatial element types 9
SQL*Loader 21
SRID 19
P start IEE 33
password 34 styles (metadata) 25
pessimistic locking 39 area 26
pixels units 41 color 25
point element data 6 line 26
point geometry 47 marker 26
polygon element data 6 text 26
polygon feature 52 styling rules 27
polygon geometry 47 styling rules example 27
polygon interact feature 52
port (connection) 34
T
precision tolerancing 43
text style metadata 26
predefined themes 27
theme control 46
56 Index
theme lock 45
themes 27
Tolerance 20
topo_geometry 24
topological data model 24
topology 43
topology settings 43
topology-related tables 25
transaction management commands 39
U
undo all command 39
undo command 39
UNION ALL operation 28
units 41
use pessimistic locking 41
USER_SDO_GEOM_METADATA 19, 40
USER_SDO_MAPS 25, 30
USER_SDO_STYLES 25, 30
USER_SDO_THEMES 25, 27, 30
USER_SDO_xxx 30
username (connection) 34
V
validation errors 21
VARCHAR2 data type 3
VariableMarkerStyle 26
vertex points 42
visible end points 42
visible vertex points 42
visualization 23
W
well_known_text (WKT) grammar 20
WHERE clause 28
Index 57
58 Index

IEE User Guide

Uploaded by

Copyright:

Available Formats

IEE User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IEE User Guide

Uploaded by

Copyright:

Available Formats

IMAGINE Enterprise

All rights reserved.

Printed in the United States of America.

Manager, Technical Documentation

The information contained in this document is subject to change without notice.

SOCET SET is a registered trademark of BAE Systems Mission Solutions.

Documentation This manual is part of a suite of on-line documentation that you

• double-click — click twice with the left mouse button.

• Shift-click — hold down the Shift key on your keyboard and

• middle-click — click once with the middle mouse button.

• right-click — click once with the right mouse button.

The following paragraphs are used throughout the ERDAS IMAGINE

These paragraphs contain strong warnings or important tips.

These paragraphs give you software version-specific

These paragraphs provide information about Leica Geosystems

These paragraphs lead you to other areas of this book or other

NOTE: Notes give additional instruction.

Overview of IEE The IMAGINE Enterprise Editor provides a seamless interface

Oracle Spatial IMAGINE Enterprise Editor provides a seamless interface between

File / Directory Based Oracle Spatial

2 to 8 files for All data for a layer is

Layers are added Layers are grouped

Spatial Data Model –

Table 1: Road Table Example

ROAD ROAD ROAD NUM SURFACE GEOM

HWY-25 32456 Primary 4 Concrete sdo_geometry

I-70 32456 Primary 4 Concrete sdo_geometry

Main St 345621 City 2 Asphalt sdo_geometry

CR-34 234001 County 1 Dirt sdo_geometry

Table 2: sdo_geometry Structure

Name Type Description

SDO_GTYPE NUMBER Defines the kind of geometry

SDO_SRID NUMBER Used to identify a coordinate system

SDO_POINT SDO_POINT_TYPE Optimized storage for point data

SDO_ELEM_INFO SDO_ELEM_INFO_ARRAY Defines how to interpret the ordinate array

SDO_ORDINATES SDO_ORDINATE_ARRAY Storage for ordinates of geometry

Supported Geometric Oracle Spatial supports three multi-dimensional geometric primitive

• Points (X1, Y1)

• Polygons (X1, Y1,... Xn, Yn)

Geometric Primitive Types

Polygon Compound Optimized Self-

Points are elements composed of between two and four ordinates, if

Point data consists of one or more coordinates (or more than 2

A complex geometric feature such as a polygon with holes would be

Layers The graphic below illustrates geometries stored in a polygonal layer

Table 3: Oracle Spatial Gtypes

0 Unknown 2000 3000 4000

1 Point 2001 3001 4001

2 Linestring 2002 3002 4002

3 Polygon 2003 3003 4003

4 Collection 2004 3004 4004

5 MultiPoint 2005 3005 4005

6 MultiLinestring 2006 3006 4006

7 MultiPolygon 2007 3007 4007

The main reason for discussing earlier version of Oracle Spatial is

1 POINT # of points in collection

2 LINESTRING 1 - Straight lines

3 POLYGON 1 - Straight lines

4 COMPOUND LINESTRING # of type 2 sub-elements that make up

5 COMPOUND POLYGON # of type 2 sub-elements that make up