Missing some terrain tiles

[Jule-]

Following #6 and #9 issues, I am trying to generate and use terrain in Cesium.

When I try to generate terrain for N24E032.hgt SRTM 3 file:

ctb-tile --output-dir test N24E032.hgt
0...10...20...30...40...50...60...70...80...90...100 - done.

And then load the TMS layer in Cesium, I have error 404 loading issues:

GET http://localhost/test/2/4/3.terrain 404 (Not Found) Cesium.js:18650
An error occurred in "CesiumTerrainProvider": Failed to obtain terrain tile X: 4 Y: 0 Level: 2. Cesium.js:19770

GET http://localhost/test/4/18/11.terrain 404 (Not Found) Cesium.js:18650
An error occurred in "CesiumTerrainProvider": Failed to obtain terrain tile X: 18 Y: 4 Level: 4. 

As you can notice, Cesium cannot find 2/4/3.terrain file but error report that it failed to obtain terrain tile X: 4 Y: 0 Level: 2... Hum?!

Other upper tiles seems to load flawlessly, but Cesium behavior prevent child tile loading from these two tiles.

Here is the layer.json file I use for Cesium terrain loading:

{
  "tilejson": "2.1.0",
  "format": "heightmap-1.0",
  "version": "1.0.0",
  "scheme": "tms",
  "tiles": ["{z}/{x}/{y}.terrain"]
}

Indeed, 2/4/3.terrain and 4/18/11.terrain were not generated. If this is the expected behavior, parent tiles must have wrong child tags, if not there is some issue in the generation process.

Other possibility, I use wrong command line for my terrain generation, maybe I missed some default parameter...

[homme]

@Jule- Can you test this against the latest commit (ba59bba)? This now works for me without issue producing the following output (ignoring the artefacts produced by the NODATA values in the source dataset!):

I can replicate your output using an earlier commit (cebf0b9) so it looks like pull request #8 solved this problem.

[Jule-]

Ok you're right, taking head I have no more issue. Problem solved thank you!