Don't use length filters in waterway.sql about openmaptiles HOT 4 CLOSED

It is true that this breaks some waterways. But I would argue it is even more important to have a way to drop less important waterways on low zoom aggressively - since there really should be less waterway data than roads.

What I do now in b77cc7a is joining the linestrings by name. I assume that only waterways with a name are actually important for low zoom levels and then filter by linestring.

Do you have other ideas to find out the importance of a waterway apart from the length?

from openmaptiles.

I haven't stood up an mbtiles yet, but how busy is it if instead of length, there is the possibility of sorting of based on class alone? It is recognized that river>stream>ditch

from openmaptiles.

I haven't stood up an mbtiles yet, but how busy is it if instead of length, there is the possibility of sorting of based on class alone? It is recognized that river>stream>ditch

Too many waterway=river at z8-z11 which is already the most important waterway tag.

from openmaptiles.

From what I can see this is resolved?

from openmaptiles.