# Tile Map zoom in disabled on Kibana 5.4.0

**URL:** <https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095>\
**Category:** Kibana\
**Created:** [May 9, 2017, 1:06pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095 "2017-05-09T13:06:49Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![maenu](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@maenu](https://discuss.elastic.co/u/maenu)\
**Post date:** [May 9, 2017, 1:06pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/1 "2017-05-09T13:06:49Z")

</div>

Hi

I have exactly the same Tile Map visualization (Shaded Circle Markers), once on **Kibana 5.3.0** and once on **Kibana 5.4.0**.

 ![](https://us1.discourse-cdn.com/elastic/original/3X/4/5/4530fb05162eca1b32703a11be7c606732750053.png) ![](https://us1.discourse-cdn.com/elastic/original/3X/4/2/426d2016c05294fec24da335cf1697e98678a82a.png)

The Tile Maps use external WMS source.

In Kibana 5.4.0, the zoom is restricted to a certain level, after that no more zooming in is possible.

The same problem occurs with other WMS sources, with heat maps as well as with the standard OpenStreetMap source.

Do I have to set something like `tilemap.options.maxZoom: 18` in kibana.yml?

---

<div class="post-metadata">

**Author:** ![maenu](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@maenu](https://discuss.elastic.co/u/maenu)\
**Post date:** [May 9, 2017, 1:48pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/2 "2017-05-09T13:48:55Z")

</div>

tilemap.options.maxZoom: 18 in `kibana.yml` didn't solve the problem.

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [May 9, 2017, 6:52pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/3 "2017-05-09T18:52:59Z")

</div>

Hi @maenu,

we're looking into this but it might take a day. 😇

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [May 10, 2017, 3:49pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/4 "2017-05-10T15:49:03Z")

</div>

hi @maenu,

thanks for pointing this out.

this is a regression in 5.4. I created this issue: [https://github.com/elastic/kibana/issues/11697](https://github.com/elastic/kibana/issues/11697)

This will be fixed in a next patch. Apologies for the inconvenience, thx.

---

<div class="post-metadata">

**Author:** ![maenu](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@maenu](https://discuss.elastic.co/u/maenu)\
**Post date:** [May 11, 2017, 8:10am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/5 "2017-05-11T08:10:24Z")

</div>

@weltenwort @thomasneirynck

Thanks for your replies.

Would you recommend to wait for the patch or to downgrade to 5.3.0?

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [May 11, 2017, 12:33pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/6 "2017-05-11T12:33:01Z")

</div>

@maenu

If you can, I'd wait for a patch. You can also downgrade until the patch is released, which should be not too long from now. I'll ping on the github issue when the issue is resolved, thx.

---

<div class="post-metadata">

**Author:** ![M.S.S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.s.s/32/134307_2.png) [@M.S.S](https://discuss.elastic.co/u/M.S.S)\
**Post date:** [June 6, 2017, 10:49am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/7 "2017-06-06T10:49:35Z")

</div>

Hi,  
I'm using version 5.4.1 kibana. But after 10th level zoom in button is disabling.  
In kibana.yml file "tilemap.options.maxZoom: 18" defined but it is not working for me. For an instance running on cloud it seems, zoom is working more than level 10. But instance running on aws machine,kibana tile map not zooms more than 10.  
What can i do ?

I was watching for [11707](https://github.com/elastic/kibana/pull/11707). It is in 5.4.1 release notes. But still no luck.

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [June 6, 2017, 11:35am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/8 "2017-06-06T11:35:59Z")

</div>

Hi @M.S.S,

have you installed X-Pack in the Elasticsearch and Kibana instances on AWS? Starting even from the free X-Pack basic tier zoom levels are increased from 10 to 18. X-Pack is pre-installed on all Elasticsearch and Kibana instances running on Elastic Cloud.

---

<div class="post-metadata">

**Author:** ![M.S.S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.s.s/32/134307_2.png) [@M.S.S](https://discuss.elastic.co/u/M.S.S)\
**Post date:** [June 6, 2017, 12:31pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/9 "2017-06-06T12:31:20Z")

</div>

Do i need to install x-pack on both kibana and elasticsearch instances?

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [June 6, 2017, 2:12pm UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/10 "2017-06-06T14:12:07Z")

</div>

Yes, because Elasticsearch manages the license information.

---

<div class="post-metadata">

**Author:** ![M.S.S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.s.s/32/134307_2.png) [@M.S.S](https://discuss.elastic.co/u/M.S.S)\
**Post date:** [June 7, 2017, 6:15am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/11 "2017-06-07T06:15:17Z")

</div>

Thank you very much for your help. It is zooming more than 10th level now.  
But actually i couldn't understand the relation between x-pack and zoom level? Installation of x-pack effects visualisation's core properties?

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [June 7, 2017, 11:18am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/12 "2017-06-07T11:18:03Z")

</div>

It's less about the technical zoom level in Kibana but more about the level of detail provided in the geographic maps. The service that provides the tiles for the map visualization is hosted by Elastic itself. While the normal zoom levels are provided also for users without X-Pack installed, the high-resolution tiles are part of the commercial X-Pack offering.

---

<div class="post-metadata">

**Author:** ![M.S.S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.s.s/32/134307_2.png) [@M.S.S](https://discuss.elastic.co/u/M.S.S)\
**Post date:** [June 8, 2017, 6:12am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/13 "2017-06-08T06:12:12Z")

</div>

I see. Thanks again.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 6:12am UTC](https://discuss.elastic.co/t/tile-map-zoom-in-disabled-on-kibana-5-4-0/85095/14 "2017-07-06T06:12:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
