|
55 | 55 | background-position: center 1px; |
56 | 56 | background-size:50%; |
57 | 57 | } |
58 | | - .git-snapshots { |
59 | | - background-color: #2980b9; |
60 | | - background-image: url(./images/snapshots.png); |
61 | | - background-repeat: no-repeat; |
62 | | - background-position: center 1px; |
63 | | - background-size:100%; |
64 | | - } |
65 | | - .git-areas { |
66 | | - |
67 | | - background-image: url(./images/areas.png); |
68 | | - background-repeat: no-repeat; |
69 | | - background-position: center 1px; |
70 | | - background-size:100%; |
71 | | - } |
| 58 | + |
72 | 59 | .octocat { |
73 | 60 | background-color: #fff; |
74 | 61 | background-image: url(./images/octocat-original.png); |
|
95 | 82 | background-position: center 1px; |
96 | 83 | background-size:75%; |
97 | 84 | } |
| 85 | + .gh-pages-1 { |
| 86 | + background-image: url(./images/gh-pages-1.PNG); |
| 87 | + background-repeat: no-repeat; |
| 88 | + background-position: center 1px; |
| 89 | + background-size:100%; |
| 90 | + } |
98 | 91 | .osm-1 { |
99 | 92 | background-image: url(./images/osm-1.png); |
100 | 93 | background-repeat: no-repeat; |
|
143 | 136 | <div>Part 2: Data & GitHub</div> |
144 | 137 | <div><h2>2 interrelated aims:</h2> |
145 | 138 | <ol> |
146 | | - <li>Create a place to store & access data</li> |
| 139 | + <li>Find a place to store & access data</li> |
147 | 140 | <li>Get, create, & edit data for the web</li> |
148 | 141 | </ol> |
149 | 142 | </div> |
150 | 143 | <div>Why?</div> |
151 | | - <div>We need to know where our data is</div> |
| 144 | + <div>We need to know where our data is so we can get to it when we need it</div> |
152 | 145 | <div>We need to be able to optimize our data for the web!</div> |
153 | 146 | <div><h2>Goals:</h2> |
154 | 147 | <ul> |
155 | 148 | <li>Get to know geoJSON</li> |
156 | 149 | <li>Understand the basics of GitHub</li> |
157 | | - <li>Be able to contribute to and make changes to files on GitHub</li> |
158 | | - <li>Get & prepare data for the web</li> |
| 150 | + <li>Be able to access and make changes to files on GitHub</li> |
| 151 | + <li>Identify tools and sources to get & prepare data for the web</li> |
159 | 152 | </ul> |
160 | 153 | </div> |
161 | 154 |
|
162 | 155 | <!--Intro to geoJSON--> |
| 156 | + <div>What data formats are we working with usually in GIS?</div> |
163 | 157 | <div data-bodyclass="gdb purple-text imageTextLight">geodatabase</div> |
164 | 158 | <div data-bodyclass="shapefile purple-text imageTextLight">shapefile</div> |
165 | 159 | <div>OK for GIS</div> |
|
172 | 166 | <!--This section contains several slides from Lyzi Diamond: http://lyzidiamond.com/learn-geojson/--> |
173 | 167 | <div>What is <em>GeoJSON</em>?</div> |
174 | 168 | <div><em>GeoJSON:</em> geographic data format. (Contains spatial information.)</div> |
175 | | - <div><em>GeoJSON:</em> extension of JSON, with a specific structure.</div> |
| 169 | + <div><em>GeoJSON:</em> extension of JSON, with a specific structure.<br><small>(JSON==<em>J</em>ava<em>S</em>cript <em>O</em>bject <em>N</em>otation)</small></div> |
176 | 170 | <div>This is what it looks like:</div> |
177 | 171 | <div data-bodyclass="geojson-1"></div> |
178 | 172 | <div><em>GeoJSON:</em> has room for nested attribute information.</div> |
|
186 | 180 | <div>And it's pretty easy to edit <em>GeoJSON</em>in your browser with a tool called <a href="http://geojson.io/" target="_blank">geojson.io</a></div> |
187 | 181 | <div>(We'll come back to that.)</div> |
188 | 182 |
|
| 183 | + <div>We know about a data format (geoJSON)...</div> |
| 184 | + <div>Where are we going to <em>store</em> it so it's also <em>accessible</em> for webmaps?</div> |
| 185 | + <div>We'll use <a href="https://github.com/" target="_blank">GitHub</a>!</div> |
| 186 | + <div>But first...</div> |
189 | 187 | <div>What is git?</div> |
190 | 188 |
|
191 | 189 | <div><em>git:</em> distributed version control system.</div> |
192 | 190 | <div>No central source</div> |
193 | 191 | <div><em>git:</em> allows for collaboration without totally screwing everything up.</div> |
194 | 192 | <div><em>git:</em> super powerful.</div> |
195 | | - <div data-bodyclass="git-snapshots"></div> |
196 | | - <div data-bodyclass="git-areas"></div> |
197 | 193 | <div data-bodyclass="octocat purple-text imageTextLight">What is <em>GitHub?</em></div> |
198 | 194 | <div><em>GitHub:</em> a home for lots and lots of code repositories.</div> |
199 | | - <div><em>GitHub:</em> interacted with using <em>git</em>.</div> |
| 195 | + <div><em>GitHub:</em> helps you interact with <em>git</em>and <em>beyond</em>!</div> |
200 | 196 | <div><em>GitHub:</em> provides easy-to-use tools and tutorials for using and learning git to collaborate on and contribute to projects.</div> |
201 | 197 | <div class="center-text">git version control<br /><em>+</em><br />storage<br /><em>+</em><br />social</div> |
202 | 198 | <div>Why GitHub?</div> |
|
207 | 203 | <li>Permalinks</li> |
208 | 204 | <li>Collaboration</li> |
209 | 205 | </ul> |
210 | | - </div> |
| 206 | + </div> |
| 207 | + <div>And since we <em>looove</em> maps...</div> |
211 | 208 | <div><em>GitHub:</em> best friends with <em>GeoJSON</em>!</div> |
212 | 209 | <div>Support for geo (especially geoJSON)</div> |
213 | 210 | <div><h2>Support for geo</h2> |
214 | 211 | <ul> |
215 | 212 | <li>Store & access data |
216 | | - <ul> |
217 | | - <li><a href="http://vimeo.com/106228441">"Small Town GIS Leveraging Github"</a> - Aaron Racicot at FOSS4G2014</li> |
| 213 | + <ul> |
| 214 | + <li>Versioning without SDE!</li> |
| 215 | + <li><a href="http://vimeo.com/106228441">"Small Town GIS Leveraging Github"</a> - Aaron Racicot at FOSS4G2014</li> |
218 | 216 | </ul> |
219 | 217 | </li> |
220 | | - <li>Versioning without SDE!</li> |
221 | 218 | <li>geoJSON rendered as a map</li> |
222 | 219 | </ul> |
223 | 220 | </div> |
|
231 | 228 | </div> |
232 | 229 | <div>Let's get started with GitHub!</div> |
233 | 230 | <div data-bodyclass="github-signup imageTextLight">Create GitHub account</div> |
234 | | - <div>You're ready to get going</div> |
| 231 | + <div>You're ready to get going!</div> |
235 | 232 | <div>Interact with Github by 3 means: |
236 | 233 | <ul> |
237 | 234 | <li>browser</li> |
|
264 | 261 | <div data-bodyclass="fork"></div> |
265 | 262 | <div>Clone repo</div> |
266 | 263 | <div data-bodyclass="clone"></div> |
| 264 | + <div>Note the <em>branch</em></div> |
| 265 | + <div data-bodyclass="gh-pages-1"></div> |
| 266 | + <div>New repos start with a <em>Master</em> branch</div> |
| 267 | + <div>But we want to be able to use GitHub to show our maps and data within a webpage</div> |
| 268 | + <div>So we're working with the gh-pages</div> |
267 | 269 | <div>Let's look at some data<br /><br /><a href="https://github.com/maptastik/os-webmap-workshop/blob/gh-pages/data/prepared/toledo_poi.geojson" target="_blank">Toledo POIs</a></div> |
268 | 270 | <div>We can edit the POIs...</div> |
269 | 271 | <div>...or make new geoJSON!</div> |
|
0 commit comments