Hi Daniele,
Thanks for getting back to me.
I've tried FootprintBehavior set to None, Transparent, and Cut with no
improvement. The footprint in this case is the extents shapefile
automatically generated by geoserver.
I could go the route of detailed footprint coverages but I don't want to as
there will shortly be hundreds of similar rasters in the mix. We just want
a consistent transparency behavior and are comfortable with the possibility
of pixels being stacked incorrectly (they probably won't be) without
preemptive steps such as merging all of the input rasters.
Can you or anyone think of another way to create the effect I'm looking
for? Is it possible the problem is specific to grayscale rasters, since
most of the imagemosaic configuration examples reference rgb rasters?
On Tue, Jul 17, 2018 at 4:01 AM Daniele Romagnoli <
daniele.romagn...@geo-solutions.it> wrote:
> Hi Michael,
> Are you applying some style to that image?
> Note that your image is 32 bit whilst rendered images are usually 8 bit so
> the default style applying some kind of automatic contrast stretch may be
> in place if you are not setting up anything.
>
> On Tue, Jul 17, 2018 at 8:49 AM, Adam Cecile <adam.cec...@hitec.lu> wrote:
>
>> Hello,
>>
>> Sadly I'm experiencing the same issue and nobody has a clue:
>> It seems GeoServer transparency is just not working.
>>
>>
>> https://www.mail-archive.com/geoserver-users@lists.sourceforge.net/msg30078.html
>>
>>
> As I have said to Adam on that thread, the FootprintBehavior is normally
> set to something when you have footprint information stored somewhere, as
> an instance:
>
> - sidecar shapefile containing masking geometries
> - internal bitmask on the raster containing 0/1 nodata/pixelValid info
> - sidecar WKTs/WKBs containing masking geometries
> - ....
>
> Please, let us know.
> Regards,
> Daniele
>
>
>
>> Regards, Adam.
>>
>>
>
>
>>
>> On 07/17/2018 02:08 AM, Michael J. Kitchin wrote:
>>
>> Hi Everyone,
>>
>> I have a number of grayscale rasters with overlapping extents. When
>> incorporated into an imagemosic source the extents of these rasters appear
>> to clip with an arbitrary z-ordering, obscuring whatever data happens to be
>> in lower-level rasters.
>>
>> In most/all of these cases the overlapping areas have data in one raster
>> and nodata in another so what I'd really like to see is either (a) only
>> data to be rendered (nodata to be transparent) or (b) data to be stacked,
>> since I'm confident merged results will generally dovetail.
>>
>> To make this happen I've tried most of the imagemosaic options, including:
>>
>> - BackgroundValues: Setting this to the nodata value (0) appears to
>> do nothing
>> - FootprintBehavior: Transparent causes render to fail
>> (java.lang.NullPointerException in BorderOpImage.copyRasterData)
>> - InputTransparentColor: Setting this to anything causes render to
>> fail (java.lang.IllegalStateException: Unsupported data type in
>> BaseSubmosaicProducer.collectGranules)
>> - MergeBehavior: Both FLAT and STACK appears to do the same thing
>>
>> ...without any luck. Styling the nodata value (0) to opacity 0 doesn't
>> help, either.
>>
>> What am I doing wrong?
>>
>> Here's gdalinfo from one of the rasters:
>>
>> Driver: GTiff/GeoTIFF
>> Files: xxxx_yyyy_zzzz.tif
>> Size is 2243, 2165
>> Coordinate System is:
>> GEOGCS["NAD83",
>> DATUM["North_American_Datum_1983",
>> SPHEROID["GRS 1980",6378137,298.2572221010002,
>> AUTHORITY["EPSG","7019"]],
>> TOWGS84[0,0,0,0,0,0,0],
>> AUTHORITY["EPSG","6269"]],
>> PRIMEM["Greenwich",0],
>> UNIT["degree",0.0174532925199433],
>> AUTHORITY["EPSG","4269"]]
>> Origin = (-109.885930978329270,39.430237563412469)
>> Pixel Size = (0.000925938113674,-0.000925913224073)
>> Metadata:
>> AREA_OR_POINT=Area
>> Image Structure Metadata:
>> INTERLEAVE=BAND
>> Corner Coordinates:
>> Upper Left (-109.8859310, 39.4302376) (109d53' 9.35"W, 39d25'48.86"N)
>> Lower Left (-109.8859310, 37.4256354) (109d53' 9.35"W, 37d25'32.29"N)
>> Upper Right (-107.8090518, 39.4302376) (107d48'32.59"W, 39d25'48.86"N)
>> Lower Right (-107.8090518, 37.4256354) (107d48'32.59"W, 37d25'32.29"N)
>> Center (-108.8474914, 38.4279365) (108d50'50.97"W, 38d25'40.57"N)
>> Band 1 Block=2243x1 Type=Int32, ColorInterp=Gray
>> NoData Value=0
>>
>> - Best wishes,
>> Michael J. Kitchin
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
