-
Notifications
You must be signed in to change notification settings - Fork 373
Open
Description
Hi guys,
I have an issue with an offset on a terrain generated with ctb-docker (https://github.com/tum-gis/cesium-terrain-builder-docker)
INPUTS
I tried with the 2 tifs in this Google Drive share: https://drive.google.com/drive/folders/1li8FEecFmMNwD85JcN_q5Ieu149bLtoZ?usp=drive_link
- NAMUR_ODWB_WGS84: a tif file I reprojected from EPSG:31370 (original file: https://carto.ville.namur.be/data/MNT_CLIP/Namur_MNT_1.tif) to WGS84 with FME
- NAMUR_OPENTOPO: a tif natively downloaded in WGS84 from https://portal.opentopography.org/raster?opentopoID=OTSDEM.032021.4326.3
Commands
docker run -it --name ctb_transform -v "$(pwd):/data" tumgis/ctb-quantized-mesh
ctb-tile -f Mesh -C -N -o output NAMUR_ODWB_WGS84_FME.tif
Cesium setup:
// Cesium terrain from ion.cesium
// scene.setTerrain(new Cesium.Terrain(Cesium.CesiumTerrainProvider.fromIonAssetId(1)));
// Built terrain from mago-3d-terrainer
scene.setTerrain(new Cesium.Terrain(Cesium.CesiumTerrainProvider.fromUrl('http://localhost:8099/OUTPUTS/TERRAIN_FME')));
// Cesium world building
scene.primitives.add(await Cesium.Cesium3DTileset.fromIonAssetId(96188));
I dont have any offset of course when I use CesiumWorldTerrain
Do you have any clue of what could cause this offset and how I could make it work ?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels