Attn Dave: Defunct Counties, Maps, and Old Boundaries
       |           

Welcome, Guest. Please login or register.
Did you miss your activation email?
April 19, 2024, 05:47:29 AM
News: Election Simulator 2.0 Released. Senate/Gubernatorial maps, proportional electoral votes, and more - Read more

  Talk Elections
  About this Site
  Talk Elections Q & A
  How To (Moderator: Virginiá)
  Attn Dave: Defunct Counties, Maps, and Old Boundaries
« previous next »
Pages: [1]
Author Topic: Attn Dave: Defunct Counties, Maps, and Old Boundaries  (Read 2216 times)
Oldiesfreak1854
Atlas Icon
*****
Posts: 13,674
United States


WWW Show only this user's posts in this thread
« on: September 29, 2014, 08:42:22 AM »

Two questions:

1. How would you go about uploading data for defunct counties that never had a FIPS code?
2. Would it be at all possible to add historical county-level shapefiles that don't already exist?
Logged
True Federalist (진정한 연방 주의자)
Ernest
Moderators
Atlas Legend
*****
Posts: 42,156
United States


Show only this user's posts in this thread
« Reply #1 on: September 29, 2014, 11:59:54 PM »

Two questions:

1. How would you go about uploading data for defunct counties that never had a FIPS code?
2. Would it be at all possible to add historical county-level shapefiles that don't already exist?

Depending on how recently it went defunct, it may have had a FIPS code.  For example  Nansemond County, Virginia which got swallowed up by the City of Suffolk in the 70's had the FIPS code of 51-123.

In theory you could insert defunct counties into the gaps that had been intended for new counties, for example Elk County, Alabama could sensibly be assigned 01-050, but that would not work in all cases.  (South Carolina being a prime example because of our funky governmental structure in the antebellum period in which we had districts, counties, and parishes.  Every place was part of a district, but there were also counties and parishes which largely didn't overlap, but there were places that were part of both a county and a parish.)
Logged
Oldiesfreak1854
Atlas Icon
*****
Posts: 13,674
United States


WWW Show only this user's posts in this thread
« Reply #2 on: December 08, 2014, 08:52:03 PM »

Two questions:

1. How would you go about uploading data for defunct counties that never had a FIPS code?
2. Would it be at all possible to add historical county-level shapefiles that don't already exist?

Depending on how recently it went defunct, it may have had a FIPS code.  For example  Nansemond County, Virginia which got swallowed up by the City of Suffolk in the 70's had the FIPS code of 51-123.

In theory you could insert defunct counties into the gaps that had been intended for new counties, for example Elk County, Alabama could sensibly be assigned 01-050, but that would not work in all cases.  (South Carolina being a prime example because of our funky governmental structure in the antebellum period in which we had districts, counties, and parishes.  Every place was part of a district, but there were also counties and parishes which largely didn't overlap, but there were places that were part of both a county and a parish.)
What if it was before FIPS?
Logged
True Federalist (진정한 연방 주의자)
Ernest
Moderators
Atlas Legend
*****
Posts: 42,156
United States


Show only this user's posts in this thread
« Reply #3 on: December 08, 2014, 09:24:39 PM »
« Edited: December 09, 2014, 01:29:40 AM by True Federalist »

Two questions:

1. How would you go about uploading data for defunct counties that never had a FIPS code?
2. Would it be at all possible to add historical county-level shapefiles that don't already exist?

Depending on how recently it went defunct, it may have had a FIPS code.  For example  Nansemond County, Virginia which got swallowed up by the City of Suffolk in the 70's had the FIPS code of 51-123.

In theory you could insert defunct counties into the gaps that had been intended for new counties, for example Elk County, Alabama could sensibly be assigned 01-050, but that would not work in all cases. (South Carolina being a prime example because of our funky governmental structure in the antebellum period in which we had districts, counties, and parishes.  Every place was part of a district, but there were also counties and parishes which largely didn't overlap, but there were places that were part of both a county and a parish.)
What if it was before FIPS?
Read and comprehend.  FIPS was never designed to handle historical data as it wasn't of interest to those who designed it.  Between that and the fact that FIPS is now deprecated as a standard (tho INCITS uses the existing FIPS codes as its starting point), it's not really a great choice for a site such as this.
Logged
RI
realisticidealist
Atlas Icon
*****
Posts: 14,760


Political Matrix
E: 0.39, S: 2.61

Show only this user's posts in this thread
« Reply #4 on: December 08, 2014, 11:38:47 PM »

Washabaugh County, SD is 46131 on the Atlas.
Logged
True Federalist (진정한 연방 주의자)
Ernest
Moderators
Atlas Legend
*****
Posts: 42,156
United States


Show only this user's posts in this thread
« Reply #5 on: December 09, 2014, 01:28:12 AM »

Washabaugh County, SD is 46131 on the Atlas.


Because that is its FIPS/INCITS code.  While Washabaugh County no longer exists (and it only existed for some purposes when it did exist) it didn't get merged into Jackson County until well after FIPS was up and running.  It's the county equivalents that ceased to exist before FIPS was established that don't have FIPS codes.
Logged
Pages: [1]  
« previous next »
Jump to:  


Login with username, password and session length

Terms of Service - DMCA Agent and Policy - Privacy Policy and Cookies

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Page created in 0.036 seconds with 12 queries.