-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.html
executable file
·316 lines (251 loc) · 12.8 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
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
308
309
310
311
312
313
314
315
316
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GeoJSON</title>
<meta name="author" content="Sean Gillies">
<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">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/white.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]-->
<style>
.reveal section img {
border: 1px solid #ccc;
}
</style>
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>GeoJSON</h1>
<p>Howard Butler, Martin Daly, Allan Doyle, Sean Gillies, Stefan Hagen, Tim Schaub, Erik Wilde</p>
<aside class="notes">
Good afternoon. Thank you very much for attending this presentation.
I'm going to make the case for forming a working group to
standardize the GeoJSON format. There's much benefit for not a
lot of additional work.
</aside>
</section>
<section>
<h2>What is GeoJSON?</h2>
<ul>
<li>Structured information about geospatially-bounded things (aka "features") and their properties</li>
<li>Using JavaScript Object Notation</li>
<li>Simplifies as much as possible</li>
</ul>
<aside class="notes">
"as much as possible, but no further."
The simplification I'm talking about isn't
a XML vs JSON issue, it's an issue of geographic information
system architecture. There's been a trend toward complexity
in GIS. GeoJSON is deliberately more simple, not just a JSON
translation of other complex formats.
</aside>
</section>
<section>
<h2>GeoJSON History</h2>
<ul>
<li>Discovered on Freenode: #openlayers and #gdal, late 2006</li>
<li>Informal WG launched 2007-03-15</li>
<li>375 Messages later...</li>
<li>Format Specification published 2008-06-18</li>
<li>Informal WG moved to GitHub 2011-09-22</li>
<li>draft-butler-geojson-00 submitted 2014-01-08</li>
</ul>
<aside class="notes">
The format is coming up on its 7th birthday. Building
consenus and writing it up took over a year. The informal
working group copied the IETF in some ways: we committed
ourselves to working openly and tried to put empirical
results before theory. We did not always suceed at the
latter (empiricism).
</aside>
</section>
<section>
<img src="img/geojsonio.jpg">
<aside class="notes">
GeoJSON is making it easier to design and develop
applications for capturing data.
</aside>
</section>
<section>
<img src="img/github.jpg">
<aside class="notes">
GeoJSON is making it easier to design and develop
applications for managing and sharing data.
</aside>
</section>
<section>
<h2>Where we are now</h2>
<ul>
<li>GeoJSON is improving data interchange</li>
<li>Maps abound, processes are evolving</li>
<li>Intense demand for improvement</li>
<aside class="notes">
GeoJSON is very widely used. It has good to first class
support in geospatial software. In proprietary products
as well as in open source.
There's demand for improvement from GeoJSON.
For example, GitHub. It's a very popular site for
sharing and curating GeoJSON. But because GeoJSON isn't
a real standard, GitHub's support is variable in quality.
GitHub takes IETF standards like HTTP, JSON, link headers
seriously, but GeoJSON less so.
People want GeoJSON to play a role in their infrastructures.
They want to build on it. They want to extend it. They
aren't sure how to do this. An RFC will make a huge difference
and a working group.
</aside>
</section>
<section>
<h2>Influences</h2>
<ul>
<li>OGC Simple Features Specification</li>
<li>W3C Basic Geo Vocabulary</li>
<li>GeoRSS</li>
<li>Atom</li>
</ul>
<aside class="notes">
GeoJSON is informed by Open Geospatial Standards and
strongly infuenced by the Atom syndication format.
</aside>
</section>
<section>
<h2>Related Work</h2>
<ul>
<li>GML, GPX, KML</li>
<li>IETF geopriv WG (RFC 5870 - geo URI scheme)</li>
<li>Schema.org</li>
<li>JSON-LD</li>
</ul>
<aside class="notes">
GeoJSON independently discovered some of the same keywords
later discovered by the W3C's RDF working group. We are
mindful of JSON-LD and have avoided duplication since it
was published.
We are in contact with schema.org principals and are
working toward interoperability.
</aside>
</section>
<section>
<h2>Related Work</h2>
<p>W3C/OGC Spatial Data on the Web WG</p>
<ul>
<li>Not developing technologies</li>
<li>Considering GeoJSON</li>
</ul>
<aside class="notes">
From the SDWWG charter:
"The Spatial Data on the Web Working Group must be mindful of the needs of front end Web developers, however, it will not develop any geospatial or map rendering technologies. In other words, this WG is focused specifically on the intersection of the issues facing OGC and W3C members."
The SDWWG is not developing any tech, which is as it should be.
GeoJSON standardization helps their cause. I fully expect
member of that WG to participate in a GeoJSON WG.
</aside>
</section>
<section>
<h2>Applications</h2>
<p>Almost any kind of geospatial JSON data interchange</p>
<ul>
<li>HTTP CRUD and JavaScript APIs</li>
<li>Spatial database queries</li>
<li>Alerting and geo-fencing protocols</li>
<li>Defining coverage of networked mobile apps</li>
<li>Engineering basis for geo protocol buffers</li>
</ul>
</section>
<section>
<h2>Why the IETF?</h2>
<ul>
<li>Agreement with the IETF mission and its principles</li>
<li>Desire to have GeoJSON join other JSON RFCs</li>
<li>History of interaction between informal GeoJSON WG and geopriv WG</li>
</ul>
<aside class="notes">
GeoJSON is widely adopted in the geospatial domain, but there
are still programmers and engineers in government who want
to use it, but are blocked by the lack of formal
standardization. One of them has expressed the situation
as "brown-bagging GeoJSON" in their enterprise.
</aside>
</section>
<section>
<h2>Proposed WG Scope</h2>
<ul>
<li>Narrow as possible</li>
<li>Start with draft-butler-geojson-05</li>
<li>More precisely specify the GeoJSON format</li>
<li>Document best practices discovered since 2008</li>
<li>Investigate implications of recent JSON RFC 7159</li>
<li>Alignment with work such as <em>JSON Text Sequences</em> and <em>I-JSON</em> (RFC 7464/7493)</li>
</ul>
<aside class="notes">
We want the scope to be as narrow as possible.
Our I-D already contains many fixes and clarifications.
It substantially improves the original Spec.
</aside>
</section>
<section>
<h2>How much work remains?</h2>
<ul>
<li>Extensibility of GeoJSON</li>
<li>Consideration of other geometry primitives</li>
<li>Re-consideration of coordinate systems</li>
<li>All GeoJSON authors approve</li>
<li>5 of 6 raise their hands to do the remaining work</li>
</ul>
<aside class="notes">
Work on extensibility of GeoJSON remains to be done. We
don't want to do this in a GIS-specific way and
need JSON expertise to get it right.
I'm certain that we'll need to discuss other geometry
primitives such as curves.
Coordinate reference systems will need to be discussed.
The original GeoJSON specification did a poor job with
coordinate reference systems.
There are people who will help work on this but not
outside a more formal WG.
</aside>
</section>
<section>
<h2>Links</h2>
<ul>
<li>Presentation on the Web: <a href="http://geojson.org/ietf-92-presentation/">http://geojson.org/ietf-92-presentation/</a></li>
<li>Presentation source: <a href="https://github.com/geojson/ietf-92-presentation">https://github.com/geojson/ietf-92-presentation</a></li>
<li>Proposed charter: <a href="https://github.com/geojson/draft-geojson/blob/master/charter.md">https://github.com/geojson/draft-geojson/blob/master/charter.md</a></li>
<li>draft-butler-geojson: <a href="http://tools.ietf.org/html/draft-butler-geojson-05">http://tools.ietf.org/html/draft-butler-geojson-05</a></li>
</ul>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></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,
slideNumber: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
});
</script>
</body>
</html>