Category: Maps

This is why we need more people editing OpenStreetMap

Unmapped homes in the Irving Park community area

These homes were built after the City of Chicago’s building footprints dataset was created (2010?). Ian Dees imported the dataset in 2012. Many of the buildings that you can now see on Bing Maps have not been present on Bing’s satellite imagery since at least 2012.

1. OpenStreetMap is the world’s most complete free map, to which anyone can contribute their “ground truth” data (the location of wells and convenience stores, road names, and whether Lula Café at 2537 N Kedzie Boulevard in Logan Square has outdoor seating).

2. OpenStreetMap is used by thousands of non-profit and non-governmental organizations, corporations, apps, and people daily to locate themselves, locate others, get directions, and find places.

3. Nearly every map is out of date the moment it is published, including online, “current” maps like Google Maps, Bing Maps, their competitors, and OpenStreetMap.

4. Bing Maps provides its satellite imagery to OpenStreetMap editors – you and me – so that we can trace (copy) things on the planet to be things on the map. Google Maps doesn’t allow tracing (copying).

5. Bing updated its satellite imagery for Chicago (and probably a lot of other places) within the last six weeks…and there are hundreds of objects that aren’t yet mapped in OpenStreetMap. In Chicago most of these buildings are newly constructed houses.

Those hundreds of houses now need to be added to OpenStreetMap, with addresses, to complete the buildings collection in Chicago, and to expand the gazetteer (an address book) of places in Chicago.

I’m glad you want to help me do it! Here are two helpful things you can do:

  1. Start tracing the buildings yourself (here’s how new mappers can get started), or
  2. Leave notes at buildings which aren’t yet mapped so that map editors like myself know where to look to trace buildings.

Update: There’s a bonus third thing you can do, and that’s come to the next MaptimeCHI event on Thursday, February 26th, at the Chicago Community Trust (225 N Michigan, 22nd floor). RSVP for Anatomy of a Web Map. The Trust will also provide food and beverages. I’ll be there to teach new mappers and assist generally.

Adding notes is extremely helpful

You can contribute without editing by adding notes describing new things, or identifying problems with existing things. Click the “Add a note” button on OpenStreetMap.org.

Why architects should learn OpenStreetMap

I’m teaching OpenStreetMap 101 at the first MaptimeCHI.

Architects will learn that OpenStreetMap can be used as a data source when developing projects and as a basis for designing custom maps in project publications (website, anthology, monograph, client presentations).

This meeting is about getting an introduction to OpenStreetMap and learning to make your first edit in the “Wikipedia of maps”.

Thursday, July 17th, from 6-8 PM
Thoughtworks office
200 E Randolph St

RSVP on EventBrite.

Here are two examples of how architects could use OpenStreetMap data.

Example 1 of how to use OpenStreetMap. Instead of publishing a screenshot of Google Maps in your documents or website, create a custom design map like this without having to spend so much time tweaking it in Illustrator. This map was created by Stamen Design using TileMill.

Example 1 of how to use OpenStreetMap. Instead of publishing a screenshot of Google Maps in your documents or website, create a custom design map like this without having to spend so much time tweaking it in Illustrator. This map was created by Stamen Design using TileMill.

And the second.

Willow Creek Church on OpenStreetMap: After

Here’s one example where OpenStreetMap could be useful. Let’s say you’re working on a site plan for Willow Creek Church in South Barrington and you need a general layout of the parking lot. 1. You can get it from OpenStreetMap because it’s already there. 2. You can draw it in OpenStreetMap yourself (to benefit all other OSM users) and then extract it as a shapefile.

Maptime is time for mapmaking and it’s taking the country by storm.

How Chicagoans commute map: An interview with the cartographer

Chicago Commute Map by Transitized

A screenshot of the map showing Lakeview and the Brown, Red, Purple and Purple Line Express stations.

Shaun Jacobsen blogs at Transitized.com and yesterday published the How Chicagoans Commute map. I emailed him to get some more insight on why he made it, how, and what insights it tells about Chicago and transit. The map color-symbolizes census tracts based on the simple majority commuting transportation mode.

What got you started on it?

It was your post about the Census data and breaking it down by ZIP code to show people how many homes have cars. I’ve used that method a few times. The method of looking up each case each time it came up took too long, so this kind of puts it in one place.

What story did you want to tell?

I wanted to demonstrate that many households in the city don’t have any cars at all, and these residents need to be planned for as well. What I really liked was how the north side transit lines stuck out. Those clearly have an impact on how people commute, but I wonder what the cause is. Are the Red and Brown Lines really good lines (in people’s opinions) so they take them, or are people deciding to live closer to the lines because they want to use it (because they work downtown, for example)?

The reason I decided to post the map on Thursday was because while I was writing the story about a proposed development in Uptown and I wanted  information on how many people had cars around that development. As the map shows, almost all of Uptown is transit-commuting, and a lot of us don’t even own any cars.

What data and tools did you use?

I first used the Chicago Data Portal to grab the census tract boundaries. Then I grabbed all of the census data for B08141 (“means of transportation to work by number of vehicles available”) and DP04 (“selected housing characteristics”) for each tract and combined it using the tract ID and Excel’s VLOOKUP formula.

Read the rest of this interview on Web Map Academy.

Wayfinding signs at Van Buren Street Metra station are incomplete

New RTA interagency transfer signage near Van Buren Street Metra Electric station

“B” marks a new bus boarding area near the Van Buren Street Metra Electric station.

The Regional Transportation Authority has spent $2 million to improve wayfinding between CTA, Metra, and Pace train stations and bus stops in a needed effort to connect newbies and long-time residents to their next transfer.

Some of the signs need to show better information, though. The RTA installed signs at the Van Buren Street Metra Electric station at Michigan Avenue that create “bus loading groups,” similar to bus bays at suburban park & rides.

It works like this: you come across the nearest bus stop – I happened upon boarding area B – hoping to find the route you need. Instead, though, that route stops at boarding area A. The sign at boarding area B points you in the direction of A and from where you stand you can see a sign that identifies A.

RTA’s signs have two issues. First, they don’t tell you that boarding area C is across the street – unless you inspect the small map – and instead point you in the direction of A (from B). If you walk in the direction of the arrow from boarding area B you will not run into boarding area C or a sign that tells you where to cross the street in order to access C.

The first issue creates the second problem: by reading and relying upon the sign’s text you can’t know at which boarding area, A or C, you should board a bus route that stops at both boarding areas. (Those who also study the maps on another side of the sign will have better luck.) That’s because the same route operates in both directions and if you’re not familiar with the route, you won’t know which direction takes you towards your destination.

New RTA interagency transfer signage near Van Buren Street Metra Electric station

Both boarding areas A and C will get you on the 3, 4, J14, and 26, but only the map on the other side tells you which direction they go. Also, while the arrow points in the direction of boarding areas A and C, only the map tells you that A is across the street.

The fix seems an easy one. First, point the arrows on A and B across the street instead of north or south towards B or A, and add an intermediary sign along the walking path that communicates that “boarding area C is across the street.” Then, update the signs to indicate which direction the bus routes are going so that travelers are assured they need to visit C across the street for King Drive buses going towards Bronzeville or A for King Drive buses going toward Streeterville.

The RTA has installed other signage in this program at 95th and Western (CTA & Pace), Joliet Union Station (Metra & Pace), and Davis Station in Evanston (CTA, Metra, & Pace).

Chicago Crash Browser, miraculously, has 2012 bicycle and pedestrian crash data

Screenshot shows that you can choose your own search radius. When researching, be sure to copy the permalink so you can revisit your results. 

I’ve upgraded the Chicago Crash Browser, my web application that gives you some basic crash and injury statitics for bicyclist and pedestrian crashes anywhere in Chicago, to include 2012 data. It took the Illinois Department of Transportation eight months to compile the data and it took me four months to finally get around to uploading it into my database. While I spent that time, I made some improvements to the usability of the app and output more information. Since the last major changes I made (back in February 2013) I’ve gained two code contributors (Richard and Robert) making this my first communal project on GitHub.

I know that it’s been used as part of research in the 46th Ward participatory budgeting process for 2013, and by residents in the 26th Ward to show Alderman Maldonado the problem intersections in the Humboldt Park area. Transitized recently included pedestrian crash stats obtained from the Crash Browser in a blog post about pedestrianizing Michigan Avenue in Streeterville.

The first change I made was adding another zoom level, number 19, so you can get closer to the data. I made some changes to count how many people were injured and total them. You can now choose your search distance in multiples of 50 feet between 50 and 200, inclusive. As is typical, I get sidetracked when I notice errors on the map. Thankfully I just fire up JOSM and correct them so the next person that looks at the map sees the correction. Future changes I want to make include upgrading to the latest jQuery, LeafletJS, and Leaflet plugins. I’d also like to migrate to Bootstrap to improve styling and add responsive design so it works better on small screens.

Sign up for the newsletter where I’ll send a couple emails each year describing new changes (I’ve so far only published one newsletter).