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
[email protected]
+358407509542
On 10/02/2014 06:44 PM, Andrea Aime wrote:
On Thu, Oct 2, 2014 at 3:48 PM, Ville Karppinen
<[email protected] <mailto:[email protected]>> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
