Tile Map dots too small when zoomed in

[LeeDr]

Kibana version: 4.1.11, 4.5.4, (any version supporting new Elastic Tile Service)

Elasticsearch version: 1.7.3 with Kibana 4.1.11

Server OS version: CentOS 7

Browser version: Firefox 45.2.0

Browser OS version: CentOS 7

Original install method (e.g. download page, yum, from source, etc.): un-tar

Description of the problem including expected versus actual behavior: We just added ability to zoom to level 10 in this release. But during testing, when zoomed all the way in, the dots seem too small. But maybe I just don't understand how the precision scales with the map levels.

Steps to reproduce:

1. I'll paste a screenshot from each zoom level
2. I'm not sure if the precision scales along with the zoom level of the maps, but it looks like the even numbered images below, especially 6, 8, and 10, have very small dots (higher precision) relative to the map than the odd images.

Image 1:

Image 2:

Image 3:

Image 4:

Image 5:

Image 6:

Image 7:

Image 8:

Image 9:

Image 10:

[LeeDr]

I confirmed that the Tile Map request "precision" only increases every other zoom level. So that explains why the dots appear larger and smaller every other zoom level.

[thomasneirynck]

Just to confirm, I can reproduce this on 5.0 as well.

[thomasneirynck]

The scaling of the circle radii is based on a lot magic numbers. Also the scaling logic itself, appears somewhat ad hoc and not well-founded (cf. pointToLayer: and _radiusScale in scaled_circles.js) .

The scaling should likely be simplified to the following:

• [a] the size of the circle cannot exceed that of the geohash-grid cell that the aggregation was computed for. The largest circle could expand to the full fize of the geohash grid cell.
• [b] the size of the circle should be proportional to the size of the aggregate value

Regarding [a], the size of the dots bounces all over, often much too small for the corresponding geohash-cell. This issue describes one visual artifact of this.

Regarding [b], the circle-radius is now proportional to the square root of the aggregate value (+ some other weighting). This seems somewhat arbitrary.

[thomasneirynck]

Another related issue is the ad-hoc way that Leaflet's zoom levels are mapped to a Geohash precision level. This mapping is now manually defined in agg_types/buckets/geo_hash.js.

These geohash-precision-levels seem to grow much too quickly as the map's zoom level increases. While geohash-precision levels do not map to Leaflet zoom-levels one-to-one (former subdivides with base 8, the latter with base 2), here too it may help to introduce some rigidity for a more predictable user experience. For example, a geohash-grid may not be smaller than some number of pixels.

[thomasneirynck]

see also this user's screenshots, who has a similar issue with his data (geohash too precise for zoom level).

https://discuss.elastic.co/t/how-can-i-zoom-on-city/57972

[thomasneirynck]

closed with #8000.