MapML Use Case, Requirement, and Capability Matrix

This document compares the capabilities of existing popular web mapping libraries, comparing and contrasting implementations with the MapML specification and the reference MapML-Viewer custom-component polyfill.

The capabilities indicated are split between common functionality that should be in any implementation (and thus suitable for standards) and aspirational features that should be natively implementated in browsers but which are not yet widely supported in most JavaScript libraries.


Web maps provide a predominantly visual, spatial view into geographic data, for a wide variety of use cases. It is a complicated field, organically developed over many decades, with many different capabilities among the different web mapping APIs, SDKs, and embeddable map widgets. The aim of this study is to assess which needs the existing solutions meet, which services they provide in common with each other, and what the levels of granularity are available in web mapping APIs.

This document is a summary of the more detailed Use Cases and Requirements for Standardizing Web Maps document developed by the W3C Maps For HTML Community Group. (References to that document in the tables below are indicated with an external link icon.)

Technical Note

The tables in this document are dynamically generated from a JSON file, mapml-ucr.json, shared between this document and the Use Cases and Requirements for Standardizing Web Maps report. The shared JSON file is intended to keep the documents synchronized, but requires that client-side JavaScript is enabled.


Approved capabilities

Proposed capabilities

Note: This is a placeholder section for future discussion of proposed capabilties.

proposed capability category MapML specification Web-Map custom component Bing Maps D3 Google Maps Leaflet.js Mapbox MapKit OpenLayers OpenStreetMap TomTom
Name and link to Github issue                        

Use Cases