Since it as less than 4gb, if you have the image in different tiles just
merge them together. The image format should be tif.
1- Fisrt enable internal tiling with the command
gdal_translate -co "TILED=YES" original.tif tiled.tif
2-than add overviews
gdaladdo -r average 2 4 8 16 32 64 128
3-c
Hi folks
Thanks for all the suggestions about raster preparation - v.useful tips. I
had guessed tiffs were probably the format to go for, the dataset is
currently in an ESRI grid format after being recently exported from some
modelling results.
Many thanks
Chris
_
Jean, thats my problem too.
I haven't resolved it yet the perfect way, but i have created mosaics of the
data with lowered resolution, and a lower number of tiles . The number of
tiles that are requested to see the map increases when you zoom out, so it
needs to seek and read the tiles. Having th
Hello Jean,
You can use the gdal_retile.py script to generate the tiles and the zoom
levels, than use the minscale and maxscale for showing and hiding the
appropriate level. The raster data are not suggested to have them in a
database or in your case in postgis. If they are file system it is faste
If you are merging tiles together to create 1 large tif, why would you
need to create an index to it? I would think you would just directly
reference the tif.
so, rather than
TILEINDEX ../data/myindex
skip the index building steps
just
DATA ../data/big.tif
On Fri, Feb 25, 2011 at 9:08 AM, Ed
I would agree with Edi and recommend TIFF. It's easy to move around and
deal with, and is the fastest of the raster formats. (unless something
new has come up?)
I would also agree with Mark: a tileindex is for mosaicing many TIFFs,
and if your result is 1 single TIFF the tileindex is unnecessa
