Total Members Voted: 2
There are supposedly huge cost savings to do rail and road simultaneously, especially high-speed rail and those super highways, but also for more modest projects. Construction is easier and cheaper, you cut the land once instead of twice, their requirements for curvature and gradients are similar. The rail lines are usually in the middle, but alternatively may be elevated into viaducts.
That definitely goes for bridges and tunnels as well. Arguably it may sometimes make sense to pre-emptively include rail capabilities to a bridge. If the rail project fell through or is delayed the space could be used for more road capacity. Bicycle and pedestrian path should be there as well, though not on a 30+ km project like this.
I suspect that's partially because they were (originally) constructed decades or in some cases centuries apart. Rail infrastructure goes back a long time.
Bicycle and pedestrian path should be there as well, though not on a 30+ km project like this.
Travelling through the endless forests of Canada, Scandinavia, and Russia is incredibly boring.
I suspect not piling everything up in one single super-booperbridge is not at all bad for security reasons. (However, nothing will help if Katsung visits the neighbourhood.)
Why? An hour's trip.
For you?I reckon it's romantic. Let alone the popping time to time up of small semi-rural stations when babushki wait for you to jump out and buy a packet of hot potato and some other snack.
The problem, Jax, is that the train's engineer is not immune to falling asleep. If it can happen to drivers of cars, it can happen to the operator of the train's controls.
Take note, China
On a related note, there's already e.g. a driverless metro in Lille and a driverless terminal train thingy in Detroit Wayne Airport. And that's just two I personally came across.
Agreed. The 32km long Afsluitdijk is very popular with cyclists. The cycling path was an integral part of the original construction plans, as it is in the 2016 renovation plans. jax shows that he is neither Dutch nor Danish, despite my earlier emphasis on cycling outside of the (inner) city. Another nice example of a cycling path can be found at one of the most impressive feats of 20th century Dutch engineering, the Oosterscheldekering.The structure itself is a mere 8km, but if you look at it on the map you'll realize the distance from e.g. Middelburg to Zierikzee is 42km.This is why cycling actually works in the Netherlands. Infrastructure. Saying a bridge is 30km so people won't cycle there is just a Catch 22. One that's easily disproved by 80 years of Afsluitdijk. Take note, China.
Just remembered Frenzie (as an afterthought) that when I visited that Royal Palace at Het Loo, i took my regalia with me and a Royal attdenet was more than happy to take my picture at points of interest. I can smile now but some other tourists thought I was something to do with the palace and wanted to take pictures. I often laugh at the reaction! It is as you say a nice place and intend to renew my acquaintance with it again.
Your example is a structure that would be there anyway, the cost is sunk.
The problem, Jax, is that the train's engineer is not immune to falling asleep. If it can happen to drivers of cars, it can happen to the operator of the train's controls.Note: We had it happen not long back here in Chicago. You may have heard about the CTA train that tried to climb the escalators a couple of months back. The operator was asleep, the train had overshot the auto-braking system and-- it made for great photos and much comment on Reddit. Turned out the engineer had a bit of history of falling asleep at the controls, she had overshot a stop sometime earlier because she was asleep. She got fired for the incident at the airport escalator.
I occasionally use the dedicated pedestrian tunnel to go to the other side of the Scheldt. There are also dedicated bridges to be found in many places.
Bicycle paths are for sissies. I have all the right in this world to use streets and roads that I've paid for as much as automobilists did.
Page created in 0.124 seconds with 52 queries.