Is this update you mention for WCS 2.0 specifically for the case where bounding boxes cross the dateline, or is it more general to the situation of bounding boxes being specified with longitude ranges [0:360] instead of [-180:180] such as GRIB2 data?
On Fri, Aug 29, 2014 at 4:55 PM, Benz, David E <David.Benz@anonymised.com> wrote:
Is this update you mention for WCS 2.0 specifically for the case where
bounding boxes cross the dateline, or is it more general to the situation
of bounding boxes being specified with longitude ranges [0:360] instead of
[-180:180] such as GRIB2 data?
It is the for the case of dateline crossing, and it supports what the WCS
standard traditionally
suggested, that is, to use specify a minx > maxx, but it will work also for
cases in which you
go beyond 180 (but are still crossing the dateline).
I'm not sure however what might happen if you ask for an area that's fully
beyond 180,
the sponsoring for dateline crossing in WCS did not cover this case.
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------