The goal is to enable a geoserver WFS request with a 3D bounding box so that we receive only geometries not disjoint with that 3D bounding box.
In other words, there is a min and max for the third coordinate as well as the first two.
In 2D we have in KVP:BBOX=x0,y0,x1,y1
However, in 3D we get:
Only 3d geometries that qualify for the min and max pairs for all three axes are returned.
Furthermore, OGC filters in POST requests will also support 3D BoundingBoxes, as for example:
In order to accomplish this, Geotools must support
- 3D Envelopes: a 3D envelope geometry class and a 3D referenced envelope geometry class.
- 3D Bounding Boxes: a 3D Bounding Box has two additional attributes (min z and max z) and filters geometries using all three dimensions.
Voting has started:
- Andrea Aime: +1
- Ben Caradoc-Davies: +1
- Christian Mueller:
- Ian Turton:
- Justin Deoliveira:
- Jody Garnett: +1
- Simone Giannecchini:
This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success
1. Update ReferencedEnvelope hierarchy
- NC: Add BBox.getBounds() and javadocs, the deprecated methods can refer to bbox.getBounds() above
5. XML Encoding / Decoding
- BCD: Ensure OGC Standard supports n-dimensional bounding boxes
- provide a sample test using shapefile
- cut and paste the test in for shapefile-ng, wfs and so on
- JG: sample property file provided, with tests, showed several problems
10. ReferencedEnvelope fails when provided a 3D CRS
- JG: GEOT-4325 Introduce factory method ReferencedEnvelope.create
11. FeatureCollection getBounds() implementations fail when provided a 3D CRS
- JG: Fix PropertyDataStore so we have a working example
- JG: GEOT-4331 Fix OracleDataStore (customer funded)
The changes are API additions, rather than changes.
There will be the following new interfaces in geoapi:
- BBOX3D, for the 3D bbox filter, subinterface of BBOX
- BoundingBox3D, a subinterface of BoundingBox specifying bounding box coordinates
Furthermore, the existing BBOX as well as BBOX3D will support a new method BoundingBox getBounds() which returns a BoundingBox object representing the boundaries of the filter (BoundingBox3D if it is a BBOX3D).
There will be the following new classes in main
- BBOX3DImpl, implementation of filter interface
- ReferencedEnvelope3D, Extension of ReferencedEnvelope3D, extends JTS Envelope methods to use 3D coordinates and provides referenced envelope support for 3D coordinates
The FIlterFactory interfaces will be extended with the following methods:
- BBOX3D bbox(String propertyName, BoundingBox3D bbox);
- BBOX3D bbox( Expression geometry, BoundingBox3D bbox);
- BBOX3D bbox( Expression geometry, BoundingBox3D bbox, MatchAction matchAction);
Furthermore, the implementation of the existing bbox( ..., BoundingBox bbox) methods will be extended to automatically call the 3D methods if the supplied BoundingBox is in fact a BoundingBox3D.
The existence of BBOX3D filter has implications for FilterVisitors. Although the APi does not change, the visitor method bbox must support BBOX3D if it wants to regenerate the filter without loosing information.
Because of the generic bbox( ..., BoundingBox bbox) and getBounds() methods it is possible to copy a BBOX filter in a generic way (see last example below).
These implications must all be documented.
list the pages effected by this proposal