Contact:

Niels Charlier

Tracker:

GEOS-5148

Tagline:

bbox 3d

 

Children:

Description

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:

BBOX=x0,y0,z0,x1,y1,z1

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:

<ogc:Filter>" 
 <ogc:BBOX>" 
  <gml:Envelope srsName=\"EPSG:4979\">
    <gml:lowerCorner>-200 -200 0 </gml:lowerCorner>
    <gml:upperCorner> 200 200 50 </gml:upperCorner>
   </gml:Envelope>
 </ogc:BBOX>
</ogc:Filter>

In order to accomplish this, Geotools must support

Status

Voting has started:

Tasks

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

 

no progress

(tick)

done

(error)

impeded

(warning)

lack mandate/funds/time

(question)

volunteer needed


1. Update ReferencedEnvelope hierarchy  
     - (tick)NC: Define ReferencedEnvelope3D and a BoundingBox3D interface
     - (tick)NC: Update ReferencedEnvelope.reference method to appropriately cast
     - (tick)NC: Test cases for the above
      -(tick)NC: pull request / patch
2. Update BBox filter interface
     - (tick)NC: Add BBox.getBounds() and javadocs, the deprecated methods can refer to bbox.getBounds() above
     - (tick)NC: Update FilterFactory2 if needed (it works as a literal expression, but javadocs may need a note)
     - (tick)NC: pull request / patch
3. Initial Filter support
    - (tick) NC: initially implement as a "post" filter
    - (tick) NC: test on property datastore (ie AbstractDataStore base class)
   -  (warning)  test on property-ng datastore (ie. ContentDataStore base class) 
    - (tick) NC: test on postgis and oracle
4. Update documentation - before tagging in others so there are working examples
     - (tick) JG: review javadocs
     - (tick) NC: gt-main filter examples - prep code example or update existing example
     - (tick) NC: gt-opengis filter api update ObjectAID diagram and describe the new class
5. XML Encoding / Decoding
     - ? Update Filter 2 bindings
     - (tick) Update Filter 1.1 bindings
     - ? Update Filter 1.0 bindings
     - (tick) WFS POST/GET request Encoding
     - (tick) BCD: Ensure OGC Standard supports n-dimensional bounding boxes
6. Pull request
    - (tick) submit pull request
    - (tick) AA :review
7. Update and test downstream applications
   - (tick) NC: GeoServer patch 
   - JG: uDig Patch
8. (warning) Support SQL encoding of 3D Bounding Boxes
    - split the 3D bbox filter into two. PRE: reduce to a 2D bbox to take advantage of spatial index. POST: Client side check of the Z values
    - proof of concepts using jdbc-hsql
    - roll out to remaining implementations: jdbc-postgis, jdbc-oracle etc...
9. QA Run to confirm existing datastore implementations do not fail when provided a 3D BBox to test against

10. ReferencedEnvelope fails when provided a 3D CRS

11. FeatureCollection getBounds() implementations fail when provided a 3D CRS

12. Finish and cleanup
   - NC: revise based on integration with downstream applications (usually just javadocs, or the occasional bug report)
   - NC: Close the jira, news announcement, possible milestone release (depending on what you need for your deadline)

API Changes

The changes are API additions, rather than changes.
There will be the following new interfaces in geoapi:

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

The FIlterFactory interfaces will be extended with the following methods:

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.

Filter

BEFORE:

Envelope env = new ReferencedEnvelope(minx, maxx, miny, maxy, crs)



BBOX filter = filterfac.bbox(propertyName, minx, miny, minz, maxx, maxy, maxz, srs);
boolean result = filter.eval(geom);


BBOX otherFilter = ...
BBOX filter = filterfac.bbox(propertyName, otherfilter.getMinX(), ... , srs); 

AFTER:

BoundingBox3D env = public ReferencedEnvelope3D(x1, x2, y1, y2, z1, z2, crs)
BBOX3D filter = filterfac.bbox(propertyName, env);
boolean result = filter.eval(geom);

BBOX otherFilter = ...
BBOX filter = filterfac.bbox(propertyName, otherfilter.getBounds());

Documentation Changes

list the pages effected by this proposal