You are not logged in.
Pages: 1
Curious if anyone makes anything similar to this. Basically 620/Anderson Mill to just north of 183 on Burnet.
This is the route I'm thinking of taking:
https://www.google.com/maps/dir/30.4627 … 378577!3e1
Anyone have any better suggestions? Not really thrilled about riding on Braker between Burnet and 183.....
Offline
I've commuted from CP to the arboretum and am pretty familiar with most of your proposed route. 2 changes I would suggest:
1) El Salido instead of Anderson Mill north of 620 is a little more favorable unless its way adding too much to your commute.
2) Braker between 183 and Burnet is not great as you suggest. Duval to Burnet might be a better option since Duval has better bike lanes and slower traffic than that section of Braker but Burnet will still be Burnet with no dedicated lane.
The rest is no problem.
As I'm sure you already realize the worst section will be the last mile or two to work so you'll probably want to experiment different routes to find what you are comfortable with.
D
Offline
To avoid Braker you have a couple of choices:
1. From Jollyville/Balcones Woods take Balcones Woods east through the neighborhood. At the end of the road, you will reach a path you can take to cross the railroad tracks. http://goo.gl/maps/4gif4
Then, just make your way through the Domain. http://goo.gl/maps/YOKKQ
2. From Jollyville/Balcones Woods take Balcones Woods east past 183 until you pass a bank on your right (just before entering the neighborhood). Go through the bank and head south to Seton Northwest and on to Seton Center Parkway. From there it is possible to cut through parking lots until you get to Stonelake Blvd. Take that east to Mopac. From there you can cross at Braker / Mopac either riding or walking it. Braker has a bike lane from this point on to Burnet.
Once you get to Burnet, all I can say is good luck! I ride on it everyday and I hate it.
Oh, actually, there is a way around that too: http://goo.gl/maps/3hwb2 Once you get on Braker, just east of Mopac, turn into the Home Depot driveway. Head south staying behind the strip center until you reach the Firestone place. There is a path that leads along the tracks on the west side. This is next to Lake Fail. There is a small trail that you can use to cross the tracks and you will get to Longhorn Blvd. This path gets pretty overgrown, and it floods after a rain. I have taken a machete to it a few times, but if you rode this everyday it may help to widen it.
This puts you south of JJ Pickle. Take Longhorn to Burnet. You may still have a short ride on Burnet, but the traffic comes in spurts so you often have the road to yourself if you are not going too far.
john
Last edited by RedFalcon (2014-05-29 09:12:55)
Offline
I
2) Braker between 183 and Burnet is not great as you suggest. Duval to Burnet might be a better option since Duval has better bike lanes and slower traffic than that section of Braker but Burnet will still be Burnet with no dedicated lane.
The rest is no problem.D
Good idea.
If you go this way, you can take a short cut that keeps you off the nasty part of Duval where it approaches Mopac. The bike lane disappears here and the motorists seem to get into a frenzied state, probably in anticipation of having to drive on Mopac.
Just after crossing the tracks, heading east on Duval, you will come to the rear entrance to National Instruments. They have a gate there, but it is open during normal hours. There is no guard and no one seems to care when I cut through. Take the drive straight until it gets you to the Mopac feeder. This is where the feeder loops under Mopac near the track. Riding the feeder is no problem, but there is also a concrete path just south of it. This takes you into the Domain. From there you can get to Braker to either the Home Depot driveway or to Burnet.
john
Last edited by RedFalcon (2014-05-29 09:38:38)
Offline
This is the route that I use. Some people don't like Burnet Rd. though. But it is a long, straight, flat run with very long distance visibility esp. with bright lights.
Offline
Pages: 1
[ Generated in 0.017 seconds, 11 queries executed - Memory usage: 542.12 KiB (Peak: 542.74 KiB) ]