May 11, 2010, 2:14 p.m.

Moving Forward?

So over the past week I've rolled out some great improvements to HTTP://WWW.ridefreebikemaps.com. I've added a way for users to add routes to the database; I made a short script to display those routes with their name and description in a way that Google can index; and I wrote in an option which lets users create routes outside of the USA. Awesome!

I'm well on my way to creating an honest to god web 2.0 bike maps app. Every day I learn new ways to integrate my app with the existing web 2.0 apps. Everything I learn inspires me to create better features for the app itself. I think my next big project is going to be adding author pages to the site. Here's some of the ideas I've been thinking about:

  • Author Pages

  • Achievement Badges (x number of routes, long route, short route...)

  • Share routes with facebook upon creation.

  • Combine 'Members Only' and regular map creator.

  • Image/description previews of routes.

  • Browse routes via an interactive map (wow!)

On top of all that I've got to increase the traffic to my site. As it stands I get a good trickle from http://www.crazyguyonabike.com but I have to update the 'time stamp' on my link to keep it going. My roommate keeps telling me to start working some SEO magic but I don't know where to begin. Eh I think I'll just cross my fingers and hope somebody starts passing some serious stumbleupon/del.ici.ous/digg/facebook love on the site.

Posted via email from Ian's Posterous

March 31, 2010, 7:49 p.m.

Just uploaded an update to my Map Creator

So a couple weeks ago Google announced that they added a 'bike there' option to Google Maps. The next day they added the same thing to their API so web developers could use the directions in their apps. I was super thrilled when I heard the news and got to work as soon as I could on adding the directions to my app. It took me so long to make the switch because Google added the new directions to the V3 of the Google Maps API and my app was written in V2.

V3 is technically still in Google Labs which means it's in their version of a beta. I didn't really figure that out until I had started making the switch. In hindsight I think I should have been more cautious but I felt that I had to make the transition to keep the pace. As I noted on the site the improvements are worth having, even if some gnarly bugs crawl out of the system.

I also took the time to make a bunch of improvements on the interface of the app. I think I made the whole thing a lot more streamlined and easier to use. Time will tell with that I suppose.

Posted via email from Ian's Posterous

March 31, 2010, 7:49 p.m.

Just uploaded an update to my Map Creator

So a couple weeks ago Google announced that they added a 'bike there' option to Google Maps. The next day they added the same thing to their API so web developers could use the directions in their apps. I was super thrilled when I heard the news and got to work as soon as I could on adding the directions to my app. It took me so long to make the switch because Google added the new directions to the V3 of the Google Maps API and my app was written in V2.

V3 is technically still in Google Labs which means it's in their version of a beta. I didn't really figure that out until I had started making the switch. In hindsight I think I should have been more cautious but I felt that I had to make the transition to keep the pace. As I noted on the site the improvements are worth having, even if some gnarly bugs crawl out of the system.

I also took the time to make a bunch of improvements on the interface of the app. I think I made the whole thing a lot more streamlined and easier to use. Time will tell with that I suppose.

Posted via email from Ian's Posterous

March 10, 2010, 3:58 p.m.

Big day for bike maps!

Today Google officially announced the addition of a 'bike there' option for getting directions in Google Maps. This story has been covered by a few other blogs:

For those of you who haven't heard or want the teal deer version here it is!

  • This is fscking amazing!

  • Google considers information about terrain, roads, bike paths, and traffic when creating bike maps.

  • The algorithm actually calculates the energy to pedal up hills and finds the easiest route.

  • Google has also added a new layer to their maps which shows all the bike lanes, bike trails, and preferred streets for cycling on.

  • If you ride bikes be happy!

  • I'm super into this sort of thing.

Some cool quotes:

Well now that the good news is out, I can lift the curtain and explain the many factors and variables that we've had to take into account to put this whole feature together:

  • Bike trails: Our maps contain over twelve thousand of miles of biking trails. First, we had to figure out where trails are, so we worked with the Rails-to-Trails Conservancy to get much of our trail data. Once we had trails mapped out, the next task was to incorporate them into our routing algorithm. The algorithm is weighted to strongly prefer routing on these trails rather than roads open to automobile traffic, so your directions will try to put you onto a trail as long as it won't take you totally out of your way. On our bicycling layer (found under the 'More' button), these trails show up in dark green.

  • Bike lanes: For more than 150 cities in the US, we know which streets have dedicated bicycle lanes. These are also prioritized when coming up with a routing suggestion. On the bicycling layer, you’ll see these roads indicated in bright green.

  • Recommended routes: For many cities we also provide information on streets that have been designated as good for cyclists, so we them into account in our algorithm. These roads are indicated with dashed green lines on our bicycling layer.

  • Uphill slopes: l don't know anyone who enjoys biking up a hill, especially when you're trying to get somewhere you need to be. Going uphill is worse than simply being much slower; it's also exhausting and can take a toll on the rest of your ride. Our biking directions are based on a physical model of the amount of power your body has to exert given the slope of the road you’re biking on. Assuming typical values for mass and for wind resistance, we compute the effort you’ll require and the speed you’ll achieve while going uphill. We take this speed into account when determining the time estimate for your journey, and we also try hard to avoid routes that will require an unreasonable degree of exertion. Sometimes the model will determine that it's far more efficient to make you ride several extra blocks than to have to deal with a massive hill. My teammates in San Francisco were relieved to see that this does indeed work!

  • Downhill slopes: Many cyclists will tell you that going downhill is annoying for a different reason: you may have to ride your brakes all the way down. All else equal, we try to avoid routes that require a lot of braking. Of course, in some cities, including my hometown of Seattle, this isn’t always possible! And if you feel like you need a big workout and want to climb some hills, or if you just love that wind-in-your-hair feeling of a long downhill (you better be wearing a helmet and staying safe!), you can always turn on theterrain layer to check out the hilliness of an area for yourself.

  • Busy roads: Cyclists often tend to prefer to stay off of fast roads, and not even cross them unless it's necessary. This is roughly the inverse of driving directions, where you want to stay on arterials and freeways, so we had to rework a lot of those fundamental calculations when coming up with our biking directions algorithm.

  • Busy intersections: We try to avoid making you cross busy streets with a lot of car traffic and long wait times.

When we launched Directions in Maps API v3 last year we asked "Where will you go from here?". You may have asked the same question of us, and today we're pleased to be taking another step forward with several new Maps API v3 Directions features.

  • Avoid highways and tolls. If you prefer to take the road less traveled you can now generate routes thatavoid highways. Similarly, if you find yourself a little short of loose change, you can avoid tolls.

  • Route optimization. Have many places to go but no preference as to the order you visit them in? We can now reorder the waypoints of your route to minimize the distance and time you must travel. Very useful for traveling salesman I hear.

  • Bicycling directions. Prefer your vehicles of the two wheeled human powered variety? In conjunction with the launch of Bicycling directions in Google Maps you can now also request directions in Maps API v3 that are tailored to your Penny-farthing.

Posted via email from Ian's Posterous

March 10, 2010, 3:58 p.m.

Big day for bike maps!

Today Google officially announced the addition of a 'bike there' option for getting directions in Google Maps. This story has been covered by a few other blogs:

For those of you who haven't heard or want the teal deer version here it is!

  • This is fscking amazing!

  • Google considers information about terrain, roads, bike paths, and traffic when creating bike maps.

  • The algorithm actually calculates the energy to pedal up hills and finds the easiest route.

  • Google has also added a new layer to their maps which shows all the bike lanes, bike trails, and preferred streets for cycling on.

  • If you ride bikes be happy!

  • I'm super into this sort of thing.

Some cool quotes:

Well now that the good news is out, I can lift the curtain and explain the many factors and variables that we've had to take into account to put this whole feature together:

  • Bike trails: Our maps contain over twelve thousand of miles of biking trails. First, we had to figure out where trails are, so we worked with the Rails-to-Trails Conservancy to get much of our trail data. Once we had trails mapped out, the next task was to incorporate them into our routing algorithm. The algorithm is weighted to strongly prefer routing on these trails rather than roads open to automobile traffic, so your directions will try to put you onto a trail as long as it won't take you totally out of your way. On our bicycling layer (found under the 'More' button), these trails show up in dark green.

  • Bike lanes: For more than 150 cities in the US, we know which streets have dedicated bicycle lanes. These are also prioritized when coming up with a routing suggestion. On the bicycling layer, you’ll see these roads indicated in bright green.

  • Recommended routes: For many cities we also provide information on streets that have been designated as good for cyclists, so we them into account in our algorithm. These roads are indicated with dashed green lines on our bicycling layer.

  • Uphill slopes: l don't know anyone who enjoys biking up a hill, especially when you're trying to get somewhere you need to be. Going uphill is worse than simply being much slower; it's also exhausting and can take a toll on the rest of your ride. Our biking directions are based on a physical model of the amount of power your body has to exert given the slope of the road you’re biking on. Assuming typical values for mass and for wind resistance, we compute the effort you’ll require and the speed you’ll achieve while going uphill. We take this speed into account when determining the time estimate for your journey, and we also try hard to avoid routes that will require an unreasonable degree of exertion. Sometimes the model will determine that it's far more efficient to make you ride several extra blocks than to have to deal with a massive hill. My teammates in San Francisco were relieved to see that this does indeed work!

  • Downhill slopes: Many cyclists will tell you that going downhill is annoying for a different reason: you may have to ride your brakes all the way down. All else equal, we try to avoid routes that require a lot of braking. Of course, in some cities, including my hometown of Seattle, this isn’t always possible! And if you feel like you need a big workout and want to climb some hills, or if you just love that wind-in-your-hair feeling of a long downhill (you better be wearing a helmet and staying safe!), you can always turn on theterrain layer to check out the hilliness of an area for yourself.

  • Busy roads: Cyclists often tend to prefer to stay off of fast roads, and not even cross them unless it's necessary. This is roughly the inverse of driving directions, where you want to stay on arterials and freeways, so we had to rework a lot of those fundamental calculations when coming up with our biking directions algorithm.

  • Busy intersections: We try to avoid making you cross busy streets with a lot of car traffic and long wait times.

When we launched Directions in Maps API v3 last year we asked "Where will you go from here?". You may have asked the same question of us, and today we're pleased to be taking another step forward with several new Maps API v3 Directions features.

  • Avoid highways and tolls. If you prefer to take the road less traveled you can now generate routes thatavoid highways. Similarly, if you find yourself a little short of loose change, you can avoid tolls.

  • Route optimization. Have many places to go but no preference as to the order you visit them in? We can now reorder the waypoints of your route to minimize the distance and time you must travel. Very useful for traveling salesman I hear.

  • Bicycling directions. Prefer your vehicles of the two wheeled human powered variety? In conjunction with the launch of Bicycling directions in Google Maps you can now also request directions in Maps API v3 that are tailored to your Penny-farthing.

Posted via email from Ian's Posterous