You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the tile_post_process we can merge linestring or polygon. But there is nothing for points.
I see it like dropping points with same tags within a radius (rather than clustering.)
My current issue is with over numerous points generated from point_on_line geometry. I my use case I will even prefer point on merged line string, but looks very specific. (I build map with traffic sign/limitations for road sections.)
The text was updated successfully, but these errors were encountered:
In the Java API there is a "setPointLabelGrid(size, limit)" utility that lets you cut tiles into a grid and limit the number of points that can appear in each cell in that grid. Would exposing that to the YAML layer work for your use-case?
It's a pretty coarse tool but has worked for most use-cases like this so far. I think a density-based post-processing approach would be good to but wondering if the existing capability would work in your use-case.
In the
tile_post_process
we can merge linestring or polygon. But there is nothing for points.I see it like dropping points with same tags within a radius (rather than clustering.)
My current issue is with over numerous points generated from
point_on_line
geometry. I my use case I will even prefer point on merged line string, but looks very specific. (I build map with traffic sign/limitations for road sections.)The text was updated successfully, but these errors were encountered: