Adaptively determine grid size about node-mapnik HOT 2 CLOSED

absolutely. just likely a question of the heuristic and how fast we can make it. Before full encoding to utf8 we can easily offer access to the # of features burned into the grid at full res, and how many will be retained at lower res (we could optimize quick access to these without a full grid.encode() call). But we can certainly think about more sophisticated algorithms to analyze the raw pixel grid that could estimate adjacency of features (lack of blank space) or something.

Is this idea coming from your osm style work? maybe where many small building footprints at adjacent to each other and some are not (easily) clickable?

from node-mapnik.

closing this never rose to importance (and this ticket predated the spec now over at https://github.com/mapbox/utfgrid-spec).

from node-mapnik.