@UML(identifier="GM_Primitive", specification=ISO_19107) public interface Primitive extends Geometry
Any geometric object that is used to describe a feature is a collection of geometric primitives.
A collection of geometric primitives may or may not be a geometric complex. Geometric complexes
have additional properties such as closure by boundary operations and mutually exclusive component
Complex share most semantics, in the meaning of operations
and attributes. There is an exception in that a
Primitive shall not contain its boundary
(except in the trivial case of point where the boundary is empty), while a
complex shall contain its boundary in all cases.
|Modifier and Type||Method and Description|
Returns the boundary of a
Returns the set of complexes which contains this primitive.
Returns the owner of this primitive.
Returns the orientable primitives associated with this primitive.
clone, distance, getBuffer, getCentroid, getClosure, getConvexHull, getCoordinateDimension, getCoordinateReferenceSystem, getDimension, getEnvelope, getMaximalComplex, getMbRegion, getPrecision, getRepresentativePoint, isCycle, isMutable, isSimple, toImmutable, transform, transform
@UML(identifier="boundary", obligation=MANDATORY, specification=ISO_19107) PrimitiveBoundary getBoundary()
Primitiveas a set of
Primitives. This is a specialization of the operation at
Geometry, which does not restrict the class of the returned collection. The organization of the boundary set of a
Primitivedepends on the type of the primitive.
@UML(identifier="containedPrimitive", obligation=MANDATORY, specification=ISO_19107) Set<Primitive> getContainedPrimitives()
Primitives which are by definition coincident with this one. This allows applications to override the
TransfiniteSet<DirectPosition>interpretation and its associated computational geometry, and declare one
Primitiveto be "interior to" another. This set should normally be empty when the
Primitives are within a complex, since in that case the boundary information is sufficient for most cases. This association should not be used when the two
Primitives are not close to one another. The intent is to allow applications to compensate for inherent and unavoidable round off, truncation, and other mathematical problems indigenous to computer calculations.
@UML(identifier="containingPrimitive", obligation=MANDATORY, specification=ISO_19107) Set<Primitive> getContainingPrimitives()
Primitives which are by definition coincident with this one.
@UML(identifier="complex", obligation=MANDATORY, specification=ISO_19107) Set<Complex> getComplexes()
Primitivemay be in several complexes. This association may not be navigable in this direction (from primitive to complex), depending on the implementation.
@Association(value="Composition") @UML(identifier="composite", obligation=OPTIONAL, specification=ISO_19107) Composite getComposite()
Primitive, not the other way.
nullif the association is not available or not implemented that way.
@Association(value="Oriented") @UML(identifier="proxy", obligation=CONDITIONAL, specification=ISO_19107) OrientablePrimitive getProxy()
Primitiveof dimension 1 or 2 is associated to two orientable primitives, one for each possible orientation. For curves and surfaces, there are exactly two orientable primitives for each geometric object. For the positive orientation, the orientable primitive shall be the corresponding curve or surface.
Copyright © 1996–2017 Geotools. All rights reserved.