Geometry
defines a leaf node of the scene graph. The leaf node contains the geometric data for rendering objects. It manages all rendering information such as a {@link Material} object to define how the surfaceshould be shaded and the {@link Mesh} data to contain the actual geometry.
@author Kirill Vainer
GeometryCollection
s would be useful, GeometryCollection
s are not supported as arguments to binary predicates (other than convexHull
) or the relate
method. Point
, LineString
, or Polygon
will be returned if the result contains a single element; otherwise, a MultiPoint
, MultiLineString
, or MultiPolygon
will be returned. If the result is heterogeneous a GeometryCollection
will be returned. Because it is not clear at this time what semantics for set-theoretic methods involving GeometryCollection
s would be useful, GeometryCollections
are not supported as arguments to the set-theoretic methods.
Geometry
. The SFS does not specify an unambiguous representation of a given point set returned from a spatial analysis method. One goal of JTS is to make this specification precise and unambiguous. JTS will use a canonical form for Geometry
s returned from spatial analysis methods. The canonical form is a Geometry
which is simple and noded:
isSimple
. LineString
s. It means that all intersection points on LineString
s will be present as endpoints of LineString
s in the result. Geometry
s. These new points arise from intersections between line segments in the edges of the input Geometry
s. In the general case it is not possible to represent constructed points exactly. This is due to the fact that the coordinates of an intersection point may contain twice as many bits of precision as the coordinates of the input line segments. In order to represent these constructed points explicitly, JTS must truncate them to fit the PrecisionModel
. Unfortunately, truncating coordinates moves them slightly. Line segments which would not be coincident in the exact result may become coincident in the truncated representation. This in turn leads to "topology collapses" -- situations where a computed element has a lower dimension than it would in the exact result.
When JTS detects topology collapses during the computation of spatial analysis methods, it will throw an exception. If possible the exception will report the location of the collapse.
#equals(Object) and #hashCode are not overridden, so that when two topologically equal Geometries are added to HashMaps and HashSets, they remain distinct. This behaviour is desired in many cases. @version 1.7
Each of these geometric types defines a visible object or set of objects. A Geometry object is used as a component object of a Shape3D leaf node.
Definition of a DTO geometry object. This geometry type is used for client-server communication. Internally on the server, these geometries are converted into JTS geometries.
@author Pieter De Graef @since 1.6.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|