Maps for HTML Roadmap
2022-03-31
Background and Problem Statement 2
Contextual History of Web Maps 1997 - 2019 7
By 2033, the web platform will include standard mapping features; web maps frameworks will include standards based accessibility features, will perform well, preserve privacy, and make map authoring easier for users.
Geospatial information on the Web is fragmented, inadequately covered by Web standards, and lacking interoperability and accessibility. This raises significant barriers to its effective and equitable use.
In 2016, Peter Rushforth laid out a vision for maps on the web, and started the Maps for HTML community group at the W3C. In 2020, Natural Resources Canada (NRCan) engaged Bocoup to conduct a review of MapML specification. Bocoup attended the W3C-OGC Workshop on Maps for the Web, delivered a report, and published a case study.
In November 2021, NRCan re-engaged Bocoup to establish a rationale and conceptual framework for accessible map rendering by Web browsers, and create an implementation plan. Bocoup conducted a landscape analysis, static analysis on web maps usage in HTTP Archive, engaged and interviewed web maps framework authors, and GIS experts, and surveyed web developers. A summary of this research was published in Bocoup’s Maps or HTML Research report. This roadmap contains the implementation plan resulting from this work.
According to our research, 16% of web pages use maps, but 84% of surveyed map makers don’t have the necessary tools to make accessible maps. This was strongly echoed in follow up interviews, which also called out performance issues in existing web mapping tools. These findings indicate a need for standardized accessible web maps.
Bocoup identified three viable approaches to standardize web maps (covered in the above linked research document), and presented these findings to browser implementers. Implementers encouraged taking an iterative approach to standardizing maps, and focusing on buy-in from map frameworks during the process. Based on this feedback and standards development experience, Bocoup recommended the third approach from the research document, “the iterative approach”. The iterative approach includes:
The tables below describe a high-level eleven-year roadmap for the Web Maps ecosystem infrastructure partnership, including 16 key milestones.
# | Milestone | Goals | Dates |
1 | Form a working group and continued stakeholder conversations | 1 | 2022 |
2 | Research, gap analysis, and web framework patching to support
Patch frameworks using existing technologies (e.g. ARIA, AOM, CSS Houdini, Web Animation API, WebGL). | 2, 3, 4 | 2022 - 2024 |
3 | Synthesis of gap analysis and standards plan to close those gaps. | 1 | 2024 |
4 | Disaggregate the MapML polyfill into individual, discrete custom elements based on Milestone 2 research with support for an accessible map interaction model (e.g sound based, haptic, printed, keyboard navigable), and a focus on performance, and privacy.
| 2, 3, 4, 5, 6 | 2023-2025 |
5 | Standardize the rest of the map rendering model using above process
| 2, 3, 4 | 2022 - 2026 |
6 | Implement Map rendering model in browsers | 2, 3, 4 | |
7 | Add support for map rendering model standard to map frameworks | 2, 3, 4 |
# | Milestone | Goals | Dates |
8 |
| 2, 3, 4, 5, 6 | 2026-2031 |
9 | Add support for Disaggregated MapML Polyfills to map frameworks | 5 | 2030-2032 |
10 | Create a browser-level coordinate Reference System, including support for Display images (tiles, different zoom levels), tilting and rotating, and bearing support
| 5 | 2024 - 2027 |
11 | Implement CRS in browsers | 5 | |
12 | Add support for CRS standard to map frameworks | 5 | |
13 | Standardize a pan and zoom capability in CSS
| 3, 5 | 2024 ~ 2033 depending on consensus |
14 | Implement pan and zoom in browsers | 3, 5 | |
15 | Add support for pan and zoom standard to map frameworks | 3, 5 | |
16 | Implement a high-level map element based on above standards | 5, 6 | 2026 ~ 2032 depending on consensus |
Bocoup is a mission and values driven web platform firm that partners with tech companies, nonprofits, and governments on design, engineering, standards development and strategy.
The following table shows a list of historical web maps milestones between 1994 and 2019.
Milestone | Impact | Date |
HTML <map> element introduced | Took up the name “map” in HTML for image mapping, precluding geospatial map element from being created with the same name. (source) | 1997 |
OpenStreetMap is created | First open source, open content world map. | 2004 |
Yandex Maps | Yandex becomes a web map vendor. | 2004 |
Google Maps | Google becomes a web map vendor. Today has wide adoption in terms of embeds on web pages. | 2005 |
Google Earth | 3D map client, initially as a desktop-only application, and later also as a web application. | 2005 |
OpenLayers | Open source web based map framework. | 2005 |
Apple’s iPhone is released | Momentum shift from feature phones to smartphones, and from GPS devices to smartphones. | 2007 |
AppleMaps | Apple becomes a web map vendor. | 2012 |
Maps for HTML Community Group is created | Start of discussion around making web maps part of HTML. (source) | 2016 |
“Integrate Web map support into browsers” discussion at W3C TPAC | 2019 |
Bocoup
PO Box 961436
Boston, MA 02196
617 379 2752