Tilecover with the same min and max zoom creates unpredictable results

trying to cover the US with min_zoom:7, max_zoom: 7 - no coastal tiles, and lots of scattered random ones

if I generate tiles with min_zoom: 6, max_zoom: 7 then use tilebelt to get the child-tiles for z6 tiles, I get what I was expecting

Interestingly, both runs result in the same number of tiles, which suggests there’s just some data flow issue where the coastal tiles get their coordinates scrambled up

[mourner]

@bkowshik I think this can be an expected output — it may return adjacent tiles because the tile coordinate in mercator is unprojected to latitude/longitude bbox, which is subject to floating point precision errors, and then tiles that had a border exactly matching a tile side can start overlapping it slightly.

However, the cases in the first two comments look like serious bugs.

[mourner]

@tcql I have to close this as not reproducible on the tile-cover side. Please feel free to reopen after we have a reproducible test case.