Pitney Bowes MapXtreme - Manual (Page 301)

Chapter 16: Spatial Objects and Coordinate Systems
Geometries
MapXtreme v7.1 308 Developer Guide
contains 5 points (with the first and last points being identical), and are effected by the coordinate
system. In some instances, the converted Rectangle may no longer appear rectangular. Use the
CreateMultiPolygon method to convert a RoundedRectangle to a FeatureGeometry object.
See the Developer Reference for a code example.
Ellipse
The Ellipse is inscribed in an axis-aligned rectangle defined by a DRect. The DRect is defined by two
points, the opposite corners of a rectangle, with the other two corners of the rectangle implied. The
Ellipse displays as if it were unprojected, regardless of the coordinate system, and any skew that
may be represented by the coordinate system.
Because Ellipse objects are defined by two points and always display axis-aligned and unprojected,
they are designed to be used primarily for cosmetic display purposes. While many operations are
available using Ellipse objects, internally, a MultiPolygon copy of the Ellipse is used for these
operations. The resulting MultiPolygon is effected by the coordinate system and in some cases may
no longer appear as a perfect ellipse.
See the Developer Reference for a code example.
LegacyArc
The LegacyArc object is a portion of an Ellipse and is defined by a DRect, a start angle, and an end
angle. The Ellipse is constructed to be inscribed in the rectangle defined by the DRect. The
rectangle, in which the Ellipse is inscribed, is axis-aligned and is always rectangular regardless of
the coordinate system used. The angles are measured in degrees with zero being along the positive
X-axis and positive angles being in the counterclockwise direction. The angles are only stored to a
tenth of a degree resolution with values between 0.0 and 360.0.
Because LegacyArc objects are defined by two points (for the DRect) and angles, and are always
displayed axis aligned, they are designed to be used primarily for cosmetic display purposes. While
many operations are available using LegacyArc objects, internally, a MultiCurve copy of the
LegacyArc is used for these operations. This can sometimes lead to unexpected results.
See the Developer Reference for a code example.
LegacyText
The LegacyText object is the MapInfo Professional equivalent of a text object. If a given database
does not support Text the LegacyText object can be lost when using that format. LegacyText objects
are placed within a geographically-sized rectangle with a lower-left anchor point specified. The point-
size of the text is based upon what fits best within the rectangle.
LegacyText objects do not fit nicely into the Geometry model. Several methods available on the
Geometry FeatureGeometry classes, such as Combine, make no sense for LegacyText and will
throw a NotSupportedException. Text objects do exist in MapInfo native TAB files in the Geometry
column. The LegacyText class provides a way to access these objects. Refer to online reference for
specific behaviors of LegacyText objects.