BRM414 300 km Fuji, Wet and Windy Edition

On Saturday/Sunday I cycled in the 300 km brevet around Mt Fuji organised by AJ NishiTokyo, like in the six previous years. Last year I set a personal best time of 18 hours 51 minutes, which is 1 hour 9 minutes under the 20 hour time limit. This year I was not so hopeful. As the day approached, the weather forecast had turned increasingly worse, finally predicting heavy rain and very strong winds on the course between midnight and about 10:00 on Sunday morning. As it turned out, that forecast was spot on!

I had done the 300 km Fuji brevet in the rain once before, in 2014 (see pictures here), but this time turned our far worse.

After getting a couple of hours of rest on Saturday afternoon, I cycled 28 km to Machida for the late night start (22:00). In 2014 I had taken the train there and it had already started raining on the way from Machida station to the event starting point. We then had the pre-ride briefing inside the Cherubim bike shop. This year the rain held off until almost 40 km into the brevet, on the way to Enoshima.

At the start

The crowd at the start was much smaller than usual. As it turned out, most signed-up would-be participants had chosen not to start (DNS) due to the weather conditions. I had cycled to the start in my rain wear, but took it off at a convenience store near the start because I was starting to sweat in it. Four years ago I had worn my Polaris rain jacket, which is even warmer. For fear of overheating I went with a lighter jacket this time.

At the briefing we were told about two of the bail-out options, should we chose to retire from the ride. Both Odawara and Gotemba have train stations, but by the time we were to arrive there, the last trains would have left. Nevertheless there would be places around the stations where we could take shelter from the weather until the first morning train.

After the bike inspection we set off. It was quite windy, but no rain yet. Up to Enoshima on the coast I rode more by myself than in a group.

A couple of km before we reached the coast the first rain drops started falling and it steadily picked up. The first check point was a 7-Eleven store about 2 km east of Enoshima. I got there about 10 minutes to midnight.

When I came out of the store again the wind was fierce, whipping up sand off the beach which hit our faces and got on our teeth and into the eyes. The road was narrowed for some roadworks, so being pushed around while cars were passing wasn’t pleasant.

I was worried I’d be cycling into a headwind on the way to Odawara, but the wind pattern wasn’t very consistent. Whichever way it shifted though, it did slow us down. Also, there was little chance for riding with others.

When I reached PC1 (point de controle) in Odawara, 72 km from the start and 100 km from home for me, it was 40 minutes later than last year. I knew I had to get well ahead of the 15 km/h average that dictates control closing times and the overall time limit while I was on the flat part of the course to make it to PC3 in time, after hours of climbing on the west side of Mt Fuji later in the day.

After Odawara I put on my do-it-yourself shoe covers, fashioned out of some plastic bags and tape, to keep my shoes and socks dry. Nevertheless, as I started climbing up to Gotemba, which sits on a saddle between the Fuji and Hakone volcanoes, gradually I was getting soaked more and more. My long sleeve jersey and my uniqlo long johns were absorbing cold rain that leaked through the rain gear. I think my Polaris rain jacket would have done a much better job at keeping me dry.

I cycled with another participant for the middle part of the climb, but then stopped at a convenience store for food and a toilet break. My eyes started getting irritated. Either the rain was washing sweat into my eyes, or it was sand stuck to my face since Enoshima that got washed into my eyes. Taking off my glasses and wiping my eyes with the back of my gloves or the fingers didn’t help much.

The climb leveled off near Gotemba but the wind and rain were still picking up in intensity. At this wind speed the rain drops felt like pin pricks to the skin. At dawn the atrocious weather and the near absence of people gave the scenery an almost apocalyptic feel. From here it was about 25 km downhill to Numazu, but with no prospect of the weather improving soon. This was perhaps the coldest part of the course due to of the combination of rain, early morning hours and wind chill while descending. I was already shivering with cold while alternating between closing my left and my right eye to avoid the burning feeling.

Checking my notes, I was now running about an hour behind my 2017 times. The lack of a time buffer already made it questionable if I could make it to PC3 in time even if I could make it to PC2 OK. On this course my time buffer usually decreases significantly from PC2 to PC3 due to the time loss on the long west Fuji climb.

More importantly, the combination of eye trouble, hypothermia symptoms and the strong wind made me think about the risks of continuing. Even if I could coast down to Numazu, if I had to abandon the ride after that I would have to climb back up to Gotemba to get back home or ride the full course. That’s when I, remembering the advice at the pre-ride briefing, decided to find shelter from the storm in Gotemba and to head back to Odawara once things had improved.

Two or three other cyclists passed after I turned around and I shouted out to one of them that I was retiring. I found a McDonald’s on Google Maps that was open 24h and not too far away. I locked up my bike outside and walked in with my front bag. I bought myself some breakfast with coffee and sat down in a corner. I could take off my rain jacket to let my jersey dry. After eating I took a nap. When I woke up again it was still raining hard. Around 08:00 I called the organizers and let them know I was retiring from the event and would cycle home by myself.

An hour later it looked like the rain had eased a bit. I cleared my table and headed outside again. It got warmer as I descended towards Odawara. I took pictures of the muddy, swollen rivers I passed.

After about another hour the rain stopped. The black and grey rain clouds against the sunlight at the coast were beautiful.

I joined the coastal road and headed east, past Enoshima to Kamakura.

There I crossed the mountains over to the Tokyo bay side of Miura peninsula, then up to Yokohama and Kawasaki. I got home about 24 hours after I had set off, with 283 km of cycling. I hadn’t caught a single glimpse (let alone taken a picture) of Mt Fuji, but I was glad to be home safely.

This definitely wasn’t the most fun bike ride I have done, but unlike other difficult rides I have done, I also didn’t get much of a feeling of achievement out of it — the first time in 7 years that I didn’t complete the Fuji loop. Perhaps this is one time I should have decided to stay home when I saw the consistently bad weather forecasts. It would have been the rational thing to do. But for me, long distance cycling is not that rational a thing to do. Much of it is a mental challenge as much as a physical one.

I do long rides because I love the views, but partly I also do long rides so I won’t be afraid of doing long rides. They can be intimidating. I can take on bigger challenges only because I have faced smaller challenges before. You overcome fear of being stranded in a strange place by venturing out there and facing the challenges. Sometimes I learn something about myself from the experiences. It can be a balancing act. I am never 100% committed to achieving my immediate goal, because there are more important objectives. To be able to continue doing long rides, I can’t get seriously injured or worse, so I need to decide what risks to take and when to cut my losses.

My next brevet will be BRM512 AJ NishiTokyo 400 km Fuji Big Loop (BRM512富士大回り400km), a course I also rode in 2015 and 2016. Hopefully with nicer weather than last weekend 🙂

Links:



PC Closing Times in Randonneuring

Brevets / Randonnees are timed events in which cyclists ride a pre-determined course, passing a number PCs (points de controle) and completing the overall course under a time limit. It’s not a race and results are not published ranked by completion time. The overall time limits are:

  • 200 km – 13:30 h
  • 300 km – 20:00 h
  • 400 km – 27:00 h
  • 600 km – 40:00 h
  • 1000 km – 75:00 h

These limits mostly correspond to an average speed of 15 km/h, including all breaks for rest, food, sleep, etc.

Each PC also has a defined closing time. Before a recent brevet, I took a look at the PC closing times in a cue sheet and it seemed the first PC was open too late, i.e. later than what would correspond to a speed of 15 km/h from the event start time to the PC, but it turned out to be the correct time.

Today I had a look at the official regulations and found out why. Basically, the 15 km/h equivalency only applies above 60 km and until 600 km. For any PC in the first 60 km of the course, the closing time is one hour after when you would arrive there at 20 km/h (both formulas arrive at the same result at 60 km: 4 h * 15 km/h = 60 km; 3 h * 20 km/h = 60 km). This provides a sensible rule for participants who start later than the course opening time, for example because they arrive late or because the event has so many participants that it takes a significant amount of time for all of them to cross the starting line. A ride starting at 7:00 could have a final starting time of 8:00 and people can still make check points as long as they maintain an average of 20 km/h, making up the time within the first 60 km.

The average speed required after reaching the 600 km mark also drops, to 11.428 km/h between 601 km and 1000 km. In a 1000 km brevet, participants have 35 hours for the final 400 km vs. 40 hours for the first 600 km. This provides more time for sleeping on longer events.

Participants at Paris-Brest-Paris (1200 km) also have more time for the return journey from Brest than they have on the way out. In the slowest category, participants have 90 hours for the complete trip, vs. 40 hours for the first half, leaving up to 50 hours for the second half.

I understand the rules for control closing times a bit better now.

Personally, I am too slow to leave enough time for more than extremely short naps on a reasonably hilly course, such that I am unable to complete anything over 400 km because I end up with too much of a sleep deficit after about 27 hours. Therefore I will probably never experience the benefit of the more relaxed control closing times that come it after the 600 km point.

I’ll be riding a 300 km brevet coming Saturday / Sunday and the trick, as always, will be to get enough sleep upfront to be able to make it through the (20 hour maximum) course without getting too sleepy during the event 🙂

Getting ready for BRM414 NishiTokyo 300 km Fuji

A week from now I’ll be riding BRM414 NishiTokyo 300km Fuji (BRM414西東京300km富士), a 300 km clockwise loop around Mt Fuji from Machida to Machida (Sat, 22:00 -> Sun, 18:00).

In May 2012 this course was my introduction to randonneuring and I’ll be riding it for the 7th consecutive year.

This year the course has been updated in a couple of places. The checkpoint at Enoshima has moved from the public toilets near Katase-Enoshima station to a 7-11 further east. PC1 in Odawara has also been moved to a 7-11 with better toilets. PC2 in Shibakawa is in the same place, but has switched from being a Circle K to a Familymart. Around Kawaguchiko-Fujiyoshida the route has been moved from N139 to smaller roads nearer to the lake, avoiding some of the notoriously rough road surfaces there. The rest of the route is the same as last year.

The 22:00 start followed by 7 hours of riding through the night makes it essential to get plenty of sleep before the start. I’ll take a good nap in the afternoon before I ride 28 km to the start. Some rain is forecast for Saturday. Hopefully the ride itself will be dry, but I have once done this course with it raining for the first 150 km, which is not much fun (and it’s a pity if Mt Fuji is obscured by rain clouds).

This weekend I will be riding another century distance (160.9 km or more) as my last preparation ride before the event. This should make April my 68th consecutive month with at least one century ride.

Picasa: “Failed to download album list”

If you are still using the Picasa 3 desktop application by Google and got the above error message, here’s some bad news for you: Google has finally killed this app. On March 26, 2018 they announced that it would no longer be able to upload new albums. So this error message is not temporary and there is no direct fix.

I think it’s very regrettable that Google has been killing off Picasa step-by-step. This is only the latest nail in the coffin. I had been using Picasaweb and Picasa since 2010 and they were great products.

The good news is that you can still create albums from folders using a web browser. Say you have a folder named “2018-03-26 Cherry Blossom Party”. Just follow these steps (for Windows and Chrome):

1) Select its parent folder in Windows Explorer, then slowly click on the folder that you want to upload, twice: Once to select it, then once more to enable you to edit the folder name as if to rename it. When the name becomes editable, press Ctrl+C to copy the folder name, then press Esc to keep the name unchanged. This stores the folder name in the copy-and-paste clipboard, which will save you from having to manually retype the name later.

2) In Chrome, go to https://photos.google.com/ and click on “Upload” (on the top right). A file selector dialog will open up. Click through to the contents of the folder you want to upload. Select all files in the folder using Ctrl+A and click “Open” to confirm the upload.

3) The browser will upload all files and give you a choice of “Add to album” or “Shared album”. Select “Add to album”. To create a new album with the name of the folder, select “New album”. Click on the album name showing as “Untitled” and use Ctrl+V to paste the name you copied in step 1. Hit Enter and click on the check mark to confirm creation of the new album.

Voila, you have a new album online, with the same name as the local folder. Repeat as needed for multiple folders. This is as simple as it gets without the old Picasa app.

Strava Cycling Climbing Challenges

Strava is a popular service for logging bike rides and other activities, which provides a way of comparing one’s achievements with those of other cyclists and runners. Competition is a powerful stimulant and a main driver behind the success of the service. Monthly “challenges”, such as a Gran Fondo (a ride of at least 100 or 130 km, depending on the time of the year) or a monthly cumulative distance or elevation gain challenge, are particularly popular on Strava.

While I regularly participate in the Cycling Distance and Gran Fondo Challenge, I do not normally sign up for the Cycling Climbing Challenge, which is meant to encourage you do ride hilly courses. I love hilly courses. In fact, most of my weekend rides are hilly, usually going from close to sea level to over 900 m and back.

Last year I averaged one century ride (at least 160.9 km / 100 miles) about every other week, so the Gran Fondo challenge is not really that much of a challenge for me. My typical centuries are about 170-190 km with 1800-2100 m of elevation gain. Yet at 7500 to 8000 m the goal for the Cycling Climbing Challenge is set so high, I could do a hilly century ride four Saturdays in a row and still miss the climbing goal. So how do other people, who do not ride 170 km into the hills every other weekend complete the climbing challenge?

I think the Strava climbing goals are designed for people who record their rides with phones or other GPS devices that rely only on satellite data for elevation. GPS-based elevation data is much less precise than lattitude-longitude data. Other popular GPS units like the Garmin Edge 1000, Garmin Edge 520 (or my o_synce Navi2coach) use a barometer for more precise elevation tracking. The problem with GPS-based elevation is that it’s noisy, it will go up and down pretty randomly but all those little ups will be added up by Strava, resulting in a considerably inflated climbing total. If you’re using a GPS device measuring relatively accurate barometric elevation, you can’t really compete against all that noisy data 🙁

I could confirm this in group rides with other people who were using mix of equipment, where I had a chance to compare the posted stats on Strava afterwards. The iPhone or Android-app recorded totals were often 50-100% higher than the Garmin-recorded totals, for one and the same course.

Here is one random example of 4 people doing the same course up a volcano in Tenerife, Gran Canria yesterday. Note, this not my ride, I just randomly stumbled on it while looking at high scorers in the March Cycling Climbing Challenge on the Strava website. Two of these cyclists were using the Strava iPhone app, the other two were using a Garmin Edge 520:

Strava iPhone App:
https://www.strava.com/activities/1437744625
5,080m

Strava iPhone App:
https://www.strava.com/activities/1437728113
4,635m

Garmin Edge 520:
https://www.strava.com/activities/1437709764
2,847m

Garmin Edge 520:
https://www.strava.com/activities/1437730812
2,556m

As you can see, the two cyclists using the phone app posted almost double the total climbing for the course as the Garmin users, despite riding the very same roads and posting the same elevation profile for the activity (i.e. no hill repeats).

Based on evidence like that, I don’t think elevation gain competitions on Strava are happening on a level playing field! 😉

2018BRM120 Miura Peninsula

I rode my third century of January and my first randonnée of the year on Sunday. After completing the 204 km ride (finished in 12:04) I rode home, for a total distance of 233 km. I had done the same event in 2015 – with only minor route changes – and almost the same time (12:06).

The main difference was that on Sunday it was not quite as chilly. Perhaps that was because it was overcast, which preserved more heat from the day before than if the night sky had been clear. It also meant that the sun wasn’t in our faces (and the faces of drivers coming up behind us) when we cycled towards Kawasaki around sunrise. I felt a lot safer because of that.

This brevet is the flattest by far of any events that AJ NishiTokyo (my local club) organizes. On the other hand, the first third and the last quarter had a fair number of traffic lights. Still, there was less pressure to make closing times than on any other brevet I rode.

I had to be at the start by about 5:20 to pick up the brevet card and attend the safety briefing, so the night before I rode 30 km from my home to a cheap hotel near the start where I spent the night. This I could still get almost 7 hours of sleep. Perhaps I’m getting soft in my old age 🙂

After passing by the Yokohama harbour near Chinatown, I took the optional route over the hills. This is where a lot of foreigners set up their homes when Japan opened to the world after the arrival of Commodore Perry’s Black Ships. On the Yamate district up on a hill you see many western style villas, a great view of the harbour and the historic Foreign Cemetery.

From Kawasaki to Yokohama down to Yokosuka the roads were urban, with traffic lights slowing you down. Yokosuka is home to the US Seventh Fleet. Not far from it is where William Adams (the Miura Anjin of James Clavell’s “Shogun”) had his fief back in the 1600s. The peninsula turns rural thereafter.

It was too overcast to see the mountains of Boso peninsula in Chiba, on the opposite side of the mouth of Tokyo bay. At Kurihama I passed Perry Park, a memorial to Commodore Perry who landed here in July 1853.

Following the coastline the route passed through seaside towns and fishing villages. Miura peninsula is one of the vegetable gardens of Tokyo, with mainly cabbage and daikon (radish) being grown.

After PC2 in the southwest corner of the peninsula, the route headed up the west coast. This is my favourite part, particularly in the late afternoon, with the sunlight reflected in the ocean, or when it’s cloudy and the sky can be very atmospheric. We passed the Imperial villa at Hayama. Emperor Yoshihito, father of WW2-era emperor Hirohito, died here in 1926.

A couple of km to the north we passed by Kamakura, one of the 4 historic capitals of Japan (Kyoto, Nara, Kamakura and Edo/Tokyo). In summer it’s popular for its beach, but even in winter there are many windsurfers (see picture at the top).

The next major town was Enoshima, which offers great views of Mt Fuji when it’s sunny, but not that day. Before the mouth of the Sagami river we turned inland, heading up north to loop back to the start. About 5 km later we reached PC3, that final control before the goal.

By this time I was about 1:15 ahead of closing time, so I could have made it to the goal even with an average of 10 km/h. I still kept up the speed to cover as much distance as possible before the sun went down. I only rode about the last hour in darkness, plus the ride home after the event.

Due to business travel my February distance will be lower than my January distance, but I’ll try to get one century in on the first February weekend, weather permitting. Today it’s snowing here in Tokyo. Usually we only have a couple of days of snow a year and this makes CaM a lot easier here than in many other parts of the planet.

Swisscoin (SIC) Crypto-Currency Spam

When crypto-currencies like Bitcoin (BTC) were first introduced, they were claimed to offer the potential of a low-cost, frictionless international payment system. This has not really happened, as BTC turned out to be severely restricted on the volume of transactions it could handle. From then on, it increasingly became a vehicle for criminal transactions (including fraud) and speculation.

In the past twelve months, people have been buying BTC and other crypto-currencies primarily because of the expectation that they could later sell them at a profit. This has allowed existing holders of crypto-currencies to do precisely that. This is very much how “pump and dump” scams operate, usually involving unlisted (OTC) stocks.

“Pump and dump” scams used to involve selling by phone, but in recent years many switched to email spam. Now we are seeing crypto-currencies being advertised via spam. One example is Swisscoin (SIC), as in this email received on 2018-01-16:

It’s probably not news to you at this point if I tell you that bitcoin has made tons of people tons of money. Something else you probably already know is that it will never go up like crazy again. Its time to shine is long gone. That’s why we must look into what the next big thing is, and the truth is that there have been plenty over the last few months. Can you jump on the next huge one before it soars? Swiss coin {SIC} is the most likely candidate for a fifty thousand percent return this year. It has the support of the Switzerland government. It is already considered as legal in the country. It’s the type of coin that you can buy a thousand bucks of right now, sit on for a small period of time and you could make out crazy wealthy when all is said and done. SIC has already doubled since Saturday. This long Martin Luther King weekend could bring you even more upside if you act quickly. For those of you who know what this means- you can get it for under 50 satoshi right now. And if you have no clue what this means, it basically means that you can get in on the ground floor How do you get some? You just need an account at coinexchange. Read the currency’s official page to find out more info: https://swisscoin.eu/sic-deposits.html

The truth is, far from “having the support of the Switzerland government”, Swisscoin / swisscoin.eu is listed on a warning list by FINMA, Switzerland’s independent financial-markets regulator. The Swiss company listed in the FINMA warning did not have an office there. It was founded with a capital of only CHF 20,000. Its officers are based in Leipzig, Germany.

There is no “ground floor” opportunity for Swisscoin. It has been marketed via MLM since 2016 and various people called it a Ponzi scheme. The Dynamoo blog writes in a recent post:

There are questions as to whether Swisscoin is actually a cryptocurrency or a Ponzi scheme. Honestly, I don’t know and I’d advise you to do your own research. However, this has all the markings of a pump-and-dump scheme, so it’s quite possible that someone who bought Swisscoins at their peak wants to pump the price up so they can sell off their holdings. Given that the spam is being sent out from a network of hacked machines and does not comply with anti-spam laws, you can pretty much guarantee that this is not legitimate and should be avoided.

Never buy anything advertised via spam!

Carbon Sink Concrete Snake Oil

When I was a kid, I learnt that carbon dioxide (CO₂) makes up around 0.3 % (300 ppm) of the atmosphere. Man-made CO₂ output, from burning of fossil fuels to deforestation, has increased this number year after year. In 2013 it first exceeded 400 ppm. Even back in the 1950s, after over century or coal and oil burning, the number was already the highest in 650,000 years. We are still adding CO₂ to the atmosphere every year and the amount being added per year is still increasing. As CO₂ is a heat-trapping greenhouse gas, this has far-reaching consequences. There are dangerous feedback loops that will amplify the consequences, from increased arctic warming from absorbed sunlight due to melted sea ice to increased methane output from melted permafrost regions. Disappearing mountain glaciers will have effects on rivers downstream.

As humanity realizes the dangers from changing climate, from rising sea levels to extreme weather patterns, devastating droughts and wildfires, desertification and failing harvests we need to take action. We will need to cut CO₂ emissions as much as possible as soon as possible, but we also need to look at ways of binding CO₂ that has already been released.

Some people are trying to make a quick buck on this or to deflect consequences from industries that harm the environment. Because of this, be very skeptical of any claims made for carbon sink technologies that aim to delay the phasing out of fossil energy sources (including but not limited to “clean coal”).

A couple of years ago a US company called Calera made headlines with bold claims of a process that could act as a carbon sink for CO₂ from fossil fueled power stations while producing a product that could be used in place of cement. About 5 % of global CO₂ output is from cement production while power stations account for about 1/3 of CO₂ output in the US, therefore this would sound like a win/win situation. The process would extract calcium from sea water, combine it with CO₂ from the smoke stack of a power station and output calcium carbonate (lime stone) as a building material. Calera received funding from ventures capital fund Khosla Ventures and built a prototype plant adjacent to the Moss Landing power station at Monterey bay, California.

The company has always remained fairly tight lipped about how its process would actually work and what its inputs and outputs would be. However, despite the numerous articles that repeated its ambitious claims, nothing much seems to have come off it since.

The fact is, their claims were debunked by two critics, Jerry D. Unruh and Ken Caldeira, but relatively little attention was paid by the media to the inconvenient facts they had pointed out.

Most of the calcium and magnesium dissolved in sea water is either in the form of calcium bicarbonate or magnesium bicarbonate. To precipitate dissolved (Ca,Mg) bicarbonate as solid (Ca,Mg) carbonate, one has to remove CO₂, not add it. Calcium and Magnesium dissolved in the ocean is there because rain water absorbs CO₂ from the atmosphere and then dissolves lime stone and dolomite rock as it seeps down into the ground before re-emerging in springs and rivers:

H₂O + CO₂ + CaCO₃ => Ca(HCO₃)₂
H₂O + CO2 + MgCO₃ => Mg(HCO₃)₂

Precipitating solid carbonate from dissolved bicarbonate reverses the process and thus releases CO₂:

Ca(HCO₃)₂ => CaCO₃ + H₂O + CO₂
Mg(HCO₃)₂ => MgCO₃ + H₂O + CO₂

Fundamentally, calcium and magnesium ions (Ca++, Mg++) in sea water are not a viable option for binding millions of tons of CO₂ as they are already the end result of a carbon-binding process. Turning bicarbonates into carbonates either releases CO₂ or it requires huge amounts of alkaline materials to bind that CO₂.

The truth is, besides CO₂ and seawater, Calera’s prototype plant consumes existing stocks of alkaline magnesium oxide left over from previous industrial uses at the site, but those stocks won’t last forever. If one had to replenish these stocks from scratch year after year, this typically would involve the high temperature calcination of magnesium carbonate, which consumes roughly as much energy and produces as much CO₂ as making cement does.

Calera has suggested a few alternatives in place of magnesium oxide as alkaline process inputs for a full scale production system, but these don’t make much more sense either:

  • Making sodium hydroxide from brine via electrolysis consumes more electricity than can be produced from any power station whose CO₂ this process could clean up.
  • Fly ash from power stations can be a low cost source of alkalinity, but only in the case of relatively carbon-heavy coal and not natural gas. Even there the amounts of ash are far too small relative to the amount of CO₂ to be absorbed from burning the coal. Cleaning up CO₂ from coal using fly ash still leaves you with more CO₂ than burning natural gas without cleanup.

Long term, the cheapest way of dealing with rising CO₂ levels are not carbon sinks, but not producing the CO₂ in the first place. This means reducing energy consumption, a halt to deforestation, switching transport to electricity and producing power from wind, solar, geothermal and other non-fossil energy sources. The sooner we do this, the more livable this planet will remain for its 7 to 12 billion inhabitants this century.

Further reading:

Twenty-Seven Centuries in one Year

By the end of this year I will have cycled just over 8,000 km, slightly less than in the last couple of years (I cycled about 9,000 km in 2013, 2014 and 2016 and topped 10,000 km in 2015).

At the same time, the number of century rides (rides of at least 160.9 km aka 100 miles in one day) has actually gone up. In 2012, my first season of century rides, I completed 11 of them. Both in 2013 and 2014 I rode 21. The next two years I managed 22 each. This year, with one week left to the end of the year, the total came to 27 centuries.

The biggest difference has been that I didn’t participate in any 400 or 600 km brevets this year due to my business travel schedule. Both in 2015 and 2016 I had signed up for one 400 km brevet (which I finished) and one 600 km (which I DNF’ed). Both years I also pre-rode the 400 km route on a personal long distance ride. So I missed some distance overall, but most months I managed to ride 2 or 3 centuries. It’s all about being consistent.

With my December rides I have extended my “A Century A Month” streak to 5 years and 4 months. To ensure that I can keep this up, I usually do a long ride on the first weekend of each calendar month. That way, if anything comes up later in the month, such as a typhoon hitting Japan or me having to travel abroad, I won’t have an issue.

One of the most important factors no doubt is to avoid injury. Many of my friends have been involved in road accidents. A broken collarbone or other severe injury could put you out of action for weeks or months. Any kind of road sport has risks, but I try to limit my exposure. I am not a very ambitious descender because with anything that happens at high speed, the negative effects will be magnified. I am not ambitious when cycling in a city either. Where I work hardest is on climbs, because I need to 🙂

I have been very pleased with my Elephant Bikes National Forest Explorer. Last year I converted it to 11 speed with a Sugino “compact plus” double crank and hydraulic brakes. It has been fun to ride and extremely reliable. The ride comfort from the 42 mm Compass tires is terrific and I have been without puncture for 20 months now. I still ride my Bike Friday Pocket Rocket as well and had its rear converted to a disc brake a couple of months ago.

The main attraction of long rides to me is the views I come across, at all times of day, in all kinds of weather and in all four seasons. I ride to see things, by myself or with friends.

Here are some pictures from one year of cycling:

January: BRM107 by Audax Japan Kanagawa – Zushi-Izukogen-Zushi 200 km

January: Doshi village on my Bike Friday

February: Boso Peninsula via Kurihama Ferry across Tokyo Bay (cycling to and from Miura peninsula)

March: Mt Dodaira in Saitama, visiting the observatory

March: BRM318 in West Izu, the hardest 200 km brevet I ever rode

April: BRM408 in Yamanashi, the 3rd 200 km brevet this year

May: Ome Temple Loop, a very mountainous course in Saitama that I normally only do once a year. I did it twice this year 🙂

May: BRM520 around Mt Fuji — my fastest ever finishing time on this 300 km brevet

June: Doshi village for coffee and cresson cake.

July: Some hydrangea blossoms at a mountain ride in Hinohara with friends.

July: Tokyo/sea level – Mt Fuji 5th stage/2300 m – Odawara/sea level (first time in 4 years that I rode this course again)

August: First ride on Arima Toge in Saitama

September: First ride on Nokogiri Toge

October: A hunting falcon at Lake Okutama

November: Annual Chichibu Foliage Ride

December: West Izu Century (view from Kumomi Onsen towards Mt Fuji, 72 km away)

Downloading routes from RouteLabo (Yahoo LatLongLab)

Most of the brevets I ride are with AJ NishiTokyo, a randonneuring club based in the Machida/Sagamihara area. One thing I like about their rides is that they provide a link to a RouteLabo page for each event (RouteLabo is an online map service run by Yahoo Japan). This page shows a map of the course as well as download links for KML, GPX and TCX files of the course. By copying these files to your GPS device (Garmin or other) or by uploading a KML file to Google “My Maps” for your smartphone, you can almost completely do away with the need for paper cue sheets. I navigate all my brevets and many of my personal rides by following a “breadcrumb trail” on the screen of my GPS unit.

Unfortunately other clubs often only provide a map without any download option, like this Randonneurs Tokyo 2018 BRM421 Tokyo 600 Lake Hamana (BRM421東京600浜名湖鰻) page:

This does not help you much on the road. Without a link to the full RouteLabo page with download links, there’s no obvious way to obtain a GPX or KML file. You are still expected to navigate via printed turn instruction on a paper cue sheet, which I find cumbersome and error-prone.

However, there is a way!

The web page uses some Javascript code to display the map off the RouteLabo website, including a magic value that identifies the particular course to be shown. To see this value, view the source code of the page. This step varies by browser and operating system. On Chrome under MS Windows, Ctrl+U will show the source code, on a Mac under Chrome, Option+Command+U will do it. On Safari, once you enable the option via Safari > Preferences > Advanced > Show Develop Menu, you can also use Option+Command+U (just like in Chrome).

In the displayed HTML code, search until you find a line for Javascript like this one:

<script type="text/javascript" encoding="UTF-8" src="https://latlonglab.yahoo.co.jp/route/paste?
id=b86f940851b6ebed2538ffc5f80b2fc8&width=480&
height=640&mapstyle=map&graph=true&maponly=true"></script>

The value consisting of 32 hexadecimal characters (128 bit) after “id=” is the magic value you’re looking for. A full RouteLabo page URI with the download options will look like this:

https://latlonglab.yahoo.co.jp/route/watch?id=b86f940851b6ebed2538ffc5f80b2fc8

By replacing the value after “id=” in the URI with the ID from inside the HTML code using copy and paste, you will get a browser URI that will give you full access to the route, including route file download links to feed your GPS device of choice. You can then bookmark it for future reference. Bonne route! 🙂