# Merging a IPUMS with a different county-level data

**URL:** <https://forum.ipums.org/t/merging-a-ipums-with-a-different-county-level-data/2871>\
**Category:** USA\
**Created:** [March 16, 2019, 8:32pm UTC](https://forum.ipums.org/t/merging-a-ipums-with-a-different-county-level-data/2871 "2019-03-16T20:32:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Michelle\_Pratt](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.ipums.org/michelle_pratt/32/194_2.png) [@Michelle\_Pratt](https://forum.ipums.org/u/Michelle_Pratt)\
**Post date:** [March 19, 2019, 1:11pm UTC](https://forum.ipums.org/t/merging-a-ipums-with-a-different-county-level-data/2871/2 "2019-03-19T13:11:41Z")

</div>

In years since 1950, counties are [not directly identifiable](https://usa.ipums.org/usa-action/variables/COUNTYFIP#description_section) in public use microdata, which is why many observations will have a zero. The reply from @JeffBloem on [this forum post](https://forum.ipums.org/t/are-all-counties-available-in-acs-pums-5-year-im-working-with-the-file-and-cannot-find-albemarle-va/2230) does a good job of explaining why and provides some guidance for alternatives.

Whether or not you should drop the observations depends on your analysis, but it would certainly eliminate a large portion of your data.

---

_[View the full topic](https://forum.ipums.org/t/merging-a-ipums-with-a-different-county-level-data/2871)._
