A WMS can expect to receive bbox requests that are not geographically
realistic, due to the unknown shape of the resultant image. eg a target
with height > width asking for the whole world must have latitudes well
above 90/below -90.
The WMSCoverageReader handles this well so long as the target image is
in the same CRS as the server, but if not the reader can fail on the
reprojection to the server's CRS before any of the code that handles
this is reached.
I propose to implement the following resolution:
* Reproject the server's reported bounds into the target CRS
* Intersect this with the requested CRS
* Make any adjustments to the target image size
* Reproject this to the server's CRS
* Make the request as currently, including any necessary transformations
to target CRS.
* If necessary, create an image the original target size and overlay the
returned image (masking with white ??? or transparent ???)
* Create the coverage, as currently
Does this ring any alarm bells for anyone?
Thanks
Iain
(GEOT-5604 <https://osgeo-org.atlassian.net/browse/GEOT-5604>)
--
Sent from my ZX80
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
