giohappy
commented
9 years ago Hi, If you have a patch to suggest for which and files glob pattern on Windows I will integrate it. I work on Linux...
The second issue was the same as #3 and it was fixed, and it's similar to your fix.
I'm not sure what's going wrong with the rest of your description. gdal2cesium builds tiles for the regions where there is at least one pixel from one of the origin rasters. The rest of tile will be processed as NODATA, so it should be set to 0, to make Cesium treat it as flat. Cesium also considers flat every region not covered by your tiles.
bbukovic
Hi,
I have observed two minor things:
This is simple to overcome, just list the filenames instead of using "*.tif", e.g.: gdal2cesium.py -o tiles file1.tif file2.tif file3.tif
And then I have two more issues:
Ok, I have not digged into the logic and I just added one more if clause to check whether script generates some output or not. Now this block of the code looks like this in my script: if res != tmp_res: if tz < self.tmaxz: if vrt_file is not None: self.vrts[vrt_file][1] = tz-1 tmp_res = res self.make_vrt(res,i) vrtfile = "cesium%s.vrt" % i self.vrts[vrt_file] = [tz,None] i += 1
After this change the script generated terrain tiles. Here comes the second issue that I do not know how to overcome and its source can be my source code change:
This is terrain loaded in cesium where the border between generated and not generated can be seen:
Regards