Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  <div class="vevent h-event"> <h1 class="summary p-name">OSGeo-PDX monthly meeting - SpiderOSM (spiderosm.org)</h1> <div class='date'><time class="dtstart dt-start" title="2015-04-15T18:00:00" datetime="2015-04-15T18:00:00">Wednesday, April 15, 2015 from 6</time>–<time class="dtend dt-end" title="2015-04-15T20:30:00" datetime="2015-04-15T20:30:00">8:30pm</time></div> <div class="location vcard p-location h-card"> <a class="url" href='http://calagator.org/venues/202394921'><span class='fn org p-name'>Portland State University Cramer Hall - 4th floor</span></a> <div class="adr p-adr h-adr"> </div> </div> <div class="description p-description"> <p>Monthly meeting of the open source GIS group PDX-OSGeo.</p> <p>Discussion of all things spatial and open source. Tonight's guest is Katie Urey who will speak to us about <a href="http://www.spiderosm.org">SpiderOSM</a>. Street conflation is a long time difficult problem and this is a project that looks very useful. The project gives Portland lots of attention as well.</p> <p>SpiderOSM is an open source python package for matching segments in one path network, e.g., streets and trails, to corresponding segments in another, based on geography and network connectivity. This allows joining together attribute data from separate sources. Importantly authoritative jurisdictional data can be correlated with the rich, crowd-sourced, user editable and extensible, Open Street Maps data. Multifactor match scoring, allows data to be joined only for high confidence matches.</p> <p>The initial version of the matcher was coded in early 2014 specifically to combine Open Street Map data with Portland Oregon area jurisdictional data (RLIS) to facilitate pedestrian infrastructure analysis and planning. Since then the code has been refactored into a generally useful python package that installs, via pip, and works on all three major platforms: Mac OSX, Linux and Windows. The code is stable and mature, with version 1.0 just around the corner.</p> <p>The developer, Michael Arnold, is now focusing on developing applications, and finding users and collaborators. On going projects where help would be very welcome include:</p> <ol> <li><p>The Portland Area Mismatched Name Survery (looking at name mismatches between OSM and RLIS identified by SpiderOSM.) Some folks at TriMet and others at PDOT have begun this project, but there is ALOT to be done!</p></li> <li><p>A QGIS Plug-in for spiderOSM. Ryan Peterson has recently begun this project, and would welcome help.</p></li> <li><p>Help getting the word out: publicizing spiderOSM online and at appropriate events. Alternately, advice and encouragement in this process. :)</p></li> </ol> <p>Another opportunity, not yet begun: looking for someone interested in developing an ESRI Plug-in for spiderOSM.</p> <p>Read more about <a href="http://spiderosm.org/">SpiderOSM</a></p> </div> <h3>Links</h3> <ul> <li><a class="url u-url" href="http://wiki.osgeo.org/wiki/PDX-OSGEO">Website</a></li> </ul> </div>