This summer we’re going to try something new by taking on an intern. Here are the details:

What: You’ll be making an interactive map of physician performance across New York. It’s a relatively small dataset covering 120 physician practices and 12 measures focusing on heart care. The map is in partnership with our friends and colleagues at IPRO and will be used to improve the quality of care in New York.
We want you to see the entire process of making a map so you will be responsible for this project from start to finish including:

1. Working with the client to learn about their data and functionality requirements
2. Preparing the data to go into the map
3. Designing the map and UI elements
4. Building the map in javascript
5. Testing the map

We’ll be supporting you every step of the way with project planning,  best practices, technical assistance, and design reviews.

When: 8 weeks starting June 17th

Who: We’re looking for anyone looking to sharpen their interactive cartography skills, however, students currently enrolled in undergraduate or graduate programs will be given preferential consideration. To get the most out of this experience you should:

1. Have experience working with all types of data (spatial, tabular, databases, etc.)
2. Be somewhat comfortable with map and UI design
3. Know the basics of building a map in javascript
4. Be willing to learn all the stuff you don’t know

Where: Wherever you want to be with a computer and internet connection. We all work remotely at Axis Maps and keep in constant contact through Campfire, our group chat system. You’ll be expected to keep semi-regular business hours logged in to Campfire. We’ll have scheduled weekly status meetings (via Skype) dedicated to your project and you’ll be expected to attend regular Axis status meetings as well.

How much: $3,500

To apply: Please send:

1. Cover letter
2. Resume / CV
3. Link to your online portfolio

to David Heyman at info@axismaps.com by May 6th.

Poking around on Twitter today I saw a couple mentions of this map from ESRI, next in what I’m sure will be a long line of maps about Superstorm Sandy. This was the first thematic map I’ve seen about the storm but it struck me as hugely ineffective. Comparing 2 variables (census statistics vs. storm impact) requires a bivariate map. Mapping one variable and hiding the other one behind a mouse action makes it impossible to see any trends or gain any meaning from the two datasets as a whole. Unless you’re interested in just a couple of counties or having the clicking abilities of a 14-year old Farmville addict, the relationship between the data will be lost.

After manually replicating the data from the map, I put together some quick maps of a few value-by-alpha maps (here’s a stellar though academic introduction from its inventors) using indiemapper. VBA maps were originally conceived to visualize election results by visually-weighting (using alpha) red / blue colored counties by their relative populations. The end result gives you an overall sense of the election by making those counties which contributed more to the result (because of their higher population) more visually prominent.

These maps use the same technique except now alpha is controlled by storm impact. Areas with a higher level of impact are more visually prominent that areas of less impact. These maps hopefully quickly give you an understanding of the population affected by the storm. While I’m sure this was the intention of the ESRI map, because of some misplaced interactivity trumping thoughtful cartography, it can’t say the same.

Median Income

Black Population

Percent Residents on Medicare

Percent Uninsured

Unemployment Rate

Sometimes it’s important to explain the fundamentals, just to make sure everyone is starting on the same page and to keep expectations in check. Because our heads are constantly caught up in maps and the internet, we sometimes forget that there are a few basic underlying concepts that others (clients, friends, family, etc.)  might not be grasping fully when they use our maps. A better understanding might help them through potential rough spots and frustrations, often simply resulting from a poor internet connection. We found that explaining these concepts with words alone didn’t get the message across very well. Words like “server”, “code” and “wireless” can stick better when accompanied by a picture, as can the broader concepts that surround them related to how computers request and receive code and data for mapping purposes. This is the internet infographic we came up with: