Skip to content

Home

Jump to bottom
Harry Gibson edited this page May 18, 2026 · 6 revisions

OS Power BI Map Visual

The OS Power BI Map Visual is a custom Power BI visual for displaying geospatial data on an Ordnance Survey basemap, directly within Power BI dashboards. It has been developed by Ordnance Survey and is open-sourced under the MIT licence.

The visual lets report authors create choropleth (fill) and point maps — or combine both on the same visual — without any knowledge of GIS software. It includes built-in access to Office for National Statistics (ONS) administrative boundaries, drag-and-drop geocoding for several location identifier types, and two-way cross-filtering with other visuals in a Power BI report.

End-user documentation — for installation instructions and a full user guide, see the OS Maps for Power BI Visual documentation on the OS docs site.

Key features

  • Choropleth (fill) maps and point maps on an OS basemap, combinable on a single visual
  • Built-in access to hundreds of ONS administrative boundaries (LSOAs, MSOAs, wards, and more) without importing geometry files
  • Drag-and-drop geocoding: latitude/longitude, postcodes, UPRNs, Eastings/Northings
  • Custom geometries from the Power BI data model (GeoJSON or WKT) or via upload of shapefiles etc
  • Two-way cross-filtering with other report visuals via a lasso selection tool
  • Customisable symbology — colour ramps, categorical palettes, opacity, point size
  • A reference boundary layer for displaying geographic context alongside data layers
  • Data security by design: strict sandboxing and open-data geocoding APIs only

Status

Version 1.0.1.0, released 18 May 2026. Source code is open under the MIT licence.

Wiki contents

The contents of this wiki are primarily aimed at developers who would like to modify the visual or understand more about how it's built. End users of the visual should consult the user guide instead.

Page Contents
Design Philosophy Product-level decisions — what the visual does and deliberately doesn't do, and why
Technical Decisions Implementation-level decisions — library choices, API architecture, data handling
Using the Visual Feature summary and links to the OS docs for step-by-step instructions
Developer Setup How to get a local development build running
Contributing How to contribute issues and pull requests
Architecture Source code structure and component overview

Useful links

Clone this wiki locally