Tile images sometimes are corrupted

[VicXue]

I'm not sure what happened when I downloaded tile images. Some of the downloaded images are corrupted. I used this config.json setup:

{ "country": "new_zealand", "bounding_box": [175.1848,-37.8868,175.4386,-37.6892], "zoom": 17, "classes": [ {"name": "Populated Area", "filter": ["has", "building"] } ], "imagery": "http://a.tiles.mapbox.com/v4/mapbox.satellite/{z}/{x}/{y}.jpg?access_token=pk.eyJ1IjoidmljeHVlIiwiYSI6ImNqeHRxbTk2dzB4N2ozbW50NTB5MzU5bDUifQ.HElp34ctd7HUI9i2vBoLMw", "background_ratio": 1, "ml_type": "segmentation" }

In total, there are 1032 images downloaded and 345 of these images are corrupted. Two of the corrupted images can be visualized, as shown in below. The rest of the corrupted images cannot be opened.

It seems it does not matter what classes I'm trying to retrieve, the downloaded tile images always contain corrupted images in this area. I used to use a smaller bounding box and it worked fine. Can you please give it a try and tell me what your result is? I'm not sure if there is something wrong on my end.

Thank you.

[drewbo]

@VicXue in certain areas at higher resolution, the mapbox.satellite tileset doesn't have any data or returns lower quality imagery (black and white or lower resolution). We should definitely add better "handling" for this case but there isn't a way to prevent it outright (other than using another imagery endpoint)

[VicXue]

@drewbo Is there a way for users to choose their own imagery endpoint? Or will such functionality be in later releases?

[drewbo]

@VicXue yes, you can replace the imagery property in your config.json file with any valid XYZ tile endpoint or WMS endpoint (example for the latter shown here)

[VicXue]

@drewbo Great, thank you for your support.