Hello list, We recently hit a roadblock while writing unit tests for an application that uploads data to GeoServer, the problem we encountered was that there were important differences between the data uploaded to GS and then downloaded via WCS.
Specifically: The bounding box by something in the order of 10% The number of rows and columns of the array (i.e. the shape) by +/- 1. This means that the original array cannot be compared directly to the downloaded array as they are not aligned. The origin and pixel size by a few % (This means that the georeferencing of the grid is changed) The grid values themselves are also not exact showing some quite large spikes in some places although viewing the TIF files (before and after passing through GeoServer) shows that they are overall qualitatively similar. I submitted a bug report [1], but I am raising the issue here to get input from people familiar with the WCS codebase, first to verify if it's a real limitation in GeoServer, and second to ask for pointers about places in the code to inspect for possible optimizations. Thanks in Advance, Ariel Núñez [1] http://jira.codehaus.org/browse/GEOS-4372 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
