Message-ID: <1127798933.301313.1369120079346.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_301312_569552116.1369120079346" ------=_Part_301312_569552116.1369120079346 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
v= olunteer needed
10. ReferencedEnvelope fails when provided a 3D CRS=
11. FeatureCollection getBounds() implementations fail when pr= ovided a 3D CRS
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 getBo= unds() which returns a BoundingBox object representing the boundaries of th= e filter (BoundingBox3D if it is a BBOX3D).
There will be the followi= ng new classes in main
The FIlterFactory interfaces wi= ll be extended with the following methods:
F= urthermore, the implementation of the existing bbox( ..., BoundingBox bbox)= methods will be extended to automatically call the 3D methods if the suppl= ied BoundingBox is in fact a BoundingBox3D.
The existenc= e of BBOX3D filter has implications for FilterVisitors. Although the APi do= es not change, the visitor method bbox must support BBOX3D if it wants to r= egenerate the filter without loosing information.
Because of the gene= ric bbox( ..., BoundingBox bbox) and getBounds() methods it is possible to = copy a BBOX filter in a generic way (see last example below).
These i= mplications must all be documented.
list the pages = effected by this proposal