<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Courier New, Courier, monospace" size="-1">Thank </font><font
face="Courier New, Courier, monospace" size="-1">you Even for
this new feature.</font></p>
<p><font face="Courier New, Courier, monospace" size="-1">Hope it
will be handy to many more!</font></p>
<br>
<div class="moz-cite-prefix">On 08/08/2016 11:26 AM, Even Rouault
wrote:<br>
</div>
<blockquote cite="mid:201608081126.53076.even.rouault@spatialys.com"
type="cite">
<pre wrap="">Le lundi 08 août 2016 09:30:53, Daniele Romagnoli a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Hi Even,
my usual question would be: any plan to backport it? :-)
</pre>
</blockquote>
<pre wrap="">
Not really. I guess this is a new feature.
As currently, our policy is to be rather conservative for what goes in stable
branches, so people can upgrade from one micro version to another one
blindlessly.
Regarding that particular feature, it could potentially be backported, but
then where to draw the limit ? At some point, one such backport will undoubtly
cause a regression elsewhere, or will have bugs, causing more stabilization
work in stable branches.
Potential solutions:
- More frequent major.minor.0 releases that our ~ 1 year schedule
- Less conservative policy backport policy in regular stable branches that
would allow some new features to be added, but within the current limits of no
ABI change, no backward incompatibilities.
- An extra -backport branch that would have a less conservative policy. To be
defined what would be the limits: ABI changes allowed or not ?, backward
incompatibilities ? Would potentially only of interest for people who can
build from source as it would be unlikely to be widely packaged.
All would need extra staffing / funding.
Another option that already exists: live on the bleeding edge and build from
trunk ;-)
Even
</pre>
<blockquote type="cite">
<pre wrap="">
Cheers,
Daniele
On Sun, Aug 7, 2016 at 10:38 PM, Even Rouault <a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><even.rouault@spatialys.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Le dimanche 07 août 2016 19:20:05, Even Rouault a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Le samedi 06 août 2016 15:20:54, Fernando Ribeiro a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Dear list,
Currently we are working with 4 band tifs, first 3 bands as normal
RBG and the 4th as IR. On performing a warp operation from and to a
VRT, GDAL seems considering the 4th band as alpha, resulting in full
black pixels if 4th band value =0.
</pre>
</blockquote>
<pre wrap="">
gdalwarp will consider the 4th band as alpha... only if it is
effectively tagged as alpha in the source. You can check it with
gdalinfo
</pre>
<blockquote type="cite">
<pre wrap="">Some attempts were made to solve this issue, so far without success:
- Using the warp creation options PHOTOMETRIC=RGB and ALPHA=NO
</pre>
</blockquote>
<pre wrap="">
This will not influence the warping kernel.
</pre>
<blockquote type="cite">
<pre wrap="">- Manually editing the source VRT and replace Alpha color
</pre>
</blockquote>
</blockquote>
<pre wrap="">
interpretation
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">to Undefined
</pre>
</blockquote>
<pre wrap="">
This one should work. Strange that this doesn't work for you.
</pre>
<blockquote type="cite">
<pre wrap="">Does anyone have more suggestions?
</pre>
</blockquote>
</blockquote>
<pre wrap="">
I've just committed an improvement in trunk: "gdalwarp: add a -nosrcalpha
option to wrap the alpha band as a regular band and not as the alpha
band"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Thank you
</pre>
</blockquote>
</blockquote>
<pre wrap="">
--
Spatialys - Geospatial professional services
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
_______________________________________________
gdal-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/gdal-dev">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Fernando Ribeiro
==
GeoServer Professional Services from the experts!
Visit <a class="moz-txt-link-freetext" href="http://goo.gl/it488V">http://goo.gl/it488V</a> for more information.
==
Fernando Ribeiro
DevOps / Support Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
<a class="moz-txt-link-freetext" href="http://www.geo-solutions.it">http://www.geo-solutions.it</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/geosolutions_it">http://twitter.com/geosolutions_it</a>
-------------------------------------------------------
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.
</pre>
</body>
</html>