Tag: IDOT

Using Google Refine to get the stories out of your data

April 8, 2011 / / 0 Comments

Let’s say you’re perusing the 309,425 crash reports for automobile crashes in Chicago from 2007 to 2009 and you want to know a few things quickly.

Like how many REAR END crashes there were in January 2007 that had more than 1 injury in the report. With Google Refine, you could do that in about 60 seconds. You just need to know which “facets” to setup.

By the way, there are 90 crash reports meeting those criteria. Look at the screenshot below for how to set that up.

Facets to choose to filter the data

  1. Get your January facet
  2. Add your 2007 facet
  3. Select the collision type of “REAR END” facet
  4. Choose to include all the reports where injury is greater than 1 (click “include” next to each number higher than 1)

After we do this, we can quickly create a map using another Google tool, Fusion Tables.

Make a map

  1. Click Export… and select “Comma-separated value.” The file will download. (Make sure your latitude and longitude columns are called latitude and longitude instead of XCOORD and YCOORD or sometimes Fusion Tables will choke on the location and try to geocode your records, which is redundant.)
  2. Go to Google Fusion Tables and click New Table>Import Table and select your file.
  3. Give the new table a descriptive title, like “January 2007 rear end crashes with more than 1 injury”
  4. In the table view, click Visualize>Map.
  5. BAM!

I completed all the tasks on this page in under 5 minutes and then spent 5 more minutes writing this blog. “The power of Google.”

Better bike crash map now available for Chicago

March 14, 2011 / / 0 Comments

I met Derek at a get together for “urban geeks” last Tuesday where he told me he was making a filterable/searchable version of my Chicago bike crash map using the Google Fusion Tables API. It essentially allows you to perform SQL-like queries to show different results on the map than one view. It’s possible to do this yourself if you open the bike crash map in the full Google Fusion Tables interface (do that now).

You can use it now!

New bike crash map, click through to view

Derek’s map has the benefit of great interface to drill down to the data you want. You can select a day, a surface condition, and the injury type. To download the data yourself, you’ll still have to access the full Fusion Tables interface.

Door lane photo and graphic by Gary Kavanagh in Santa Monica, California.

And since the data is the same as my original map, crash reports involving motor vehicle doors are not included. Here’s why doorings are excluded.

Why the Chicago bike crash map doesn’t show doorings

March 11, 2011 / / 0 Comments

The data on the Chicago bike crash map comes from the Illinois Department of Transportation (IDOT) after reports are made to the Chicago Police Department, but it’s missing certain types of crashes. IDOT currently will not collect data about doorings.

Some Chicago cyclists created this sticker to alert drivers and their passengers to the dangers of the door. “Someone opened a door and killed my friend.” This is version 1 of the sticker; see version 2. Photo by Quinn Dombrowski.

Here’s a summary of the process:

1. Police officers make the reports

Chicago police officers collect information on dooring (outlawed by MCC 9-80-035) because of a recent agreement with the Chicago Department of Transportation (CDOT) – the importance of reporting doorings became a bigger priority after someone died after being doored on LaSalle Street in 2008.

When there is a dooring, Chicago police officers use an “Additional Units Form” in addition to SR-1050 (standard reporting form for Illinois motor vehicle crashes) and write “dooring” where the IDOT barcode would be on the Additional Units Form.

2. How the Chicago Police Department records it

When the Chicago Police Records Office sees that there’s no barcode they know they can’t send it to IDOT, but they see “dooring” and scan it for their own records (so they can provide it to crash parties later) and then email that number to the CDOT Bicycle Program. (There was a general order put out by CPD on this procedure and, yes, they actually send them– at least some of them.)

The CPD also knows that doorings, according to IDOT, are not a “reportable” crash. In addition to doorings, IDOT doesn’t consider the following as “reportable” crashes:

  • Any crash in which the first point of impact does not involve a moving motor vehicle.
  • Any non-injury crash which causes less than $1500 in property damage, unless one or more of the drivers was uninsured.

3. CDOT and Chicago Police Department connect

CDOT can then connect to the Police Departments records system, download a scan of the crash report, reads it and enters specifics into a tracking spreadsheet.

This is how dooring data is collected in Chicago because IDOT will throw away reports or attachments without barcodes. This should change. This process affects ALL cities in the State of Illinois but as far as I’m aware, only Chicago records doorings. It’s unfortunate that local agencies are forced to bear this additional task and provide special training for thousands of officers outside of statewide practices because IDOT doesn’t acknowledge the importance of this issue and revise its reporting policy.

Below is the SR-1050 form and you can see the IDOT barcode with the case number below it. The bike and pedestrian crash data I have from IDOT includes those case numbers.

Read more about doorings on Grid Chicago.

Trying out uDig, a free, multi-platform GIS application

February 10, 2011 / / 0 Comments

ArcGIS is the standard in geographic information system applications. I don’t like that it’s expensive, unwieldy to install and update, and its user interface is stymying and slow*. I also use Mac OS X most of the time and ArcGIS is not available for Mac. It doesn’t have to be the standard.

I’ve tried my hand at Cartographica and QGIS. I really like QGIS because there’re many plugins, it’s open source, there’s a diverse community supporting it, and best of all, it’s free. I’ve written about Cartographica once – I’m not a fan right now.

My project

  • The data: Bicycle crashes in the City of Chicago as reported to IDOT for 2007-2009
  • Goal: Publish an interactive map of this data using Google Fusion Tables and its instant mapping feature.
  • Visualizing it: Added streets (prepared beforehand to exclude highways), water features, and city boundary (get that here)
  • Process: Combine bike crash data; reproject to WGS84 for Google; remove extraneous information; add latitude/longitude coordinates; export as CSV; upload to Google Fusion Tables; map it!
  • View the final product

Trying out uDig

In reaching my goal I had a task that I couldn’t figure out how to complete with QGIS: I needed to combine three shapefiles with identical table schemes into one shapefile – this one shapefile would eventually be published as one map. The join feature in fTools wasn’t working so I looked for a new solution, uDig, or “User-friendly Desktop Internet GIS.”

The solution was very easy. Highlight all the records in the attribute table of one shapefile, click Edit>Copy, then select the destination table and click Edit>Paste. The new records were added within a couple seconds. I could then bring this data back into QGIS to finish the process (outlined above under Project). I did use fTools later in the process to add lat/long coordinates to my single shapefile.

After adding more data to better visualize the crashes in Chicago, I noticed that uDig renders maps to look smoother and slightly prettier than QGIS or ArcGIS. See the screenshot below.

A screenshot of the three bicycle crash datasets (2007, 2008, 2009) with the visualization data added.

The end product: three years of police reported bicycle crashes in the City of Chicago on an interactive map powered by Google Fusion Tables, another product in Google’s arsenal of GIS for the poor man. View the final product.

*I haven’t used ArcGIS version 10 yet, which I see and read has an improved user interface; it’s unclear to me and other users if the program’s been updated to take advantage of multi-core processors. ESRI has a roundabout way of describing their support.

High-speed rail in Illinois, February 2011 edition

February 9, 2011 / / 0 Comments

View a map of the places described in this article.

A friend of mine traveled by Amtrak’s Lincoln Service from Chicago to St. Louis in January 2011. He reported, “It’s extremely smooth north of Alton and south of Lincoln. You can barely even hear or feel that you’re on a train.” Track replacement as part of President Obama’s economic stimulus and high-speed rail plan is complete between Alton and Lincoln, Illinois.

Photo shows a Union Pacific work train next to new track in Carlinville, Illinois. Photo by Tim Carman, taken in November 2010.

The next track replacement phase will take place between Lincoln and Dwight, scheduled to be completed in Fall 2011. A December 2010 press release from the Illinois Department of Transportation (IDOT) explains the next steps for the first state to begin construction on high-speed rail grants provided by American Reinvestment and Recovery Act (ARRA):

  1. Installation of new, enhanced grade crossing warning protection
  2. New cars and locomotives
  3. Station upgrades

Like all press releases, this one also seems to ooze idealistic endeavors by adding that the “public can expect to enjoy its first taste of 110 mile-per-hour train service when a 20-mile segment between Dwight and Pontiac is completed in 2012.” But this project has a high likelihood of being completed as described.

Read more posts on high-speed rail in Steven can plan.