the script link is unavailable now. Could you send me(pim.researcher#gmail.com) the script or post it online.
Thanks a lot
Shawn
Could you provide an example of the command line?
Thanks,
Shawn
I'm just looking at getting this script up and running, and am getting some filename issues.
Looking at the code it seems we are creating a .terrain file, then creating .terrain.new file, (which we do stuff with), and then finally we try and rename the .terrain.new file back to the .terrain file, which, not surprisingly, fails for us ('Cannot create a file when that file already exists').
Any ideas? We're looking at the area between 1355 and 1385 (line numbers) in the code from the above script.
Also, there was mention of a new script, do you happen to have this?
Thanks
Deirdre.
--
You received this message because you are subscribed to the Google Groups "cesium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cesium-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi,Agree with Arne. The Script will work if you change line 1552 similar to "os.rename(tilefilename + '.new', tilefilename+'1')". From the screenshot I found the author use Mac, not Windows. Probably that's the reason of a Windows error ('Cannot create a file when that file already exists'). I am new to Cesium. My question is how to be used by Cesium after generated the tiles? Kevin, could you give me some instruction? Thanks.
--
Here is a brain dump in case someone wants to run with this. I haven't touched it in months.
I will post what I did to get it to run in Windows and attach Serge's script which I modified to run in Windows. It will at least give you some usable output. It's been a while since I ran this so I don't know if the overview tiles below the highest level are generated to be blank or not. If they're not blank, you will just get big spikes in terrain which I have not figured out yet. If anyone can fix this it would be greatly appreciated. Our current use is just to write level 8 for the world for example (which works) then we have custom javascript code to ignore all terrain levels lower than that (to avoid problems, blackness, etc).
To run the script:
gdal2srtmtiles.py --cesium -z 0-8 -p geodetic SRTM_NE_250m.tif terrain
note1: this command needs to be run from the GDAL110 (MSVC 2010) command prompt
note2: some sample SRTM data is available here (http://srtm.csi.cgiar.org/). Use the hc.box.net link.
note3: The gdal2srtmtiles script will generate real
terrain files for the highest level of terrain(ex: 8) then try to calculate
the terrain tiles for all lower levels as "overviews". This
generate_overview_tiles part does not work properly (gives big spikes in
terrain in certain areas) so currently I write all lower levels (0-7)
to have zero elevation. This needs to be fixed at some point. A Windows
Python debugger is available here (https://code.google.com/p/winpdb/wiki/DebuggingTutorial).
I can't see any information about this in documentation.