Hi Jukka,
Thanks for the response. Adding the "&compression=LZW" parameter to the end of
the WCS GetCoverage request sends a compressed GeoTIFF that I expect.
Some observations:
1) When I use the "Deflate" value as the compression parameter, GeoServer
returns a service exception saying "Provided compression does not seem
supported".
2) When I try the "&geotiff:compression=LZW" parameter, GeoServer does not
return any exceptions but sends an uncompressed GeoTIFF (with GeoServer 2.9.2).
On Wednesday, April 4, 2018, 5:10:03 PM GMT+3, Rahkonen Jukka (MML)
<[email protected]> wrote:
<!--#yiv4195850511 _filtered #yiv4195850511 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv4195850511 {font-family:"Cambria
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv4195850511
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv4195850511
{font-family:"Segoe UI";panose-1:2 11 5 2 4 2 4 2 2 3;}#yiv4195850511
#yiv4195850511 p.yiv4195850511MsoNormal, #yiv4195850511
li.yiv4195850511MsoNormal, #yiv4195850511 div.yiv4195850511MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", serif;}#yiv4195850511 h2
{margin-right:0cm;margin-left:0cm;font-size:18.0pt;font-family:"Times New
Roman", serif;}#yiv4195850511 a:link, #yiv4195850511
span.yiv4195850511MsoHyperlink
{color:blue;text-decoration:underline;}#yiv4195850511 a:visited, #yiv4195850511
span.yiv4195850511MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv4195850511
span.yiv4195850511Otsikko2Char {font-family:"Calibri Light",
sans-serif;color:#2E74B5;}#yiv4195850511
p.yiv4195850511ydp983a8572card-description, #yiv4195850511
li.yiv4195850511ydp983a8572card-description, #yiv4195850511
div.yiv4195850511ydp983a8572card-description
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:"Times New
Roman", serif;}#yiv4195850511 span.yiv4195850511Shkpostityyli19
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv4195850511
.yiv4195850511MsoChpDefault {font-size:10.0pt;} _filtered #yiv4195850511
{margin:70.85pt 2.0cm 70.85pt 2.0cm;}#yiv4195850511
div.yiv4195850511WordSection1 {}-->
Hi,
There is nothing strange with that. Your original image is compressed with
“deflate” and if you expand it into uncompressed format with gdal_translate
(gdal_translate 1201.tif expand.tif) the file size seems to grow into 324626939
bytes. WCS by default sends coverages as uncompressed.
Read about WCS 2.0 GeoTIFF
extensionhttps://portal.opengeospatial.org/files/?artifact_id=54813 and ask
Geoserver to send you a compressed image by adding the required parameter
&compression=Deflate. Using also &predictor=Horizontal probably yields even
smaller output.
BTW. according to the standard the parameters should be
&geotiff:compression=Deflate&geotiff:predictor=Horizontal but older Geoserver
versions do not handle the “geotiff:” part. Geoserver 2.13 and 2.14 support
both variants but users should learn to use the correct geotiff: prefixed
syntax as soon as possible because that is the correct format and required by
other WCS servers.
-Jukka Rahkonen-
Lähettäjä: Mustafa ÖZÇETiN via Geoserver-users
[mailto:[email protected]]
Lähetetty: 4. huhtikuuta 2018 11:12
Vastaanottaja: [email protected]
Aihe: [Geoserver-users] GeoServer Web Coverage Service Issue
Hi,
I have a strange behaviour with GeoServer WCS. I am using a GeoTIFF image with
WCS. The image contains terrain type data like land/sea etc. The original size
of the image is just 939 KB but when I download this image from WCS it becomes
309 MB! How can a GeoTIFF file expands its size to 300+ times after downloaded
from WCS?
System info:
JRE 8
GeoServer 2.9.2
WCS 2.0.1
You can download and inspect the image with the following link:
Temp
|
|
|
|
|
|
|
|
Temp
Shared with Dropbox
|
|
|
Thanks.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
