Fix accidental loss (at all zooms) of features with an explicit minzoom #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As reported in #219, versions of tippecanoe since 2.43.0 have accidentally dropped all features that specified an explicit minzoom with
"tippecanoe":{"minzoom":nnn}
. This PR adds anelse
clause to retain these features in the specified zoom range.The test file is the Natural Earth 110m populated places, with the scalerank used as the minzoom. Each feature contains an object like this to specify its minzoom:
The unrelated change to
mbtiles.cpp
andjoined_reordered.json
is to round the tileset bounding boxes and centers to six digits to avoid test failures on some platforms from slightly different floating point behavior.