subject:"Re\: \[Geoserver\-users\] GeoServer Web Coverage Service Issue"

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

2018-04-06 Thread Daniele Romagnoli

Hi Mustafa

On Fri, Apr 6, 2018 at 9:43 AM, Mustafa ÖZÇETiN 
wrote:

> Hi Daniele,
>
> Using the all-upper case DEFLATE value worked as you specify. Thanks a lot.
>
Good. thanks for having reported that.
I have also opened a ticket for that (
https://osgeo-org.atlassian.net/browse/GEOS-8674) and prepared fixes for GS
2.14.x and 2.13.x so latest releases will also support Deflate as per
specification.

Cheers,
Daniele


> On Thursday, April 5, 2018, 10:52:48 AM GMT+3, Daniele Romagnoli <
> daniele.romagn...@geo-solutions.it> wrote:
>
>
> Hi Mustafa,
>
> On Wed, Apr 4, 2018 at 5:48 PM, Mustafa ÖZÇETiN via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
> Hi Jukka,
>
> Thanks for the response. Adding the "=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".
>
>
> Looking from the code, you may want to try with "DEFLATE", all upper-case.
> I will open a JIRA to make sure the value defined in the specification [1]
> is supported too.
>
>
>
> 2) When I try the ":compression=LZW" parameter, GeoServer does not
> return any exceptions but sends an uncompressed GeoTIFF (with GeoServer
> 2.9.2).
>
>
> I think that the "geotiff:" prefixes have been added from 2.11 as part of
> this JIRA, so 2.9.2 is not supporting them yet:
> https://osgeo-org.atlassian.net/browse/GEOS-8555
>
>
> [1]: https://portal.opengeospatial.org/files/?artifact_id=54813 [Page 16,
> Table 2]
>
> Hope this helps.
> Regards,
> Daniele
>
>
>
> On Wednesday, April 4, 2018, 5:10:03 PM GMT+3, Rahkonen Jukka (MML) 
>  maanmittauslaitos.fi > wrote:
>
>
> 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 extension https://portal.opengeospatial.
> org/files/?artifact_id=54813
>  and ask
> Geoserver to send you a compressed image by adding the required parameter
> =Deflate.  Using also =Horizontal probably yields
> even smaller output.
>
>
>
> BTW. according to the standard the parameters should be
> :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:geoserver-users@lists.
> sourceforge.net ]
> *Lähetetty:* 4. huhtikuuta 2018 11:12
> *Vastaanottaja:* geoserver-users@lists. sourceforge.net
> 
> *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
> 
>
>
>
>
>
> [image: Tekstiruutu:]
>
> [image: Lähettäjä poisti kuvan.]
> 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
>

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

2018-04-06 Thread Mustafa ÖZÇETiN via Geoserver-users

Hi Daniele,
Using the all-upper case DEFLATE value worked as you specify. Thanks a lot.
On Thursday, April 5, 2018, 10:52:48 AM GMT+3, Daniele Romagnoli 
 wrote:  
 
 Hi Mustafa,
On Wed, Apr 4, 2018 at 5:48 PM, Mustafa ÖZÇETiN via Geoserver-users 
 wrote:

Hi Jukka,

Thanks for the response. Adding the "=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".


Looking from the code, you may want to try with "DEFLATE", all upper-case.I 
will open a JIRA to make sure the value defined in the specification [1] is 
supported too. 

2) When I try the ":compression=LZW" parameter, GeoServer does not 
return any exceptions but sends an uncompressed GeoTIFF (with GeoServer 2.9.2).


I think that the "geotiff:" prefixes have been added from 2.11 as part of this 
JIRA, so 2.9.2 is not supporting them yet:
https://osgeo-org.atlassian.net/browse/GEOS-8555


[1]: https://portal.opengeospatial.org/files/?artifact_id=54813 [Page 16, Table 
2]
Hope this helps.Regards,Daniele 

On Wednesday, April 4, 2018, 5:10:03 PM GMT+3, Rahkonen Jukka (MML) 
 wrote:  
 
  
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 =Deflate.  Using also 
=Horizontal probably yields even smaller output.
 
  
 
BTW. according to the standard the parameters should be 
: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:geoserver-users@lists. 
sourceforge.net]
Lähetetty: 4. huhtikuuta 2018 11:12
Vastaanottaja: geoserver-users@lists. sourceforge.net
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


Geoserver-users@lists. sourceforge.net
https://lists.sourceforge.net/ lists/listinfo/geoserver-users





-- 
Regards,Daniele Romagnoli==GeoServer Professional Services from the experts! 
Visit http://goo.gl/it488V for more information.==
Ing. Daniele RomagnoliSenior Software Engineer
GeoSolutions S.A.S.Via di Montramito 3/A55054  Massarosa (LU)Italyphone: +39 
0584 962313fax:      +39 0584 1660272
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
---AVVERTENZE AI SENSI DEL 
D.Lgs. 196/2003Le informazioni contenute in questo messaggio di posta 
elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente 
riservate. Il loro utilizzo è consentito esclusivamente al destinatario del 
messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate 
questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di 
darcene notizia via e-mail e di procedere alla distruzione del

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

2018-04-05 Thread Daniele Romagnoli

Hi Mustafa,

On Wed, Apr 4, 2018 at 5:48 PM, Mustafa ÖZÇETiN via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi Jukka,
>
> Thanks for the response. Adding the "=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".
>

Looking from the code, you may want to try with "DEFLATE", all upper-case.
I will open a JIRA to make sure the value defined in the specification [1]
is supported too.


>
> 2) When I try the ":compression=LZW" parameter, GeoServer does not
> return any exceptions but sends an uncompressed GeoTIFF (with GeoServer
> 2.9.2).
>

I think that the "geotiff:" prefixes have been added from 2.11 as part of
this JIRA, so 2.9.2 is not supporting them yet:
https://osgeo-org.atlassian.net/browse/GEOS-8555


[1]: https://portal.opengeospatial.org/files/?artifact_id=54813 [Page 16,
Table 2]

Hope this helps.
Regards,
Daniele


>
> On Wednesday, April 4, 2018, 5:10:03 PM GMT+3, Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
>
> 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 extension https://portal.opengeospatial.
> org/files/?artifact_id=54813 and ask Geoserver to send you a compressed
> image by adding the required parameter =Deflate.  Using also
> =Horizontal probably yields even smaller output.
>
>
>
> BTW. according to the standard the parameters should be
> :compression=Deflate: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:
> geoserver-users@lists.sourceforge.net]
> *Lähetetty:* 4. huhtikuuta 2018 11:12
> *Vastaanottaja:* geoserver-users@lists.sourceforge.net
> *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
> 
>
>
>
>
>
> [image: Tekstiruutu:]
>
> [image: Lähettäjä poisti kuvan.]
> 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
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>


-- 
Regards,
Daniele Romagnoli
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:  +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

2018-04-04 Thread Mustafa ÖZÇETiN via Geoserver-users

Hi Jukka,

Thanks for the response. Adding the "=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 ":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)
wrote:

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
=Deflate. Using also =Horizontal probably yields even
smaller output.

BTW. according to the standard the parameters should be
:compression=Deflate: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:geoserver-users@lists.sourceforge.net]
Lähetetty: 4. huhtikuuta 2018 11:12
Vastaanottaja: geoserver-users@lists.sourceforge.net
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

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

2018-04-04 Thread Rahkonen Jukka (MML)

Hi,

Read about WCS 2.0 GeoTIFF extension
https://portal.opengeospatial.org/files/?artifact_id=54813 and ask Geoserver to
send you a compressed image by adding the required parameter
=Deflate. Using also =Horizontal probably yields even
smaller output.

-Jukka Rahkonen-

Hi,

System info:

JRE 8
GeoServer 2.9.2
WCS 2.0.1

You can download and inspect the image with the following link:

Temp

[cid:image001.png@01D3CC36.3DF82810]

[Tekstiruutu:]

[Lähettäjä poisti kuvan.]

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

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

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

Re: [Geoserver-users] GeoServer Web Coverage Service Issue

5 matches

Site Navigation

Mail list logo

Footer information