/*
 * ENUM: SE_SEARCH_DIMENSION_ENUM
 *
 *   Used to specify
 *   (1) whether a search will return 2D objects, if they are present.
 *
 *       To ignore <Location 2Ds>, specify SE_3D_ONLY_SEARCH. (Review
 *       the comments for SE_3D_ONLY_SEARCH for details on how such
 *       a search will evaluate mixed-dimension objects.)
 *
 *       All other searches will consider <Location 2Ds> in evaluating
 *       objects.
 *
 *   (2) whether a search will consider the "height" components of
 *       <Location 3Ds>.
 *
 *       To ignore the "height" component, specify SE_2D_SEARCH.
 *       All other searches will consider the "height" components
 *       of <Location 3Ds> when evaluating them. (See comments
 *       for specific options for details on how other searches
 *       will treat 2D objects and mixed-dimension objects).
 */

Enumerator Notes

SE_2D_SEARCH

 Can be used only for a search boundary that is defined for either
 (1) a 2D spatial reference frame, or
 (2) a 3D spatial reference frame that has a 2D counterpart
     (e.g., geodetic).

 If the SE_SEARCH_BOUNDS are defined in 3D, their "height" components
 are ignored.

 If a <Location 3D> is encountered by the search mechanism, its
 "height" component is ignored, and it is treated as though it
 were its 2D counterpart.

SE_3D_ONLY_SEARCH

 Can be used only for a search boundary that is defined for a
 3D spatial reference frame. The SE_SEARCH_BOUNDS specified
 must be defined in a 3D spatial reference frame.

 For SE_3D_ONLY_SEARCH, the search mechanism will ignore all
 <Location 2D> objects. Consequently,
 (1) no purely 2D object will be returned by this search, since
     all its <Locations> would be ignored by the search mechanism,
 and
 (2) 2D components of a mixed-dimension object will be ignored
     in determining the status of the mixed-dimension object.

SE_2D_OR_3D_SEARCH

 Can be used for a search boundary that is defined in either a
 2D or a 3D spatial reference frame.

 If a <Location 2D> is encountered by the search mechanism, the
 SE_SEARCH_BOUNDS' height range (if there is one) is ignored,
 and just the other two dimensions are considered.

 If a <Location 3D> is encountered by the search mechanism,
 however, its "height" component is evaluated against the
 SE_SEARCH_BOUNDS' height range.