[Geoserver-devel] [jira] (GEOS-6323) Keep ND coverages dimensions into account when checking size limits

[_Failed_to_Retrieve]

Daniele Romagnoli created an issue

GeoServer / GEOS-6323

Keep ND coverages dimensions into account when checking size limits

Issue Type:	Bug
Affects Versions:	2.5-beta
Assignee:	Andrea Aime
Components:	WCS
Created:	30/Jan/14 5:01 AM
Fix Versions:	2.5-rc1
Priority:	Major
Reporter:	Daniele Romagnoli

Right now, as per GeoServer documentation, the input size limits / output size limits are computed using a formula like this: requestedWidth * requestedHeight * pixelSize for the input size limit outputWidth * outputHeight * pixelSize for the output size limit. However this doesn’t take into account the presence of multiple dimension. If you think about a coverage made of 128x128 gray byte pixels images each one representing a different time/elevation combination from a set of 500 times and 20 elevations, you may easily understand that a WCS request asking for all of them may result into a huge dataset for both input and output. So we need to take into account the dimensions too when computing the size limits.

Add Comment

This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)