Jukka Rahkonen ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A883da887-d047-4a0a-8aab-3c5d883c4f43 ) *created* an issue
GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZGI2YTY5ZTBhYjBlNDRmOTg5MzM3YmUzMWZkODhkOTQiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-9553?atlOrigin=eyJpIjoiZGI2YTY5ZTBhYjBlNDRmOTg5MzM3YmUzMWZkODhkOTQiLCJwIjoiaiJ9 ) GEOS-9553 ( https://osgeo-org.atlassian.net/browse/GEOS-9553?atlOrigin=eyJpIjoiZGI2YTY5ZTBhYjBlNDRmOTg5MzM3YmUzMWZkODhkOTQiLCJwIjoiaiJ9 ) WCS 2.0 should support SUBSET with limitLow=limitHigh ( https://osgeo-org.atlassian.net/browse/GEOS-9553?atlOrigin=eyJpIjoiZGI2YTY5ZTBhYjBlNDRmOTg5MzM3YmUzMWZkODhkOTQiLCJwIjoiaiJ9 ) Issue Type: Improvement Assignee: Unassigned Components: WCS Created: 26/Mar/20 6:04 PM Priority: Medium Reporter: Jukka Rahkonen ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A883da887-d047-4a0a-8aab-3c5d883c4f43 ) Geoserver does not support subsetting (trimming) if the trim value range has same values as both lower and upper limit. That makes GDAL WCS driver to fail in some circumstances. According to WCS standard subset request with trimLow=trimHigh is valid. Geoserver supports WCS 2.0 GetCoverage request that is making subset slicing with one slice value for both spatial axis (lat, long or east,north). The output of such request is a raster with one pixel. This can be tested with URL https://demo.geo-solutions.it/geoserver/wcs?service=WCS&version=2.0.1&request=GetCoverage&coverageid=nurc__Img_Sample&subset=Long(-100)&subset=Lat(22 ) or with local Geoserver http://localhost:8080/geoserver/wcs?service=WCS&version=2.0.1&request=GetCoverage&coverageid=nurc__Img_Sample&subset=Long(-100)&subset=Lat(22 ) However, trimming with ranges that have the lower limit equal to upper limit are failing. https://demo.geo-solutions.it/geoserver/wcs?service=WCS&version=2.0.1&request=GetCoverage&coverageid=nurc__Img_Sample&subset=Long(-100,-100)&subset=Lat(22,22 ) or http://localhost:8080/geoserver/wcs?service=WCS&version=2.0.1&request=GetCoverage&coverageid=nurc__Img_Sample&subset=Long(-100,-100)&subset=Lat(22,22 ) <ows:Exception exceptionCode= "InvalidSubsetting" locator=""> <ows:ExceptionText>Empty intersection after subsetting</ows:ExceptionText> </ows:Exception> According to WCS 2.0.1 standard the trimLow and trimHigh values in SUBSET can be equal: > > > > Requirement 32 /req/core/getCoverage-request-trim-within-extent: > Let the extent of the coverage’s gml:Envelope along the dimension > specified in the trim > request range from L to H. Then, for the trim bounds trimLow and trimHigh > the following > shall hold: L <= trimLow <= trimHigh <= H. > > It would be nice if subset trimming with trimLow=trimHigh would output a single pixel output just like subset slicing with a single subset values already does. Notice: By reading the standard closely it is actually wrong to output a GeoTIFF or any other raster file with the slicing request. A single pixel raster file has still the same number of dimensions as bigger raster coverages while the WCS standard requires that the output must have fewer dimensions. That is only possible when the outputformat is for example GML or something similar. > > > > Requirement 39 /req/core/getCoverage-response-slicing: > The response to a successful GetCoverage request on coverage identifier id > of admissible > type containing no trimming and exactly one slicing operation with > dimension name dname, > and slice point s shall be a coverage identical to c, but containing > exactly those cells from c > which lie within B, with dimension dname removed from both the coverage’s > domain set and > all of the coverage’s cell coordinate positions, with the number of > dimensions of the result > coverage set to the number of dimensions of c minus 1. > > I consider that the way how Geoserver behaves now is a feature and not a bug. ( https://osgeo-org.atlassian.net/browse/GEOS-9553#add-comment?atlOrigin=eyJpIjoiZGI2YTY5ZTBhYjBlNDRmOTg5MzM3YmUzMWZkODhkOTQiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9553#add-comment?atlOrigin=eyJpIjoiZGI2YTY5ZTBhYjBlNDRmOTg5MzM3YmUzMWZkODhkOTQiLCJwIjoiaiJ9 ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100122- sha1:93a3ad8 )
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
