Aaron, This could be solved by using the nodata attribute. You can set the nodata value in the source in the vrt file[1]. The vrt driver will ignore the nodata areas. If you have problem with that, rerun the gdalwarp operation and make sure you get the nodata values. Use the -srcnodata and -dstnodata options in gdalwarp.
[1]: http://www.gdal.org/gdal_vrttut.html On Mon, Jul 9, 2012 at 7:49 AM, aphunter <a1hun...@ucsd.edu> wrote: > Hi Jean-Claude. Thanks for the idea. Unfortunately it made the split a > little > larger. Is it possible to make the borders transparent, or remove them so > the blending works properly as it does in gdal_merge.py? > > Thanks, > Aaron > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/gdal-merge-py-on-large-Tiff-s-gdalwarp-not-working-properly-tp4986729p4986806.html > Sent from the GDAL - Dev mailing list archive at Nabble.com. > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev > -- Best regards, Chaitanya kumar CH. +91-9494447584 17.2416N 80.1426E
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
