Pitney Bowes MapXtreme - Manual (Page 217)

Chapter 11: Accessing Data from a DBMS
Accessing Data from Oracle
MapXtreme v7.1 224 Developer Guide
The table below describes the translation from Oracle (GTYPES) to MapInfo Spatial objects.
Oracle Support for Z and M Values
MapXtreme supports reading and writing Oracle GTYPEs with Z and M values. The presence and
order of Z and M is determined by inspecting the DIM_INFO array in the
USER_SDO_GEOM_METADATA for the table. MapXtreme checks for the following dimension
names (case insensitive):
• For Z dimension: "Z", "Elevation", " Depth" and "Z Dimension"
• For M dimension: “M", "Measure", and "M Dimension"
Tables that contain M and/or Z values now return FeatureGeometry objects that contain the data for
the dimensions present. FeatureGeometry instances inserted or updated into an Oracle table will
preserve each of the four dimensions of the new geometry (XYZM) that the Oracle table is defined to
support. For geometries containing dimensions unsupported by the Oracle table, the values for
Rectangle NULL
LegacyText NULL
RoundedRectangle NULL
PieTheme, BarTheme NULL
From MapInfo To Oracle
From Oracle GTYPES To MapInfo
0 * UNKNOWN_GEOMETRY (Spatial ignores this geometry.)
*Some data loss may occur when translating to or from MapInfo object format. They are interpreted
(when possible) as single point SDO_POINTTYPE values if not already NULL. They “grab” the first
point in the ordered array which would be interpreted as a NULL geometry.
1 POINT Geometry contains one point. Point
2 LINESTRING Geometry contains one line string. MultiCurve
3 POLYGON Geometry contains one polygon. MultiPolygon
4 * Collection Geometry is a heterogeneous collection of elements.
FeatureGeometryCollection
5 MULTIPOINT Geometry has multiple points. MultiPoint
6 MULTILINESTRING Geometry has multiple line strings. MultiCurve
7 MULTIPOLYGON Geometry has multiple polygons (more than
one exterior boundary). MultiPolygon