Hello! We've noticed our geo pushpin charts have a more restricted max zoom level since the new MapLibre-based geo charts were released. Users can no longer zoom in as closely as they could with the old Mapbox engine. Our pushpin insights don't have an explicit

maxZoom

set, they just use

viewport: { area: "auto" }

or

continent_na

. The issue is especially noticeable when the map is inside a dashboard switcher (smaller container). We see the SDK changelog mentions: "Respect null value in max zoom level for geo charts, null means unrestricted zoom level" which implies

maxZoom: null

would fix it. But we're not sure: 1. What is the default`maxZoom`in the new MapLibre engine when not explicitly set? 2. Can we set`maxZoom`from the Analytical Designer UI, or only via SDK/YAML? 3. Is there a known behavior change with zoom limits when pushpin charts are embedded inside switchers?

Good questions! Here's what the knowledge sources can tell you, along with some honest gaps: 1. Default maxZoomLevel in the new MapLibre engine The knowledge sources do not explicitly state what the default numeric value of

maxZoomLevel

is in the MapLibre-based engine when the property is left

undefined

. What they do clarify is the semantics: •

undefined

(i.e., not set) → keeps the default max zoom level (whatever MapLibre applies internally) •

null

→ removes the limit entirely (unrestricted zoom) • A specific

number

→ caps zoom at that value [Geo Pushpin Chart config] [API docs] So if your charts previously had unrestricted zoom and now feel more restricted, setting

maxZoomLevel: null

explicitly is the correct fix based on the changelog behavior you referenced. For GoodData.CN (self-hosted), there is also a platform-level setting that defaults to unlimited but can be capped:

platform_limits:
  max_zoom_level: 12

[Geo Chart Configuration] 2. Setting maxZoomLevel via Analytical Designer UI vs. SDK/YAML The knowledge sources do not mention any Analytical Designer UI option for configuring

maxZoomLevel

. Based on the available documentation, this property is only configurable via: • The SDK

config

prop (

IGeoChartConfig

/

IGeoPushpinChartConfig

) [API docs] • The platform-level YAML setting (GoodData.CN only) [Geo Chart Configuration] I'm sorry, but there's no information in the knowledge sources confirming that

maxZoomLevel

can be set from the Analytical Designer UI. 3. Zoom behavior inside dashboard switchers (smaller containers) The knowledge sources do not contain specific information about zoom limit behavior changes when pushpin charts are embedded inside switchers or smaller containers. However, there is a related option that may help in constrained containers: •

cooperativeGestures: true

— requires Ctrl/Cmd + scroll to zoom, which is useful inside scroll containers and prevents accidental zoom interference [Geo Pushpin Chart config] •

viewport.frozen: true

— locks pan and zoom entirely if needed [Geo Pushpin Chart config] Recommended Fix To restore unrestricted zoom on your pushpin charts, explicitly set

maxZoomLevel: null

in your chart config:

config={{
  maxZoomLevel: null,
  viewport: { area: "continent_na" },
}}

This should override whatever default the MapLibre engine applies and restore unrestricted zoom behavior. [API docs] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

@kapa.ai We applied

maxZoomLevel: null

to our pushpin insights and confirmed via API that the value is stored correctly. However, zoom is still capped at what appears to be level ~14 (metro area level — can see individual cities but not street-level). A few questions: 1. Is there a

platform_limits.max_zoom_level

set on our Cloud instance (golmn / analytics.golmn.com) that would override the per-insight

maxZoomLevel: null

setting? The GoodData.CN docs reference this server-side cap. 2. Does the zoom behavior differ when an insight is embedded in a dashboard (or inside a dashboard switcher/tab) versus viewed standalone? Our maps are inside insight switchers on dashboards. 3. Did the default platform zoom limit change as part of the Mapbox → MapLibre migration? Previously our users could zoom to street level.

These are very specific operational questions. Let me be upfront about what the knowledge sources can and cannot answer. 1. Platform-level max_zoom_level on your Cloud instance The

platform_limits.max_zoom_level

YAML setting is documented only for GoodData.CN (self-hosted deployments). [Geo Chart Configuration] The knowledge sources contain no information about whether this platform-level cap exists or is configurable on GoodData Cloud (SaaS) instances like

analytics.golmn.com

, nor whether a server-side limit would take precedence over a per-insight

maxZoomLevel: null

. I cannot confirm or deny that a platform cap is overriding your setting — you would need to contact GoodData Support directly to check the platform configuration for your organization. 2. Zoom behavior: dashboard/switcher vs. standalone The knowledge sources do not document any difference in zoom behavior between an insight viewed standalone versus embedded in a dashboard or inside a switcher/tab. There is no information confirming that the dashboard container context affects the effective

maxZoomLevel

. 3. Default zoom limit change with Mapbox → MapLibre migration The knowledge sources do not document any specific change to the default platform zoom limit as part of the Mapbox → MapLibre migration, nor do they confirm that the default cap changed between engines. What the knowledge sources do confirm [Geo Pushpin Chart config] [Geo Chart Configuration] Recommendation Given that

maxZoomLevel: null

is confirmed stored correctly but zoom is still capped, and given the questions involve your specific Cloud instance configuration, I'd strongly recommend: 1. Opening a support ticket with GoodData to check if an organization-level zoom cap is set on your instance. 2. Asking specifically whether the Mapbox → MapLibre migration introduced a new default zoom ceiling on Cloud-hosted instances. The knowledge sources available to me don't contain enough detail to diagnose this further. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed., with interactive elements

Could I get some feedback/confirmation on this? After the Mapbox → MapLibre migration, pushpin map zoom is capped at approximately level 14 on our Cloud instance. We set

maxZoomLevel: null

per-insight and confirmed via API it's stored correctly but zoom is still restricted. Previously users could zoom in further than they can now. Is this caused by: (a) a platform-level zoom cap on our org, or (b) a tile provider limitation after switching from Mapbox? Either way, what's needed to restore the previous zoom depth?

Hi Nick, Thanks for the detailed context, this is really helpful. We're checking internally with our engineering team. One question in the meantime: before the Mapbox → MapLibre migration, were your users able to zoom to street level on this same Cloud instance, or is this the first time you've tested deep zoom on GD Cloud? This will help us confirm whether this is a regression or a pre-existing platform limit you hadn't hit before.

Hi Mauricio, they didn't confirm if they were able to zoom to street level in the past but they said they used to zoom in closer to see individual customers. I can see if I can get a better response as to how far they used to be able to zoom.

Hi Nick, thanks for the additional context. We're still checking internally and will get back to you with a proper update.

Hi @Mauricio Cabezas, we checked with our client and they stated:

We were able to zoom down to the Street Level overhead. We used to be able to see all the individual houses on the block.

Hi Nick, our apologies for the delay in getting back to you here - But we are still waiting feedback from our Engineering team. Once we have more details, we will let you now right away. Thanks for bearing with us in the meantime.

Hi Michael, thank you for the update.

Hi Nick, Thank you for your patience. After discussing with our engineering and product teams, we can confirm the following: The zoom restriction you are experiencing is an intentional platform-level limit on GoodData Cloud, set independently of the map engine. Currently, the default cap for Cloud is around level 14. This is a known limitation, and we have logged it as a product feedback item. The team is aware that this is a requirement for multiple customers. I have one follow-up question: When you mention that the zoom issue is more noticeable within the dashboard insight switcher, is this because the map opens more zoomed out in the smaller container, or do users genuinely find they cannot zoom in as far compared to viewing the chart independently? Understanding this will help us determine if there is a separate viewport or fit issue in addition to the zoom cap. We would appreciate it if you could provide a screenshot for comparison.

Hi Mauricio, thank you for the update. In regards to your follow-up question, the map zoom is the same whether the insight is in a switcher or not. It was just that the customer first noticed the issue in a map insight that happened to be in a switcher. I've tested both to verify the zoom limitation is the same.

Hi Nick, Unfortunately, I have to say that we cannot provide a solution at this time. As I mentioned our engineers have indicated that this is a known limitation that they are currently addressing, but I cannot provide an estimated timeline for when it will be resolved. Thank you for your understanting and clarification about the issue with the insight switcher.

Hi Mauricio, thank you for the confirmation.