-
Notifications
You must be signed in to change notification settings - Fork 11
/
index.html
120 lines (114 loc) · 4.31 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
---
permalink: "/"
# See _config.yml for site title and description
---
{% include relBase.html %}
<p><a id="introduction"></a>
This workshop series brings together experts in
geographic standards and Web map data services,
Web mapping client tools and applications,
and Web platform standards and browser development,
to explore the potential of maps for the Web.
</p>
<div class="info">
<p>
This workshop series was originally planned as an in-person event in Montreal.
Due to risks associated with global travel and the spread of COVID-19,
the Maps for the Web workshop in 2020 was online only,
spread out over a month of video presentations and asynchronous discussion.
</p>
<p>
We hope that this helps build a community that lasts beyond the scheduled event,
and that a physical gathering of participants will be possible in the future.
</p>
</div>
<h2 id="objective">Workshop Objectives</h2>
<p>
The workshop organizers want to make map viewers on the web better
— more usable, accessible, secure, private, and performant —
for website visitors and web app users.
At the same time, we want to make it easier
for web developers and other creators to build those map-based experiences.
And we want to make it more natural
for cartographers and geospatial researchers
to share their content over the web.
</p>
<p>
To do this, we need input from all relevant stakeholders,
from all over the world wide web,
who are creating or using web map content and applications,
along with those who are building or standardizing web browsers.
From the discussion,
we hope to build a consensus on
which aspects of web maps are suitable for standardization,
and what those standardized solutions should include.
</p>
<h2 id="why-maps">Why Maps for the Web?</h2>
<p>
Maps are a facet of our daily lives.
The Web (and other internet-connected applications)
have made maps more personal and more pervasive.
From deciding what route to take to work,
to vacation planning, to researching the effects of climate change,
online maps guide our decisions and inform our world view.
</p>
<p>
Maps on the Web have the potential to empower individuals,
connecting our physical environment
to online information and applications.
But that hyperconnectivity comes with risks:
that people's movements may be tracked,
or that their lives and livelihoods may become dependent
on closed, proprietary data and services.
</p>
<h2 id="scope">Scope of the Workshops</h2>
<p>
The workshop series is specifically about the standardization of dynamic,
interactive maps as a first-class native component in the browser or other
applications built using the Web platform.
</p>
<p>
This includes how the map data is served to the web application,
how it is embedded or manipulated by the website author,
how the result is displayed to the website visitor by the web browser,
and how that end user interacts with or makes use of the information in the map.
</p>
<p>
Broader uses of internet-connected geographic data or spatial metadata
are only in scope so far as they share technologies and impacts with Web maps.
</p>
<h2 id="topics">Topics Covered</h2>
<p>
The <a href="{{ relBase }}/report">workshop final report</a> provides an overview
of the presentations and discussions,
grouped according to these key themes:
</p>
<ul>
<li>
Accessibility, including both
how to make web map viewers accessible to diverse users,
and how to enhance map data so that it can be used to make real world locations more accessible;
</li>
<li>
Augmented Reality (AR) with geospatial data;
</li>
<li>
Internationalization and privacy issues with map data;
</li>
<li>
Performance issues with dynamic map rendering in web browsers;
</li>
<li>
Scoping out the requirements, and comparing proposals for,
new web standards to define map viewers natively in HTML.
</li>
</ul>
<p>
Additional sessions brought together groups of stakeholders
from similar organizations (government, open source, or commercial)
to discuss common needs and concerns.
</p>
<p>See the original <a href="{{ relBase }}/call-for-participation">call for participation</a>
for more background on how the workshop agenda was developed,
including the list of possible topics proposed by the organizers.
</p>