Page 122 of 170

Grocery Store Ratings: Nevada takes a stab

I’m glad at least one of my ideas is “taking off.”

Muscle Powered, a community group in Carson City, Nevada, “dedicated to making Nevada’s capital city a better community for bicycling and walking,” has posted their first review of Carson City Grocery Store Bike Parking. They’ve geocoded their locations and graded the racks as well. The grading system is well-defined but still abstract enough so as not to let the issue of getting bike parking at stores in one’s community get bogged down by small details.

In Chicago, we have a “crew” of two working on identifying good and bad bike parking in Chicago. There’s me and Samantha, better known as Ding Ding Let’s Ride. The tough part is communicating good bike parking practices to the grocery stores. While the City of Chicago has clear guidelines on how and where to install bike racks, it cannot solve the grocery store problem because the store entrances are often so far away from the sidewalk. It’s also partially a business’s responsibility to provide “transportation storage” for their customers, especially for a destination that’s popular for people to ride their bikes to.

This Home Depot in Carson City, Nevad, has a decent bike rack (wide waves make it easy to maneuver bike into position) but poor placement. Bike racks should be place 24 inches from any wall or other object, at a minimum. Photos by Dan Allison of Muscle Powered. More photos from Dan below.

I’m glad that there are others out there that take bicycle parking as seriously as I do. I know of some other people around the country. Are you one?

These racks at Safeway are not acceptable. They do not allow the bike rider to lock any part of the bicycle frame.

Another scene of bike parking in Carson City, Nevada.

Bike crash reporting tool: I receive a response to my FOIA request

UPDATE 12-15-10: I forgot to add that the letter stated that the Freedom of Information Act doesn’t require the responding agency to create new datasets or records where one doesn’t already exist. This means that if what you ask for doesn’t exist in their databases or file cabinets, the agency is not about to filter or search through existing data to create a custom set for you.

I continue to prepare to create a bicycle crash reporting tool (or web application). Here are the previous posts. Readers have sent me many great suggestions and concerns about how to create it, what data to use, and how to present such data. I don’t expect to begin any demonstrable work on this until mid-January when I return from my 21-day European vacation.

Today I received a response letter from the Chicago Police Department regarding my recent FOIA request for bicycle crash data.

This was disappointing: “After a thorough search, it was determined that the Department has no existing record responsive to your request.” I thought, “that doesn’t seem right. They don’t make reports on bicycle crashes?”

Police respond to a bicycle crash in Newberg, Oregon. Photo by Matt Haughey.

The letter later states, “The Department  does not currently possess a record which aggregates bicycle crash data.” Ah, this means something now. It seems that while the Chicago Police Department does make reports on bicycle crashes, it doesn’t keep a running tally or stored database query which it can use to produce the data I want – what I want would require a little more work, I guess.

The final paragraph does recommend that I contact the Illinois Department of Transportation Division of Traffic Safety’s Crash Reporting Section, where the police forward their reports. It turns out that I already received crash data on IDOT and I’m “playing around with it” using Google’s Fusion Tables.

I value photography

I’ve made photography a very important feature of this blog. The photos help me tell the story. I spend an equal time taking and processing photos for the blog as I do writing it. I take over 200 photos each week. When I travel, I take 1,000 photos. Of 5,814 published photos, almost 64% have been added to the map, bringing more context to the subject and allowing it to be discovered geographically.

I think photography (and photos) is an important aspect of quality urban planning. When talking to the public and trying to get across your ideas, photos and other graphics make a vision come to life. They demonstrate what is and what could be. The right photo will invoke, without prompting, passion and enthusiasm – support you might need. The wrong photo may do the opposite, or have no effect at all. Take as many photos as needed so you ensure they will intimate the feelings you need for your project, or story.

What’s the story here? It could be several things. Simply, that it snowed recently. Or complexly, that while growth in this area has been phenomenal and immediately recognizable (most of the visible buildings starting at the blue-topped one and going south did not exist 10 years ago), our 100 year-old electric interurban train still runs.

I take photos for two reasons: to share on my blog, and to share them publicly, worldwide so that anyone who needs a photo can find it. A variety of my photos have been used to narrate events and ideas in organizational publications (with and without attribution), websites, and even a book!

I want my readers to take photography seriously. I don’t want you to be discouraged by that term, either. Don’t think you need a good camera or know how to take good pictures. Begin today and take one photo per day for a year. In one year, you will be an extremely proficient photographer (or “picture taker”). You’ll be able to tell your story, without a caption, in little time.

Read more about my photographic arsenal:

This photo tells us about the practice of designing malls, and designing malls for dense cities (like Chicago, where it’s located). The escalators are designed to get you in fast, but getting out requires a bit more walking.

It’s official: U.S. DOT takes away Wisconsin’s high-speed rail money

UPDATE 12-13-10: Yonah Freemark at The Transport Politic explains that the governors-elect of Wisconsin and Ohio have caused Florida to receive all the necessary funding to build its Tampa to Orlando link, but also which barriers might still stand in the way. Also check out the comments on that page to read about the backlash in Wisconsin and Ohio because of the lost opportunities.

And gives some to Illinois!

Transportation Nation has the press release from the United States Department of Transportation (secretary Ray LaHood) describing who will get $1.195 billion in ARRA funding for high-speed rail projects.

A tinny portion will stay in Wisconsin to support the Hiawatha line, a key route between Milwaukee and Chicago with growing ridership. Illinois began using its ARRA grants to build new track on the Chicago-St. Louis right.

San Francisco Mayor, Gavin Newsom, and DOT secretary Ray LaHood, attend the groundbreaking of the Transbay Transit Center, expected to be the peninsula terminus of the California High-Speed Rail network. Read more about the first segment of that project. Photo taken in August 2010.

Who else gets some of that? These states:

California: up to $624 million
Florida: up to $342.3 million
Washington State: up to $161.5 million
Illinois: up to $42.3 million
New York: up to $7.3 million
Maine: up to $3.3 million
Massachusetts: up to $2.8 million
Missouri up to $2.2 million
Wisconsin: up to $2 million for the Hiawatha line
Oregon: up to $1.6 million
North Carolina: up to $1.5 million
Iowa: up to $309,080
Indiana: up to $364,980

Best ways to present bicycle crash data

I started some preliminary work on my crash reporting tool. I haven’t written any code, but I’ve been working on the logistics of analyzing and presenting the data to the public.

I obtained bicycle crash data for 2009 from the Illinois Department of Transportation’s Division of Traffic Safety. I’m not able to distribute raw data (you’ll have to ask for it yourself) and Illinois statutes prevent me from distributing personally identifying data (but it’s really hard to know what this is). In the meantime, based on Ben Sheldon’s suggestion, I loaded some of the data into a private Google Fusion Table that instantly maps geocoded data (it can also geocode the data for you).

Richard cautions me about way I choose to present data. I need to choose terms and descriptions carefully to avoid misinterpretations. Pete from the Boston Cyclist’s Union recommends against accepting self-reported data. I’ll be taking their advice into consideration as I move forward.

You see in the map (top) that a lot of crashes happen on Milwaukee Avenue (above). That’s where a lot of people ride (over 3,000 in 24 hours in the fall).

I have not begun to review the narrative details in the crash reports. Actually, they’re not very narrative because they’re fixed responses – no free writing allowed. And not every record represents a collision (meaning a crash with at least two parties). Many are self-crashes (is that a legit phrase)?

I’m not sure exactly what story I want the data to tell so it will probably be a while before I make anything public. One of my favorite geographic information books, Making Maps, talks about the endless ways maps can be designed and portrayed and that each tells a different story. It’s best if I know the story (a goal) ahead of time.