why there is a sharp terrain scenery about cesium-terrain-builder HOT 11 OPEN

My case is like this, the edges are spikes

from cesium-terrain-builder.

@dg3feiko I have such problem when zero values in DEM were not equal to zero.

from cesium-terrain-builder.

Thanks for reply. yes, it is, especially at the eage of each raster. This could be fixed through raster calculator in ArcToolbox.

from cesium-terrain-builder.

I use http://www.gdal.org/gdal_fillnodata.html

from cesium-terrain-builder.

@helmi03 could you share the details. It seems lots of guys suffers from this issue.

from cesium-terrain-builder.

For my use case, I only interested with data above sea level. I have same 'spike' issue as @dg3feiko , and found out error caused by DEM value < 0, same as mentioned by @mrgloom.

My first try, reprocess the geotiff with http://www.gdal.org/gdal_fillnodata.html. But have issue with nodata on sea surface.

Since I don't care below sea level, reprocessed the geotiff using "set values of zero and below to null" as http://www.gdal.org/gdal_calc.html

from cesium-terrain-builder.

Is there any smart way to process DEM with no-value and zero values (not setting no-value to zero)?

from cesium-terrain-builder.

I have a fix for this problem:
#49

from cesium-terrain-builder.

Before my DEM.tif have NoData Value=0 and now NoData Value=-100 and it doesn't work.

@helmi03
gdal_fillnodata.py DEM.tif DEM_2.tif not hepled, can you specify full example? Also maybe with gdalinfo before and after applying gdal_fillnodata.py?

@kazanture
How to apply this fix? Just git clone https://github.com/kazanture/cesium-terrain-builder ?

from cesium-terrain-builder.

The best way is the repo owner to accept my pull request. Until that time you can either clone my fork or apply my small fix manually.

from cesium-terrain-builder.

My case is like this, the edges are spikes

iam having this same issue, did you find any fix?

from cesium-terrain-builder.