View Single Post
Posts: 40 | Thanked: 18 times | Joined on May 2008
#51
Originally Posted by jaybonomad View Post
The file has 4 /PLY elements. Using your latest bsb2gdal.py does not change the core problem
Code:
DEBUG:root:('-123.183900 47.032780\n-123.183900 47.599720\n-122.168100 47.599720 \n-122.168100 47.032780\n',) 
DEBUG:root:gdaltransform -tps -i -t_srs +proj=longlat 18448_1.kap 
DEBUG:root:('', '')
Apparently, the script cannot catch gdaltransform output. It must be something like:
Code:
DEBUG:root:('-123.183900 47.032780\n-123.183900 47.599720\n-122.168100 47.599720\n-122.168100 47.032780\n',)
DEBUG:root:gdaltransform -tps -i -t_srs +proj=longlat 18448_1.KAP
DEBUG:root:('264.235828047997 8192.85411369754 0\n264.23553921845 313.584303449666 0\n9864.84455602684 313.584331807953 0\n9864.84455306079 8192.854118532 0\n', '')
Can you try to feed this
Code:
-123.183900 47.032780
-123.183900 47.599720
-122.168100 47.599720
-122.168100 47.032780
manually into
Code:
gdaltransform -tps -i -t_srs +proj=longlat 18448_1.KAP
I've came across such an effect some time ago at the Russian thread.
Do you use 32-bit python distribution? If so, perhaps it's worth trying 64-bit version.

Update: Just tried your chart on 32-bit XP -- no problem
BTW Found a little bug though, so here a yet another version
Attached Files
File Type: txt bsb2gdal.py.txt (13.3 KB, 157 views)

Last edited by vadp; 2010-11-16 at 14:16.