[postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz.Loskot at cadcorp.com
Fri Mar 27 08:35:57 PDT 2009
Mateusz Loskot wrote:
> Pierre Racine wrote:
> > >> This is why regular blocking is not as important for me as tiling.
> > >> WKT Raster does not care if tiles are not all the same size.
> > >
> > >One correction, WKT Raster can work in two modes:
> > >1. By default, it does not care if tiles are of the same
> > > size or not.
> > >2. If regular blocking enabled, WKT Raster does care.
> > >
> > >Agreed?
> > How does it care?
> > Otherwise than setting regular_blocking to true?
> Through constraints set by AddRasterBlocking.
Grr, I meant AddRasterColumn
> > You could have used gdal_retile.py to create a bunch of filesystem
> > tiles and import them with the wilcard. This is what I did when I
> > first imported my 3600 100x100 tiles three weeks ago.
> Note, that -k uses size of "natural" block which is provided by GDAL.
> > I was almost happy with
> > this solution until you added -k. Then I also wanted it to work on
> > multiple files.
> Yes, I understand.
> > To simplify everything we could also remove the -k option and tell
> > our
> > users "if you want this tile structure when importing your raster(s),
> > use gdal_retile.py"... Is it really "simplifying" if we tell people
> > to use an other tool?
> Not exactly. My understanding is that regular blocking is based on size
> of "natural" block:
Pierre, we have re-discussed things with Martin and we've
decided to implement -k with tile size specification:
gdal2wktraster -k 256 256
So, I'm working on that :-)
Senior Programmer, Cadcorp
More information about the postgis-devel