I have clients which send a WPS post request with a WCS getCoverage wrapped
into the post body.
Currently all requests contain a CRS of EPSG:4326 with bounding box longitudes
in the [-180:180] range except requests for GRIB2 data. Problems arise (Null
pointer exception thrown by geoserver when computing intersection) for requests
for GRIB2 data which have longitude range in [0:360]. Is there a more
appropriate CRS then EPSG:4326 which should be used to get geoserver to map or
transform the [0:360] bounding box range in the GRIB2 request to the [-180:180]
range expected by the computeIntersectionEnvelope method?
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users