-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slimming down boundaries #1715
Comments
E.g: |
Back to locality names... Here's zoom 12, the point label is enough, along with boundary line (in tiles but not shown in Bubble Wrap). At zoom 13+ it's legit to show the locality names along the lines as long as they fit (drop locality kind before running fit dropping): In practice, most basemaps don't show boundary lines with labels until zoom 15+ (still not shown in Bubble Wrap, but suitable for some maps styles): |
PR #1725 looks good. I filed 2 followup issues:
|
Since tilezen/tilequeue#354 fixed a bug, we've been pulling in far more boundaries, median increase in layer size of 40%. Note that the boundaries layer is generally fairly small, and by stripping long names off (#1683) we've reduced layer size significantly at lower zooms. The increase mainly affects mid zooms 9-11, although also zoom 5 (nominal).
We annotate the boundaries with the left and right OSM IDs of the relations they delineate, but these are probably not used in styling. We could remove them to save a significant amount of space in tiles with a lot of boundaries. In addition, this would open up opportunities for merging which are not available at the moment as the left/right ID pair is nearly-unique.
As well, or instead, we could consider showing detail boundaries (
kind: locality
) at higher zooms (currently start at 10). The problem is that countries vary wildly in the density of their localities, so it's possible that a good value for themin_zoom
in one country wouldn't be appropriate for another. Annotating with the country code and clipping might be an option, although complex.The text was updated successfully, but these errors were encountered: