*facepalm*
Happy Monday, everyone.
Jake
>>> Even Rouault 12/18/2017 11:04 AM >>>
Jake,
>
> mem_s_fh = gdal.GetDriverByName("MEM").Create('', temp_cols, temp_rows,
> 1, gdal.GDT_Float32) mem_s_fh.SetGeoTransform([0, cell_size, 0, 0, 0,
> cell_size])
> mem_s_fh.SetNoDataValue(s_nodata)
SetNo
I think I've found a bug in the python bindings, but I want to run it by the
list before I open a ticket to make sure I'm not missing anything (I'm assuming
you'd rather I check it out on the list first rather than cluttering the ticket
system with bugs that aren't actually bugs).
Environment:
> I wouldn't expect that effect to be as strong as you observed, but indeed
> there are technical
> grounds for your findings. When a tile is partial, ie for the right most or
> bottom most tiles
> when tile size is not a multiple of the tile dimension, the TIFF format still
> impose that the
I'd like to check my understanding of the impact of the tile size on
JPEG-compressed geotiffs.
I've been getting dark bands 4 or 5 pixels wide on the bottom and right edges
of the image when manually creating large image tiles from a collection of
smaller tiles. I'm using the common aggressive
s so that someone else doesn't make the
same beginner's mistake I did of trying to specify creation options on
an existing dataset ;) Is this something I open a ticket for, or is
there a more direct way?
Thanks,
Jacob Adams
GIS Specialist, Cache County
>>> Even Rouault 9/2
ut.
Is there a way to remove these artifacts in a format amenable to Geoserver
while preserving the compression levels achievable with ycbcr-based jpeg
compression?
Thanks,
Jacob Adams
GIS Specialist, Cache County
___
gdal-dev mailing list
gdal-d
