Showing posts with label maps. Show all posts
Showing posts with label maps. Show all posts
Friday, May 21, 2010
600K Route in Trimble
Tony G has uploaded Saturday's 600K route to Trimble. As always, electronic files are no substitute for a printed cue sheet.
Wednesday, March 10, 2010
Google Announces Biking Directions
Following is a press release from the League of American Bicyclists:
This is great news, and hopefully it will avoid some of the routing issues that came up when using "Walking Directions," like this cue on a ride I routed last summer to Sunset Beach, NC. I suspect some of you Dirt Road Randonneurs would thoroughly enjoy this option.

One nice feature: Google maps now shows bike routes in major cities, including Raleigh. Look at the map below and you'll see city greenways in dark green and cycling routes in a lighter green:

Of course, there may be a few kinks to work out. I just tried routing from Raleigh up to Clarksville, Virginia, a town the Lake Loop passes through. Google biking directions put me on a 15-mile stretch of Capital Blvd, a major artery into and out of Raleigh and possibly the worst cycling road in our area. Have a look:
Washington, D.C. - March 10, 2010 - The League of American Bicyclists is proud to be the forum for Google to announce what all bike riders have been waiting for - Grab Your Bike and Go with Google Maps. Google is announcing at the Opening Plenary Session at the National Bike Summit that they are adding biking directions in the U.S. to Google Maps."This new tool will open people's eyes to the possibility and practicality of hopping on a bike and riding," said Andy Clarke, President of the League of American Bicyclists. "We know people want to ride more, and we know it's good for people and communities when they do ride more - this makes it possible. It is a game-changer, especially for those short trips that are the most polluting,"
Users can now choose biking when deciding how to get to their destination, starting today, March 10, 2010. If you're one of the 57 million Americans who ride a bike, mapping your daily commute, and planning recreational or trail rides just became easier. According to Google this has been the most requested addition to Google Maps, and the League is delighted that they have chosen the National Bike Summit to unveil this new feature. Google's announcement further proves the importance of the Summit and the bicycle movement in helping our nation become a more Bicycle Friendly America. The Google biking directions will make it that much easier for bicyclists to get to work, school or play.
This new feature includes: step-by-step bicycling directions; bike trails outlined directly on the map; and a new "Bicycling" layer that indicates bike trails, bike lanes, and bike-friendly roads. The directions feature provides step-by-step, bike-specific routing suggestions - similar to the directions provided by our driving, walking, or public transit modes. Simply enter a start point and destination and select "Bicycling" from the drop-down menu. You will receive a route that is optimized for cycling, taking advantage of bike trails, bike lanes, and bike-friendly streets and avoiding hilly terrain whenever possible.
Visit http://maps.google.com/biking to try out this new feature. Biking directions for Google Maps is currently in Beta. Follow the League's news feed on the new Google feature on the League's Blog, Facebook and Twitter. If you have any further questions, contact Meghan Cahill at 202.822.1333 or meghan@bikeleague.org.
This is great news, and hopefully it will avoid some of the routing issues that came up when using "Walking Directions," like this cue on a ride I routed last summer to Sunset Beach, NC. I suspect some of you Dirt Road Randonneurs would thoroughly enjoy this option.

One nice feature: Google maps now shows bike routes in major cities, including Raleigh. Look at the map below and you'll see city greenways in dark green and cycling routes in a lighter green:

Of course, there may be a few kinks to work out. I just tried routing from Raleigh up to Clarksville, Virginia, a town the Lake Loop passes through. Google biking directions put me on a 15-mile stretch of Capital Blvd, a major artery into and out of Raleigh and possibly the worst cycling road in our area. Have a look:
Thursday, June 25, 2009
Fun With Google Maps (and your iPhone)

I recently used my iPhone to take pictures on the way to and from the beach (see this post and that post). The iPhone is GPS-enabled, and the pictures are tagged by location. When they're loaded into a Google Web album, the pictures are tagged along the route so you can see where each was taken.
Here's the link to the image above. Zoom in for a look at where each shot was snapped.
Tuesday, June 16, 2009
Fun with Google Maps
I'm planning a ride to the beach this weekend, and these days my first source for a cue sheet & route is Google Maps. When you use it in "Walking" mode, you get routed on to smaller roads. You can adjust the route by dragging it to the roads of your choice after Google does the preliminary route.
The problem, I've discovered, is that when you use Walking directions you often end up on roads that are either dirt or true walking paths. I've been caught off-guard a couple times by this problem.
As I drew this weekend's route, I noticed the camera icon next to many of the turns. Clicking the icon shows you what kind of road you're getting ready to turn on. Voila! I found this gem, the turn after Bud Geddie Road. Have a look. Notice the "road" is unnamed in the directions.

It appears to be a tractor path across a tobacco field -- in fact, you can see the tractor. It's only 1.3 miles, and may go through, but just in case I'll have a Plan B for that section.
Thank you, Google.
The problem, I've discovered, is that when you use Walking directions you often end up on roads that are either dirt or true walking paths. I've been caught off-guard a couple times by this problem.
As I drew this weekend's route, I noticed the camera icon next to many of the turns. Clicking the icon shows you what kind of road you're getting ready to turn on. Voila! I found this gem, the turn after Bud Geddie Road. Have a look. Notice the "road" is unnamed in the directions.

It appears to be a tractor path across a tobacco field -- in fact, you can see the tractor. It's only 1.3 miles, and may go through, but just in case I'll have a Plan B for that section.
Thank you, Google.
Wednesday, August 20, 2008
Two New Great Tools for Creating Maps & Cue Sheets
Things happen fast on the Internet, don't they? I've been working on a new brevet/permanent route from North Raleigh to New Bern. That route was chosen to track NC's Mountain to Sea Trail, which currently uses bike routes as it travels east of Raleigh. Friend Kate Dixon, the executive director of the Friends of the Mountain to Sea Trails, is trying to have all 935 miles of the trail covered in October. I've agreed to help with a cycling effort.
But back to the maps and cue sheets. Kate gave me a topo map book where she'd traced out the route. It was easy to convert that into a fixed electronic map and somewaht usable cue sheet, thanks to changes in Google Maps and a program that Branson found. Here's how.
First, I went into Google Maps and set directions from North Raleigh to New Bern. Then I set Google Maps to "Walking Directions." Voila! Google actually routed on many of the roads I'd picked for my Blackbeard Permanent. I used the "drag map" feature to pull the route onto the roads that Kate had selected.
Unfortunately, Google maps must have some limit on the number of map drags you can do. That forced me to split the map into two segments: 1) North Raleigh to La Grange and 2) La Grange to New Bern.
Next, once the map was created in Google Maps, I used the information on this site to generate a cue sheet. All you have to do is click on that bookmark after you've created the map.
Here's the cue sheet from No. Raleigh to La Grange (the spacing among the columns is gone, but you get the idea):
Route: Wakefield Pines Dr to La Grange, N Carolina
Distance: 91.94 miles
Total Distance Directions
----------------------------------------------------
0.00 0.00 Depart from: Wakefield Pines Dr
0.11 0.11 Right: Falls of Neuse Rd
1.60 1.49 Bear Right: Old NC 98 Hwy
1.76 0.16 Left: Thompson Mill Rd
4.72 2.96 Bear Right: Bud Smith Rd
4.79 0.08 Right: Purnell Rd
6.10 1.30 Left: Jackson Rd
7.67 1.57 Right: Holden Rd
9.94 2.27 Straight: NC-1147
11.03 1.09 Straight: Main St
11.80 0.77 Straight: Tarboro Rd
18.72 6.92 Left: NC-98
20.75 2.02 Right: Strickland Rd
22.61 1.86 Left: Old Halifax Rd
23.91 1.30 Straight: Medlin a Ln
24.08 0.18 Straight: Brantleytown Rd
25.95 1.86 Right: NC-39
26.12 0.17 Left: Pine Ridge Rd
28.85 2.73 Straight: Daddysville Rd
29.02 0.17 Left: Old US-64
30.14 1.12 Right: Sanders Rd
30.41 0.27 Straight: Frazier Rd
37.83 7.42 Left: Strickland Rd
41.83 4.00 Right: W Hornes Church Rd
45.91 4.08 Right: Old Bailey Hwy
46.71 0.80 Straight: Lamm Rd
52.99 6.28 Straight: Quaker Rd
54.23 1.24 Left: Downing Rd
54.96 0.73 Right: Shirley Rd
55.69 0.73 Right: Wiggins Mill Rd
56.14 0.45 Left: Boswellville Rd
57.98 1.84 Straight: Lely Rd
58.60 0.62 Straight: Wellons Ct
59.54 0.94 Left: Blalock Rd
60.78 1.24 Right: US-117 Alt
60.85 0.08 Left: Church Loop N
61.65 0.79 Left: Central Ave
61.84 0.19 Right: Mercer St
62.17 0.33 Left: Cemetery St
62.38 0.21 Straight: NC-1628/Woodbridge Rd
63.06 0.68 Right: Frank Price Church Rd
66.33 3.27 Straight: Black Creek Rd NE
66.44 0.11 Left: Aycock Church Rd NE
68.24 1.80 Left: Davis Mill Rd NE
69.17 0.93 Right: Turner Swamp Rd NE
70.94 1.77 Straight: N Church St NE
71.74 0.79 Straight: Faro Rd NE
75.75 4.01 Straight: Old NC-1201
77.02 1.27 Straight: Bullhead Rd
77.26 0.24 Left: Saulston Rd
77.33 0.07 Right: Davis Grove Church Rd
78.46 1.13 Left: Cow Branch Rd
79.35 0.89 Right: Edmundson Rd
81.32 1.96 Straight: Creech Rd/Free Gospel Rd
83.90 2.58 Left: Titus Mewborn Rd
84.98 1.08 Right: Mewborn Church Rd
85.26 0.28 Bear Right: NC-903
91.94 6.69 Arrive at: La Grange, N Carolina
Finally, the cue sheet generator also has a function to add the map to Bikely, which is the map you see at the top of this post.
Tuesday, December 18, 2007
Lost? It Ain't Just a TV Show..
I've spent the last week or so extracting data from my GPS and figuring out how to turn that into electronic maps.
Now, for your reading pleasure, is another terrific post by N.C. rider Chuck Lathe. He takes great joy in getting lost on our chip & seal back roads. GPS devices threaten that kind of "bumble," he says.
And:
I'm reminded of the time when Capn John Ende led a team of N.C. riders astray on the Cascade 1200K. We wound up with 6 bonus miles on top of the very hilly first-day total of 230. Ouch! But Chuck's right. I now look with the great fondness on our little detour. It's one more notch in the belt of a Big Adventure.
BTW: I should make it clear that I don't use the Garmin Edge for navigation. I use it to show me where I've been, not where I'm going.
I don't like reading cue sheets while riding and prefer to leave that to others. When I ride solo on a route I don't know, I typically copy pages from the N.C. topo map book. That gives me the option of making up the route as I go.
The first time I rode the 175-mile route from Raleigh to the Swan Quarter ferry, I stuck the entire topo book in a Carradice seat bag. Besides being a handy reference guide, it also gave the bag a nice shape.
Now, for your reading pleasure, is another terrific post by N.C. rider Chuck Lathe. He takes great joy in getting lost on our chip & seal back roads. GPS devices threaten that kind of "bumble," he says.
The global positioning system is poised to become truly bicycle friendly -- well, maybe unfriendly depending on how you think about those things. From what I am reading, a lack of battery power will keep the little handlebar mounted GPS receivers from most brevets over 200 kilometers long this year, but the day is coming when even a bad cue on the cue sheet won’t allow us to become blissfully lost again.
And:
When you realize that you’ve gone down the wrong road and that you will have to backtrack to get back on course, it isn’t always immediately apparent that you’ve added something special to the ride, but later, the wrong turns are often the part of the brevet that remains most clearly in your memory. In fact, all randonneurs understand at some deeply internal level that getting lost is something special. We reveal that deep understanding by calling those extra miles ridden in wayward directions, bonus miles.
I'm reminded of the time when Capn John Ende led a team of N.C. riders astray on the Cascade 1200K. We wound up with 6 bonus miles on top of the very hilly first-day total of 230. Ouch! But Chuck's right. I now look with the great fondness on our little detour. It's one more notch in the belt of a Big Adventure.
BTW: I should make it clear that I don't use the Garmin Edge for navigation. I use it to show me where I've been, not where I'm going.
I don't like reading cue sheets while riding and prefer to leave that to others. When I ride solo on a route I don't know, I typically copy pages from the N.C. topo map book. That gives me the option of making up the route as I go.
The first time I rode the 175-mile route from Raleigh to the Swan Quarter ferry, I stuck the entire topo book in a Carradice seat bag. Besides being a handy reference guide, it also gave the bag a nice shape.
Sunday, December 16, 2007
Siler City Express / 1 Way Ticket
Note: I turned on my GPS tracking about a mile past the route start. Also, I picked up a picture Yo Adrian had posted online. Not sure where it's from, but it looked cool so I stuck it in there. And I added one of JoeRay on Flint Hill Road.
Notice the amount of climbing on this route. That's one way.

Length: 61.6 miles
Vertical up: 3023.2 ft
Vertical down: 3212.4 ft
Saturday, December 15, 2007
Morrisville, NC 200K
Labels:
2007 Rides,
maps,
Randonneuring,
Rides,
routes,
RUSA
High Point, N.C. 200K
Here is Richard Lawrence's 200K. A tough route, especially the first half.

Length: 123.7 miles
Vertical up: 4835.2 ft
Vertical down: 4868.3 ft
Labels:
2007 Rides,
maps,
Randonneuring,
Rides,
routes,
RUSA
S.C. 200K / Caesars Head
This map shows most of the S.C. 200K. I think I ran out of battery about 10 miles from the finish.
A terrific and extremely tough early season ride. Check out this profile.

Length: 113.8 miles (my GPS signal -- add 12 miles for entire route)
Vertical up: 5628.5 ft
Vertical down: 5518.1 ft
Monday, December 10, 2007
Breakthrough: Fixed Route from Google Maps
Ah ha! I played around long enough and I figured out which online programs to use.
I did not have the middle portion of Blackbeard, about 30 miles, but had recorded both ends using my Garmin Edge.
In the previous post, I put up a Google Map with that middle section. But how to lock that as a route map, like the other two legs?
I found an online program called GM2GPX that converted the Google map I'd made into GPX coordinates. Once I saw the code it generated, I knew I had the final piece of the puzzle.
I copied that code and pasted it into the map generator at GPS Visualizer. Once the map was created, I saved it as a route in EveryTrail.com (I could have done the same thing in Bikely.com, I believe.)
That program created the map you see above with the waypoints. Those waypoints are coming out of the original Google map. Those are the markers I used to nudge the Google line onto the Blackbeard route.
This has huge potential for creating permanents and other cycling routes. It also allows cyclists with GPS units to download the routes.
You may notice that the route is not drawn on top of the roads like the other Google maps. Not sure why that is, but I'll keep digging.
Blackbeard's Permanent / Leg 1
Here's the first leg of the Blackbeard Permanent. There's still a section missing from Stantonsburg to Winterville.
Sunday, December 9, 2007
Lake Loop in EveryTrail.com
One more version, generated using the map from GPS visualizer.
Lake Loop created in GPS Visualizer
This map is much cooler than the one in Bikely. Notice the various view options you have. Unfortunately, I think it's going to disappear at midnight, like a pumpkin coach, because the map is based on a site that deletes new files every day. I haven't figured out how to convert it into html, although the code is there for doing that.
Lake Loop at Bikely
In my ongoing experimentation with the Wonderful World of Maps, I've figured out (finally) how to turn my Garmin Edge courses into GPX files. From there, it's a piece of cake to import to Bikely.com
Voila: The Lake Loop.
Voila: The Lake Loop.
Subscribe to:
Posts (Atom)
