Hi, I would expect an issue like that one if your footprints are vector, as the vectors cannot scale the same way as pixels (a pixel cannot be split in half, vector data scales linearly). If you're not already doing so, try to embed raster masks using gdal and enable raster footprints. If you're already doing so, try first the latest GeoServer version (2.15.x) and if the issue is still there, open a ticket with data, configuration, and a request to reproduce, at https://osgeo-org.atlassian.net/projects/GEOS/summary
Cheers Andrea On Mon, May 20, 2019 at 10:59 AM HSt <[email protected]> wrote: > Hello all, > > we are currently serving many tiff files (ca. 4000 per layer) as > ImageMosaic > via WMS and WMTS (scale-dependent). > These tiffs are heterogeneous (=true), i. e. mix of RGB and RGBI, various > resolutions. Therefore we use coverage view and we only display RGB > (channel > selection in .sld). > > One image can have two footprints (because the original image is composed > of > two different dates, when the photo was taken, each footprint represents > one > date, but referring to the same image). We've generated unique IDs in the > shapefile table, where the footprints.properties is pointing to > (footprint_filter = FID = granule.FID --> shapefile for ImageMosaic = > footprint_source). Footprint behavior is set to CUT. > > All in all this works perfectly, but along the footprint line within one > image (remember, exact same image is used twice in the ImageMosaic, each > time with a different footprint), white (nodata) pixels appear and only > occur if the footprint lies exactly in the pixel (divides pixels into 50-50 > pieces). > > <http://osgeo-org.1560.x6.nabble.com/file/t384935/FP01_1.png> > > <http://osgeo-org.1560.x6.nabble.com/file/t384935/Fp2.png> > > <http://osgeo-org.1560.x6.nabble.com/file/t384935/Fp3.png> > > > I don’t know if this is a bug. But is there a possibility to adjust the > tolerance of the footprint behavior or another way to avoid these pixels? > Wasn’t there an option that the footprints can cut through pixels instead > of > omitting/picking entire pixels? > Cutting the images beforehand or interpolation (bicubic) are not an option > because the original images should be untouched. > > Thanks, > HSt > > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html > > > _______________________________________________ > 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 > -- 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 ------------------------------------------------------- *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.*
_______________________________________________ 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
