Skip to main content

Clean Transportation Enlightenment

Today I was reading about power cosumption and CO2 emissions, and I ran across a blog entry from someone in Holland. Apparently he was going to travel to a consumer conference that was 100 kilometers away and had to decide if he should drive or take the train. His decision was to take the train because it was more environmentally friendly and economical than driving.

Like many people, I am skeptical of the argument that a train is more friendly than a car. Right? Cars have catalytic converters and all sorts of emission controls that reduce their output. There aren't any hefty catalytic converters on diesel locomotives.

So I decided to run some numbers and do a little research.

[1] http://en.wikipedia.org/wiki/Maglev_train#_note-0

I assumed that the fella was taking a magnetic levitation train because that's what I'd like to do. Eventhough there isn't a maglev train in Holland that could have been used, I calculated it anyway.

According to Wikipedia, a maglev train consumes 22 watt-hours of power per kilometer and per person travelling.

Maglev = 22 Wh/pkm

[2] http://www.eia.doe.gov/cneaf/electricity/page/co2_report/co2report.html#electric

The generation of this ephemeral electric power produces CO2. We know that power generation loses much power during transmission and distribution. According to a study done in the late 1990s on the USA, electric distribution loss was about 7.2%.

[3] http://en.wikipedia.org/wiki/Electric_power_transmission

I'll use this loss factor for my calculations, eventhough the UK study had their loss estimates at 7.4%.

Maglev = 1.072 * 22 Wh/pkm = 23.584 Wh/pkm

For a 100 km, one-way, jaunt, the maglev transportation would consume 4716.8 Wh per passenger. This is the same as saying it takes 4.7168 kWh per person to travel to his conference.

Back to the coal burning plant that is pushing electricity to our maglev train. The DOE study in [2] states that a coal fire plant produces 2.117 pounds of CO2 per kWh. At 2.2 pounds per kilogram, that means coal fire produces 0.962 kg/kWh of CO2.

We need 4.7168 kWh to run our maglev train, so that means the train really produces 4.5376 kg of CO2 during this trip.

Reality is that the traveller likely took a diesel commuter train. These trains produce a bit more effluence and CO2, so let's consider that for a moment.

[4] http://www.aeris.eko.org.pl/niem/kalkulator/Methodology_transport.doc

A diesel train is estimated to produce 0.0294 kg of CO2 per passenger-km. In this analysis, the traveller is going 200 km, so the train would produce 5.88 kg of CO2 on his behalf.

It is surprising to note that a modern diesel train produces about 30% more CO2 than its maglev cousin. If the maglev train only cost 30% more to build, maybe we'd have more of them for travel.

The final consideration is that of a passenger car. Finding CO2 emission data for passenger cars is not too easy. I had to poke around for a bit until I found a nifty UK site that had a calculator:

[5] http://www.smmtco2.co.uk/co2search2.asp

I punched in BMW 325CI SE and got 229 g/km. I tried some other cars, such as a VW Passat, and had no luck. I was able to get the rating on a Nissan XTerra SE, which was 237 g/km. Given that the SUV and the BMW sedan were about the same, this 229 g/km figure was my metric.

200 km to go produces 45,800 g of CO2, or 45.8 kg. Holy smokes, literally! That's nearly 10 times the output of a maglev train, and about 8 times that of a diesel train. Why are we still driving our cars?? Oh yeah, because we don't have trains going everywhere we need to go.

When the traveller gets to the city, he still has to take passenger transportation to get to the conference. That produces a trace amount of CO2 by way of the bus, which is likely a clean burning natural gas vehicle.

I used to be a doubter in the train versus car argument, seeing the billowy black effluence from a diesel train. Now, though, I am convinced. If you truly have a choice, then you should make the train your choice of transportation. It simply is cleaner.

Popular posts from this blog

Number of Primes

Anderson's Theorem (a) The number of primes in [1,n] is no more than 2+floor(n/2). The probability of n being prime when n is not prime is 1/2 - see Dasgupta,Papadimitriou,Vazirani "Algorithms" page 26. Therefore, the E(pi(n)) is n/2. (b) There does not exist another set of adjacent primes other than {1,2,3} 5: 2 + floor(5/2) = 2 + 2 = 4:=> {1,2,3,5} : 4 <= 4 7: 2 + floor(7/2) = 2 + 3 = 5 => {1,2,3,5,7} : 5 <= 5 11: 2 + floor(11/2) = 2 + 5 = 7 => {1,2,3,5,7,11} 6 <= 7 26: 2 + floor(26/2) = 15 => {1,2,3,5,7,11,13,17,19,23} : 10 <= 15 Lagrange's Theorem is Inaccurate Lagrange's theorem about primes states that pi(x) is the number of primes <= x. The pi(x) is approximately x/ln(x). He postulated that the lim of pi(x)/(x/lnx) as x-> infinity was 1. This is incorrect. if the number of primes is bounded by n/2 then refactoring and reducing Lagrange's Theorem results in the lim of ln(x) as x approaches infinity. This is alwa...

How To Cancel ATT Uverse

I was a subscriber to the AT&T Uverse service for a little over 2 years. In that time, we had experienced good service for the first year, and then it sucked. After 12 months, or there in, the service degraded quickly, and would stop working all together at times. At first it would die for a short period of time, usually when we were not home. Then it would get progressively worst, until there was an entire week of no service. We had technicians at the house trying to fix the service, but it would repeat the behavior quite consistently. On January 15th we finally gave up and switched to a lesser service, COX TV and Internet. In the past we had cable service and it was always reliable, but not as good as the AT&T digital service. COX doesn't have nearly as many HD channels, but that's not enough. We needed internet to be reliable, and AT&T couldn't deliver that. Cancelling the AT&T service was a nightmare. Try to find anything about such things on their web s...

DNS Custom Logs and selinux

If you google "named custom logs selinux" you will find quite a bit of chatter about setting up custom logs outside of /var/log for DNS (named). These posts are interesting, but they tend to be run on posts about learning selinux and becoming an expert on named. What you need to know? If you have setup custom logging locations in your /etc/named.conf file, such as:     channel default_file {         file "/var/log/named/default.log" versions 3 size 5m;         severity dynamic;         print-time yes;     }; Then you will likely see errors like this in /var/log/messages: Oct 26 11:41:13 namedsvr setroubleshoot: SELinux is preventing /usr/sbin/named from write access on the directory /var/named/chroot/var/log/named. For complete SELinux messages. run sealert -l 6eab4aaf-e615-4ade-9e88-4efdc789eaf2 Then you run the sealert command as suggested by the very friendly selinux audit log and yo...