Further testing shows that the artifact seems to show up at consistently at x=6000 and x=12000 columns. --
On Mon, Sep 29, 2008 at 7:30 PM, Roger André <[EMAIL PROTECTED]> wrote: > Hi List, > > 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. > > 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? > > Thanks in advance for any clues or advice you can give. > > Roger > -- >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
