The latest articles on DEV Community by Richard (Ryszard) Cieplechowicz (@richardcieplechowicz). https://dev.to/richardcieplechowicz https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4197055%2F493bec7d-80e4-4417-bc1f-957b9149df55.png https://dev.to/richardcieplechowicz en Richard (Ryszard) Cieplechowicz Wed, 21 Oct 2026 00:09:30 +0000 https://dev.to/richardcieplechowicz/building-a-reproducible-tampa-bay-rent-burden-dataset-from-census-acs-data-5h9d https://dev.to/richardcieplechowicz/building-a-reproducible-tampa-bay-rent-burden-dataset-from-census-acs-data-5h9d <p>County averages hide where renters are actually stretched. I wanted ZIP-level rent burden numbers for the Tampa Bay area that anyone could check and reuse, so I built a table covering 132 ZIP Code Tabulation Areas across Hillsborough, Pinellas, Pasco and Hernando counties. This post walks through how it is put together.</p> <h2> Source data </h2> <p>Everything comes from the U.S. Census Bureau's American Community Survey 2020-2024 five-year estimates. The table pulls, for each ZCTA:</p> <ul> <li>Gross rent as a percentage of household income (the shares of renter households paying 30%+ and 50%+ of income on rent)</li> <li>Median gross rent</li> <li>Median household income</li> <li>The household counts behind each share</li> </ul> <p>The five-year estimates are the only ACS product with enough sample size to report at ZCTA level. They describe a survey period, not current rent quotes, and I keep that caveat attached wherever the data is published.</p> <h2> Geography gotcha: ZCTA is not a USPS ZIP </h2> <p>A ZCTA is a Census tabulation geography, not a delivery ZIP. Boundaries will not always match the ZIP on an envelope. If you join this table to other data, join on ZCTA and document the mismatch rather than pretending the two are identical.</p> <h2> Keep the margins of error </h2> <p>Every survey estimate carries a margin of error, and small areas carry larger ones. The table keeps the Census Bureau's published margins next to the estimates instead of dropping them. If a ZCTA's share looks surprising, the margin is the first thing to check.</p> <h2> Reproducibility stack </h2> <ul> <li>CSV with a data dictionary on Kaggle: <a href="https://www.kaggle.com/datasets/richardcieplechowicz/tampa-bay-zip-housing-and-rent-burden-2020-2024" rel="noopener noreferrer">https://www.kaggle.com/datasets/richardcieplechowicz/tampa-bay-zip-housing-and-rent-burden-2020-2024</a> </li> <li>Processed files and code on GitHub: <a href="https://github.com/richard-cieplechowicz/tampa-bay-zip-housing-data" rel="noopener noreferrer">https://github.com/richard-cieplechowicz/tampa-bay-zip-housing-data</a> </li> <li>Mirror dataset card on Hugging Face: <a href="https://huggingface.co/datasets/richardcieplechowicz/tampa-bay-rent-burden-zcta-2020-2024" rel="noopener noreferrer">https://huggingface.co/datasets/richardcieplechowicz/tampa-bay-rent-burden-zcta-2020-2024</a> </li> <li>Archived release with a citable DOI on Zenodo: <a href="https://doi.org/10.5281/zenodo.22940611" rel="noopener noreferrer">https://doi.org/10.5281/zenodo.22940611</a> </li> <li>Method and background on the study page: <a href="https://richardcieplechowicz.com/tampa-bay-rent-burden-by-zcta-2020-2024/" rel="noopener noreferrer">https://richardcieplechowicz.com/tampa-bay-rent-burden-by-zcta-2020-2024/</a> </li> </ul> <p>Two companion tables built the same way cover vacancy composition and owner-occupied home values across the same ZCTAs:</p> <ul> <li>Vacancy: <a href="https://doi.org/10.5281/zenodo.23114340" rel="noopener noreferrer">https://doi.org/10.5281/zenodo.23114340</a> </li> <li>Home values: <a href="https://doi.org/10.5281/zenodo.23114338" rel="noopener noreferrer">https://doi.org/10.5281/zenodo.23114338</a> </li> </ul> <p>If you use the data, cite the Zenodo DOI so the version is pinned.</p> data census python opendata