When applying a CesiumTerrainProvider, the map is only showing half

CesiumJS
1

Hello,

I have applied a CesiumTerrainProvider.fromUrl with my own URL. However, when I apply it, half of the map disappears. I tried to find similar cases before but couldn’t.

Has anyone else experienced a similar issue, or can anyone provide insight or a solution?

Here is my image and example code.

image
image1920×1032 91.7 KB

image
image1920×1032 99.2 KB

async function initViewer() {
  try {
    const terrainProvider = await Cesium.CesiumTerrainProvider.fromUrl(
      // This is my url
      "http://192.168.1.45:8081/"
    );
    const viewer = new Cesium.Viewer("cesiumContainer", {});

    viewer.scene.terrainProvider = terrainProvider;

  } catch (error) {
    console.error(error);
  }
}

initViewer();

This JSON file is in use on the terrain server.

{
  "tilejson": "2.1.0",
  "name": "koreaDem",
  "description": "",
  "version": "1.1.0",
  "format": "quantized-mesh-1.0",
  "attribution": "",
  "schema": "tms",
  "tiles": [ "{z}/{x}/{y}.terrain?v={version}" ],
  "projection": "EPSG:4326",
  "bounds": [ 0.00, -90.00, 180.00, 90.00 ],
  "available": [
    [ { "startX": 1, "startY": 0, "endX": 1, "endY": 0 } ]
   ,[ { "startX": 3, "startY": 1, "endX": 3, "endY": 1 } ]
   ,[ { "startX": 6, "startY": 2, "endX": 6, "endY": 2 } ]
   ,[ { "startX": 13, "startY": 5, "endX": 13, "endY": 5 } ]
   ,[ { "startX": 26, "startY": 10, "endX": 27, "endY": 11 } ]
   ,[ { "startX": 53, "startY": 21, "endX": 55, "endY": 23 } ]
   ,[ { "startX": 107, "startY": 43, "endX": 111, "endY": 47 } ]
   ,[ { "startX": 215, "startY": 87, "endX": 222, "endY": 94 } ]
   ,[ { "startX": 431, "startY": 174, "endX": 444, "endY": 189 } ]
   ,[ { "startX": 863, "startY": 349, "endX": 889, "endY": 378 } ]
   ,[ { "startX": 1727, "startY": 698, "endX": 1778, "endY": 757 } ]
   ,[ { "startX": 3455, "startY": 1397, "endX": 3556, "endY": 1515 } ]
   ,[ { "startX": 6911, "startY": 2795, "endX": 7113, "endY": 3030 } ]
  ]
}

Thank you!

2

The corresponding WGS84 boundaries for EPSG:4326 is [-180, -90, 180, 90], and your data is exactly half missing.

  "projection": "EPSG:4326",
  "bounds": [ 0.00, -90.00, 180.00, 90.00 ],
3

Thank you for replying!

I changed the bounds and tried it, but it still isn’t working.
Could this issue be related to the projection?

4

I’m not an expert on this, but my guess is that if a data set doesn’t have that much scope, and you force it to have more scope, then the areas that don’t have data will still have no data.

5

I had the same problem last month
My environment is based on the ball developed by my company, which is based on cesium.
The problem is our data. Because the parameters were not set correctly when slicing the terrain data, the slices only included the terrain data of the Eastern Hemisphere. I think you could check the requests made by the terrain tiles to see if the files corresponding to those data exist. You can also find another terrain file that is confirmed to have no problems for loading testing.