Page pattern

Geographic / Location

“Derived from the page purpose; write it explicitly before implementation.”

Understand spatial differences and compare performance across locations or regions.

[ KPIs / filters ] [ Map ] [ Ranking / comparison ] [ Location breakdown ] [ Detail ]

Simulation of native Power BI behaviour

Zone 1

KPIs / filters

Zone 2

Map

Zone 3

Ranking / comparison

Zone 4

Location breakdown

Zone 5

Detail

Reading order follows the zones above, top-left to bottom-right.

Designer

Components: Azure Maps, Cards, Bar charts, Table/Matrix

Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.

Developer

Interaction: Use only interactions that support the page's next analytical step; typical next level: **Location detail**.

Navigation: Location detail

Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.

Common mistakes

Treating the archetype as a rigid screen; adding unrelated analytical tasks; duplicating controls already handled globally.