<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Off The Map: Urban Mapping Releases Mass Transit Data for 50+ Systems</title>
    <link>http://blog.urbanmapping.com/articles/2008/05/14/urban-mapping-releases-mass-transit-data-for-over-50-systems</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Urban Mapping Releases Mass Transit Data for 50+ Systems</title>
      <description>&lt;p&gt;Phew! After more than a year in development and two years deep in Umibot&amp;#8217;s RAM, today we unveil a grand plan: normalized mass transit data for (today) 53 public transportation systems in the US, Canada and UK. To get here we had to develop other pieces&amp;#8211;a data intake platform and a schema. Some more info on all of these:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Web-based Mass Transit Data Intake Platform (no acronym yet)&lt;/strong&gt; Umibot believes the greatest cost in data collection is identifying and purging the system of &lt;a href="http://en.wikipedia.org/wiki/Garbage_In%2C_Garbage_Out"&gt;dirty data&lt;/a&gt;. By auto-validating data at point of input, we&amp;#8217;re able to significantly reduce this cost. UMI&amp;#8217;s proprietary web-based platform is flexible and captures the vast collection of spatial and attribute data we manage. This includes things like routes, station footprints, exits (you can&amp;#8217;t generally exit at a &lt;a href="http://maps.google.com/maps?f=q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=west+4th+street+nyc&amp;amp;sll=37.0625,-95.677068&amp;amp;sspn=42.987658,96.328125&amp;amp;ie=UTF8&amp;amp;ll=40.731682,-74.000484&amp;amp;spn=0.00252,0.005879&amp;amp;z=18"&gt;&amp;#8216;station&amp;#8217;&lt;/a&gt;), hours of operation, handicap accessibility, elevator location, amenities (retail, bathroom, telephone, etc&amp;#8230;) and a great deal more. We then associate this attribute data with the &amp;#8216;spine&amp;#8217; of spatial data and then compute a graph network, making the data &amp;#8216;routing ready&amp;#8217; across a variety of platforms.&lt;/p&gt;

&lt;p&gt;Transit agencies can take advantage of this platform by using UMI&amp;#8217;s infrastructure as a platform to inventory their own data. It&amp;#8217;s a well-known fact that transit agencies face bureaucratic, technical and legal challenges to releasing data, and this platform is one &lt;em&gt;more&lt;/em&gt; reason for transit agencies to partner with industry to increase data distribution and support increased ridership by driving awareness.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Normalized schema&lt;/strong&gt;
Before we began data collection, a uniform schema that recognizes transit nuances and complexities needed to be developed. For example, scheduling for the London Tube operates on a &lt;a href="http://www.apta.com/research/info/online/glossary.cfm"&gt;headway&lt;/a&gt;, meaning &lt;a href="http://www.tfl.gov.uk/gettingaround/1125.aspx"&gt;trains depart&lt;/a&gt; every Xish minutes. New York&amp;#8217;s MTA operates on a tabular schedule, with &lt;a href="http://www.mta.info/nyct/service/schemain.htm"&gt;scheduled departure times&lt;/a&gt;. Sounds like a detail, and it that&amp;#8217;s exactly what it is&amp;#8211;multiply this nuance 100 times and there&amp;#8217;s a great deal of data definition that matters. What we&amp;#8217;ve developed is internal to UMI and offers tremendous flexibility to add new mode types (ferry, &lt;a href="http://www.panoramio.com/photo/3947711"&gt;funicular&lt;/a&gt;, etc). It has nothing to do with the output customers receive, and we&amp;#8217;ll have more news about that soon.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Coverage&lt;/strong&gt; The map below reflects current US coverage. Across the &lt;a href="http://urbanmapping.com/urbanware/mass-transit/coverage.html"&gt;53 transit systems&lt;/a&gt;, UMI has defined over 14,000 individual stations and over 100,000 data attributes. Stay tuned for increased coverage, attributes, service delivery and partnerships! &lt;/p&gt;

&lt;p&gt;&lt;img src="/files/transit-coverage-500w.png" alt="transit coverage"/&gt;&lt;/p&gt;

&lt;p&gt;And some fun transit statistics for current coverage:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;22% of transit stations have bathrooms (they may not be operable/accessible, but they exist)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;35% of transit stations have dedicated parking&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;FYI: &lt;a href="http://www.marketwire.com/mw/release.do?id=856195"&gt;Wire release&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 14 May 2008 11:21:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:02af85cc-e9a7-4e75-abd1-c9989e56c455</guid>
      <author>umibot</author>
      <link>http://blog.urbanmapping.com/articles/2008/05/14/urban-mapping-releases-mass-transit-data-for-over-50-systems</link>
      <category>local search</category>
      <category>press-type stuff</category>
      <category>urban mapping</category>
      <category>geotargeting</category>
      <category>neighborhood boundary</category>
      <category>umi</category>
      <category>geolocation</category>
      <category>mass transit</category>
      <category>transit data</category>
      <category>public transportation data</category>
      <category>google transit</category>
      <enclosure type="image/png" length="21337" url="http://blog.urbanmapping.com/files/transit-coverage-500w.png"/>
    </item>
  </channel>
</rss>
