Fare data post

files/uploads/farematrix.rb

@@ -0,0 +1,67 @@
+#!/usr/bin/env ruby
+
+require 'csv'
+
+# current as of July 2013
+fare_types = {
+  "pub_aircon" => {
+    "fare" => 12.00,
+    "firstkm" => 5,
+    "perkm" => 2.2,
+    "limit" => 60
+  },
+  "pub_ordinary" => {
+    "fare" => 10.00,
+    "firstkm" => 5,
+    "perkm" => 1.85,
+    "limit" => 60
+  },
+  "puj" => {
+    "fare" => 8.00,
+    "firstkm" => 4,
+    "perkm" => 1.4,
+    "limit" => 50,
+    "override" => {
+      10 => { "discounted" => '13.25' },
+      12 => { "discounted" => '15.50' },
+      14 => { "discounted" => '17.75' },
+      18 => { "discounted" => '22.25' },
+      20 => { "discounted" => '24.50' },
+      22 => { "discounted" => '26.75' },
+      33 => { "discounted" => '38.75' },
+      35 => { "discounted" => '41.25' },
+      37 => { "discounted" => '43.50' },
+      39 => { "discounted" => '45.75' },
+      45 => { "discounted" => '52.50' },
+      47 => { "discounted" => '54.75' }
+    }
+  }
+}
+
+def round(original)
+  "%.2f" % ((original*4).round/4.0)
+end
+
+def if_override(original, type, dist, name)
+  value = original
+  value = type['override'][dist][name] if type['override'] && type['override'][dist] && type['override'][dist][name]
+  value
+end
+
+fare_types.each do |key, type|
+  CSV.open(key+'.csv', 'wb') do |csv|
+    csv << ['distance', 'regular', 'discounted']
+    type['limit'].times do |x|
+      dist = x+1
+      fare = type['fare']
+      if dist > type['firstkm']
+        fare += type['perkm'] * (dist - type['firstkm'])
+      end
+      discounted = round(fare*0.8)
+      fare = round(fare)
+      discounted = if_override(discounted, type, dist, 'discounted')
+      fare = if_override(fare, type, dist, 'fare')
+      csv << [dist, fare, discounted]
+    end
+  end
+end

files/uploads/pub_aircon.csv

@@ -0,0 +1,61 @@
+distance,regular,discounted
+1,12.00,9.50
+2,12.00,9.50
+3,12.00,9.50
+4,12.00,9.50
+5,12.00,9.50
+6,14.25,11.25
+7,16.50,13.00
+8,18.50,15.00
+9,20.75,16.75
+10,23.00,18.50
+11,25.25,20.25
+12,27.50,22.00
+13,29.50,23.75
+14,31.75,25.50
+15,34.00,27.25
+16,36.25,29.00
+17,38.50,30.75
+18,40.50,32.50
+19,42.75,34.25
+20,45.00,36.00
+21,47.25,37.75
+22,49.50,39.50
+23,51.50,41.25
+24,53.75,43.00
+25,56.00,44.75
+26,58.25,46.50
+27,60.50,48.25
+28,62.50,50.00
+29,64.75,51.75
+30,67.00,53.50
+31,69.25,55.25
+32,71.50,57.00
+33,73.50,59.00
+34,75.75,60.75
+35,78.00,62.50
+36,80.25,64.25
+37,82.50,66.00
+38,84.50,67.75
+39,86.75,69.50
+40,89.00,71.25
+41,91.25,73.00
+42,93.50,74.75
+43,95.50,76.50
+44,97.75,78.25
+45,100.00,80.00
+46,102.25,81.75
+47,104.50,83.50
+48,106.50,85.25
+49,108.75,87.00
+50,111.00,88.75
+51,113.25,90.50
+52,115.50,92.25
+53,117.50,94.00
+54,119.75,95.75
+55,122.00,97.50
+56,124.25,99.25
+57,126.50,101.00
+58,128.50,103.00
+59,130.75,104.75
+60,133.00,106.50

files/uploads/pub_ordinary.csv

@@ -0,0 +1,61 @@
+distance,regular,discounted
+1,10.00,8.00
+2,10.00,8.00
+3,10.00,8.00
+4,10.00,8.00
+5,10.00,8.00
+6,11.75,9.50
+7,13.75,11.00
+8,15.50,12.50
+9,17.50,14.00
+10,19.25,15.50
+11,21.00,17.00
+12,23.00,18.25
+13,24.75,19.75
+14,26.75,21.25
+15,28.50,22.75
+16,30.25,24.25
+17,32.25,25.75
+18,34.00,27.25
+19,36.00,28.75
+20,37.75,30.25
+21,39.50,31.75
+22,41.50,33.25
+23,43.25,34.75
+24,45.25,36.00
+25,47.00,37.50
+26,48.75,39.00
+27,50.75,40.50
+28,52.50,42.00
+29,54.50,43.50
+30,56.25,45.00
+31,58.00,46.50
+32,60.00,48.00
+33,61.75,49.50
+34,63.75,51.00
+35,65.50,52.50
+36,67.25,54.00
+37,69.25,55.25
+38,71.00,56.75
+39,73.00,58.25
+40,74.75,59.75
+41,76.50,61.25
+42,78.50,62.75
+43,80.25,64.25
+44,82.25,65.75
+45,84.00,67.25
+46,85.75,68.75
+47,87.75,70.25
+48,89.50,71.75
+49,91.50,73.00
+50,93.25,74.50
+51,95.00,76.00
+52,97.00,77.50
+53,98.75,79.00
+54,100.75,80.50
+55,102.50,82.00
+56,104.25,83.50
+57,106.25,85.00
+58,108.00,86.50
+59,110.00,88.00
+60,111.75,89.50

files/uploads/puj.csv

@@ -0,0 +1,51 @@
+distance,regular,discounted
+1,8.00,6.50
+2,8.00,6.50
+3,8.00,6.50
+4,8.00,6.50
+5,9.50,7.50
+6,10.75,8.75
+7,12.25,9.75
+8,13.50,11.00
+9,15.00,12.00
+10,16.50,13.25
+11,17.75,14.25
+12,19.25,15.50
+13,20.50,16.50
+14,22.00,17.75
+15,23.50,18.75
+16,24.75,19.75
+17,26.25,21.00
+18,27.50,22.25
+19,29.00,23.25
+20,30.50,24.50
+21,31.75,25.50
+22,33.25,26.75
+23,34.50,27.75
+24,36.00,28.75
+25,37.50,30.00
+26,38.75,31.00
+27,40.25,32.25
+28,41.50,33.25
+29,43.00,34.50
+30,44.50,35.50
+31,45.75,36.75
+32,47.25,37.75
+33,48.50,38.75
+34,50.00,40.00
+35,51.50,41.25
+36,52.75,42.25
+37,54.25,43.50
+38,55.50,44.50
+39,57.00,45.75
+40,58.50,46.75
+41,59.75,47.75
+42,61.25,49.00
+43,62.50,50.00
+44,64.00,51.25
+45,65.50,52.50
+46,66.75,53.50
+47,68.25,54.75
+48,69.50,55.75
+49,71.00,56.75
+50,72.50,58.00

output/2013/index.html

@@ -36,7 +36,8 @@
         <!--Body content-->
         <div class="postbox">
         <h1>Posts for year 2013</h1>
-        <ul class="unstyled"><li><a href="../posts/gtfs-editor.html">[2013-07-10 11:30] GTFS Editor</a>
+        <ul class="unstyled"><li><a href="../posts/fare-data.html">[2013-07-13 21:15] Fare Data</a>
+            </li><li><a href="../posts/gtfs-editor.html">[2013-07-10 11:30] GTFS Editor</a>
             </li><li><a href="../posts/open-trip-planner.html">[2013-07-09 23:16] Open Trip Planner</a>
             </li><li><a href="../posts/one-bus-or-maybe-jeep-away.html">[2013-07-09 01:53] One Bus (or maybe Jeep) Away</a>
             </li><li><a href="../posts/jeepney-and-bus-routes.html">[2013-07-07 10:32] Jeepney and Bus Routes</a>

output/assets/js/tag_cloud_data.json

@@ -1 +1 @@
-{"programming": [5, "/categories/programming.html"], "lets-debug": [1, "/categories/lets-debug.html"], "philippine-transit-app": [5, "/categories/philippine-transit-app.html"]}
+{"programming": [6, "/categories/programming.html"], "lets-debug": [1, "/categories/lets-debug.html"], "philippine-transit-app": [6, "/categories/philippine-transit-app.html"]}

output/categories/lets-debug.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer (lets-debug)</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Thu, 11 Jul 2013 00:31:36 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer (lets-debug)</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Sat, 13 Jul 2013 22:44:53 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; they really meant under development&lt;/p&gt;
 &lt;p&gt;When I first saw the source of GTFS Editor, I was ecstatic. They used &lt;a href="http://playframework.com/"&gt;Play framework&lt;/a&gt;!!! Not only that, they're targeting PostgreSQL as the main database. Those are our favorite tools for building webapps at By Implication. I was a bit sad though, when I saw it was on the 1.x release of Play though. I did have some experience with that release, but not as much compared to 2.x.&lt;/p&gt;
 &lt;p&gt;Getting it to actually run though, wasn't very pleasant. The initial setup was easy enough. Get &lt;a href="http://www.playframework.com/download"&gt;Play 1.2.5&lt;/a&gt;, install Postgres with PostGIS, clone the repo and create backing database in Postgres. Some minor additional steps you need are to create the PostGIS extension on the database. The schema is automatically generated and applied by Play so that should be all that's necessary. Wonderful. Then, run play, open a browser, go to &lt;a href="http://localhost:9000"&gt;http://localhost:9000&lt;/a&gt;, compilation error. Fantastic.&lt;/p&gt;

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/gtfs-editor.html">[2013-07-10 11:30] GTFS Editor</a>
+        <br><ul class="unstyled"><li><a href="../posts/fare-data.html">[2013-07-13 21:15] Fare Data</a>
+            </li><li><a href="../posts/gtfs-editor.html">[2013-07-10 11:30] GTFS Editor</a>
             </li><li><a href="../posts/open-trip-planner.html">[2013-07-09 23:16] Open Trip Planner</a>
             </li><li><a href="../posts/one-bus-or-maybe-jeep-away.html">[2013-07-09 01:53] One Bus (or maybe Jeep) Away</a>
             </li><li><a href="../posts/jeepney-and-bus-routes.html">[2013-07-07 10:32] Jeepney and Bus Routes</a>

output/categories/philippine-transit-app.xml

@@ -1,5 +1,44 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer (philippine-transit-app)</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Thu, 11 Jul 2013 00:31:36 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer (philippine-transit-app)</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Sat, 13 Jul 2013 22:44:53 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Fare Data</title><link>http://pleasantprogrammer.com/posts/fare-data.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;As part of the data released by the DOTC, we also have the &lt;a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/"&gt;fare matrix&lt;/a&gt; for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the &lt;a href="http://ltfrb.gov.ph/main/farerates"&gt;LTFRB website&lt;/a&gt;. Generally, the fare scheme is represented as "pay &lt;em&gt;X&lt;/em&gt; pesos for the first &lt;em&gt;Y&lt;/em&gt; kilometers, pay &lt;em&gt;Z&lt;/em&gt; for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,&lt;/p&gt;
+&lt;div class="code"&gt;&lt;pre&gt;&lt;span class="n"&gt;base_fare&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;distance&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;initial&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;per_km&lt;/span&gt;
+&lt;/pre&gt;&lt;/div&gt;
+
+
+&lt;p&gt;The relevant values for the three services are:&lt;/p&gt;
+&lt;table&gt;&lt;tr&gt;&lt;td&gt;type&lt;/td&gt;
+    &lt;td&gt;base_fare&lt;/td&gt;
+    &lt;td&gt;initial&lt;/td&gt;
+    &lt;td&gt;per_km&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;bus aircon&lt;/td&gt;
+    &lt;td&gt;12.00&lt;/td&gt;
+    &lt;td&gt;5 km&lt;/td&gt;
+    &lt;td&gt;2.20&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;bus ordinary&lt;/td&gt;
+    &lt;td&gt;10.00&lt;/td&gt;
+    &lt;td&gt;5 km&lt;/td&gt;
+    &lt;td&gt;1.85&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;jeep aircon&lt;/td&gt;
+    &lt;td&gt;8.00&lt;/td&gt;
+    &lt;td&gt;4 km&lt;/td&gt;
+    &lt;td&gt;1.40&lt;/td&gt;
+  &lt;/tr&gt;&lt;/table&gt;&lt;p&gt;It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,&lt;/p&gt;
+&lt;div class="code"&gt;&lt;pre&gt;&lt;span class="n"&gt;round&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;calculated_fare&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;4.0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="mf"&gt;4.0&lt;/span&gt;
+&lt;/pre&gt;&lt;/div&gt;
+
+
+&lt;p&gt;There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.&lt;/p&gt;
+&lt;p&gt;Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.&lt;/p&gt;
+&lt;p&gt;Here's a &lt;a href="/uploads/farematrix.rb"&gt;script&lt;/a&gt; that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the &lt;a href="/uploads/pub_aircon.csv"&gt;aircon bus&lt;/a&gt;, &lt;a href="/uploads/pub_ordinary.csv"&gt;ordinary bus&lt;/a&gt; and &lt;a href="/uploads/puj.csv"&gt;jeep&lt;/a&gt; fare matrices.&lt;/p&gt;
+&lt;h4&gt;GTFS compatibility&lt;/h4&gt;
+&lt;p&gt;As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the &lt;a href="https://code.google.com/p/googletransitdatafeed/wiki/FareExamples"&gt;fare examples&lt;/a&gt;, the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced &lt;a href="https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw"&gt;issues&lt;/a&gt; and made &lt;a href="https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ"&gt;proposals&lt;/a&gt; for having distance-based fares included into GTFS.&lt;/p&gt;
+&lt;p&gt;Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated &lt;a href="https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit"&gt;GTFS fare proposal here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a &lt;a href="https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30"&gt;pull request&lt;/a&gt; for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.&lt;/p&gt;
+&lt;h4&gt;Remaining Problems&lt;/h4&gt;
+&lt;p&gt;Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.&lt;/p&gt;
+&lt;p&gt;We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.&lt;/p&gt;
+&lt;h4&gt;Conclusion&lt;/h4&gt;
+&lt;p&gt;Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.&lt;/p&gt;
+&lt;p&gt;Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description><guid>http://pleasantprogrammer.com/posts/fare-data.html</guid><pubDate>Sat, 13 Jul 2013 13:15:09 GMT</pubDate></item><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; they really meant under development&lt;/p&gt;
 &lt;p&gt;When I first saw the source of GTFS Editor, I was ecstatic. They used &lt;a href="http://playframework.com/"&gt;Play framework&lt;/a&gt;!!! Not only that, they're targeting PostgreSQL as the main database. Those are our favorite tools for building webapps at By Implication. I was a bit sad though, when I saw it was on the 1.x release of Play though. I did have some experience with that release, but not as much compared to 2.x.&lt;/p&gt;
 &lt;p&gt;Getting it to actually run though, wasn't very pleasant. The initial setup was easy enough. Get &lt;a href="http://www.playframework.com/download"&gt;Play 1.2.5&lt;/a&gt;, install Postgres with PostGIS, clone the repo and create backing database in Postgres. Some minor additional steps you need are to create the PostGIS extension on the database. The schema is automatically generated and applied by Play so that should be all that's necessary. Wonderful. Then, run play, open a browser, go to &lt;a href="http://localhost:9000"&gt;http://localhost:9000&lt;/a&gt;, compilation error. Fantastic.&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/gtfs-editor.html">[2013-07-10 11:30] GTFS Editor</a>
+        <br><ul class="unstyled"><li><a href="../posts/fare-data.html">[2013-07-13 21:15] Fare Data</a>
+            </li><li><a href="../posts/gtfs-editor.html">[2013-07-10 11:30] GTFS Editor</a>
             </li><li><a href="../posts/open-trip-planner.html">[2013-07-09 23:16] Open Trip Planner</a>
             </li><li><a href="../posts/one-bus-or-maybe-jeep-away.html">[2013-07-09 01:53] One Bus (or maybe Jeep) Away</a>
             </li><li><a href="../posts/jeepney-and-bus-routes.html">[2013-07-07 10:32] Jeepney and Bus Routes</a>

output/categories/programming.xml

@@ -1,5 +1,44 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer (programming)</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Thu, 11 Jul 2013 00:31:36 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer (programming)</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Sat, 13 Jul 2013 22:44:53 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Fare Data</title><link>http://pleasantprogrammer.com/posts/fare-data.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;As part of the data released by the DOTC, we also have the &lt;a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/"&gt;fare matrix&lt;/a&gt; for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the &lt;a href="http://ltfrb.gov.ph/main/farerates"&gt;LTFRB website&lt;/a&gt;. Generally, the fare scheme is represented as "pay &lt;em&gt;X&lt;/em&gt; pesos for the first &lt;em&gt;Y&lt;/em&gt; kilometers, pay &lt;em&gt;Z&lt;/em&gt; for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,&lt;/p&gt;
+&lt;div class="code"&gt;&lt;pre&gt;&lt;span class="n"&gt;base_fare&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;distance&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;initial&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;per_km&lt;/span&gt;
+&lt;/pre&gt;&lt;/div&gt;
+
+
+&lt;p&gt;The relevant values for the three services are:&lt;/p&gt;
+&lt;table&gt;&lt;tr&gt;&lt;td&gt;type&lt;/td&gt;
+    &lt;td&gt;base_fare&lt;/td&gt;
+    &lt;td&gt;initial&lt;/td&gt;
+    &lt;td&gt;per_km&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;bus aircon&lt;/td&gt;
+    &lt;td&gt;12.00&lt;/td&gt;
+    &lt;td&gt;5 km&lt;/td&gt;
+    &lt;td&gt;2.20&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;bus ordinary&lt;/td&gt;
+    &lt;td&gt;10.00&lt;/td&gt;
+    &lt;td&gt;5 km&lt;/td&gt;
+    &lt;td&gt;1.85&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;jeep aircon&lt;/td&gt;
+    &lt;td&gt;8.00&lt;/td&gt;
+    &lt;td&gt;4 km&lt;/td&gt;
+    &lt;td&gt;1.40&lt;/td&gt;
+  &lt;/tr&gt;&lt;/table&gt;&lt;p&gt;It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,&lt;/p&gt;
+&lt;div class="code"&gt;&lt;pre&gt;&lt;span class="n"&gt;round&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;calculated_fare&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;4.0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="mf"&gt;4.0&lt;/span&gt;
+&lt;/pre&gt;&lt;/div&gt;
+
+
+&lt;p&gt;There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.&lt;/p&gt;
+&lt;p&gt;Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.&lt;/p&gt;
+&lt;p&gt;Here's a &lt;a href="/uploads/farematrix.rb"&gt;script&lt;/a&gt; that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the &lt;a href="/uploads/pub_aircon.csv"&gt;aircon bus&lt;/a&gt;, &lt;a href="/uploads/pub_ordinary.csv"&gt;ordinary bus&lt;/a&gt; and &lt;a href="/uploads/puj.csv"&gt;jeep&lt;/a&gt; fare matrices.&lt;/p&gt;
+&lt;h4&gt;GTFS compatibility&lt;/h4&gt;
+&lt;p&gt;As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the &lt;a href="https://code.google.com/p/googletransitdatafeed/wiki/FareExamples"&gt;fare examples&lt;/a&gt;, the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced &lt;a href="https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw"&gt;issues&lt;/a&gt; and made &lt;a href="https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ"&gt;proposals&lt;/a&gt; for having distance-based fares included into GTFS.&lt;/p&gt;
+&lt;p&gt;Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated &lt;a href="https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit"&gt;GTFS fare proposal here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a &lt;a href="https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30"&gt;pull request&lt;/a&gt; for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.&lt;/p&gt;
+&lt;h4&gt;Remaining Problems&lt;/h4&gt;
+&lt;p&gt;Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.&lt;/p&gt;
+&lt;p&gt;We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.&lt;/p&gt;
+&lt;h4&gt;Conclusion&lt;/h4&gt;
+&lt;p&gt;Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.&lt;/p&gt;
+&lt;p&gt;Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description><guid>http://pleasantprogrammer.com/posts/fare-data.html</guid><pubDate>Sat, 13 Jul 2013 13:15:09 GMT</pubDate></item><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; they really meant under development&lt;/p&gt;
 &lt;p&gt;When I first saw the source of GTFS Editor, I was ecstatic. They used &lt;a href="http://playframework.com/"&gt;Play framework&lt;/a&gt;!!! Not only that, they're targeting PostgreSQL as the main database. Those are our favorite tools for building webapps at By Implication. I was a bit sad though, when I saw it was on the 1.x release of Play though. I did have some experience with that release, but not as much compared to 2.x.&lt;/p&gt;
 &lt;p&gt;Getting it to actually run though, wasn't very pleasant. The initial setup was easy enough. Get &lt;a href="http://www.playframework.com/download"&gt;Play 1.2.5&lt;/a&gt;, install Postgres with PostGIS, clone the repo and create backing database in Postgres. Some minor additional steps you need are to create the PostGIS extension on the database. The schema is automatically generated and applied by Play so that should be all that's necessary. Wonderful. Then, run play, open a browser, go to &lt;a href="http://localhost:9000"&gt;http://localhost:9000&lt;/a&gt;, compilation error. Fantastic.&lt;/p&gt;

output/index.html

@@ -33,6 +33,55 @@
     <div class="span2"></div>
     <div class="span8">
     
+        <div class="postbox">
+        <h1><a href="posts/fare-data.html">Fare Data</a>
+        <small>  
+             Posted: <time class="published" datetime="2013-07-13T21:15:09+08:00">2013-07-13 21:15</time></small></h1>
+        <hr><p>As part of the data released by the DOTC, we also have the <a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/">fare matrix</a> for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the <a href="http://ltfrb.gov.ph/main/farerates">LTFRB website</a>. Generally, the fare scheme is represented as "pay <em>X</em> pesos for the first <em>Y</em> kilometers, pay <em>Z</em> for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,</p>
+<div class="code"><pre><span class="n">base_fare</span> <span class="o">+</span> <span class="p">(</span><span class="n">distance</span> <span class="o">-</span> <span class="n">initial</span><span class="p">)</span> <span class="o">*</span> <span class="n">per_km</span>
+</pre></div>
+
+
+<p>The relevant values for the three services are:</p>
+<table><tr><td>type</td>
+    <td>base_fare</td>
+    <td>initial</td>
+    <td>per_km</td>
+  </tr><tr><td>bus aircon</td>
+    <td>12.00</td>
+    <td>5 km</td>
+    <td>2.20</td>
+  </tr><tr><td>bus ordinary</td>
+    <td>10.00</td>
+    <td>5 km</td>
+    <td>1.85</td>
+  </tr><tr><td>jeep aircon</td>
+    <td>8.00</td>
+    <td>4 km</td>
+    <td>1.40</td>
+  </tr></table><p>It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,</p>
+<div class="code"><pre><span class="n">round</span><span class="p">(</span><span class="n">calculated_fare</span> <span class="o">*</span> <span class="mf">4.0</span><span class="p">)</span><span class="o">/</span><span class="mf">4.0</span>
+</pre></div>
+
+
+<p>There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.</p>
+<p>Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.</p>
+<p>Here's a <a href="uploads/farematrix.rb">script</a> that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the <a href="uploads/pub_aircon.csv">aircon bus</a>, <a href="uploads/pub_ordinary.csv">ordinary bus</a> and <a href="uploads/puj.csv">jeep</a> fare matrices.</p>
+<h4>GTFS compatibility</h4>
+<p>As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the <a href="https://code.google.com/p/googletransitdatafeed/wiki/FareExamples">fare examples</a>, the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced <a href="https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw">issues</a> and made <a href="https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ">proposals</a> for having distance-based fares included into GTFS.</p>
+<p>Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated <a href="https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit">GTFS fare proposal here</a>.</p>
+<p>Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a <a href="https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30">pull request</a> for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.</p>
+<h4>Remaining Problems</h4>
+<p>Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.</p>
+<p>We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.</p>
+<h4>Conclusion</h4>
+<p>Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.</p>
+<p>Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.</p>
+            
+    <p>
+        <a href="posts/fare-data.html#disqus_thread" data-disqus-identifier="cache/posts/fare-data.html">Comments</a>
+
+        </p></div>
         <div class="postbox">
         <h1><a href="posts/gtfs-editor.html">GTFS Editor</a>
         <small>  

output/listings/index.html

@@ -0,0 +1,48 @@
+<!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> | 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=".">/listings</a>
+        </li><li><a href="#">/index.html</a>
+</li></ul><ul class="unstyled"></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/posts/fare-data.html

@@ -0,0 +1,128 @@
+<!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>Fare Data | 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="fare-data.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>Fare Data</h1>
+
+    <hr><small>
+        Posted: <time class="published" datetime="2013-07-13T21:15:09+08:00">2013-07-13 21:15</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>As part of the data released by the DOTC, we also have the <a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/">fare matrix</a> for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the <a href="http://ltfrb.gov.ph/main/farerates">LTFRB website</a>. Generally, the fare scheme is represented as "pay <em>X</em> pesos for the first <em>Y</em> kilometers, pay <em>Z</em> for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,</p>
+<div class="code"><pre><span class="n">base_fare</span> <span class="o">+</span> <span class="p">(</span><span class="n">distance</span> <span class="o">-</span> <span class="n">initial</span><span class="p">)</span> <span class="o">*</span> <span class="n">per_km</span>
+</pre></div>
+
+
+<p>The relevant values for the three services are:</p>
+<table><tr><td>type</td>
+    <td>base_fare</td>
+    <td>initial</td>
+    <td>per_km</td>
+  </tr><tr><td>bus aircon</td>
+    <td>12.00</td>
+    <td>5 km</td>
+    <td>2.20</td>
+  </tr><tr><td>bus ordinary</td>
+    <td>10.00</td>
+    <td>5 km</td>
+    <td>1.85</td>
+  </tr><tr><td>jeep aircon</td>
+    <td>8.00</td>
+    <td>4 km</td>
+    <td>1.40</td>
+  </tr></table><p>It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,</p>
+<div class="code"><pre><span class="n">round</span><span class="p">(</span><span class="n">calculated_fare</span> <span class="o">*</span> <span class="mf">4.0</span><span class="p">)</span><span class="o">/</span><span class="mf">4.0</span>
+</pre></div>
+
+
+<p>There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.</p>
+<p>Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.</p>
+<p>Here's a <a href="../uploads/farematrix.rb">script</a> that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the <a href="../uploads/pub_aircon.csv">aircon bus</a>, <a href="../uploads/pub_ordinary.csv">ordinary bus</a> and <a href="../uploads/puj.csv">jeep</a> fare matrices.</p>
+<h4>GTFS compatibility</h4>
+<p>As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the <a href="https://code.google.com/p/googletransitdatafeed/wiki/FareExamples">fare examples</a>, the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced <a href="https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw">issues</a> and made <a href="https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ">proposals</a> for having distance-based fares included into GTFS.</p>
+<p>Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated <a href="https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit">GTFS fare proposal here</a>.</p>
+<p>Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a <a href="https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30">pull request</a> for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.</p>
+<h4>Remaining Problems</h4>
+<p>Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.</p>
+<p>We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.</p>
+<h4>Conclusion</h4>
+<p>Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.</p>
+<p>Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.</p>
+    
+    <ul class="pager"><li class="previous">
+            <a href="gtfs-editor.html">← Previous post</a>
+        </li>
+    </ul><div id="disqus_thread"></div>
+        <script type="text/javascript">
+        var disqus_shortname ="pleasantprog";
+            var disqus_url="http://pleasantprogrammer.com/posts/fare-data.html";
+        var disqus_title="Fare Data";
+        var disqus_identifier="cache/posts/fare-data.html";
+        var disqus_config = function () {
+            this.language = "en";
+        };
+        (function() {
+            var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
+            dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
+            (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
+        })();
+    </script><noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
+
+    
+
+    </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/fare-data.md

@@ -0,0 +1,71 @@
+<!-- 
+.. link: 
+.. description: 
+.. tags: philippine-transit-app, programming
+.. date: 2013/07/13 21:15:09
+.. title: Fare Data
+.. slug: fare-data
+-->
+
+As part of the data released by the DOTC, we also have the [fare matrix](http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/) for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the [LTFRB website](http://ltfrb.gov.ph/main/farerates). Generally, the fare scheme is represented as "pay *X* pesos for the first *Y* kilometers, pay *Z* for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,
+
+    base_fare + (distance - initial) * per_km
+
+The relevant values for the three services are:
+
+<table>
+  <tr>
+    <td>type</td>
+    <td>base_fare</td>
+    <td>initial</td>
+    <td>per_km</td>
+  </tr>
+  <tr>
+  	<td>bus aircon</td>
+  	<td>12.00</td>
+  	<td>5 km</td>
+  	<td>2.20</td>
+  </tr>
+  <tr>
+  	<td>bus ordinary</td>
+  	<td>10.00</td>
+  	<td>5 km</td>
+  	<td>1.85</td>
+  </tr>
+  <tr>
+  	<td>jeep aircon</td>
+  	<td>8.00</td>
+  	<td>4 km</td>
+  	<td>1.40</td>
+  </tr>
+</table>
+
+It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,
+
+    round(calculated_fare * 4.0)/4.0
+
+There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.
+
+Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.
+
+Here's a [script](../uploads/farematrix.rb) that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the [aircon bus](../uploads/pub_aircon.csv), [ordinary bus](../uploads/pub_ordinary.csv) and [jeep](../uploads/puj.csv) fare matrices.
+
+### GTFS compatibility
+
+As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the [fare examples](https://code.google.com/p/googletransitdatafeed/wiki/FareExamples), the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced [issues](https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw) and made [proposals](https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ) for having distance-based fares included into GTFS.
+
+Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated [GTFS fare proposal here](https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit).
+
+Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a [pull request](https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30) for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.
+
+### Remaining Problems
+
+Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.
+
+We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.
+
+### Conclusion
+
+Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.
+
+Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.

output/posts/gtfs-editor.html

@@ -233,6 +233,9 @@ Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     <ul class="pager"><li class="previous">
             <a href="open-trip-planner.html">← Previous post</a>
         </li>
+        <li class="next">
+            <a href="fare-data.html">Next post →</a>
+        </li>
     </ul><div id="disqus_thread"></div>
         <script type="text/javascript">
         var disqus_shortname ="pleasantprog";

output/rss.xml

@@ -1,5 +1,44 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss version="2.0"><channel><title>Pleasant Programmer</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Thu, 11 Jul 2013 00:31:36 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
+<rss version="2.0"><channel><title>Pleasant Programmer</title><link>http://pleasantprogrammer.com</link><description></description><lastBuildDate>Sat, 13 Jul 2013 22:44:53 GMT</lastBuildDate><generator>nikola</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Fare Data</title><link>http://pleasantprogrammer.com/posts/fare-data.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;As part of the data released by the DOTC, we also have the &lt;a href="http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/"&gt;fare matrix&lt;/a&gt; for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the &lt;a href="http://ltfrb.gov.ph/main/farerates"&gt;LTFRB website&lt;/a&gt;. Generally, the fare scheme is represented as "pay &lt;em&gt;X&lt;/em&gt; pesos for the first &lt;em&gt;Y&lt;/em&gt; kilometers, pay &lt;em&gt;Z&lt;/em&gt; for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,&lt;/p&gt;
+&lt;div class="code"&gt;&lt;pre&gt;&lt;span class="n"&gt;base_fare&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;distance&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;initial&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;per_km&lt;/span&gt;
+&lt;/pre&gt;&lt;/div&gt;
+
+
+&lt;p&gt;The relevant values for the three services are:&lt;/p&gt;
+&lt;table&gt;&lt;tr&gt;&lt;td&gt;type&lt;/td&gt;
+    &lt;td&gt;base_fare&lt;/td&gt;
+    &lt;td&gt;initial&lt;/td&gt;
+    &lt;td&gt;per_km&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;bus aircon&lt;/td&gt;
+    &lt;td&gt;12.00&lt;/td&gt;
+    &lt;td&gt;5 km&lt;/td&gt;
+    &lt;td&gt;2.20&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;bus ordinary&lt;/td&gt;
+    &lt;td&gt;10.00&lt;/td&gt;
+    &lt;td&gt;5 km&lt;/td&gt;
+    &lt;td&gt;1.85&lt;/td&gt;
+  &lt;/tr&gt;&lt;tr&gt;&lt;td&gt;jeep aircon&lt;/td&gt;
+    &lt;td&gt;8.00&lt;/td&gt;
+    &lt;td&gt;4 km&lt;/td&gt;
+    &lt;td&gt;1.40&lt;/td&gt;
+  &lt;/tr&gt;&lt;/table&gt;&lt;p&gt;It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,&lt;/p&gt;
+&lt;div class="code"&gt;&lt;pre&gt;&lt;span class="n"&gt;round&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;calculated_fare&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;4.0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="mf"&gt;4.0&lt;/span&gt;
+&lt;/pre&gt;&lt;/div&gt;
+
+
+&lt;p&gt;There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.&lt;/p&gt;
+&lt;p&gt;Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.&lt;/p&gt;
+&lt;p&gt;Here's a &lt;a href="/uploads/farematrix.rb"&gt;script&lt;/a&gt; that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the &lt;a href="/uploads/pub_aircon.csv"&gt;aircon bus&lt;/a&gt;, &lt;a href="/uploads/pub_ordinary.csv"&gt;ordinary bus&lt;/a&gt; and &lt;a href="/uploads/puj.csv"&gt;jeep&lt;/a&gt; fare matrices.&lt;/p&gt;
+&lt;h4&gt;GTFS compatibility&lt;/h4&gt;
+&lt;p&gt;As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the &lt;a href="https://code.google.com/p/googletransitdatafeed/wiki/FareExamples"&gt;fare examples&lt;/a&gt;, the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced &lt;a href="https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw"&gt;issues&lt;/a&gt; and made &lt;a href="https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ"&gt;proposals&lt;/a&gt; for having distance-based fares included into GTFS.&lt;/p&gt;
+&lt;p&gt;Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated &lt;a href="https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit"&gt;GTFS fare proposal here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a &lt;a href="https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30"&gt;pull request&lt;/a&gt; for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.&lt;/p&gt;
+&lt;h4&gt;Remaining Problems&lt;/h4&gt;
+&lt;p&gt;Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.&lt;/p&gt;
+&lt;p&gt;We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.&lt;/p&gt;
+&lt;h4&gt;Conclusion&lt;/h4&gt;
+&lt;p&gt;Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.&lt;/p&gt;
+&lt;p&gt;Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description><guid>http://pleasantprogrammer.com/posts/fare-data.html</guid><pubDate>Sat, 13 Jul 2013 13:15:09 GMT</pubDate></item><item><title>GTFS Editor</title><link>http://pleasantprogrammer.com/posts/gtfs-editor.html</link><description>&lt;html&gt;&lt;body&gt;&lt;p&gt;Link: &lt;a href="https://github.com/conveyal/gtfs-editor"&gt;https://github.com/conveyal/gtfs-editor&lt;/a&gt;&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; they really meant under development&lt;/p&gt;
 &lt;p&gt;When I first saw the source of GTFS Editor, I was ecstatic. They used &lt;a href="http://playframework.com/"&gt;Play framework&lt;/a&gt;!!! Not only that, they're targeting PostgreSQL as the main database. Those are our favorite tools for building webapps at By Implication. I was a bit sad though, when I saw it was on the 1.x release of Play though. I did have some experience with that release, but not as much compared to 2.x.&lt;/p&gt;
 &lt;p&gt;Getting it to actually run though, wasn't very pleasant. The initial setup was easy enough. Get &lt;a href="http://www.playframework.com/download"&gt;Play 1.2.5&lt;/a&gt;, install Postgres with PostGIS, clone the repo and create backing database in Postgres. Some minor additional steps you need are to create the PostGIS extension on the database. The schema is automatically generated and applied by Play so that should be all that's necessary. Wonderful. Then, run play, open a browser, go to &lt;a href="http://localhost:9000"&gt;http://localhost:9000&lt;/a&gt;, compilation error. Fantastic.&lt;/p&gt;

output/sitemap.xml

@@ -6,102 +6,117 @@
                         http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
  <url>
   <loc>http://pleasantprogrammer.com</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/2013/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/2013/index.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/archive.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/assets/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/assets/css/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/assets/css/images/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/assets/css/images/ie6/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/assets/img/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/assets/js/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/categories/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/categories/index.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/categories/lets-debug.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/categories/philippine-transit-app.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/categories/programming.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/galleries/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/galleries/index.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/galleries/transit/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/galleries/transit/index.html</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
+  <priority>0.5000</priority>
+ </url>
+ <url>
+  <loc>http://pleasantprogrammer.com/listings/</loc>
+  <lastmod>2013-07-13</lastmod>
+  <priority>0.5000</priority>
+ </url>
+ <url>
+  <loc>http://pleasantprogrammer.com/listings/index.html</loc>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
  <url>
   <loc>http://pleasantprogrammer.com/posts/</loc>
-  <lastmod>2013-07-11</lastmod>
+  <lastmod>2013-07-13</lastmod>
+  <priority>0.5000</priority>
+ </url>
+ <url>
+  <loc>http://pleasantprogrammer.com/uploads/</loc>
+  <lastmod>2013-07-13</lastmod>
   <priority>0.5000</priority>
  </url>
 </urlset>

output/uploads/farematrix.rb

@@ -0,0 +1,67 @@
+#!/usr/bin/env ruby
+
+require 'csv'
+
+# current as of July 2013
+fare_types = {
+  "pub_aircon" => {
+    "fare" => 12.00,
+    "firstkm" => 5,
+    "perkm" => 2.2,
+    "limit" => 60
+  },
+  "pub_ordinary" => {
+    "fare" => 10.00,
+    "firstkm" => 5,
+    "perkm" => 1.85,
+    "limit" => 60
+  },
+  "puj" => {
+    "fare" => 8.00,
+    "firstkm" => 4,
+    "perkm" => 1.4,
+    "limit" => 50,
+    "override" => {
+      10 => { "discounted" => '13.25' },
+      12 => { "discounted" => '15.50' },
+      14 => { "discounted" => '17.75' },
+      18 => { "discounted" => '22.25' },
+      20 => { "discounted" => '24.50' },
+      22 => { "discounted" => '26.75' },
+      33 => { "discounted" => '38.75' },
+      35 => { "discounted" => '41.25' },
+      37 => { "discounted" => '43.50' },
+      39 => { "discounted" => '45.75' },
+      45 => { "discounted" => '52.50' },
+      47 => { "discounted" => '54.75' }
+    }
+  }
+}
+
+def round(original)
+  "%.2f" % ((original*4).round/4.0)
+end
+
+def if_override(original, type, dist, name)
+  value = original
+  value = type['override'][dist][name] if type['override'] && type['override'][dist] && type['override'][dist][name]
+  value
+end
+
+fare_types.each do |key, type|
+  CSV.open(key+'.csv', 'wb') do |csv|
+    csv << ['distance', 'regular', 'discounted']
+    type['limit'].times do |x|
+      dist = x+1
+      fare = type['fare']
+      if dist > type['firstkm']
+        fare += type['perkm'] * (dist - type['firstkm'])
+      end
+      discounted = round(fare*0.8)
+      fare = round(fare)
+      discounted = if_override(discounted, type, dist, 'discounted')
+      fare = if_override(fare, type, dist, 'fare')
+      csv << [dist, fare, discounted]
+    end
+  end
+end

output/uploads/pub_aircon.csv

@@ -0,0 +1,61 @@
+distance,regular,discounted
+1,12.00,9.50
+2,12.00,9.50
+3,12.00,9.50
+4,12.00,9.50
+5,12.00,9.50
+6,14.25,11.25
+7,16.50,13.00
+8,18.50,15.00
+9,20.75,16.75
+10,23.00,18.50
+11,25.25,20.25
+12,27.50,22.00
+13,29.50,23.75
+14,31.75,25.50
+15,34.00,27.25
+16,36.25,29.00
+17,38.50,30.75
+18,40.50,32.50
+19,42.75,34.25
+20,45.00,36.00
+21,47.25,37.75
+22,49.50,39.50
+23,51.50,41.25
+24,53.75,43.00
+25,56.00,44.75
+26,58.25,46.50
+27,60.50,48.25
+28,62.50,50.00
+29,64.75,51.75
+30,67.00,53.50
+31,69.25,55.25
+32,71.50,57.00
+33,73.50,59.00
+34,75.75,60.75
+35,78.00,62.50
+36,80.25,64.25
+37,82.50,66.00
+38,84.50,67.75
+39,86.75,69.50
+40,89.00,71.25
+41,91.25,73.00
+42,93.50,74.75
+43,95.50,76.50
+44,97.75,78.25
+45,100.00,80.00
+46,102.25,81.75
+47,104.50,83.50
+48,106.50,85.25
+49,108.75,87.00
+50,111.00,88.75
+51,113.25,90.50
+52,115.50,92.25
+53,117.50,94.00
+54,119.75,95.75
+55,122.00,97.50
+56,124.25,99.25
+57,126.50,101.00
+58,128.50,103.00
+59,130.75,104.75
+60,133.00,106.50

output/uploads/pub_ordinary.csv

@@ -0,0 +1,61 @@
+distance,regular,discounted
+1,10.00,8.00
+2,10.00,8.00
+3,10.00,8.00
+4,10.00,8.00
+5,10.00,8.00
+6,11.75,9.50
+7,13.75,11.00
+8,15.50,12.50
+9,17.50,14.00
+10,19.25,15.50
+11,21.00,17.00
+12,23.00,18.25
+13,24.75,19.75
+14,26.75,21.25
+15,28.50,22.75
+16,30.25,24.25
+17,32.25,25.75
+18,34.00,27.25
+19,36.00,28.75
+20,37.75,30.25
+21,39.50,31.75
+22,41.50,33.25
+23,43.25,34.75
+24,45.25,36.00
+25,47.00,37.50
+26,48.75,39.00
+27,50.75,40.50
+28,52.50,42.00
+29,54.50,43.50
+30,56.25,45.00
+31,58.00,46.50
+32,60.00,48.00
+33,61.75,49.50
+34,63.75,51.00
+35,65.50,52.50
+36,67.25,54.00
+37,69.25,55.25
+38,71.00,56.75
+39,73.00,58.25
+40,74.75,59.75
+41,76.50,61.25
+42,78.50,62.75
+43,80.25,64.25
+44,82.25,65.75
+45,84.00,67.25
+46,85.75,68.75
+47,87.75,70.25
+48,89.50,71.75
+49,91.50,73.00
+50,93.25,74.50
+51,95.00,76.00
+52,97.00,77.50
+53,98.75,79.00
+54,100.75,80.50
+55,102.50,82.00
+56,104.25,83.50
+57,106.25,85.00
+58,108.00,86.50
+59,110.00,88.00
+60,111.75,89.50

output/uploads/puj.csv

@@ -0,0 +1,51 @@
+distance,regular,discounted
+1,8.00,6.50
+2,8.00,6.50
+3,8.00,6.50
+4,8.00,6.50
+5,9.50,7.50
+6,10.75,8.75
+7,12.25,9.75
+8,13.50,11.00
+9,15.00,12.00
+10,16.50,13.25
+11,17.75,14.25
+12,19.25,15.50
+13,20.50,16.50
+14,22.00,17.75
+15,23.50,18.75
+16,24.75,19.75
+17,26.25,21.00
+18,27.50,22.25
+19,29.00,23.25
+20,30.50,24.50
+21,31.75,25.50
+22,33.25,26.75
+23,34.50,27.75
+24,36.00,28.75
+25,37.50,30.00
+26,38.75,31.00
+27,40.25,32.25
+28,41.50,33.25
+29,43.00,34.50
+30,44.50,35.50
+31,45.75,36.75
+32,47.25,37.75
+33,48.50,38.75
+34,50.00,40.00
+35,51.50,41.25
+36,52.75,42.25
+37,54.25,43.50
+38,55.50,44.50
+39,57.00,45.75
+40,58.50,46.75
+41,59.75,47.75
+42,61.25,49.00
+43,62.50,50.00
+44,64.00,51.25
+45,65.50,52.50
+46,66.75,53.50
+47,68.25,54.75
+48,69.50,55.75
+49,71.00,56.75
+50,72.50,58.00

posts/fare-data.md

@@ -0,0 +1,71 @@
+<!-- 
+.. link: 
+.. description: 
+.. tags: philippine-transit-app, programming
+.. date: 2013/07/13 21:15:09
+.. title: Fare Data
+.. slug: fare-data
+-->
+
+As part of the data released by the DOTC, we also have the [fare matrix](http://philippine-transit.hackathome.com/dataset-philippines-transit-information-service-gtfs/) for aircon buses, ordinary buses and jeeps. All as wonderful images. The data is also actually available from the [LTFRB website](http://ltfrb.gov.ph/main/farerates). Generally, the fare scheme is represented as "pay *X* pesos for the first *Y* kilometers, pay *Z* for every succeeding kilometer." Instead of a table, we can simply represent this as a formula instead,
+
+    base_fare + (distance - initial) * per_km
+
+The relevant values for the three services are:
+
+<table>
+  <tr>
+    <td>type</td>
+    <td>base_fare</td>
+    <td>initial</td>
+    <td>per_km</td>
+  </tr>
+  <tr>
+  	<td>bus aircon</td>
+  	<td>12.00</td>
+  	<td>5 km</td>
+  	<td>2.20</td>
+  </tr>
+  <tr>
+  	<td>bus ordinary</td>
+  	<td>10.00</td>
+  	<td>5 km</td>
+  	<td>1.85</td>
+  </tr>
+  <tr>
+  	<td>jeep aircon</td>
+  	<td>8.00</td>
+  	<td>4 km</td>
+  	<td>1.40</td>
+  </tr>
+</table>
+
+It isn't as simple as that though. Fares are also rounded to the nearest 25 centavos. So we'd need to round them off correctly. This can be achieved by doing,
+
+    round(calculated_fare * 4.0)/4.0
+
+There's also the discounted fare for students, senior citizens and persons with disability. They get 20% off the fare (prior to rounding) and the resulting fare is rounded off as well.
+
+Doing just this, we actually do get the same results as the fare matrices in the image for the most part. There are some discrepancies with the discounted jeep fares. I've tried to resolve it by tweaking around with the formulas, but it really doesn't make sense in any way. I presume these were manually adjusted for one reason or another.
+
+Here's a [script](../uploads/farematrix.rb) that generates CSVs of all the three fare matrices. If you're too lazy to run it, here are links to the [aircon bus](../uploads/pub_aircon.csv), [ordinary bus](../uploads/pub_ordinary.csv) and [jeep](../uploads/puj.csv) fare matrices.
+
+### GTFS compatibility
+
+As is, the provided GTFS data does not have any fare data. I imagine this is because the existing spec doesn't have good support for distance-based fares like we have in the Philippines. Judging from the [fare examples](https://code.google.com/p/googletransitdatafeed/wiki/FareExamples), the only reasonable way we could implement distance-based fares is following example 6. This would involve setting a fare for each possible pair of stops based on the distance between them. This isn't exactly ideal. In fact, the people originally working on the DOTC project have voiced [issues](https://groups.google.com/forum/#!topic/gtfs-fare-wg/V63xRSnQJGw) and made [proposals](https://groups.google.com/forum/#!msg/gtfs-changes/uybrAokZ9Cg/rqlzXdMypUgJ) for having distance-based fares included into GTFS.
+
+Apparently, public transit fares are a really complicated thing. You have fares based on distance, number of stops passed through, and transfers which may or may not cost extra. Not only that, you might have discounted fares, or first-class vs economy fares. The community will want to get it right before it's formally included in the spec. You can see the current state of the consolidated [GTFS fare proposal here](https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit).
+
+Even in it's proposal form though, we might have hope of being able to see these being used. There's currently a [pull request](https://github.com/OneBusAway/onebusaway-gtfs-modules/pull/30) for supporting the distance-based fare scheme into the OneBusAway libraries. The libraries actually used by GTFS Editor and OpenTripPlanner for working with GTFS data.
+
+### Remaining Problems
+
+Given all that, it would probably still be a long way before this allows us to make a really good routing app. We still don't have shape data, so the distance estimates would really be rough estimates at best. There's no support for rounding to the nearest centavo. I realize that's just nitpicking, but if we want something truly polished, even that has to be taken care of.
+
+We also don't know if the jeeps or buses strictly follow the distance-based scheme. After all, if you can get on and off anywhere, you can't really measure distance that exactly. I assume they generally work off the notion of "zones" than actual distance travelled. In that sense, they work more similarly to the LRT which has fares based on how many stops you pass. For jeeps and buses, your fare is probably based more on how many "zones" you pass through.
+
+### Conclusion
+
+Philip, a co-worker of mine at By Implication, had suggested that we might want to use a different model than what the GTFS proposes. I have to agree with him. At this point, the GTFS doesn't really fit with our system. But I do think that open data and standards are great. In fact, I applaud the developers who made proposals for the fare system, as those are great first steps towards making the GTFS a more universal standard.
+
+Side note: I'd also actually really like to hear about the DOTC developers' experience with the project. It would be nice if they had a devblog.