Nick Doiron is a developer focusing on web maps, interactive media, and environmental sensors. Nick has developed and taught open source programs with One Laptop per Child in Uganda, Uruguay, and Haiti. Working with open data, he has produced innovative maps for the Humanitarian OpenStreetMap Team in Port-au-Prince, the Cherokee Nation, the City of Pittsburgh, a water research group at Carnegie Mellon University, and a Mongolian offroad travel agency. He was recently a GIS intern at Esri’s Applications Prototype Lab and a student in the Knight-Mozilla News Learning Lab.

Filed Under

Demolition hotspots and smarter data


One thing that stands out about San Francisco is its neighborhoods. Months after moving to the city, I still hear of new neighborhoods and their specialties. There are some projects for digital maps that make sense of fuzzy neighborhood boundaries – maps using online consensus or Flickr geotags. For the most part, though, our datasets are oblivious to the streets intertwining below them.

I tried feeding one of these datasets into Neo4j, a NoSQL network database, to search for food deserts and demolition hotspots in my partner city: Macon, Ga. It’s hard to pick a high-risk neighborhood out of a spreadsheet or a list of coordinates.

Once you broaden the scope of the data to include connecting streets, the immediate neighborhood adds context, hints at whether a street connects to a major artery or a maze of back roads, reveals whether a condemned house is around the corner or across a highway.

The project showed that among houses cited by the City, neighborhoods of demolished houses stood out. Where most cited houses had 0-5 demolished houses in their network, networks of demolished houses peak at around 10-12 demolitions.

What else might we see in data tied to streets instead of spreadsheets?

I’m launching an experimental site and API for San Francisco called DemoDexter. At its core are 2,800 streets from OpenStreetMap. Each street is open for you to add your own data and get analysis back.

Two examples:

I added a “BART” tag to every street with a BART station. An API endpoint (/access/bart) helps map streets by how many links away they are from a station:


SF BART Access Map

Link to interactive map

Jessica, another Code for America fellow, told me that urban planners are concerned about choice. People are happiest when they have access to multiple supermarkets and parks, not just one nearby. Here’s a different map from the API, with streets color-coded by access to the two closest Chipotles (/choice/chipotle). Streets off of Market Street have bright color-coding, while those near the Sunset’s one Chipotle are more subdued.


SF Chipotle Choice Map

Link to interactive map

DemoDexter is open if you’d like to add tags showing how neighborhoods are served by local libraries, farmers’ markets, or hackerspaces. If you have the right datasets, you could search for hotspots of business development or blight. For other cities, such as Oakland, take the code from GitHub and the underlying street map from Michal Migurski’s OpenStreetMap metro extracts.


Questions? Comments? Hit us up @codeforamerica.

← Back To All Articles