<div dir="ltr">Further testing shows that the artifact seems to show up at consistently at x=6000 and x=12000 columns.<br>--<br><br><br><br><div class="gmail_quote">On Mon, Sep 29, 2008 at 7:30 PM, Roger André <span dir="ltr"><<a href="mailto:randre@gmail.com">randre@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">Hi List,<br><br>I've hit the same problem twice now, and I'm pretty certain after Round 2 that I'm not introducing it. Basically, I'm using gdal_merge.py to mosaic a group of low-resolution, 32-bit floating point rasters together, then running "gdalwarp -ts xxx yyy -r cubicspline" on the mosaic to get a higher resolution image. I'm finding afterwards that there are linear artifacts in the mosaic which run vertically through the mosaic, which look like edge artifacts, but which are not located near the edge of either an original low-res tile, or the resulting high res one. I've tested the interpolation of a single low-res tile in the area where the artifact is present in the mosaic and I do not get the same results - the interpolated tile is clear of artifacts.<br>
<br>Is it possible that I'm hitting some sort of memory limit that is causing only a certain number of columns to be interpolated at one time, rather than the entire row?<br><br>Thanks in advance for any clues or advice you can give.<br>
<br>Roger<br>--<br></div>
</blockquote></div><br></div>