PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
when running superoverlay.py or testextractor.py I am getting the following error:
ERROR 1: TIFFOpen:/tmp/file.gtiff: No such file or directory Traceback (most recent call last): File "C:\regionator\tests\testextractor.py", line 36, in ? ex.Extract(0,0,256,256,'0') File "C:\regionator\kml\extractor.py", line 100, in Extract o_ds.WriteRaster(0,0,twid,tht,i_data) AttributeError: 'NoneType' object has no attribute 'WriteRaster'
can anyone help?
-------------------- -Pattt
http://adventuresforthecure.com
|
PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
oh nevermind. I simply had to create a C:\tmp directory on my system.
-------------------- -Pattt
http://adventuresforthecure.com
|
regionator
The Crusader
Reged: 01/24/06
Posts: 63
|
|
Tnx for reporting this.
I just updated the code to use a safer and platform independent temp file method.
happy regionating...
|
PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
Awesome! Thanks Regionator... I just checked out the new code and it works great.
I am new to python (started using it 2 days ago when I checked out regionator).
when running the regionator code I am getting the following errors:
version 81 original dimensions (880, 880) maxdepth 4 count 24 root region (28.828125, 28.125, -80.15625, -80.859375) llb-3\4.kml llb-3\5.kml llb-3\6.kml llb-3\7.kml llb-3\3.kml llb-3\9.kml llb-3\10.kml llb-3\11.kml llb-3\12.kml llb-3\8.kml llb-3\2.kml llb-3\15.kml llb-3\16.kml llb-3\14.kml llb-3\13.kml llb-3\18.kml llb-3\20.kml llb-3\21.kml llb-3\22.kml llb-3\23.kml llb-3\19.kml llb-3\17.kml llb-3\24.kml llb-3\1.kml Extractor NASA_KSC.jpg 3 bands 1/24 llb-3\1.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpx-lf88GTiff failed.
2/24 llb-3\2.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmp__uo3bGTiff failed.
3/24 llb-3\3.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpudegm5GTiff failed.
4/24 llb-3\4.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmp78vghwGTiff failed.
5/24 llb-3\5.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpctoubgGTiff failed.
6/24 llb-3\6.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpl8odn2GTiff failed.
7/24 llb-3\7.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpungpbyGTiff failed.
8/24 llb-3\8.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpzaxovtGTiff failed.
9/24 llb-3\9.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpisjsccGTiff failed.
10/24 llb-3\10.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpan4qtcGTiff failed.
11/24 llb-3\11.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmp4qcwkyGTiff failed.
12/24 llb-3\12.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpo-ppxvGTiff failed.
13/24 llb-3\13.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpef8lb1GTiff failed.
14/24 llb-3\14.JPEG 15/24 llb-3\15.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpp7swwtGTiff failed.
ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpcdunluGTiff failed.
16/24 llb-3\16.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpxvz7h5GTiff failed.
17/24 llb-3\17.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpsf4jhcGTiff failed.
18/24 llb-3\18.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpffdsakGTiff failed.
19/24 llb-3\19.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpq5c5s3GTiff failed.
20/24 llb-3\20.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpcchkdmGTiff failed.
21/24 llb-3\21.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmppeoxfeGTiff failed.
22/24 llb-3\22.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpf3wcv4GTiff failed.
23/24 llb-3\23.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmpiqfgotGTiff failed.
24/24 llb-3\24.JPEG ERROR 1: GTiff: Attempt to unlink c:\docume~1\admini~1\locals~1\temp\tmptfzq5sGTiff failed.
What does that mean and where is it comming from? The error message is not very descriptive.
Thanks!
-------------------- -Pattt
http://adventuresforthecure.com
|
PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
I had to do the same thing on my Windows system. Has anyone figured out a better way to do this?
-------------------- -Pattt
http://adventuresforthecure.com
|
PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
Here are the steps that I followed to get it working on my windows machine.
1. Go to Google Earth Regionator Project Home and checkout the latest version of the code using svn (I used TortuseSVN ) 2. Go to Python 2.4 and download Python 2.4 3. Go to UrbanSim's GDAL installation page and download/install GDAL (I followed the instructions for Quick Installation ) 4. Go to NumPy and download/install NumPy from it’s Sourceforge download site (you should download numpy-1.0.win32-py2.4.exe)
Put all those pieces together in the same order as above and everything should work great (on windows).
For fun I also downloaded PyDev which is a super awesome extension to Eclipse 3.2 for python development!!
-------------------- -Pattt
http://adventuresforthecure.com
|
PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
So, I have a ridiculously big jpg image ~ 20,000px x 20,000px. I tried running regionator on it and it quickly creates ~ 5,500.kml files. Then it starts making the .jpeg files. The first few take almos 1 minute each to create but it gets faster after that. I have not delved into the code yet and I am not saying that it runs too slow, but I am wondering if there is any easy way to make it faster? Or could someone at least point me in the right direction or have any ideas about this?
Thanks!
-------------------- -Pattt
http://adventuresforthecure.com
|
Forkboy2
Cartographer
Reged: 07/16/05
Posts: 445
|
|
I have a feeling you're going to start running into problems with a file that large even if you do get it to work. The more levels of nested KMLs you have, the more GE seems to choke trying to process all of them as you zoom in. Anything more than a 32x32 grid of tiles and things really start to slow down. At least that's been my experience. Might not be so bad if you're not planning on putting the files online.
Matt
|
regionator
The Crusader
Reged: 01/24/06
Posts: 63
|
|
20k x 20k is entirely reasonable (and pretty much the whole point :-) and we've done significantly larger with this exact software.
Extracting 5000+ tiles takes time indeed. Some will be faster than others as the code is extracting and resampling the original at each level of hierarchy. I would guess 10's of minutes, but it obviously depends on your hardware and likely very much on how much RAM you have.
We've created SuperOverlays upwards of 400,000 tiles and pretty deep hierarchies.
|
PatrickB
Tourist
Reged: 07/28/05
Posts: 17
|
|
Thats good news.
Say I am running on a multiprocessor system does anyone have any suggestions on how I could better thread the program to make it run faster? Would adding threading even make a difference?
Or is the only solution to this problem (kinda slow with huge files) to throw more hardware at it?
-------------------- -Pattt
http://adventuresforthecure.com
|