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.

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.

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! 🙂

Exploring the Chuo Shinkansen Maglev Route

Not many cars drive on prefectural road 35 near Akiyama, but I’ve cycled there many times on the way to or from Tsuru city during brevets and other long rides. Akiyama’s claim to fame, other than being a charming rural backwater, is it’s Maglev test track, which will grow into a section of the 286 km Tokyo-Nagoya line scheduled to open 10 years from now in 2027.

The test track was built in the 1990s to develop and test prototypes for the train and track, first 18 km in length, then extended to 42 km to be able to test the train at higher speed. The best detailed summary about the route that I’ve found so far that is not in Japanese is this (in German).

Ten years is not a very long time for a project of this scale, especially when there is always the risk of unforeseen difficulties during tunneling (the known unknowns). A 25 km long tunnel will run between Hayakawa in Yamanashi and Oshika in Nagano. Construction has started at both ends. As the Maglev train needs a near level track, this will be a base tunnel at low elevation. Consequently there will be 1400 m of rock above at its deepest point.

Near the end points at Tokyo and Nagoya, new stations will be built under existing train stations (Shinagawa station in case of Tokyo). The lines will run in tunnels at least 40 m underground. Under Japanese law (“Deep Underground Law”), construction at least 40 m below the surface can be done without having to purchase the land above, as long as its purpose is deemed to be in the public interest.

The Chuo Maglev line has been called the world’s longest subway line, as more than 85% of it will be in tunnels. From Shinagawa the tunnel will first run southwest towards the Tamagawa, passing Senzokuike and crossing the river near Todoroki (between the Daisan Keihin and Tokyo Toyoko line bridges).

It continues on the Kanagawa side towards Sagamihara. Avoiding Machida to the south and Tama New Town to the north, it will run south of Onekansen. The first stop after Shinagawa will be near Hashimoto station, to connect it to the existing rail network (JR Yokohama line, JR Sagami line, Keiō Sagamihara line) with proximity to the Ken’ō Expressway. The Maglev line will cross the Sagami river on a bridge, heading between Tsukui-ko and Miyagase-ko.

A 50 ha railway yard for maintenance with train depot is planned near Toya, which my cycling friends mostly remember for the Sunkus convenience store north of Miyagase-ko. From there the line tunnels west through more mountains to the existing test track.

Altogether there will be 9 emergency exits that connect the line to the surface in the tunnel section near Tokyo.

If you check Google maps for the satellite view, you’ll see the test track line emerge to northwest of Tsuru. where it crosses national route 139 from Otsuki to Kawaguchiko. If you drive out from Tokyo on Chuo expressway, you can see the line cross over the expressway on a bridge. There’s a Yamanashi Prefectural Maglev Exhibition Center nearby.

Heading further west into Yamanashi, the line first stays a little south of Chuo mainline and the Chuo expressway, before those two swing northwest while the Maglev route heads straight west. You can see it emerge for shorts covered bridges near Hatsukari, then pop out for longer viaducts as it crosses national route 137 and prefectural route 36 on the edge of the big Yamanashi plain. The current end of the viaduct is at Fuefuki, Yamanashi, according to Google maps.

There will be a station for Yamanashi prefecture in Ōtsumachi near Kofu, with access to JR Minobu Line.

The Yamanashi plain is where most of the above ground distance of the line will be found. The viaduct sections will either have noise barriers or complete covers. A main reason to opt for viaducts in this area is the relatively high water table, which would complicate tunneling.

The debris from 246.6 km of tunnel drilling amounts to 56.8 million m3 (some 145 million t by weight) that will be deposited at locations along the line.

Personally I’m a skeptic about this project. The time savings compared to regular bullet trains are relatively minor, once you factor in that most people will also spend a fair amount of time getting to and from one of the Maglev stations via conventional public transport.

For the people along the line who don’t live in Tokyo or Nagoya, they get one station per prefecture. Chances are, with Japan’s population on the decline, as the new line starts up that train services on the JR Chuo line, which runs somewhat parallel to the Chuo Shinkansen line, will get thinned out. We’ve seen the same thing with bullet train lines that opened that lead to cutbacks on other regional train connections.

So how much time will people actually save, if they don’t happen to live in Shinagawa and want to go to Nagoya or vice versa? Even Nagoya is only a halfway solution without the extension to Osaka that isn’t scheduled to be completed until 2045 (or 2037, if the central government steps in with a huge loan).

I think the only thing we can say with any certainty about benefits from the project is that, yes, the construction companies and the suppliers of equipment will benefit handsomely. Drilling and lining 247 km of tunnels with concrete and pouring some more of it for 24 km viaducts and 11 km of bridges will make them some money but will add a fair amount of CO2 to the atmosphere. The air resistance of trains at 505 km/h and therefore their energy consumption will definitely be higher than that of conventional trains. One source I saw listed it as having a CO2 output of 2-4x that of conventional commuter trains (not sure how those compare to a shinkansen).

Nevertheless, the dice have been cast and construction is under way. I will try and find more information about where construction is going on and what parts can be explored on bike rides or visited. You can already get train rides at the Maglev visitor center in Tsuru. There was some discussion of extending the test track 7 km to the west and building a station by 2020 to be able to offer test track rides as far as Kofu by the Olympics but without the Kanto connection that seems like a gimmick to me. I doubt that’s going to happen, as all kinds of construction projects are already competing for capacity before the magic Olympic year, driving up prices and busting budgets.

Disc brakes on my Bike Friday (part II)

As I explained here almost two years ago, I have had the front brake of my Bike Friday replaced with a disk brake, an upgrade that involved installing a new fork with disk brake tabs. Now I’m having the same upgrade done one the rear:

I needed to replace the rear wheel anyway because after 37,000 km its rim was worn out. The aluminium of the brake surfaces was already worn past the wear markers. I decided, this was a good time to switch not only the rim but the brake too. With disc brakes, a well built rim will basically last forever. The brake wear will be on the rotor, but that is a cheaper part that can be replaced without the need for a full wheel rebuild. But more importantly, disc brakes are much more effective in the rain, where they are more predictable. I was reminded of that fact again when I descended a winding 20 km from Mt Norikura in the rain last month.

Originally I thought I could get IS disc tabs at the rear by simply swapping the rear triangle, which is a separate hinged part of the folding bike frame, but as it turns out Bike Friday needs to build the main tube and its hinge together with the rear triangle to ensure they will be properly aligned.

I went ahead and placed an order. A couple of weeks later the new main tube and rear triangle arrived. Tokyo Bike Friday dealer ehicle will be swapping all other parts from the existing bike to the new hinged section that has the disc tabs.

I bought a second Shimano BR-CX77 disc brake calliper. I still had a 140 mm centerlock rotor that I had bought two years ago as well as the matching IS adapter. The smaller rotor should be sufficient at the rear, especially with the smaller 20″ wheels. Heat dissipation should be less of a problem for a rear brake, which normally doesn’t have to work as hard as a front brake. I never had any heat problems with the 160 mm rotor at the front.

GS Astuto, my favourite wheel builder, built me a new rear wheel based on the Shimano Deore FH-M615 rear hub and an AlexRims DA22 rim (same as originally came with the bike). The disc brake wheel uses an O.L.D. (Over Locknut Dimension) of 135 mm, but the existing rim brake rear triangle uses 130 mm. Therefore installing the new wheel in the existing frame before the Norikura ride required some effort, but it worked OK. With the new rear triangle that issue will go away.

Once the conversion will be complete, I’ll actually have a spare main tube and rear triangle, a spare fork, two spare rim brakes and two spare hubs. The only frame parts missing to a complete non-disc brake frame will be the steerer and the folding seat tube 🙂 Nevertheless, doing it this way will have been worth it.

Instead of buying a new bicycle, I could first try out at the front what difference a disc brake would make, making only the minimal investment. I never had to send my bike back to the US for a few weeks for an upgrade or pay shipping costs either way. I only lost the use of the bike for a short period for each of the upgrade steps.

I’m looking forward to riding my upgraded bike this weekend, when the work will be complete! 🙂

Disc brake pad and rotor wear

It looks like I get about 6,000 km of useful life out of the disc brake pads on the front of my main bicycle. That’s about 9 months for me (I ride all year round, about 8,000 to 10,000 km per year).

Two years ago I switched my Bike Friday Pocket Rocket to a disc brake on the front by replacing the fork and the front wheel. 1 1/2 years ago I received my Elephant Bikes National Forest Explorer (NFE), a low trail randonneur bike with disc brakes. 9 Months ago I switched the NFE from TRP Spyre mechanical disc brakes with metallic pads to Shimano hydraulic brakes with resin pads. These pads had now worn out, see picture above.

Along with the brake pads I also replaced the front rotor, as the old one had worn quite thin.

Most of the 7,000 km that I had done on the TRP Spyre brakes I had been using metallic pads, as the factory resin pads wore extremely rapidly: I had to keep adjusting the brakes after each Saturday long ride (typically 130-200 km). The metallic pads needed less attention but were very noisy in the rain.

My experience with the Shimano BR-RS785 brakes was much better. As hydraulic brakes their pads were self adjusting. There weren’t any noise issues. Wear is quite acceptable: One set of resin pads every 9 months is not too bad and I expect the new brake rotor will last even longer than 13,000 km / 20 months now that I am only using resin pads. On top of that the modulation on the hydros is great and they need very little effort. I could not be happier!

It is good to have real-life figures from actual use as to how quickly parts will wear on the bike so you can do preventive maintenance. It is better to replace a worn out pad at home when you know that it will be due for replacement soon, rather than finding out on a mountain descent that suddenly you’ve got nothing left to stop you! 🙁

Likewise, I regularly replace shifter cables (about once a year), before they wear out enough to break inside the brifters during a ride away from home, as happened twice to me before I learnt that lesson.

In the past I have been quite easygoing about replacing worn out bicycle chains, but a chain that has “stretched” will wear out your chain rings or cassette more quickly. Chains do decrease in robustness with increasing numbers of gears (from 8 speed to 11 speed) as they increasingly become narrower, so I will probably be replacing my 11 speed chain annually too.