Projects. TileMill. Welcome. AmMap: Interactive flash maps. Better web cartography with dot density maps and new tools « News Apps Blog. Between Brian, Joe, and myself there hasn’t been a time in the last six months where at least one of us wasn’t working with census data.
Back in February we attacked the less-detailed (redistricting) data for print and the web. In April, May, and June we contributed to a joint effort with an esteemed cadre of news nerds to develop census.ire.org, a site intended to make it easier for journalists to report from census data. And to prepare for this recent release, we even spent a week hacking near-complete prototype maps using data that the census had already released, Kings County, New York. We learned hard lessons about the scale and nuance of the census in the last few months, and along the way, further built out our toolkit for making maps.
These maps demonstrate a map style we haven’t attempted before: dot density mapping. Many of the tools needed to create the maps we wanted didn’t exist. Invar Invar automates the generation of map tiles, and the deployment of tiles to S3. Englewood. 2010 Census: Children less than five years old in Chicagoland. By Chris Groskopf and Brian Boyer Aug. 7, 2011 This map shows the distribution of children less than five years old in Cook, Lake, Kane, McHenry, Kankakee, Kendall and DuPage counties as reported by the 2010 U.S. Census. Each dot represents a single child.* Read the story:New U.S. census numbers herald a greater Latino presence in the Chicago area Move your mouse over the map for details.
*What do these numbers mean? This map shows one dot for each child less than five years old as reported in the 2010 U.S. DATAR - Zonages. [soft] Maperitive. [soft] ArcGIS. [API] OpenHeatMap. [soft] OpenStreetMap France. [site] Free Geography Tools. Observatoire des Territoires. [soft] Quantum GIS. [library opensource] Polymaps. [site] Cartographie esthétique prettymaps. The short version is simply that there's a huge amount of data being sent across the network and then processed and finally rendered by your computer. We've looked at the logs for the machine hosting prettymaps and it seems happy enough serving all the requests that people are sending it.
The other reason is that the data hasn't been compressed or optimized as much it could be. For example, the four separate image layers could be collapsed in to a single layer. Likewise the data layers, although we've found a few more places to tighten things up since we first launched. We haven't done a lot of optimizations by design because we wanted to leave all the plumbing exposed so that people could look at it and learn from it and, hopefully, build something new.
(close this message) [site de carto] explication de prettymaps. Prettymaps is an experimental map from Stamen Design. It is an interactive map composed of multiple freely available, community-generated data sources: All the Flickr shapefiles rendered as a semi-transparent white ground on top of which all the other layers are displayed.
Urban areas from Natural Earth both as a standalone layer and combined with Flickr shapefiles for cities and neighbourhoods. Road, highway and path data collected by the OpenStreetMap (OSM) project. In all there are four different raster layers and six data layers (that mean all the map data is sent in its raw form and rendered as visual elements by the browser) that may be visible depending on the bounding box and zoom level of the map. It looks (at least for the stuff you can see) like this: But when you put it all together here's what the world looks like at zoom level 3: At zoom level 4 the shapes of urban areas begin to respond to mouse events on the screen.
At zoom level 8 city names are shown alongside motorways: