exciting findings

26 01 2010

total # of bike commuters vs. non bike commuters

I’ve been using excel as a tool to better understand my survey data and here are a few hard facts–check out these graphs to the right. I must first admit—this information is REALLY REALLY exciting! Ok–so…Of my total population of 686 people surveyed (note; there were a total of 726 responses to the survey however data from 40 responder was eliminated due to incomplete data rendering it useless)60% of respondents were cycling commuters. 40% were not. This is represented in the purple graph.

breakdown of non commuters

I then wanted to breakout the non commuters to understand whether those people had ever considered riding. This is represented by the green graph. As you can see, I looked at people who owned bikes, and those who didn’t own bikes–this may provide some context for why some didn’t commute via bike. If you look closely, you can see that a total of 33% of non commuters were bike owners. I broke this out to see, of those bike owning, non bike commuters, which ones have ever considered riding to campus. 23% have considered.

The question is: what is stopping them? If you total up, of the 40% of non cycling commuters to Pratt, 59% of those responders have considered riding to campus (36% of non bike owners + the 23% of bike owners). With just this little bit of data, we can conclude from this information that there is huge potential for increasing bike use on the Pratt campus. 59% of the non commuters–that’s huge!

Now what…? More survey analysis! Who knew I could love excel so much?



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: