Thanks for the awesome work vadp! I'm almost there, but have an error on Win7 x64 using the following command:

bsb2gdal.py -d -c -tout 18448_1.KAP

DEBUG:root'', '')
DEBUG:root:gdalwarp -tps -dstalpha -wo INIT_DEST=NO_DATA -wo CUTLINE=POLYGON(())
-of VRT out\18446_1.aux_vrt out\18446_1.vrt
DEBUG:root'', 'ERROR 1: Failed to parse CUTLINE geometry wkt.\n')
Traceback (most recent call last):
File "bsb2gdal.py", line 286, in <module>
kap2vrt(f)
File "bsb2gdal.py", line 238, in kap2vrt
command(warp_cmd)
File "bsb2gdal.py", line 80, in command
raise Exception("*** External program failed: %s\n%s" % (' '.join(params),st
derr))
Exception: *** External program failed: gdalwarp -tps -dstalpha -wo INIT_DEST=NO
_DATA -wo CUTLINE=POLYGON(()) -of VRT out\18446_1.aux_vrt out\18446_1.vrt
ERROR 1: Failed to parse CUTLINE geometry wkt.

If I remove the "-c" then it works fine, but somehow the cutline is making it complain. Should the "POLYGON" field should have some real content? Also, I'm not quite certain which of the many versions of gdal2tiles.py which are floating around I should use. I'm currently using "$Id: gdal2tiles.py 18194 2009-12-06 20:07:45Z rouault $". All of the other tools I'm using are referenced on the Russian website mentioned on page 4 of this thread.

Here's a copy of the local variables just before the call to gdalwarp.

http://www.flickr.com/photos/41484197@N00/5180700599/

Note that "poly_tr" is also null.

My apologies for not getting very far with this, but this is my first day trying to debug python code.