Routes routes

output/assets/js/tag_cloud_data.json

@@ -1 +1 @@
-{"programming": [1, "/categories/programming.html"], "philippine-transit-app": [1, "/categories/philippine-transit-app.html"]}
+{"programming": [2, "/categories/programming.html"], "philippine-transit-app": [2, "/categories/philippine-transit-app.html"]}

output/categories/philippine-transit-app.html

@@ -37,7 +37,8 @@
         <div class="postbox">
         <h1>Posts about philippine-transit-app</h1>
             <a href="philippine-transit-app.xml">RSS</a>
-        <br><ul class="unstyled"><li><a href="../posts/philippine-transit-app-challenge.html">[2013-07-07 00:17] Philippine Transit App Challenge</a>
+        <br><ul class="unstyled"><li><a href="../posts/jeepney-and-bus-routes.html">[2013-07-07 10:32] Jeepney and Bus Routes</a>
+            </li><li><a href="../posts/philippine-transit-app-challenge.html">[2013-07-07 00:17] Philippine Transit App Challenge</a>
         </li></ul></div>
         <!--End of body content-->
 

output/categories/philippine-transit-app.xml

@@ -1,5 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer (philippine-transit-app)</title><link>http://thatsmydoing.github.io</link><description></description><lastBuildDate>Sun, 07 Jul 2013 01:23:44 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Philippine Transit App Challenge</title><link>http://thatsmydoing.github.io/posts/philippine-transit-app-challenge.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Last week, the DOTC launched the &lt;a href="http://philippine-transit.hackathome.com"&gt;Philippine Transit App Challenge&lt;/a&gt;. It's a competition to build something great using the newly available 1) jeepney/bus/rail routes and 2) traffic incident data in Metro Manila and Cebu.&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer (philippine-transit-app)</title><link>http://thatsmydoing.github.io</link><description></description><lastBuildDate>Sun, 07 Jul 2013 11:50:44 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Jeepney and Bus Routes</title><link>http://thatsmydoing.github.io/posts/jeepney-and-bus-routes.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;In the &lt;a href="/posts/philippine-transit-app-challenge.html"&gt;last post&lt;/a&gt;, I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the &lt;a href="https://developers.google.com/transit/gtfs/"&gt;GTFS format&lt;/a&gt;, which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.&lt;/p&gt;
+&lt;p&gt;In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.&lt;/p&gt;
+&lt;p&gt;One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.&lt;/p&gt;
+&lt;p&gt;From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.&lt;/p&gt;
+&lt;p&gt;&lt;img alt="sample route" src="/galleries/transit/gtfs_preview.jpg"&gt;&lt;/p&gt;
+&lt;p&gt;The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.&lt;/p&gt;
+&lt;p&gt;There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for &lt;a href="https://github.com/harrisony/gtfs_SQL_importer"&gt;GTFS SQL importer&lt;/a&gt;. There were also problems with matching the shape data with the stops when I tried it with &lt;a href="http://onebusaway.org"&gt;OneBusAway&lt;/a&gt;. They could probably be &lt;a href="https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching"&gt;fixed&lt;/a&gt; but that's for another day.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description><guid>http://thatsmydoing.github.io/posts/jeepney-and-bus-routes.html</guid><pubDate>Sun, 07 Jul 2013 10:32:36 GMT</pubDate></item><item><title>Philippine Transit App Challenge</title><link>http://thatsmydoing.github.io/posts/philippine-transit-app-challenge.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Last week, the DOTC launched the &lt;a href="http://philippine-transit.hackathome.com"&gt;Philippine Transit App Challenge&lt;/a&gt;. It's a competition to build something great using the newly available 1) jeepney/bus/rail routes and 2) traffic incident data in Metro Manila and Cebu.&lt;/p&gt;
 &lt;p&gt;I'm actually quite excited about this as it's not everyday our government does wonderful things. Many people have been waiting for this kind of data to be available. Before, the only way to figure out which jeeps to ride to get from A to B is by asking other people. The website of the LTFRB used to just have a list of jeepney routes, but nothing else, no maps or list of stops.&lt;/p&gt;
 &lt;p&gt;During the launch, they also presented how CITOM (the Cebu MMDA) is pilot-testing a &lt;a href="http://cebutraffic.org/"&gt;traffic tracking system&lt;/a&gt;. What they did was supply Android phones to taxi drivers. The phones send GPS data which can then be aggregated to see what the average speeds along streets are. This also benefits the taxi company as it provides easy tracking of their taxis compared to their old telephone/radio with pen-and-paper process.&lt;/p&gt;
 &lt;p&gt;The &lt;a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/"&gt;route data&lt;/a&gt; are already available, as well as the &lt;a href="http://philippine-transit.hackathome.com/dataset-citom-traffic-alert-platform/"&gt;Cebu&lt;/a&gt; and &lt;a href="http://philippine-transit.hackathome.com/dataset-mmda-traffic-alert-platform/"&gt;Metro Manila&lt;/a&gt; incident data. You do have to register to access them though. Right now, they're just one-off dumps of the data but the various agencies have promised to provide consistently updated data. This will be provided via ASTI later in the year.&lt;/p&gt;

output/categories/programming.html

@@ -37,7 +37,8 @@
         <div class="postbox">
         <h1>Posts about programming</h1>
             <a href="programming.xml">RSS</a>
-        <br><ul class="unstyled"><li><a href="../posts/philippine-transit-app-challenge.html">[2013-07-07 00:17] Philippine Transit App Challenge</a>
+        <br><ul class="unstyled"><li><a href="../posts/jeepney-and-bus-routes.html">[2013-07-07 10:32] Jeepney and Bus Routes</a>
+            </li><li><a href="../posts/philippine-transit-app-challenge.html">[2013-07-07 00:17] Philippine Transit App Challenge</a>
         </li></ul></div>
         <!--End of body content-->
 

output/categories/programming.xml

@@ -1,5 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer (programming)</title><link>http://thatsmydoing.github.io</link><description></description><lastBuildDate>Sun, 07 Jul 2013 01:23:44 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Philippine Transit App Challenge</title><link>http://thatsmydoing.github.io/posts/philippine-transit-app-challenge.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Last week, the DOTC launched the &lt;a href="http://philippine-transit.hackathome.com"&gt;Philippine Transit App Challenge&lt;/a&gt;. It's a competition to build something great using the newly available 1) jeepney/bus/rail routes and 2) traffic incident data in Metro Manila and Cebu.&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer (programming)</title><link>http://thatsmydoing.github.io</link><description></description><lastBuildDate>Sun, 07 Jul 2013 11:50:44 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Jeepney and Bus Routes</title><link>http://thatsmydoing.github.io/posts/jeepney-and-bus-routes.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;In the &lt;a href="/posts/philippine-transit-app-challenge.html"&gt;last post&lt;/a&gt;, I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the &lt;a href="https://developers.google.com/transit/gtfs/"&gt;GTFS format&lt;/a&gt;, which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.&lt;/p&gt;
+&lt;p&gt;In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.&lt;/p&gt;
+&lt;p&gt;One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.&lt;/p&gt;
+&lt;p&gt;From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.&lt;/p&gt;
+&lt;p&gt;&lt;img alt="sample route" src="/galleries/transit/gtfs_preview.jpg"&gt;&lt;/p&gt;
+&lt;p&gt;The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.&lt;/p&gt;
+&lt;p&gt;There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for &lt;a href="https://github.com/harrisony/gtfs_SQL_importer"&gt;GTFS SQL importer&lt;/a&gt;. There were also problems with matching the shape data with the stops when I tried it with &lt;a href="http://onebusaway.org"&gt;OneBusAway&lt;/a&gt;. They could probably be &lt;a href="https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching"&gt;fixed&lt;/a&gt; but that's for another day.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description><guid>http://thatsmydoing.github.io/posts/jeepney-and-bus-routes.html</guid><pubDate>Sun, 07 Jul 2013 10:32:36 GMT</pubDate></item><item><title>Philippine Transit App Challenge</title><link>http://thatsmydoing.github.io/posts/philippine-transit-app-challenge.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Last week, the DOTC launched the &lt;a href="http://philippine-transit.hackathome.com"&gt;Philippine Transit App Challenge&lt;/a&gt;. It's a competition to build something great using the newly available 1) jeepney/bus/rail routes and 2) traffic incident data in Metro Manila and Cebu.&lt;/p&gt;
 &lt;p&gt;I'm actually quite excited about this as it's not everyday our government does wonderful things. Many people have been waiting for this kind of data to be available. Before, the only way to figure out which jeeps to ride to get from A to B is by asking other people. The website of the LTFRB used to just have a list of jeepney routes, but nothing else, no maps or list of stops.&lt;/p&gt;
 &lt;p&gt;During the launch, they also presented how CITOM (the Cebu MMDA) is pilot-testing a &lt;a href="http://cebutraffic.org/"&gt;traffic tracking system&lt;/a&gt;. What they did was supply Android phones to taxi drivers. The phones send GPS data which can then be aggregated to see what the average speeds along streets are. This also benefits the taxi company as it provides easy tracking of their taxis compared to their old telephone/radio with pen-and-paper process.&lt;/p&gt;
 &lt;p&gt;The &lt;a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/"&gt;route data&lt;/a&gt; are already available, as well as the &lt;a href="http://philippine-transit.hackathome.com/dataset-citom-traffic-alert-platform/"&gt;Cebu&lt;/a&gt; and &lt;a href="http://philippine-transit.hackathome.com/dataset-mmda-traffic-alert-platform/"&gt;Metro Manila&lt;/a&gt; incident data. You do have to register to access them though. Right now, they're just one-off dumps of the data but the various agencies have promised to provide consistently updated data. This will be provided via ASTI later in the year.&lt;/p&gt;

output/galleries/transit/index.html

@@ -0,0 +1,50 @@
+<!DOCTYPE html><html lang="en"><head><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta charset="utf-8"><meta name="description" content=""><meta name="author" content="Thomas Dy"><title>transit | Pleasant Programmer</title><link href="../../assets/css/bootstrap.min.css" rel="stylesheet" type="text/css"><link href="../../assets/css/bootstrap-responsive.min.css" rel="stylesheet" type="text/css"><link href="../../assets/css/rst.css" rel="stylesheet" type="text/css"><link href="../../assets/css/code.css" rel="stylesheet" type="text/css"><link href="../../assets/css/colorbox.css" rel="stylesheet" type="text/css"><link href="../../assets/css/theme.css" rel="stylesheet" type="text/css"><link href="../../assets/css/custom.css" rel="stylesheet" type="text/css"><!--[if lt IE 9]>
+      <script src="http://html5shim.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script>
+    <![endif]--><link rel="alternate" type="application/rss+xml" title="RSS" href="../../rss.xml"></head><body>
+<!-- Menubar -->
+<div class="navbar navbar-fixed-top">
+    <div class="navbar-inner">
+        <div class="container">
+
+        <!-- .btn-navbar is used as the toggle for collapsed navbar content -->
+        <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+        </a>
+
+            <a class="brand" href="../../">
+            Pleasant Programmer
+            </a>
+            <!-- Everything you want hidden at 940px or less, place within here -->
+            <div class="nav-collapse collapse">
+                <ul class="nav"><li><a href="../../archive.html">Archives</a>
+            </li><li><a href="../../categories/index.html">Tags</a>
+            </li><li><a href="../../rss.xml">RSS</a>
+
+                </li></ul><ul class="nav pull-right"></ul></div>
+        </div>
+    </div>
+</div>
+<!-- End of Menubar -->
+<div class="container-fluid" id="container-fluid">
+    <!--Body content-->
+    <div class="row-fluid">
+    <div class="span2"></div>
+    <div class="span8">
+    
+    <ul class="breadcrumb"><li><a href="../">/ galleries</a>
+            </li><li><a href="#">/ transit</a>
+    </li></ul><ul></ul><ul class="thumbnails"><li><a href="gtfs_preview.jpg" class="thumbnail image-reference" id="gtfs_preview" alt="gtfs_preview" title="Gtfs preview">
+                <img src="gtfs_preview.thumbnail.jpg"></a>
+    </li></ul></div>
+    </div>
+    <!--End of body content-->
+</div>
+<div class="footerbox">
+    <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/80x15.png"></a> © 2013 Thomas Dy - Powered by <a href="http://nikola.ralsina.com.ar">Nikola</a>
+</div>
+
+
+
+            <script src="../../assets/js/jquery-1.7.2.min.js" type="text/javascript"></script><script src="../../assets/js/bootstrap.min.js" type="text/javascript"></script><script src="../../assets/js/jquery.colorbox-min.js" type="text/javascript"></script><script type="text/javascript">jQuery("a.image-reference").colorbox({rel:"gal",maxWidth:"80%",maxHeight:"80%",scalePhotos:true});</script></body></html>

output/index.html

@@ -33,6 +33,21 @@
     <div class="span2"></div>
     <div class="span8">
     
+        <div class="postbox">
+        <h1><a href="posts/jeepney-and-bus-routes.html">Jeepney and Bus Routes</a>
+        <small>  
+             Posted: <time class="published" datetime="2013-07-07T10:32:36">2013-07-07 10:32</time></small></h1>
+        <hr><p>In the <a href="posts/philippine-transit-app-challenge.html">last post</a>, I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the <a href="https://developers.google.com/transit/gtfs/">GTFS format</a>, which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.</p>
+<p>In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.</p>
+<p>One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.</p>
+<p>From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.</p>
+<p><img alt="sample route" src="galleries/transit/gtfs_preview.jpg"></p>
+<p>The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.</p>
+<p>There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for <a href="https://github.com/harrisony/gtfs_SQL_importer">GTFS SQL importer</a>. There were also problems with matching the shape data with the stops when I tried it with <a href="http://onebusaway.org">OneBusAway</a>. They could probably be <a href="https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching">fixed</a> but that's for another day.</p>
+            
+    <p>
+
+        </p></div>
         <div class="postbox">
         <h1><a href="posts/philippine-transit-app-challenge.html">Philippine Transit App Challenge</a>
         <small>  

output/posts/jeepney-and-bus-routes.html

@@ -0,0 +1,77 @@
+<!DOCTYPE html><html lang="en"><head><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta charset="utf-8"><meta name="description" content=""><meta name="author" content="Thomas Dy"><title>Jeepney and Bus Routes | Pleasant Programmer</title><link href="../assets/css/bootstrap.min.css" rel="stylesheet" type="text/css"><link href="../assets/css/bootstrap-responsive.min.css" rel="stylesheet" type="text/css"><link href="../assets/css/rst.css" rel="stylesheet" type="text/css"><link href="../assets/css/code.css" rel="stylesheet" type="text/css"><link href="../assets/css/colorbox.css" rel="stylesheet" type="text/css"><link href="../assets/css/theme.css" rel="stylesheet" type="text/css"><link href="../assets/css/custom.css" rel="stylesheet" type="text/css"><!--[if lt IE 9]>
+      <script src="http://html5shim.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script>
+    <![endif]--><link rel="alternate" type="application/rss+xml" title="RSS" href="../rss.xml"></head><body>
+<!-- Menubar -->
+<div class="navbar navbar-fixed-top">
+    <div class="navbar-inner">
+        <div class="container">
+
+        <!-- .btn-navbar is used as the toggle for collapsed navbar content -->
+        <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+        </a>
+
+            <a class="brand" href="../">
+            Pleasant Programmer
+            </a>
+            <!-- Everything you want hidden at 940px or less, place within here -->
+            <div class="nav-collapse collapse">
+                <ul class="nav"><li><a href="../archive.html">Archives</a>
+            </li><li><a href="../categories/index.html">Tags</a>
+            </li><li><a href="../rss.xml">RSS</a>
+
+                </li></ul><ul class="nav pull-right"><li>
+    <a href="jeepney-and-bus-routes.md" id="sourcelink">Source</a>
+    </li>
+
+                </ul></div>
+        </div>
+    </div>
+</div>
+<!-- End of Menubar -->
+<div class="container-fluid" id="container-fluid">
+    <!--Body content-->
+    <div class="row-fluid">
+    <div class="span2"></div>
+    <div class="span8">
+    
+    <div class="postbox">
+    
+    <h1>Jeepney and Bus Routes</h1>
+
+    <hr><small>
+        Posted: <time class="published" datetime="2013-07-07T10:32:36">2013-07-07 10:32</time>
+        
+
+        
+          |  More posts about
+            <a class="tag" href="../categories/philippine-transit-app.html"><span class="badge badge-info">philippine-transit-app</span></a>
+            <a class="tag" href="../categories/programming.html"><span class="badge badge-info">programming</span></a>
+
+    </small>
+    <hr><p>In the <a href="philippine-transit-app-challenge.html">last post</a>, I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the <a href="https://developers.google.com/transit/gtfs/">GTFS format</a>, which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.</p>
+<p>In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.</p>
+<p>One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.</p>
+<p>From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.</p>
+<p><img alt="sample route" src="../galleries/transit/gtfs_preview.jpg"></p>
+<p>The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.</p>
+<p>There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for <a href="https://github.com/harrisony/gtfs_SQL_importer">GTFS SQL importer</a>. There were also problems with matching the shape data with the stops when I tried it with <a href="http://onebusaway.org">OneBusAway</a>. They could probably be <a href="https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching">fixed</a> but that's for another day.</p>
+    
+    <ul class="pager"><li class="previous">
+            <a href="philippine-transit-app-challenge.html">← Previous post</a>
+        </li>
+    </ul></div>
+
+    </div>
+    </div>
+    <!--End of body content-->
+</div>
+<div class="footerbox">
+    <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/80x15.png"></a> © 2013 Thomas Dy - Powered by <a href="http://nikola.ralsina.com.ar">Nikola</a>
+</div>
+
+
+
+            <script src="../assets/js/jquery-1.7.2.min.js" type="text/javascript"></script><script src="../assets/js/bootstrap.min.js" type="text/javascript"></script><script src="../assets/js/jquery.colorbox-min.js" type="text/javascript"></script><script type="text/javascript">jQuery("a.image-reference").colorbox({rel:"gal",maxWidth:"80%",maxHeight:"80%",scalePhotos:true});</script></body></html>

output/posts/jeepney-and-bus-routes.md

@@ -0,0 +1,22 @@
+<!-- 
+.. link: 
+.. description: 
+.. tags: philippine-transit-app, programming
+.. date: 2013/07/07 10:32:36
+.. title: Jeepney and Bus Routes
+.. slug: jeepney-and-bus-routes
+-->
+
+In the [last post](philippine-transit-app-challenge.html), I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the [GTFS format](https://developers.google.com/transit/gtfs/), which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.
+
+In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.
+
+One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.
+
+From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.
+
+![sample route](../galleries/transit/gtfs_preview.jpg)
+
+The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.
+
+There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for [GTFS SQL importer](https://github.com/harrisony/gtfs_SQL_importer). There were also problems with matching the shape data with the stops when I tried it with [OneBusAway](http://onebusaway.org). They could probably be [fixed](https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching) but that's for another day.

output/posts/philippine-transit-app-challenge.html

@@ -57,7 +57,10 @@
 <p>The <a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/">route data</a> are already available, as well as the <a href="http://philippine-transit.hackathome.com/dataset-citom-traffic-alert-platform/">Cebu</a> and <a href="http://philippine-transit.hackathome.com/dataset-mmda-traffic-alert-platform/">Metro Manila</a> incident data. You do have to register to access them though. Right now, they're just one-off dumps of the data but the various agencies have promised to provide consistently updated data. This will be provided via ASTI later in the year.</p>
 <p>I've just started looking at the route data and playing around with it. The quality could be better, but I'm glad we at least have something to work with.</p>
     
-    <ul class="pager"></ul></div>
+    <ul class="pager"><li class="next">
+            <a href="jeepney-and-bus-routes.html">Next post →</a>
+        </li>
+    </ul></div>
 
     </div>
     </div>

output/rss.xml

@@ -1,5 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer</title><link>http://thatsmydoing.github.io</link><description></description><lastBuildDate>Sun, 07 Jul 2013 01:23:44 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Philippine Transit App Challenge</title><link>http://thatsmydoing.github.io/posts/philippine-transit-app-challenge.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Last week, the DOTC launched the &lt;a href="http://philippine-transit.hackathome.com"&gt;Philippine Transit App Challenge&lt;/a&gt;. It's a competition to build something great using the newly available 1) jeepney/bus/rail routes and 2) traffic incident data in Metro Manila and Cebu.&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer</title><link>http://thatsmydoing.github.io</link><description></description><lastBuildDate>Sun, 07 Jul 2013 11:50:44 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Jeepney and Bus Routes</title><link>http://thatsmydoing.github.io/posts/jeepney-and-bus-routes.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;In the &lt;a href="/posts/philippine-transit-app-challenge.html"&gt;last post&lt;/a&gt;, I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the &lt;a href="https://developers.google.com/transit/gtfs/"&gt;GTFS format&lt;/a&gt;, which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.&lt;/p&gt;
+&lt;p&gt;In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.&lt;/p&gt;
+&lt;p&gt;One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.&lt;/p&gt;
+&lt;p&gt;From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.&lt;/p&gt;
+&lt;p&gt;&lt;img alt="sample route" src="/galleries/transit/gtfs_preview.jpg"&gt;&lt;/p&gt;
+&lt;p&gt;The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.&lt;/p&gt;
+&lt;p&gt;There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for &lt;a href="https://github.com/harrisony/gtfs_SQL_importer"&gt;GTFS SQL importer&lt;/a&gt;. There were also problems with matching the shape data with the stops when I tried it with &lt;a href="http://onebusaway.org"&gt;OneBusAway&lt;/a&gt;. They could probably be &lt;a href="https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching"&gt;fixed&lt;/a&gt; but that's for another day.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description><guid>http://thatsmydoing.github.io/posts/jeepney-and-bus-routes.html</guid><pubDate>Sun, 07 Jul 2013 10:32:36 GMT</pubDate></item><item><title>Philippine Transit App Challenge</title><link>http://thatsmydoing.github.io/posts/philippine-transit-app-challenge.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Last week, the DOTC launched the &lt;a href="http://philippine-transit.hackathome.com"&gt;Philippine Transit App Challenge&lt;/a&gt;. It's a competition to build something great using the newly available 1) jeepney/bus/rail routes and 2) traffic incident data in Metro Manila and Cebu.&lt;/p&gt;
 &lt;p&gt;I'm actually quite excited about this as it's not everyday our government does wonderful things. Many people have been waiting for this kind of data to be available. Before, the only way to figure out which jeeps to ride to get from A to B is by asking other people. The website of the LTFRB used to just have a list of jeepney routes, but nothing else, no maps or list of stops.&lt;/p&gt;
 &lt;p&gt;During the launch, they also presented how CITOM (the Cebu MMDA) is pilot-testing a &lt;a href="http://cebutraffic.org/"&gt;traffic tracking system&lt;/a&gt;. What they did was supply Android phones to taxi drivers. The phones send GPS data which can then be aggregated to see what the average speeds along streets are. This also benefits the taxi company as it provides easy tracking of their taxis compared to their old telephone/radio with pen-and-paper process.&lt;/p&gt;
 &lt;p&gt;The &lt;a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/"&gt;route data&lt;/a&gt; are already available, as well as the &lt;a href="http://philippine-transit.hackathome.com/dataset-citom-traffic-alert-platform/"&gt;Cebu&lt;/a&gt; and &lt;a href="http://philippine-transit.hackathome.com/dataset-mmda-traffic-alert-platform/"&gt;Metro Manila&lt;/a&gt; incident data. You do have to register to access them though. Right now, they're just one-off dumps of the data but the various agencies have promised to provide consistently updated data. This will be provided via ASTI later in the year.&lt;/p&gt;

posts/jeepney-and-bus-routes.md

@@ -0,0 +1,22 @@
+<!-- 
+.. link: 
+.. description: 
+.. tags: philippine-transit-app, programming
+.. date: 2013/07/07 10:32:36
+.. title: Jeepney and Bus Routes
+.. slug: jeepney-and-bus-routes
+-->
+
+In the [last post](philippine-transit-app-challenge.html), I talked about how we now have data about jeepney and bus routes in the Philippines. The data is actually in the [GTFS format](https://developers.google.com/transit/gtfs/), which is the format the Google Maps consumes transit data. Apparently, the government will be submitting the GTFS data later this year. Transit directions for Metro Manila in Google Maps would be wonderful. That said, it definitely raises the bar for the app challenge people.
+
+In the last post, I mentioned the quality of the data isn't quite good. Even before seeing the data, I was already a bit unsure of it. The key problem is how you model the routes. The GTFS format was inherently designed for more well developed and organized transit agencies which isn't exactly what we have in the Philippines now.
+
+One potential problem is the nature of the jeeps and buses. GTFS routes are a collection of trips which are a sequence of stops. However, we don't have jeepney stops, and even if we did they still just stop anywhere. There are also times where jeeps will take a shortcut if no passengers need to get dropped off along their normal route.
+
+From what I've seen of the data, they handled the first problem well enough. Stops are defined as where people typically get on the jeep or bus. This is good, but they didn't define a shape for the routes. There is no information as to which exact roads they pass through. All we have to go by are the stops to show the route on a map.
+
+![sample route](../galleries/transit/gtfs_preview.jpg)
+
+The problem isn't that bad though. The agencies could still add the shapes later on. Or maybe an app challenge participant could make an app around fixing the routes via crowd-sourcing or similar. The shape itself isn't that important for a rudimentary directions app, but if we want better apps, we will need better data.
+
+There were also some minor issues with the data itself. Some of the files had extra columns. This normally isn't an issue, but it caused problems for [GTFS SQL importer](https://github.com/harrisony/gtfs_SQL_importer). There were also problems with matching the shape data with the stops when I tried it with [OneBusAway](http://onebusaway.org). They could probably be [fixed](https://github.com/OneBusAway/onebusaway-application-modules/wiki/Stop-to-Shape-Matching) but that's for another day.