BikePlanner.org

[Chris Eatough]

Thanks for trying this out and your initial feedback.
I want to make sure everyone realizes that the base map for Bikeplanner (openstreetmap) is open for edit by anyone. So if you get a result that doesn’t seem right, you can view the base map and usually there is a correction that can bring the map and the routing more in line with reality. The openstreetmap that is used as the basemap is here: http://www.openstreetmap.org/
You can log in and start making improvements!
This is truly a community tool. Avid cyclists like yourselves are the people that collectively know all the details of our bike network, and that knowledge can be incorporated into the base map over time.
The more we use Bikeplanner and provide feedback, the more accurate it becomes!
Open Plans and BikeArlington will be bringing more tutorial info (both online and in person) to you soon to help with map editing skills).
What’s important is that we see this as a great starting point that we can improve collectively, rather than dismissing it because it does not replicate our preferred routes the first time.

[jhr]

@Chris Eatough 27925 wrote:

Thanks for trying this out and your initial feedback.
I want to make sure everyone realizes that the base map for Bikeplanner (openstreetmap) is open for edit by anyone. So if you get a result that doesn’t seem right, you can view the base map and usually there is a correction that can bring the map and the routing more in line with reality. The openstreetmap that is used as the basemap is here: http://www.openstreetmap.org/
You can log in and start making improvements!
This is truly a community tool. Avid cyclists like yourselves are the people that collectively know all the details of our bike network, and that knowledge can be incorporated into the base map over time.
The more we use Bikeplanner and provide feedback, the more accurate it becomes!
Open Plans and BikeArlington will be bringing more tutorial info (both online and in person) to you soon to help with map editing skills).
What’s important is that we see this as a great starting point that we can improve collectively, rather than dismissing it because it does not replicate our preferred routes the first time.

I hope you’re not discouraged by the initial reaction to this site; it really is already quite impressive and I think everyone is just excited by the further potential they see in it. Nearly all the route problems appear to either be minor issues with the current OSM data, which can be easily fixed as you note, or a side effect of the fact that there’s no way to flag unsafe routes in OSM. For the latter issue it seems (based on Kevin’s comment on Greater Greater Washington) that OpenPlans is already quite aware of the situation and has a solution (adding their own information to the OSM data) that they’re using in Portland, so it shouldn’t be a problem on bikeplanner.org much longer. I certainly intend to keep using it and I think with just a little improvement it can reach a level where I’ll feel comfortable recommending it to new cyclists without feeling the need to warn them to take the directions with a grain of salt. The site is really neat and I can’t wait to see how it continues to improve.

[chris_s]

@Chris Eatough 27925 wrote:

Open Plans and BikeArlington will be bringing more tutorial info (both online and in person) to you soon to help with map editing skills).

Looking forward to the tutorial material. I’ve edited OSM before and it’s a bit intimidating. I bet it’ll be pretty easy to teach folks the tiny subset of knowledge that’s useful for fixing bike routes though.

[jrenaut]

Wow, the “Use a shared bike” option is pretty awesome.

[Chris Eatough]

@jhr 27938 wrote:

I hope you’re not discouraged by the initial reaction to this site; it really is already quite impressive and I think everyone is just excited by the further potential they see in it. Nearly all the route problems appear to either be minor issues with the current OSM data, which can be easily fixed as you note, or a side effect of the fact that there’s no way to flag unsafe routes in OSM. For the latter issue it seems (based on Kevin’s comment on Greater Greater Washington) that OpenPlans is already quite aware of the situation and has a solution (adding their own information to the OSM data) that they’re using in Portland, so it shouldn’t be a problem on bikeplanner.org much longer. I certainly intend to keep using it and I think with just a little improvement it can reach a level where I’ll feel comfortable recommending it to new cyclists without feeling the need to warn them to take the directions with a grain of salt. The site is really neat and I can’t wait to see how it continues to improve.

Great post, jhr. I totally agree. I just wanted to make sure everyone realized that this is just the beginning for bikeplanner. It’s impressive already, but it has even more potential if we all stay involved and engaged.
Also worth noting that we are fortunate enough to be the first region to get this tool with full integration with bikeshare. New York City has the cibi.me version but their bikeshare system is not operational yet. Plus all this came at no cost to the jurisdictions (read: taxpayers) or users (read: local cyclists).

[Greenbelt]

I really like this service.

One nit — like several other mapping services, I noticed doesn’t recognize a key traverse on one of my most common routes.

For example, the fastest way for me to get from my house in Old Greenbelt to my LBS in North College Park is to ride through the Greenbelt Metro station and walk my bike through the tunnel underneath the train lines. (OK, I’ll admit it, sometimes I ride slowly through the tunnel if no one’s there and the Metro station manager isn’t looking…)

[Chris Eatough]

Thanks Greenbelt, this is exactly the kind of local knowledge that the base map needs. You can log into openstreetmap.org and add your tunnel as a bike path, then the tool will include that in future routes. There is a bit of a learning curve at first, but once you get the hang of it, playing map maker is actually really fun!

[MV Clyde]

Very cool. I played around using my 11 mile commute. The bike friendly route is very close to my normal route. The recommended route would save me a mile. The quickest route shaves about 1.5 miles but it would be a hairy ride. The estimated times are very conservative. My actual commute is 15-20 minutes shorter than the estimate.

Some good news is that the route to my mother-in-law’s house is not possible.

[eminva]

I also inputted my usual commuter route — interesting that it routed me through the streets of North Arlington rather than the Custis Trail for the Ballston-Rosslyn stretch. I also thought the time estimate was too conservative.

I inputted some data for little routes around Vienna that I use for errands, just to “test” for those informal short cuts on paved trails. The mapping tool didn’t recognize those. I will look forward to any guidance that will be given on editing the mapping tool. It’s probably not something I can figure out myself (the household Chief Technology Officer nods his head emphatically).

Liz

[DismalScientist]

@eminva 28037 wrote:

I also inputted my usual commuter route — interesting that it routed me through the streets of North Arlington rather than the Custis Trail for the Ballston-Rosslyn stretch. I also thought the time estimate was too conservative.

Liz

If you move the slider to more bike-friendly, you’ll probably be put back on the Custis. The faster routing puts me on Fairfax and Clarendon. Interestingly, I take Fairfax and Clarendon because I think it is safer and because of the lights, I think that the Custis is faster.:rolleyes:

[Greenbelt]

DDOT’s bike map has some very handy marked routes that are not being picked up. For example the most bike friendly route on my commute shows from MD through NE DC shows suggests taking Monroe street. However, that’s a pretty bad alternative east of 12th street NE where the bike lane ends.

DDOT instead marks Newton Street, 18th Street, and Varnum Street as bike routes. These are a much better way to connect with the Anacostia Tributary trails in my opinion (I get on the NW branch at 38th street) to get out to Maryland.

I’d also suggest that the Met Branch trail is about the fastest thing going — just because it’s a MUT doesn’t make it slow. Way faster than taking surface streets since there are no stops and it’s a wide trail.

[Arlingtonrider]

My technological skills are probably behind almost everyone’s. Until I’m able to improve them, it would be great if someone could let the planner know that there is still a hill on Walter Reed Drive. It seems to think that the hill has been bulldozed flat.

[ShawnoftheDread]

My most bike friendly route home from DC has me going through Seven Corners – actually across the Wilson Blvd-Rt7-Sleepy Hollow interchange. Fun!

[5555624]

It gets about a third of my morning commute using the default settings. Some of the alternatives, such as suggesting Southgate Road over Columbia Pike, I can understand. (After all, there’s no setting for time of day.) I’m not sure why it likes going down the Mall, unless it’s trying for as much off the road travel as possible.

Sliding the adjuster to about 74% “Quick” does come very close to my afternoon commute. The big difference between the two route — which it picked up — is Memorial Bridge vs. George Mason Memorial Bridge. In the afternoon, I’m in a hurry to get home and the George Mason is the first bridge I hit.

[Greenbelt]

Looks like the Post has picked up on this story, and is running that great picture from the Tim Johnson ride featuring the forum’s pinkest cyclist!

http://www.washingtonpost.com/local/trafficandcommuting/a-bike-map-for-washington-and-eventually-by-washington/2012/08/11/1b6dee18-e30e-11e1-98e7-89d659f9c106_story.html?hpid=z9

[Author]

Posts