BoundingBox


superclasses:

Tuple

attributes:

[coordSystem] CoordinateSystem

[geodeticReference] GeodeticReferenceSystem

minPoint Point

maxPoint Point

comments:

Typically a bounding box is specified in the same coordinate and geodetic reference systems as the data contained in the transfer. In this case coordSystem is not specified. In some situations, it is of interest to be able to specify a bounding box in one coordinate system, and the spatial data in another. For example, a mapsheet boundary may be specified in latitude and longitude, whereas the data within the mapsheet map be in UTM. In such cases coordSystem is specified; it applies to the coordinates provided for minPoint and maxPoint.

Two diagonally opposed points are specified, using the same type of Coordinate to indicate position. A minimum x and y ( or x, y, and z; or x, y, and t; or x, y, z, and time) define the position of the first point, and a maximum x and y ( or x, y, and z; or x, y, and t; or x, y, z, and time) define the second position of the second point. The data is assumed to be within (or on the boundary) of the location and time so defined. The type of Coordinate used controls whether the boundary is two, three or four dimensional in nature.

Typically, a bounding box (rangle rectangle) is specified by instantiating the coordinate for each point using the subclass Coordinate, CoordXY, CoordXYZ, CoordXYT, or CoordXYZT.


Links to Section 3.6.3 and the complete SAIF class list