One thing I'm wary of is that (AFAIK) the lat-long bounding box is normally
calculated from a reprojected native bounding box.
Transforming 4x points is not adequate to transform the area covered by
that box, and there are several cases where valid data can be excluded in
the resulting lat-lon bounds. Mapnik and other tools work around this by
synthesizing 20(?) intermediate points along each side of the native box,
transforming the polygon, then taking the extent of that polygon to get the
final transformed bounds. And dealing with anti-meridian issues along the
way.
If GeoServer is starting to use lat-lon bounds for filtering (rather than
as indicative areas) then maybe a similar approach should be adopted.
0°>360° or -360°>+360° data should probably also be taken into account.
Cheers,
Rob :)
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
