Skip to content

Commit

Permalink
Merge pull request #282 from osmus/gh-pages
Browse files Browse the repository at this point in the history
New major updates
  • Loading branch information
d3netxer authored Jan 12, 2024
2 parents 806b2fc + 1cc8258 commit 13b604f
Show file tree
Hide file tree
Showing 232 changed files with 538 additions and 82,236 deletions.
3 changes: 3 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -6,3 +6,6 @@ _site/
.sass-cache
vendor/
_site/*
_sass/*
_layout/*
_config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
I"�{"source"=>"/Users/tomgertin/repos/teachosm", "destination"=>"/Users/tomgertin/repos/teachosm/_site", "collections_dir"=>"collections", "cache_dir"=>".jekyll-cache", "plugins_dir"=>"_plugins", "layouts_dir"=>"_layouts", "data_dir"=>"_data", "includes_dir"=>"_includes", "collections"=>{"posts"=>{"title"=>"Posts", "output"=>true, "permalink"=>"/:collection/:year/:month/:title.html"}, "carousel"=>{"title"=>"Carousel", "output"=>false}, "filters"=>{"title"=>"Filters", "output"=>false}, "projects"=>{"title"=>"Projects", "output"=>true}, "resources"=>{"title"=>"Resources", "output"=>true}, "uploads"=>{"title"=>"Uploads", "output"=>true}}, "safe"=>false, "include"=>["pages"], "exclude"=>[".sass-cache", ".jekyll-cache", "gemfiles", "Gemfile", "Gemfile.lock", "node_modules", "vendor/bundle/", "vendor/cache/", "vendor/gems/", "vendor/ruby/"], "keep_files"=>[".git", ".svn"], "encoding"=>"utf-8", "markdown_ext"=>"markdown,mkdown,mkdn,mkd,md", "strict_front_matter"=>false, "show_drafts"=>nil, "limit_posts"=>0, "future"=>false, "unpublished"=>false, "whitelist"=>[], "plugins"=>["jekyll-feed"], "markdown"=>"kramdown", "highlighter"=>"rouge", "lsi"=>false, "excerpt_separator"=>"\n\n", "incremental"=>false, "detach"=>false, "port"=>"4000", "host"=>"127.0.0.1", "baseurl"=>nil, "show_dir_listing"=>false, "permalink"=>"/:collection/:year/:month/:title.html", "paginate_path"=>"/page:num", "timezone"=>"UTC", "quiet"=>false, "verbose"=>false, "defaults"=>[{"scope"=>{"path"=>"", "type"=>"posts"}, "values"=>{"layout"=>"post"}}], "liquid"=>{"error_mode"=>"warn", "strict_filters"=>false, "strict_variables"=>false}, "kramdown"=>{"auto_ids"=>true, "toc_levels"=>[1, 2, 3, 4, 5, 6], "entity_output"=>"as_char", "smart_quotes"=>"lsquo,rsquo,ldquo,rdquo", "input"=>"GFM", "hard_wrap"=>false, "guess_lang"=>true, "footnote_nr"=>1, "show_warnings"=>false}, "title"=>"TeachOSM", "theme"=>"minima", "pagination"=>{"collection"=>"posts", "debug"=>true, "enabled"=>true, "per_page"=>4, "permalink"=>"/page/:num/", "title"=>":title - page :num", "limit"=>0, "sort_field"=>"date", "sort_reverse"=>true}, "featured_blog_post"=>"MapSaintLucia - a Community Development Roadmap", "livereload_port"=>35729, "serving"=>true, "watch"=>true, "url"=>"http://localhost:4000"}:ET
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
I"K <h2 id="osm-at-george-washington-university">OSM at George Washington University</h2>

<p><img src="../../../assets/images/blog/gwu-casestudy.jpg" alt="gwu-casestudy.jpg" /></p>

<h3 id="backstory">Backstory</h3>
<p>Nuala Cowan &amp; Richard Hinton of the Geography department regularly integrate the open source mapping platform, OpenStreetMap into the curriculum for their introductory undergraduate Geographical Information Systems (GIS) &amp; Cartography classes, -traditionally the domain of proprietary desktop software and data. They have sought to expand the traditional curriculum, and expose students to various open source software, web based platforms, and data collection initiatives, specifically in a service-learning environment.</p>

<h3 id="the-mapping-challenge">The Mapping Challenge</h3>
<p>In spring 2013, classes collaborated with the American Red Cross to map disaster prone communities in both Colombia and Indonesia. Using high-resolution satellite imagery, GW Geography students remotely traced road and building infrastructure, data that was subsequently field validated by domestic chapters of the Red Cross. In fall 2013 they worked on another collaborative project in conjunction with USAID and the Open Cities Project at the World Bank. Once again, students mapped street level infrastructure, this time, in the city of Kathmandu, Nepal. Field partner for this collaboration was a non-profit called <a href="http://kathmandulivinglabs.org/">Kathmandu Living Labs</a> (KLL). KLL then performed OSM Patrol Sessions (Data Quality check and Validation) on the data created by the students (and others) for Kathmandu. Richard and Nuala’s classes have continued to work on collaborations in recent semesters. In Spring 2014 students traced infrastructure in the Philippines in conjunction with the GeoCenter at USAID, and in Summer 2014 students worked once again with the American Red Cross to trace buildings in Harare, Zimbabwe.</p>

<h3 id="our-workflow">Our Workflow</h3>
<p>The instructors used the Tasking Manager tool to outline the study area (which is determined by our partners), and partition it for tracing. Each student is given a quota of nodes to trace.</p>

<h3 id="what-we-discovered">What we discovered</h3>
<p>The collaborative mapping initiatives at GWU Geography have been exclusively disaster related to date, as this coincides with the research interests of the faculty involved. We believe this type of instructional module/assignment is applicable to many disciplines and teaching scenarios, and the objective of the TeachOSM resource is to open that possibility to these other fields, in a comprehensive user friendly way.</p>

<ol>
<li>Backstory</li>
<li>The mapping challenge</li>
<li>Our workflow</li>
<li>Stumbling Blocks</li>
<li>Discuss the results and what was learned</li>
<li>Provide contact information</li>
</ol>
:ET
Original file line number Diff line number Diff line change
@@ -0,0 +1,98 @@
I"�<h1 id="dc-great-streets-a-street-level-survey-using-openstreetmap">“DC Great Streets: A Street-level Survey Using OpenStreetMap”</h1>

<h2 id="background">Background</h2>

<p>Conducting a street-level survey is a great way to get students acquainted with local land
use and land cover while learning important technical skills in the
<a href="http://openstreetmap/">OpenStreetMap</a> environment. The objective of a survey is to make
a field-level determination of how the property or building is being used, create a
geo-located photo survey of the streetscape, and add those features to OpenStreetMap. In
the paragraphs below, we discuss the rationale for a street-level survey, outline the
basic mapping activities, and offer pointers for your street-level survey.</p>

<h2 id="rationale">Rationale</h2>

<p>In late 2014, <a href="http://mappingdc.org/">MappingDC</a> began a collaboration with the <a href="http://greatstreets.dc.gov/">DC Great Streets</a>
program to conduct
a street-level survey in the twelve DC Great Streets corridors. The DC Great Streets
program dispenses capital improvement grants to small businesses in these corridors to
boost neighborhood economic resilience and help create lively urban centers around the city.
Once a month, MappingDC hosts a <a href="http://www.meetup.com/MappingDC/">mapping party</a> in or along one of the corridors where we
gather data in the field, upload, and edit the data in OpenStreetMap. The project is
evolving with an emphasis on creating service learning opportunities for young adults that
meet the needs of the DC Great Streets program.</p>

<h2 id="conducting-your-own-street-level-survey">Conducting your own street-level survey</h2>

<h3 id="tools-youll-need">Tools you’ll need</h3>

<ol>
<li>
<p>Mapillary: To create the streetview, we use <a href="http://mapillary.com/">Mapillary</a>, a
lightweight app that you add to your smartphone. So, before you get started, download and
install Mapillary. Also review the tips and techniques on the Mapillary page so you take good, usable photos.</p>
</li>
<li>
<p>Field Papers: We use <a href="http://fieldpapers.org/">Field Papers</a> to make a paper map of the streets, which
we annotate in the field. Print out large-scale maps of your area of interest so you can
annotate liberally and legibly. There is a very good Field Papers how-to on the
<a href="http://wiki.openstreetmap.org/wiki/Field_Papers">OpenStreetMap wiki</a> which shows how to
use Field Papers for field data collection.</p>
</li>
</ol>

<h2 id="workflow">Workflow</h2>
<p>The workflow:</p>

<ol>
<li>Conduct field work</li>
<li>Return to base and begin editing in OpenStreetMap</li>
<li>Upload photos to Mapillary site</li>
<li>Review work for completeness and accuracy</li>
</ol>

<h3 id="form-teams-for-field-work">Form teams for field work:</h3>
<ul>
<li>Two teams of two or three people, one team on each side of the street. One person records
basic information about the property or building (e.g. name, address, phone, website, etc.),
the second person records takes photos. A third person is useful to take supplemental notes,
help navigate, but not essential.</li>
</ul>

<h3 id="editing-process">Editing process</h3>

<ul>
<li>
<p>Trace building outlines as necessary. There are often multiple businesses in a building
so enter each business as a point and give it its own address.</p>
</li>
<li>
<p>The Great Streets program has a simple rating system to help determine which properties
qualify for assistance. Mappers tag each property with a rating, which the DC Great
Streets program can use to assess property condition. You should refer to the
<a href="http://wiki.openstreetmap.org/wiki/Key:building:condition">building condition</a> page on the
OSM wiki for help in tagging building conditions.</p>
</li>
<li>
<p>Follow the instructions on the Mapillary page for uploading your photos from your phone
to the Mapillary site.</p>
</li>
</ul>

<h2 id="lessons-learned">Lessons Learned</h2>
<p>MappingDC and DC Great Streets program are still working on how to standardize the tagging
scheme for building conditions so that they are useful to the program. We’ve also learned
that some photos are not usable because they are blurry, too dark, washed out, or taken at
a bad angle. We’re working on developing field techniques that will make for more consistently
usable photo quality.
Tactically, teams of three seem to work best, but plan on at least two per team.</p>

<h2 id="for-more-information">For more information:</h2>

<p>Mapillary provides detailed <a href="https://help.mapillary.com/hc/en-us">instructions</a></p>

<p>See also Elliott Plack’s diary <a href="https://www.openstreetmap.org/user/ElliottPlack/diary/26065">entry</a>
on how he created a street-level survey on bicycle.</p>

<p>For more information on street surveys or DC Great Streets mapping parties, please contact Steven Johnson (sejohnson8 at gmail dot com).</p>
:ET
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
I"/<h3 id="the-backstory">The Backstory</h3>
:ET
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
I"_<p>Controls classroom workflow by dividing large areas into small, easy to map tasks.</p>
:ET
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
I"[<h2 id="osm-at-george-washington-university">OSM at George Washington University</h2>
:ET
Original file line number Diff line number Diff line change
@@ -1,144 +1,4 @@
<!doctype html>
<html>

<head>

<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-175556304-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-175556304-1');
</script>

<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet" />
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet" />
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.9.0/css/all.min.css">
<link rel="stylesheet" href="/assets/css/bootstrap.min.css" />
<!--<link rel="stylesheet" href="/assets/css/agency.css" />-->
<link rel="stylesheet" href="/assets/css/style.css" />
<link rel="stylesheet" href="/assets/css/selectize.css" />
<link rel="stylesheet" href="/assets/css/jquery.steps.css" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />

<!-- recommended in https://jekyllrb.com/docs/posts/ -->
<meta charset="utf-8" />

<script src="/assets/js/jquery-1.12.4.js"></script>
<script type="text/javascript" src="/assets/js/bootstrap.js"></script>

<script>
var supportsES6 = function() {
try {
new Function("(a = 0) => a");
return true;
}
catch (err) {
return false;
}
}();

if (!supportsES6) {
alert('Some features on this site are not supported by your browser. We recommend updating your browser or using a different browser for the best possible experience.');
}
</script>

</head>


<body data-spy="scroll" data-target=".navbar2" data-offset="450">
<div class="TeachOSM Privacy Policy page">
<!-- <nav class="navbar">
<div class="nav-wrapper">
<a href="" class="brand-logo">TeachOSM</a>
<ul id="nav-mobile" class="right">
<li><a href="/blog">Triggering github pages rebuild, Blog</a></li>
<li><a href="/courses">Projects</a></li>
</ul>
</div>
</nav> -->

<nav class="navbar navbar-default navbar-fixed-top navbar-shrink">
<div class="container">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header page-scroll">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a href="/" id="logo-link">
<img class="logo" src="/assets/images/logo.png" />
<!--<span id="beta-text">beta</span>-->
</a>



</div>

<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<!--<ul class="nav navbar-nav navbar-right">-->
<ul class="nav navbar-nav navbar-right">
<li class="hidden">
<a href="#page-top"></a>
</li>
<li>
<a href="https://osmgeoweek.org/" class="fl logo-text">
<span class="text-green">#</span><span class="text-white">osm</span><span class="text-green">geo</span><span class="text-white">week</span>
</a>
</li>
<li>
<a class="page-scroll" href="/getting-started">Start</a>
</li>
<li>
<a class="page-scroll" href="/blog">Blog</a>
</li>
<li>
<a class="page-scroll" href="/projects">Projects</a>
</li>
<li>
<a class="page-scroll" href="/resources">Resources</a>
</li>
<li>
<a href="https://openstreetmap.app.neoncrm.com/forms/teachosm">Donate</a>
</li>
</ul>
</div>
</div>
</nav>

<script>
$(function(){

if (window.location.pathname == '/' || window.location.pathname == '/teachosm/') {
console.log('homepage');
console.log(window.location.href);
} else {

$('a.page-scroll').each(function() {
//console.log(location.search)
if ($(this).prop('href') == window.location.href) {
$(this).addClass('current');
}
if ($(this).prop('href')+'/' == window.location.href) {
$(this).addClass('current');
}
});
}

});
</script>

<div class="wrapper">
<section class="panel-border-style">
<div class="TeachOSM Privacy Policy content">
<div style="padding-top:50px;"></div>

<div class="container-fluid" style="padding:50px;">

<h1 id="privacy-policy">Privacy Policy</h1>
I"�<<h1 id="privacy-policy">Privacy Policy</h1>

<p>TeachOSM is committed to protecting the privacy of those who visit our websites and use our services. This Privacy Policy describes (1) the types of information we collect about you (sometimes called “personal information”) when you access or use our website, applications, products, services, and tools (collectively, the “Services”); (2) how we use the information we collect from you; and (3) your choices regarding how we use or share that information.</p>

Expand Down Expand Up @@ -284,56 +144,4 @@ <h2 id="modifications-to-this-privacy-policy">Modifications to This Privacy Poli
<h2 id="how-to-contact-us">How to Contact Us</h2>

<p>If you have a question about this Privacy Policy, please contact us at <a href="mailto:[email protected]">[email protected]</a>.</p>

</div>

</div>
</section>
</div>
</div>
<footer>
<div class="container">
<div class="row">
<div class="col-md-4">
<span class="copyright">Copyright &copy; TeachOSM 2023</span>
</div>
<div class="col-md-4">
<ul class="list-inline social-buttons">
<li>
<a href="http://twitter.com/teachosm">
<i class="fab fa-twitter"></i>
</a>
</li>
<li>
<a href="https://www.facebook.com/TEACHOSM/">
<i class="fab fa-facebook"></i>
</a>
</li>
<li>
<a href="http://github.com/osmlab">
<i class="fab fa-github"></i>
</a>
</li>
</ul>
</div>
<div class="col-md-4">
<ul class="list-inline quicklinks">
<li><a href="/privacy-policy">Privacy Policy</a>
</li>
<li><a href="/terms-of-use">Terms of Use</a>
</li>
</ul>
</div>
</div>
</div>
</footer>

<!-- Plugin JavaScript -->
<script src="/assets/js/jquery.easing.min.js"></script>
<script src="/assets/js/classie.js"></script>
<script src="/assets/js/jqBootstrapValidation.js"></script>
<script type="text/javascript" src="/assets/js/agency.js"></script>


</body>
</html>
:ET
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
I"�<p>Congratulations! You just completed a successful mapathon and are excited for the possibilities for undertaking more mapping events. What then, should you do next? This document contains elements of an open mapping plan for Saint Lucia with a special focus on continuing technical proficiency and community development. This is envisioned as a six-month roadmap, but can easily be adjusted to suit the needs of the local community.</p>
:ET
Loading

0 comments on commit 13b604f

Please sign in to comment.