Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Share your agentic AI experience, learn from others, and earn a new badge: Put Agentic AI to Work
cancel
Showing results for 
Search instead for 
Did you mean: 
Gokulsundar96
Partner - Contributor
Partner - Contributor

Selecting a view in Qlik Maps by Default, rather than using Geoanalytics

What exists today — in GeoOperations (Travel Areas)

Qlik Cloud's GeoOperations already supports transportation mode types for calculating Travel Areas. These modes include: Bird (a flying bird at 10 m/s), Car (road restrictions for cars), Bike (bike road restrictions), Pedestrian (pedestrian road restrictions), and Truck (truck road restrictions). Qlik Help

However, this capability only exists as a back-end data operation — it's used to compute a geographic polygon (a travel area zone) based on cost (time or distance). It is not a front-end map visualization property that a developer or end-user can set on a map chart as a "view type."


The Gap — What's Missing

When you build a Map chart in Qlik Cloud Analytics, maps enable you to view data geographically using multiple layers. You can limit the pan of a map to a specific view and scope, such as a region of interest. But there is no current setting that lets a developer pre-configure — or allows an end user to switch — the transportation perspective/view type of the map at the visualization level. Qlik Help

In other words:

  • The "Bird" perspective (top-down satellite/aerial view) is effectively the implicit default for all map charts.
  • There is no UI toggle or property panel option to set the default view mode (Bird, Car, Pedestrian, etc.) on the map chart itself.
  • End users cannot switch the view context dynamically within a published dashboard.

What Your Feature Request Should Cover

Here's the structured context you can use to write the request:

Problem Statement:
Qlik Cloud map charts only support a single implicit view type (bird's-eye / top-down). For use cases like logistics, field operations, urban planning, or accessibility analysis, users need the map to visually reflect the perspective relevant to their workflow — car routing view, pedestrian walkability, etc.

Requested Feature:
A "Default View Type" property in the Map chart property panel, allowing developers to set one of the following as the default rendering perspective for a map visualization:

  • 🐦 Bird — top-down aerial (current implicit default)
  • 🚗 Car — road-network focused view
  • 🚶 Pedestrian — walkway/footpath focused
  • 🚲 Bike — cycling path focused
  • 🚛 Truck — freight road network view

Additionally, optionally expose a runtime toggle so end users can switch the view type within a published app, without needing to go into edit mode.

Why It Matters:

  • Aligns the map visualization with the transportation mode already used in GeoOperations Travel Area calculations.
  • Improves analytical context — a logistics analyst using a Truck travel area should see a truck-perspective map, not a bird's-eye view.
  • Reduces cognitive load and makes dashboards more purpose-fit.
Labels (3)
1 Reply
amonjaras_c40
Luminary
Luminary

This sounds like a useful suggetion. Have you tried to compute all the layers in script and then display them selectively on the UI using a dimension or variables?

If I understand your intent correctly, are you asking people to request this feature? Have you done so yourself in the Ideation portal? (I did a quick search and could not find anything like this).

Maybe you should suggest the idea there, and then post the link so anyone interested can upvote it.

Hope this helps.