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.

SpiderOSM is frequently used to correlate jurisdictional centerline data with OpenStreetMaps data. However it is generally useful for matching path networks.

Uses include:

• Conflation
• Data Checking
• Data Import
• Data Carry Forward
• Version Diffs

Status

Now running on all major platforms: Windows, Linux, Mac-OSX. BETA software. Targeted for users with python programming skills.

Download and Installation

Spiderosm is registered with the Python Package Index . The easiest way to install (or upgrade to the current version) on your system is with the commandline tool pip:

% pip install --upgrade spiderosm

Documentation

• README

Bug Reports, Feature Requests, Questions, Comments...

Issues

Mailing Lists

• spiderosm - Discussion.
• spiderosm-announce - Low volume announcements

Github Source Repository

spiderosm github repository

Plans

• Version 1.0
• Focus on Street Name Project (as initial application.)

Links

• Street Name Project, ongoing project using spiderosm to find street name errors.
• Berkeley Mismatched Names, interactive map of unresolved street name conflicts in Berkeley California Area.
• San Jose Mismatched Names, interactive map of unresolved street name conflicts in San Jose California Area.
• Portland Mismatched Names, interactive map of unresolved street name conflicts in Portland Oregon Area.
• RLIS Localid Version Diff, interactive map illustrating the use of spiderosm to track key changes between dataset versions, facilitating automatic third party data carry forward.
• Leveraging OpenStreetMap for Pedestrian Experience Modeling and Analysis - Katie Urey, Michael Arnold - State of the Map US, April 2014, Washington DC, presentation on initial application for spiderosm ('the matcher'.)

Developer

Michael Arnold.