DOI: 10.15131/shef.data.4110156.v5
title: United States Commutes and Megaregions data for GIS

description: <b>This Figshare dataset contains the files created by and used in a related PLOS ONE paper, entitled 'An economic geography of the United States: from commutes to megaregions', by Garrett Dash Nelson and Alasdair Rae, published 30 November 2016. </b><b><br></b><b>Update: 27 January 2017 - see item 7. below</b><b><br></b>In addition to the files listed below, we have also provided a series of maps here, as high resolution PNGs. The fifth file below can be styled in QGIS using the QML style file provided in number 6.<b><br></b><b>Information on files</b><b><br></b><b>1.</b> A us_ttw_v3_US_only_epsg5070v2 zipped shapefile (for use in GIS software such as ArcGIS or QGIS) containing individual census tract to census tract commuter links for the entire United States, based on the 2006-2010 American Community Survey dataset, as cited in the paper.<br><b>2. </b>The commutes.net file is a Pajek format file used in the derivation of our megaregions within Combo, the partitioning algorithm we used in the paper. Pajek (Program for Large Network Analysis) is a free software package. Combo is an open source modularity optimisation program developed by researchers at MIT, and the source code can be accessed at: http://senseable.mit.edu/community_detection/<br><b>3. </b>A us_ttw_v3_US_only_upto160km_epsg5070v2 zipped shapefile. This is an extract of 1. above but includes only those commutes of 160km or less (approx 100 miles).<br><b>4. </b>A us_ttw_v3_US_only_800km_10plus_epsg5070v2 zipped shapefile. This is an extract of 1. above but includes only those commutes of 10 or more which cover a distance of 800km or more (approx 500 miles). There are just over 28,000 of these and we expect these may be occasional, weekly or otherwise irregular 'commuters' but we are not able to discern this from the underlying dataset.<br><b>5. </b>A merged_ttw_v3_origin_and_dest_communities zipped shapefile. This contains the commute data but each line also has a 'community assignment' field. The ofips_comm (origin community) and dfips_comm (destination community) fields tell you which megaregion each line belongs to. They are mostly the same, but in some cases a flow line crosses between two megaregions. The dfips_comm field was used to decide which megaregion an area belongs to.<br><b>6. </b>We also include a community_colors_20_dec_2016_v3.qml file to accompany 5. above. This is a QGIS style file and can be used to style the maps in the same way as our dark background images on Figshare.<br><b>7. </b>We have also uploaded a zipped folder with two US megaregion shapefiles - one generalized and one at full resolution. These files are similar to Figure 11 in our paper. Whereas Figure 11 was somewhat fluid in terms of the precise location of the boundaries, these files are constructed from Census Tracts so they do not match exactly the lines shown in Figure 11. However, they do provide a very close match to the regions labelled in Figure 11 of the paper. These files are provided so that other researchers can then analyse associated data at these scales. The Shapefiles have three columns - one contains the original megaregion names from the PLOS ONE paper, another contains a new megaregion name based in part on post-publication interactions with readers, and the third column indicates the name of a major city in each megaregion. We hope you find these files useful.<br><b><br></b>Please see the attached readme file for full information.