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.
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.)
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|