Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

Ville Karppinen
Hi,

We use 16-bit geotiff images as data source for image mosaicking plugin.
When geotiffs are asked from geoserver by using &format=image/geotiff
parameter in URL and by using default raster style, geoserver gives
8-bit geotiffs. Is there any way to make sure that 16-bit geotiffs are
given from the geoserver?

Change to 8-bit seems to be case at least in geoserver version 2.5.1 and
2.5.2.

Best regards,

--
Ville Karppinen
[hidden email]
+358407509542


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

Simone Giannecchini
Ciao Ville,
I am assuming this is pure 16 bits data not data with a 16 bits palette.
If so then there is no (easy) way to get it out untouched from the
GeoServer WMS service since the renderer does work with 8 bits data
(up top 4 bands).
If you try to render a 16 bits dataset and don't specify a
rastersymbolizer it will nevertheless reduce to 8 bits during the
rendering.

It would be possible to retain the 16 bits in certain cases, and
generating a tiff is one of them, but this is not currenly supported
(which means a small code change might be needed).


Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272
mob:   +39  333 8128928

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 stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility  for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.


On Thu, Oct 2, 2014 at 3:48 PM, Ville Karppinen <[hidden email]> wrote:

> Hi,
>
> We use 16-bit geotiff images as data source for image mosaicking plugin.
> When geotiffs are asked from geoserver by using &format=image/geotiff
> parameter in URL and by using default raster style, geoserver gives
> 8-bit geotiffs. Is there any way to make sure that 16-bit geotiffs are
> given from the geoserver?
>
> Change to 8-bit seems to be case at least in geoserver version 2.5.1 and
> 2.5.2.
>
> Best regards,
>
> --
> Ville Karppinen
> [hidden email]
> +358407509542
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Geoserver-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

geowolf
In reply to this post by Ville Karppinen
On Thu, Oct 2, 2014 at 3:48 PM, Ville Karppinen <[hidden email]> wrote:
Hi,

We use 16-bit geotiff images as data source for image mosaicking plugin.
When geotiffs are asked from geoserver by using &format=image/geotiff
parameter in URL and by using default raster style, geoserver gives
8-bit geotiffs. Is there any way to make sure that 16-bit geotiffs are
given from the geoserver?

If you want 16 bits data, the protocol to use is WCS.
Or, we could see if it's possible to create a custom code path for 16 bits data
when the WMS request is pure raster, pure 16 bits... that's going to 
require some work though.

Generally speaking, a WMS need to serve data from any random combination
of vector and raster layers, in formats that normally support only up to 8 bits
(afaik we cannot even draw vectors on a 16 bit surface)
but it would be possible to build a special case for special situations, with
the right amount of resources/funding.

Cheers
Andrea

--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==

Ing. Andrea Aime 
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549


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 stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

 

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


-------------------------------------------------------

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

Ville Karppinen
Grazie mille Simone and Andrea for you answer.

I would still like to clarify a couple of things about 16-bit geotiffs.

We have observed that in a previous version of geoserver (2.3.4) 16-bit source geotiffs were provided as 16-bit from the geoserver. So, it seems that the functionality has changed somewhere before our current version of 2.5.2. We have probably just missed some release notes about this.

Our system is based on the assumption that style "raster" means the original data is served as unaltered. Is there any way to get 16-bit geotiffs (preferably without palette) by using WMS or is WCS the only way to go? For example, could we define a style (SLD) which would effectively force 16-bit geotiff output?

Best regards,
Ville Karppinen
[hidden email]
+358407509542
On 10/02/2014 06:44 PM, Andrea Aime wrote:
On Thu, Oct 2, 2014 at 3:48 PM, Ville Karppinen <[hidden email]> wrote:
Hi,

We use 16-bit geotiff images as data source for image mosaicking plugin.
When geotiffs are asked from geoserver by using &format=image/geotiff
parameter in URL and by using default raster style, geoserver gives
8-bit geotiffs. Is there any way to make sure that 16-bit geotiffs are
given from the geoserver?

If you want 16 bits data, the protocol to use is WCS.
Or, we could see if it's possible to create a custom code path for 16 bits data
when the WMS request is pure raster, pure 16 bits... that's going to 
require some work though.

Generally speaking, a WMS need to serve data from any random combination
of vector and raster layers, in formats that normally support only up to 8 bits
(afaik we cannot even draw vectors on a 16 bit surface)
but it would be possible to build a special case for special situations, with
the right amount of resources/funding.

Cheers
Andrea

On 10/02/2014 06:23 PM, Simone Giannecchini wrote:
Ciao Ville,
I am assuming this is pure 16 bits data not data with a 16 bits palette.
If so then there is no (easy) way to get it out untouched from the
GeoServer WMS service since the renderer does work with 8 bits data
(up top 4 bands).
If you try to render a 16 bits dataset and don't specify a
rastersymbolizer it will nevertheless reduce to 8 bits during the
rendering.

It would be possible to retain the 16 bits in certain cases, and
generating a tiff is one of them, but this is not currenly supported
(which means a small code change might be needed).


Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272
mob:   +39  333 8128928

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


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

geowolf
On Fri, Oct 3, 2014 at 9:12 AM, Ville Karppinen <[hidden email]> wrote:
Grazie mille Simone and Andrea for you answer.

I would still like to clarify a couple of things about 16-bit geotiffs.

We have observed that in a previous version of geoserver (2.3.4) 16-bit source geotiffs were provided as 16-bit from the geoserver. So, it seems that the functionality has changed somewhere before our current version of 2.5.2. We have probably just missed some release notes about this.

Hum.. no, as far as I know the original functionality you're referring to was there by accident, and I guess that also by accident it got removed.
However, this also means that it may be also easy to get it back, and this time cover it with some tests, so that it does not regress (turning it
from an accident to a feature).
 

Our system is based on the assumption that style "raster" means the original data is served as unaltered. Is there any way to get 16-bit geotiffs (preferably without palette) by using WMS or is WCS the only way to go? For example, could we define a style (SLD) which would effectively force 16-bit geotiff output?

The only supported way right now is WCS (to the extent of my knowledge)

Cheers
Andrea

--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==

Ing. Andrea Aime 
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549


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 stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

 

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


-------------------------------------------------------

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

eting123
Hi,
We are researching on whether Geoserver can serve 16-bit data, and I came
across this post.

Since it has been 3-4 years, just wondering if anything has changed? Do you
happen to have support for this now? Any other ways to support this that you
can think of?

Thank you very much in advance.

eting



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

------------------------------------------------------------------------------
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


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Why is 16-bit geotiff converted to 8-bit geotiff by geoserver?

geowolf
Hi,
the answer did not change, you can have 16 bits in input, but if you want them to be preserved in output,
you need to use WCS, not WMS.

In general getting 16 bit output would require specific conditions, like single raster layer request, the layer
is already 16 bit, the output format is also 16 bit capable (so GeoTiff, or Tiff), and some configuration or
request vendor option to activate that mode, as most clients would not be able to handle it anyways.

That said, under those specific conditions it's quite doable, one just need to put development resources behind it. See:

Cheers
Andrea


On Wed, Apr 25, 2018 at 10:49 PM, eting123 <[hidden email]> wrote:
Hi,
We are researching on whether Geoserver can serve 16-bit data, and I came
across this post.

Since it has been 3-4 years, just wondering if anything has changed? Do you
happen to have support for this now? Any other ways to support this that you
can think of?

Thank you very much in advance.

eting



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

------------------------------------------------------------------------------
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


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users



--

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

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

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 stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.



------------------------------------------------------------------------------
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


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users