|
GeoAPI 2.0 Build 2005-06-08 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
@UML(identifier="GM_Primitive",
specification=ISO_19107)
public interface PrimitiveAbstract root class of the geometric primitives. Its main purpose is to define the basic "boundary" operation that ties the primitives in each dimension together. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. This includes curves and surfaces, even though they are composed of curve segments and surface patches, respectively. Those curve segments and surface patches cannot exist outside the context of a primitive.
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
parts. Primitive and 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.
PrimitiveFactory.createPrimitive(Envelope)
| Method Summary | |
|---|---|
PrimitiveBoundary |
getBoundary()
Returns the boundary of a Primitive as a set of
Primitives. |
Set<Complex> |
getComplexes()
Returns the set of complexes which contains this primitive. |
Set<Primitive> |
getContainedPrimitives()
Returns the Primitives which are by definition coincident with this one. |
Set<Primitive> |
getContainingPrimitives()
Returns the Primitives which are by definition coincident with this one. |
OrientablePrimitive[] |
getProxy()
Returns the orientable primitives associated with this primitive. |
| Methods inherited from interface Geometry |
|---|
clone, getBuffer, getCentroid, getClosure, getConvexHull, getCoordinateDimension, getCoordinateReferenceSystem, getDimension, getDistance, getEnvelope, getMaximalComplex, getMbRegion, getRepresentativePoint, isCycle, isMutable, isSimple, toImmutable, transform, transform |
| Methods inherited from interface TransfiniteSet |
|---|
contains, contains, difference, equals, intersection, intersects, symmetricDifference, union |
| Method Detail |
|---|
@UML(identifier="boundary",
obligation=MANDATORY,
specification=ISO_19107)
PrimitiveBoundary getBoundary()
Primitive as 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 Primitive depends on the
type of the primitive.
getBoundary in interface GeometryGeometry.getMbRegion(),
Geometry.getClosure(),
Geometry.getBuffer(double),
Geometry.getDistance(org.opengis.spatialschema.geometry.Geometry)
@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
Primitive to 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.
getContainingPrimitives()
Set returns type allows the user to add or remove element in
this set at his convenience. Is it the right interpretation of this specification? |
@UML(identifier="containingPrimitive",
obligation=MANDATORY,
specification=ISO_19107)
Set<Primitive> getContainingPrimitives()
Primitives which are by definition coincident with this one.
getContainedPrimitives()
Set returns type allows the user to add or remove element in
this set at his convenience. Is it the right interpretation of this specification?
Should we stretch out some relation with contained primitive? For example
should we update the specification with something like the following?
"Invoking B.getContainingPrimitive().add(A) is equivalent to
invoking A.getContainedPrimitive().add(B)". |
@UML(identifier="complex",
obligation=MANDATORY,
specification=ISO_19107)
Set<Complex> getComplexes()
Primitive may
be in several complexes. This association may not be navigable in this
direction (from primitive to complex), depending on the implementation.
Primitive can't be immutable, since
adding this primitive to a complex will change this set? |
@UML(identifier="proxy",
obligation=MANDATORY,
specification=ISO_19107)
OrientablePrimitive[] getProxy()
Primitive
of 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.
null if none.OrientablePrimitive.getPrimitive()
|
GeoAPI 2.0 Build 2005-06-08 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
|
Symbols, terms and definitions | Copyright OpenGIS® Consortium |