SOTM15/index.html at master · OpenRouting/SOTM15 · GitHub

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
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
<!doctype html>
<html lang="en">

	<head>
		<meta charset="utf-8">

		<title>Pedestrian Routing in OSM</title>

		<meta name="description" content="Pedestrian Routing in OSM">
		<meta name="author" content="Christopher Fricke">

		<meta name="apple-mobile-web-app-capable" content="yes" />
		<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />

		<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">

		<!-- Mapbox CSS -->
		<link href='https://api.tiles.mapbox.com/mapbox-gl-js/v0.7.0/mapbox-gl.css' rel='stylesheet' />

		<link rel="stylesheet" href="css/reveal.css">
		<link rel="stylesheet" href="css/theme/map.css" id="theme">

		<!-- Code syntax highlighting -->
		<link rel="stylesheet" href="lib/css/zenburn.css">


		<!-- Printing and PDF exports -->
		<script>
			var link = document.createElement( 'link' );
			link.rel = 'stylesheet';
			link.type = 'text/css';
			link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
			document.getElementsByTagName( 'head' )[0].appendChild( link );
		</script>

		<!--[if lt IE 9]>
		<script src="lib/js/html5shiv.js"></script>
		<![endif]-->
	</head>

	<body>

		<div class="reveal" id="map">

			<!-- Any section element inside of this container is displayed as a slide -->
			<div class="slides">

				<section>
					<h1>Pedestrian Routing</h1>
					<h3>State of the Map 2015</h3>
					<p>
						<small><a href="https://github.com/OpenRouting">Christopher Fricke</a> | <a href="http://twitter.com/bmoregeo">@bmoregeo</a></small>
						<br>
						<a href="http://gisiindoors.com">
							<img src="picture/footer_logo.png" alt="GISi Indoors" />
						</a>
					</p>
					<aside class="notes">
						Good Morning Everyone! I am Christopher from GISi Indoors and
						I'm here to talk to you all about a passion of mine... Pedestrian Routing!
					</aside>
				</section>

				<section>
					<img src="picture/car.jpg" alt="Picture of Car" class="primaryPicture"/>
					<aside class="notes">How many of you drive a car to work?</aside>
				</section>

				<section>
					<img src="picture/bus.jpg" alt="Picture of Train"  class="primaryPicture"/>
					<aside class="notes">How about public transportation?</aside>
				</section>

				<section>
					<img src="picture/bike.jpg" alt="Picture of Bike"  class="primaryPicture" />
					<aside class="notes">Maybe even a bike?</aside>
				</section>

				<section>
					<img src="picture/walk_hall.png" alt="Picture of person walking in hallway" class="quarterPicture" />
					<img src="picture/walk.png" alt="Picture of Person walking on path"  class="quarterPicture"/>
					<br />
					<img src="picture/stairs.png" alt="Picture of Person walking up stairs"  class="quarterPicture"/>
					<img src="picture/wheelchair.png" alt="Picture of Person in Wheelchair"  class="quarterPicture" />

					<aside class="notes">
						Alright, so now how many of you walk at some point in your journey?
					</aside>
				</section>

				<section>
					<img src="picture/walking-99188_640.png" alt="Walking Logo" class="halfPicture" />
					<img src="picture/512px-Public-images-osm_logo.svg.png" alt="OSM Logo" class="halfPicture" />

					<aside class="notes">
						Pedestrian networks are a vital component of our transportation networks. Unfortunately,
						as a geo community, we've totally overlooked sidewalks and paths. There hasn't really been any
						financial or technical incentive to develop these datasets.

						Luckily with the OSM community and the Id editor, this dataset is becoming easy to maintain.
						Also, there are a bunch of Open Source and Closed Source routing engines that consume this data.
					</aside>
				</section>

				<section>
					<h2>Other Services</h2>
					<img src="picture/Googlemapslogo2014.png" alt="Google Logo" class="thirdPicture"/>
					<img src="picture/MudLFJqh.png" alt="Esri Logo" class="thirdPicture"/>
					<img src="picture/here_logo_800x800.jpg" alt="Here Logo" class="thirdPicture"/>
					<aside class="notes">
						Google, Esri, and Here all provide pedestrian routing to one degree or
						another. They don't provide the level of detail that the OSM
						community is building. In addition, these services do not include wheel
						chair accessible pedestrian routing.


					</aside>
				</section>

				<section>
					<img src="picture/IMG_0456.PNG" alt="GeoMetri Navigator" class="thirdPicture"/>
					<img src="picture/IMG_0457.PNG" alt="GeoMetri Navigator" class="thirdPicture"  />
					<img src="picture/IMG_0458.PNG" alt="GeoMetri Navigator" class="thirdPicture" />
					<aside class="notes">
						At my 9-5 with GISi Indoors I work on an indoor pedestrian routing network application
						for college campuses, airports, and convention centers.

						I am really excited to share some of the knowledge I've learned over the
						past few years while working on this product. Here are a few tips and tricks
						for making your communities pedestrian routable!
					</aside>
				</section>

				<section>
					<h2><a href="http://wiki.openstreetmap.org/wiki/Key:highway">Highway Tag</a></h2>
					<ol>
						<li><b>Footway:</b> Designated pedestrian path or trail</li>
						<li><b>Path:</b> Generic path or trail for bikes and walking</li>
						<li><b>Steps:</b> Flight of Stairs</li>
						<li><b>Elevator:</b> Elevator</li>
						<li><b>Pedestrian:</b> Designated road or plaza for pedestrians</li>
						<li><b>*:</b> Any other road type with *Sidewalk* Tag</li>
					</ol>
					<aside class="notes">
						The MOST IMPORTANT tag is determining the highway type. The highway tag is how we
						define if the feature is a road/path/way.

						90% of your pedestrian features are footways. I know this is confusing since another
						highway type is actually called pedestrian, but bare with me.

						Paths are mixed use paths for bicycles, pedestrians, horses, or whatever.
						Steps and Elevators are... Steps and Elevators.
						Pedestrian ways are those streets in historic districts that are closed off to cars.
						You can also just assign a "sidewalk" tag to any other road feature, but you don't
							get the granularity of a standalone footway or path.
					</aside>
				</section>

				<section>
					<h2>Drawing</h2>
					<img src="picture/bridge.png" alt="Bridges" class="halfPicture"/>
					<img src="picture/vertex.png" alt="Paths at vertex"  class="halfPicture"/>
					<aside class="notes">
						There is only one rule to drawing in paths
						Everything must connect!

						Lines that don't share a point are treated as disconnected lines. So make sure you
						have that point there when you want a path to connect to another path.

						Don't put that point there if your feature is a bridge or tunnel.
					</aside>
				</section>

				<section>
					<h2><a href="https://wiki.openstreetmap.org/wiki/Key:access">Access Tag</a></h2>
					<ul>
						<li><b>Yes:</b> Accessible to Anyone</li>
						<li><b>No:</b> Not Accessible to Anyone</li>
						<li><b>Private:</b> Private Use Only</li>
						<li><b>Permissive:</b> Accessible to Anyone, at Owners Discretion (stores)</li>
						<li><b>Delivery:</b> Only for delivery people</li>
						<li><b>Discouraged:</b> If you get awkward looks</li>
					</ul>

					<aside class="notes">
						The access tag defines who can take the route. Is it
						publicly accessible, not accessible, or awkwardly accessible like that
						neighborhood trail that is kinda in your neighbor's yard.

						I usually default to Yes.
					</aside>
				</section>

				<section>
					<h2>Wheelchair Accessibility Tags</h2>
					<ul>
						<li><b><a href="http://wiki.openstreetmap.org/wiki/Key:ramp">ramp:</a></b> The path is a ramp. (Yes|No)</li>
						<li><b><a href="http://wiki.openstreetmap.org/wiki/Key:incline">incline:</a></b> Percent incline of path.</li>
						<li><b><a href="http://wiki.openstreetmap.org/wiki/Key:smoothness">smoothness:</a></b> The surface smoothness of the path.</li>
						<li><b><a href="http://wiki.openstreetmap.org/wiki/Key:width">width:</a></b> The width of the path (meter).</li>
						<br>
						<li><b><a href="http://wiki.openstreetmap.org/wiki/Key:wheelchair">wheelchair:</a></b> The path is wheelchair accessible. (Yes|No)</li>
					</ul>
					<aside class="notes">
						There is a reason that google doesn't have wheelchair
						accessible directions. The impacts of incorrect data have real impacts on people.

						The ADA requirements for accessible routes are incredibly strict. At a minimum, you can use
						the first four tags here to make a somewhat educated guess.

						1) Ramps are usually wheelchair accessible
						2) Except for when the incline is too crazy (<5%)
						3) The path shouldn't be too bumpy
						4) Finally the width should be at least meter

						If all of these attributes are set then you can probably set wheelchair to Yes But do err
						on the side of caution
					</aside>
				</section>

				<section>
					<img src="picture/walking route.png" alt="github page" />

					<aside class="notes">
						Finally, it may take up to a day or so, but your routes will show up in the OSM website.

						Or you can download the data if you have rolled your own routing engine.
					</aside>
				</section>

				<section>
					<h3><a href="https://github.com/OpenRouting">https://github.com/OpenRouting</a></h3>
					<img src="picture/openrouting.png" alt="github page" />
					<img src="picture/openrouting_datamodel.png" alt="github page" />

					<h3>Twitter: <a href="https://twitter.com/bmoregeo">@BmoreGeo</a></h3>
					<h3>GitHub: <a href="https://github.com/bmoregeo">@BmoreGeo</a></h3>
					<aside class="notes">
						I'm slowly working on an ETL process and API for pedestrian routing. Please
						hit me up at the break if you are interested in pedestrian routing and wanna chat.
					</aside>
				</section>


			</div>

		</div>

		<script src="lib/js/head.min.js"></script>
		<script src="js/reveal.js"></script>
		<script src='https://api.tiles.mapbox.com/mapbox-gl-js/v0.7.0/mapbox-gl.js'></script>

		<script>
			mapboxgl.accessToken = 'pk.eyJ1IjoiYm1vcmVnZW8iLCJhIjoiSk04dld2cyJ9.wMJSAMUtco68PrVuW2i4gA';
			var tileset = 'bmoregeo.mbnj1dg4';
			var map = new mapboxgl.Map({
				container: 'map', // container id
				style: {
					"version": 7,
					"sources": {
						"simple-tiles": {
							"tiles": "raster",
							"url": "mapbox://" + tileset,
							"tileSize": 256,
							"type": "raster"
						}
					},
					"layers": [{
						"id": "simple-tiles",
						"type": "raster",
						"source": "simple-tiles",
						"minzoom": 0,
						"maxzoom": 22
					}]
				},
				center: [39.2933, -76.6167], // starting position
				zoom: 15 // starting zoom
			});
		</script>

		<script>

			// Full list of configuration options available at:
			// https://github.com/hakimel/reveal.js#configuration
			Reveal.initialize({
				controls: true,
				progress: true,
				history: true,
				center: true,

				transition: 'slide', // none/fade/slide/convex/concave/zoom

				// Optional reveal.js plugins
				dependencies: [
					{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
					{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
					{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
					{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
					{ src: 'plugin/zoom-js/zoom.js', async: true },
					{ src: 'plugin/notes/notes.js', async: true }
				]
			});

		</script>

	</body>
</html>