us_geo 1.0.3 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1558db467c74232d766fbb9f54b31549d75e7891509ac4d9c12f4c1be213ec89
-  data.tar.gz: 516c03eca942611fe80a47e556efc7d201f8cdca829d82465bf1a326da8e5bdb
+  metadata.gz: 2dfc74542cb99a60205494e209802884c849a4bd0f05f06fc1bb644d7ad27e62
+  data.tar.gz: 39e6ca65501f0244529893ba3eb4b1a3ff07aa836649f8beeaad70ed380e9b69
 SHA512:
-  metadata.gz: da1ce0e7b45bc892cfffb8990703e2369468676698b23b5dcf0f870949e9e9d9ec411d0ed9c04893cf828f5d97dd981c7f8dc30c9479cf02b78965191b4cc110
-  data.tar.gz: eb911802a12dd31b41cf48c7f43ce8bc44e714e9d996b72327414ba2758ad600586576fcf4720c36a2f0af6b8bf5e5dfca28660dce86dbdd897d9cedd8a468c1
+  metadata.gz: 4fdf470e2c5773e4ca335b89dfdd79ba67205160bc894118be7898ccddaabd5a81fecc448ce2ab8fc775823935b6df60f493fdfd4647f90c1d35e35254a53f10
+  data.tar.gz: 7424c521ab4736f001392640240de3ba1255656babacbd2eef45b036a260060ac57e73e0bd147f3cc4f5811dcbd79da2a0a13009dbcfeea8f27196972d1bfac4

data/CHANGELOG.md

@@ -0,0 +1,82 @@
+# Changelog
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## 2.0.0
+
+### Changed
+
+- Data is now based on the 2020 U.S. Census
+  * ZCTAs have been both added and removed
+  * Places have been both added and removed
+  * Some counties and subdivisions have been renamed
+  * A number of smaller urban areas have been removed
+  * Former U.S. territories (Micronesia, Palau, and Marshall Islands) have been removed
+
+- Population and housing unit numbers are now based on the 2021 [American Community Survey Five Year Estimates](https://www.census.gov/programs-surveys/acs).
+
+- Entities that are legally independent of other county subdivisions are included as both county subdivisions and places.
+
+- Areas in the CSV data files are now in square miles instead of square meters to match the data after it is imported into a database.
+
+### Added
+
+- ZCTA's are now associated with a primary place defined as the place with the most overlapping land area with the ZCTA.
+
+- ZCTAS's are now associated with county subdivisions and have a primary county subdivision which is the one with the moste land area overlapping the ZCTA.
+
+- 2010 ZCTAs can still be used to lookup the active ZCTA through the ZCTAMapping model.
+
+- Core Based Statistical Areas and Combined Statistical Areas now have a short name which is the name of just the largest city in the area. This makes them a little easier to refer to by name.
+
+- All Geographic entity models now have land area, water area, population, and housing units columns.
+
+- Urban Areas are now associated with county subdivisions.
+
+- Counties can now have multiple time zones. You can still call `time_zone` to get a single time zone for a county, but it is more accurate to call `time_zones` instead. There are only a handful of counties that span time zones and none are heavily populated (the largest is Coconino County, AZ with 145K people).
+
+### Removed
+
+- The Designated Market Area model has been removed. This data was a crude mapping from counties to DMA's and was not accurate since it didn't respect the actual borders. The table and foreign keys to it will not be removed if they are already in your database. See the [updating guide](UPDATING_TO_VERSION_2.md) form more details.
+
+- Population and housing unit data has been removed from the overlap models used to join entities (i.e. `ZctaCounty`, `ZctaPlace`, `PlaceCounty`). This information is no longer available directly from the Census relationship files. Only the overlapping land and water area is now available.
+
+- The `USGeo::Demographics` module has been removed. The functionality is split into `USGeo::Area` and `USGeo::Population`.
+
+- Dropped support for ActiveRecord 5.0 and 5.1
+
+- Dropped support for Ruby 2.5.
+
+### Fixed
+
+- Fixed arithmetic for converting area from square miles to kilometers.
+
+## 1.0.3
+
+### Added
+
+- Make dependencies compatible with Rails 6
+
+## 1.0.2
+
+### Added
+
+- Add missing metropolitan division codes to counties
+
+### Changed
+
+- Fix short name logic to be more conservative in how it shortens names
+
+## 1.0.1
+
+### Changed
+
+- Fix logic to enforce place short name limit on databases that don't have character limits.
+
+## 1.0.0
+
+### Added
+
+- Initial release

data/MIT_LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Brian Durand
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -1,50 +1,57 @@
 # USGeo
 
 [![Build Status](https://travis-ci.com/bdurand/us_geo.svg?branch=master)](https://travis-ci.com/bdurand/us_geo)
-[![Maintainability](https://api.codeclimate.com/v1/badges/a01ffc7f707686416c0d/maintainability)](https://codeclimate.com/github/bdurand/us_geo/maintainability)
+[![Ruby Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://github.com/testdouble/standard)
 
-This gem provides a variety of U.S. geographic data ActiveRecord models. It is designed to provide a normalized way to access the data from a relational database. This is by no means a complete set of data. The primary purpose it was built is to provide a way to match most ZIP codes to higher level geographic entities.
+This gem provides a variety of U.S. geographic data ActiveRecord models. It is designed to provide a normalized way to access the data from a relational database. This is by no means a complete set of data.
+
+The primary purpose it was built for is to provide a way to match ZIP codes to higher level geographic entities.
+
+You can use the data from this gem in non-Ruby probjects. The data is provided as [CSV files](./data/2020_dist/) which you can import into any database or spreadsheet. You can see the database structure in the [schema.rb file](./db/schema.rb).
 
 ## Entities
 
-All of the entities except for DMA are defined by the U.S. Census Bureau. For more details.
+All of the entities are defined by the U.S. Census Bureau. For more details.
 
 https://www2.census.gov/geo/pdfs/reference/geodiagram.pdf
 https://www2.census.gov/geo/pdfs/reference/GARM/Ch2GARM.pdf
 
-All entities in the system are keyed using external identifier.
+[![](https://mermaid.ink/img/pako:eNqFVEFuwjAQ_IrlM_kAQpVa0iNS1YhLlcvGXqglx0a2U4lS_t7EDlESlpALZmZ2s5qd-MKFlcjXXGjwPldwdFCXhrVPRNgnHpU1pRljufpR_g4tAgRkU2xrGxPOFFY0lSTbfIkAU-RDg8B5D4dv4FF2L1U-KAH61SHMVXWlzBPRDoOzJ6tVAEOwSiyxo1ralL2rqMIIq1-UD6itbnxAd2M6T9gmy14GQyl0YulU0FvYgfHIxr0SnhYdiXzS5fYvUnHJCU_7ng-VzuzBVEkzt5xt_rJsYaexZraIpzW3ccgI9PMtvfARS1hHxYAwZqHfUpCGCKVVpu-DIEY7njHjMUiK2NEkocnsUZYHRR_UOwFf8RpdDUq2d8ulKyh5-MYaS75ujxIP0OhQ8tJcW2lzkm2W3qUK1vH1AbTHFYcm2OJsxAAkVX9HDSjGql1_i3U_13-31qQd?type=png)](https://mermaid.live/edit#pako:eNqFVEFuwjAQ_IrlM_kAQpVa0iNS1YhLlcvGXqglx0a2U4lS_t7EDlESlpALZmZ2s5qd-MKFlcjXXGjwPldwdFCXhrVPRNgnHpU1pRljufpR_g4tAgRkU2xrGxPOFFY0lSTbfIkAU-RDg8B5D4dv4FF2L1U-KAH61SHMVXWlzBPRDoOzJ6tVAEOwSiyxo1ralL2rqMIIq1-UD6itbnxAd2M6T9gmy14GQyl0YulU0FvYgfHIxr0SnhYdiXzS5fYvUnHJCU_7ng-VzuzBVEkzt5xt_rJsYaexZraIpzW3ccgI9PMtvfARS1hHxYAwZqHfUpCGCKVVpu-DIEY7njHjMUiK2NEkocnsUZYHRR_UOwFf8RpdDUq2d8ulKyh5-MYaS75ujxIP0OhQ8tJcW2lzkm2W3qUK1vH1AbTHFYcm2OJsxAAkVX9HDSjGql1_i3U_13-31qQd)
+
+All entities in the system are keyed using external identifiers.
 
-* The various `geoid` columns reference the id used by the U.S. Census Bureau.
+* The various `geoid` columns reference the id used by the [U.S. Census Bureau](https://www.census.gov/programs-surveys/geography/guidance/geo-identifiers.html).
 
-* The `gnis_id` columns are the official ID's assigned by the U.S. Board on Geographic Names https://geonames.usgs.gov.
+* The `gnis_id` columns are the official ID's assigned by the [U.S. Board on Geographic Names](https://geonames.usgs.gov).
 
 
 There are no foreign key constraints defined on the tables. This is intentional so that you can only import as much data as you need if you don't need the whole set.
 
-The data set currently contains
+The data set currently contains:
 
 * 4 Regions
 * 9 Divisions
-* 59 States and Territories
-* 210 Designated Market Areas
+* 56 States and Territories
 * 175 Combined Statistical Areas
-* 938 Core Based Statistical Areas
+* 939 Core Based Statistical Areas
 * 31 Metropolitan Divisions
-* 3223 Counties or equivalents
-* 36429 County Subdivisions
-* 3601 Urban Areas
-* 30187 Places
-* 33120 ZIP Code Tabulation Areas
+* 3234 Counties or equivalents
+* 35,657 County Subdivisions
+* 2,313 Urban Areas
+* 31,846 Places
+* 33,791 ZIP Code Tabulation Areas
 
-In addition, there entity to entity mapping tables:
+The population, number of housing units, land area, and water area is supplied for all geographic entities.
 
-* 44388 ZCTA to County
-* 17389 ZCTA to Urban Area
-* 49843 ZCTA to Place
-* 4945 Urban Area to County
-* 31492 Place to County
+In addition, there entity to entity mapping tables containing information about how entities overlap with each other:
 
-The land and water area for all entities is given in square miles.
+* 46,953 ZCTA to County
+* 109,549 ZCTA to County Subdivision
+* 14,455 ZCTA to Urban Area
+* 53,131 ZCTA to Place
+* 33,276 Place to County
+* 33,09 County to Urban Area
+* 11,755 County Subdivison to Urban Area
 
 ### Region
 
@@ -56,29 +63,23 @@ A grouping of states within a region.
 
 ### State
 
-Includes both states and territories and the District of Columbia.
+Includes both states, territories, and the District of Columbia.
 
-### Designated Market Area (DMA)
+### Core Based Statistical Area (CBSA)
 
-Media marketing areas of counties served by the same over the air radio and television signals. DMA's are not official government designations and are defined by the Nielsen Company.
+A grouping of counties around an urban core defined by commuting patterns. CBSA's are split into metropolitan (population > 50,000) and micropolitan areas. Counties within a CBSA are either identified as being core or outlyer counties. Not all counties belong to a CBSA.
 
 ### Combined Statistical Areas
 
 Groupings of adjacent CBSA's with regional ties to each other.
 
-### Core Based Statistical Area (CBSA)
-
-A grouping of counties around an urban core defined by commuting patterns. CBSA's are split into metropolitan (population > 50,000) and micropolitan areas. Counties within a CBSA are either identified as being core or outlyer counties. Not all counties belong to a CBSA.
-
 ### Metropolitan Division
 
-The largest CBSAs (New York, Chicago, etc.) are split into metropolitan divisions.
+The largest CBSAs (New York, Chicago, etc.) are further split into metropolitan divisions based around the largest regional cities.
 
 ### County (or county equivalent)
 
-Basic organizational unit of states and territories. The actual name of the unit can vary depending on the state (i.e. parishes is Louisiana).
-
-County data is only provided for states, the District of Columbia, Puerto Rico. It is not provided for other U.S. territories.
+Basic organizational unit of states and territories. The actual name of the unit can vary depending on the state (i.e. parishes is Louisiana). This also includes cities that are independent of any county.
 
 ### County Subdivision
 
@@ -88,59 +89,61 @@ Subdivision of counties. These could be minor civil divisions like townships or
 
 Urbanized areas or clusters. Areas with 2,500 to 50,000 inhabitants is considered an urban cluster while more than 50,000 is an urbanized area. Urban areas can span counties, but the one with the majority of the population is identified as the primary county.
 
-Urban area data is only provided for states, the District of Columbia, Puerto Rico. It is not provided for other U.S. territories.
-
 ### Place
 
-A place is an organized area within a state usually corresponding to a city, town, village, etc. Places are within a single state, but may span counties. If a place spans multiple counties, the county with the most population will be identified as the primary county. Places may belong to an urban area.
+A place is an organized area within a state usually corresponding to a city, town, village, etc. Places are within a single state, but may span counties. If a place spans multiple counties, the county with the most land area will be identified as the primary county.
 
 ### ZIP Code Tabulation Area (ZCTA)
 
 Approximate equivalent to U.S. Postal Service ZIP codes, but designed for geographic and demographic purposes rather than mail routing. Not all postal ZIP codes are mapped to ZCTAs (i.e. ZIP codes mapped to a single building) and the borders of ZCTAs smooth out some of the irregularities of ZIP codes. Otherwise, they are mostly interchangeable.
 
-ZCTAs can span counties, urban areas, places. The primary county and primary urban area will be the ones that contain most of the ZCTA's population.
+ZCTAs can span counties, county subdivisions, and places. A primary county, county subdivision, and place are identified for ZCTA's. This will be the one that includes most of the ZCTA's land area.
 
 ZCTA data is only provided for states, the District of Columbia, Puerto Rico. It is not provided for other U.S. territories.
 
+The U.S. Postal Service adds and removes ZIP Codes as necessary for the efficient delivery of mail. The U.S. Census Bureau updates the ZCTA's to reflect these changes during the decenniel census. The list of retired 2010 ZCTA's can still be used via the `USGeo::Zcta.for_zipcode` method. If you search on a retired ZIP code with this method, it will return the ZCTA with the most land overlap with the retired ZIP code.
+
+## Installation
 
-## Usage
+_Note: if you are not using Rails, then replace all the `rails` commands below with `rake`_
 
 First add to you Gemfile:
 
 `gem us_geo`
 
-Install the migrations:
+Install the migrations.
 
 ```bash
-rake us_geo_engine:install:migrations
+rails us_geo_engine:install:migrations
+rails db:migrate
 ```
 
-Import the data:
+Import the data.
 
 ```bash
-rake us_geo:import:all
+rails us_geo:import:all
 ```
 
 Or, if you only want to import some subset of the data, you can run any number of the following.
 
 ```bash
-rake us_geo:import:regions
-rake us_geo:import:divisions
-rake us_geo:import:states
-rake us_geo:import:designated_market_areas
-rake us_geo:import:combined_statistical_areas
-rake us_geo:import:core_based_statistical_areas
-rake us_geo:import:metropolitan_divisions
-rake us_geo:import:counties
-rake us_geo:import:county_subdivisions
-rake us_geo:import:urban_areas
-rake us_geo:import:places
-rake us_geo:import:zctas
-rake us_geo:import:place_counties
-rake us_geo:import:urban_area_counties
-rake us_geo:import:zcta_counties
-rake us_geo:import:zcta_places
-rake us_geo:import:zcta_urban_areas
+rails us_geo:import:regions
+rails us_geo:import:divisions
+rails us_geo:import:states
+rails us_geo:import:combined_statistical_areas
+rails us_geo:import:core_based_statistical_areas
+rails us_geo:import:metropolitan_divisions
+rails us_geo:import:counties
+rails us_geo:import:county_subdivisions
+rails us_geo:import:urban_areas
+rails us_geo:import:places
+rails us_geo:import:zctas
+rails us_geo:import:urban_area_counties
+rails us_geo:import:urban_area_county_subdivisions
+rails us_geo:import:place_counties
+rails us_geo:import:zcta_counties
+rails us_geo:import:zcta_county_subdivisions
+rails us_geo:import:zcta_places
 ```
 
 By default this will download the data from files hosted with the project on GitHub and insert/update into the database. If any entity records are found that don't exist in the data files, the `removed` flag on the database rows will be set to `TRUE`.
@@ -151,4 +154,18 @@ You can also load the data programatically by simply calling the `load!` method
 
 All records imported from the data files will have their status set to 1 (imported). Any records that were previously imported, but that are no longer in the data file, will have their status changed to -1 (removed) to indicate that they are no longer in the official data set. Finally, records added to the tables manually will have their status set to 0 (manual). It is perfectly acceptable to augment the data set to, for example, add new Postal Service ZIP codes that did not exist during the last census.
 
-This gem can be used outside of a Rails application. You'll just need to copy the migrations by hand and install the import rake tasks.
+You can cleanup all previously imported records that are no longer in the current data set by running:
+
+```bash
+rails us_geo:import:cleanup
+```
+
+## Contributing
+
+Open a pull request on GitHub.
+
+Please use the [standardrb](https://github.com/testdouble/standard) syntax and lint your code with `standardrb --fix` before submitting.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/UPDATING_TO_VERSION_2.md

@@ -0,0 +1,172 @@
+# Version 2 Update Guide
+
+## Update Data
+
+When updating from version 1.x of the gem, first install and run the new database migrations:
+
+_Note: if you are not using Rails, then replace all the `rails` commands below with `rake`_
+
+```bash
+rails us_geo_engine:install:migrations
+rails db:migrate
+```
+
+Then re-import the data:
+
+```bash
+rails us_geo:import:all
+```
+
+Or, if you only want to import some subset of the data, you can run any number of the following:
+
+```bash
+rails us_geo:import:regions
+rails us_geo:import:divisions
+rails us_geo:import:states
+rails us_geo:import:combined_statistical_areas
+rails us_geo:import:core_based_statistical_areas
+rails us_geo:import:metropolitan_divisions
+rails us_geo:import:counties
+rails us_geo:import:county_subdivisions
+rails us_geo:import:places
+rails us_geo:import:zctas
+rails us_geo:import:urban_areas
+rails us_geo:import:place_counties
+rails us_geo:import:zcta_counties
+rails us_geo:import:zcta_county_subdivisions
+rails us_geo:import:zcta_places
+rails us_geo:import:zcta_urban_areas
+rails us_geo:import:urban_area_counties
+rails us_geo:import:urban_area_county_subdivisions
+```
+
+## Data Changes
+
+A number of records have been removed in the 2020 data set. These records are marked with a `status` of -1 in the record. Removed records can still be found by queries and will show up in `belongs_to` associations. However, they will not be returned by any `has_many` associations.
+
+For instance, if a County Subdivision was removed in the new data set, you could still find it with `CountySubdivision.find`, but calling `county.subdivisions` would not return it. If you want to keep specific records, you can change the `status` to 0 to indicate it was manually added.
+
+You can see how many removed rows are in each table by running:
+
+```bash
+rails us_geo:import:removed_counts
+```
+
+You can export data from the removed rows to JSON by running:
+
+```bash
+rails us_geo:import:dump_removed
+```
+
+You can delete the removed rows by running:
+
+```bash
+rails us_geo:import:cleanup
+```
+
+## Database Changes
+
+There were a few database changes made in version 2. The tables and columns will not be automatically dropped from the database. If you were making use of those values, you can continue to do so. However, they will not be updated in the imported data and support for them has been removed from the code.
+
+### Option 1: Cleaning up the database
+
+If you wish to remove the tables and colums, you can add this migration to do so:
+
+```ruby
+class CleanupUsGeoVersion1Tables < ActiveRecord::Migration[5.0]
+  disable_ddl_transaction!
+
+  def up
+    drop_table :us_geo_designated_market_areas
+
+    remove_column :us_geo_counties, :dma_code
+
+    remove_column :us_geo_zcta_counties, :population
+    remove_column :us_geo_zcta_counties, :housing_units
+
+    remove_column :us_geo_zcta_places, :population
+    remove_column :us_geo_zcta_places, :housing_units
+
+    remove_column :us_geo_zcta_urban_areas, :population
+    remove_column :us_geo_zcta_urban_areas, :housing_units
+
+    remove_column :us_geo_urban_area_counties, :population
+    remove_column :us_geo_urban_area_counties, :housing_units
+  end
+
+  def down
+    raise ActiveRecord::IrreversibleMigration
+  end
+end
+```
+
+If you are using these tables in a production environment, you should instruct the models to ignore columns before dropping them. You can do that by deploying an initializer with this code *before* running the migration to drop the columns:
+
+```
+USGeo::County.ignored_columns = %w[dma_code]
+USGeo::ZctaCounty.ignored_columns = %w[population housing_units]
+USGeo::ZctaPlace.ignored_columns = %w[population housing_units]
+USGeo::ZctaUrbanArea.ignored_columns = %w[population housing_units]
+USGeo::UrbanAreaCounty.ignored_columns = %w[population housing_units]
+```
+
+### Option 2: Restoring the model
+
+You can restore the previous models and methods if you wish to continue using them with this code.
+
+```ruby
+module USGeo
+  class DesignatedMarketArea < BaseRecord
+    include Population
+    include Area
+
+    self.primary_key = "code"
+
+    has_many :counties, foreign_key: :dma_code, inverse_of: :designated_market_area
+  end
+end
+
+USGeo::County.belongs_to :designated_market_area, foreign_key: :dma_code, optional: true, inverse_of: :counties
+
+module USGeo
+  class ZctaPlace
+    include Population
+
+    def percent_zcta_population
+      population.to_f / zcta.population.to_f
+    end
+
+    def percent_place_population
+      population.to_f / place.population.to_f
+    end
+  end
+end
+
+module USGeo
+  class ZctaCounty
+    include Population
+
+    def percent_zcta_population
+      population.to_f / zcta.population.to_f
+    end
+
+    def percent_county_population
+      population.to_f / county.population.to_f
+    end
+  end
+end
+
+module USGeo
+  class ZctaUrbanArea
+    include Population
+
+    def percent_zcta_population
+      population.to_f / zcta.population.to_f
+    end
+
+    def percent_urban_area_population
+      population.to_f / urban_area.population.to_f
+    end
+  end
+end
+```

data/VERSION

@@ -0,0 +1 @@
+2.0.0

data/db/migrate/20190221054200_create_regions.rb

@@ -1,6 +1,9 @@
-class CreateRegions < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateRegions < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_regions)
+
     create_table :us_geo_regions, id: false do |t|
       t.integer :id, primary_key: true, null: false, limit: 1
       t.string :name, null: false, limit: 30, index: {unique: true}
@@ -12,5 +15,4 @@ class CreateRegions < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_regions
   end
-
 end

data/db/migrate/20190221054300_create_divisions.rb

@@ -1,6 +1,9 @@
-class CreateDivisions < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateDivisions < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_divisions)
+
     create_table :us_geo_divisions, id: false do |t|
       t.integer :id, primary_key: true, null: false, limit: 1
       t.integer :region_id, null: false, limit: 1, index: true
@@ -13,5 +16,4 @@ class CreateDivisions < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_divisions
   end
-
 end

data/db/migrate/20190221054400_create_states.rb

@@ -1,6 +1,9 @@
-class CreateStates < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateStates < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_states)
+
     create_table :us_geo_states, id: false do |t|
       t.string :code, primary_key: true, null: false, limit: 2
       t.string :name, null: false, limit: 30, index: {unique: true}
@@ -16,5 +19,4 @@ class CreateStates < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_states
   end
-
 end

data/db/migrate/20190221054500_create_combined_statistical_areas.rb

@@ -1,6 +1,9 @@
-class CreateCombinedStatisticalAreas < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateCombinedStatisticalAreas < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_combined_statistical_areas)
+
     create_table :us_geo_combined_statistical_areas, id: false do |t|
       t.string :geoid, primary_key: true, null: false, limit: 3
       t.string :name, null: false, limit: 60, index: {unique: true}
@@ -16,5 +19,4 @@ class CreateCombinedStatisticalAreas < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_combined_statistical_areas
   end
-
 end

data/db/migrate/20190221054600_create_core_based_statistical_areas.rb

@@ -1,6 +1,9 @@
-class CreateCoreBasedStatisticalAreas < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateCoreBasedStatisticalAreas < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_core_based_statistical_areas)
+
     create_table :us_geo_core_based_statistical_areas, id: false do |t|
       t.string :geoid, primary_key: true, null: false, limit: 5
       t.string :csa_geoid, limit: 5, index: true
@@ -20,5 +23,4 @@ class CreateCoreBasedStatisticalAreas < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_core_based_statistical_areas
   end
-
 end

data/db/migrate/20190221054650_create_metropolitan_divisions.rb

@@ -1,6 +1,9 @@
-class CreateMetropolitanDivisions < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateMetropolitanDivisions < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_metropolitan_divisions)
+
     create_table :us_geo_metropolitan_divisions, id: false do |t|
       t.string :geoid, primary_key: true, null: false, limit: 5
       t.string :cbsa_geoid, limit: 5, index: true
@@ -17,5 +20,4 @@ class CreateMetropolitanDivisions < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_metropolitan_divisions
   end
-
 end

data/db/migrate/20190221054700_create_counties.rb

@@ -1,6 +1,9 @@
-class CreateCounties < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateCounties < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_counties)
+
     create_table :us_geo_counties, id: false do |t|
       t.string :geoid, primary_key: true, limit: 5, null: false
       t.integer :gnis_id, null: false, index: true
@@ -12,7 +15,6 @@ class CreateCounties < ActiveRecord::Migration[5.0]
       t.boolean :central, default: false
       t.string :fips_class_code, null: false, limit: 2
       t.string :time_zone_name, null: true, limit: 30
-      t.string :dma_code, limit: 3, null: true, index: true
       t.float :land_area, null: true
       t.float :water_area, null: true
       t.integer :population, null: true
@@ -30,5 +32,4 @@ class CreateCounties < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_counties
   end
-
 end

data/db/migrate/20190221054800_create_zctas.rb

@@ -1,6 +1,9 @@
-class CreateZctas < ActiveRecord::Migration[5.0]
+# frozen_string_literal: true
 
+class CreateZctas < ActiveRecord::Migration[5.0]
   def up
+    return if table_exists?(:us_geo_zctas)
+
     create_table :us_geo_zctas, id: false do |t|
       t.string :zipcode, primary_key: true, null: false, limit: 5
       t.string :primary_county_geoid, null: false, limit: 5, index: true
@@ -19,5 +22,4 @@ class CreateZctas < ActiveRecord::Migration[5.0]
   def down
     drop_table :us_geo_zctas
   end
-
 end