-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why there is a sharp terrain scenery #33
Comments
@dg3feiko I have such problem when zero values in DEM were not equal to zero. |
Thanks for reply. yes, it is, especially at the eage of each raster. This could be fixed through raster calculator in ArcToolbox. |
@helmi03 could you share the details. It seems lots of guys suffers from this issue. |
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 |
Is there any smart way to process DEM with no-value and zero values (not setting no-value to zero)? |
I have a fix for this problem: |
Before my DEM.tif have @helmi03 @kazanture |
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. |
Hi. I have built CTB by Visual Studio 2015 with GDAL2.0.1, then use CTBtile to tile my DEM data with command -o XXX XXX.tif. The tool worked great while it appears a sharp scenery in CesiumJS which is not that much smooth with it in arcglobe, I am not talking about the sharp boundary but the area with some real data such as a hill will look like a pyramid. The original data is in WGS84 coordinate. I don't know if there are some restraints for input data such as supposed bits or there are something else I have left out?
The text was updated successfully, but these errors were encountered: