Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZCTA5 names #613

Open
3 tasks
juanignaciosl opened this issue Jan 25, 2019 · 0 comments
Open
3 tasks

ZCTA5 names #613

juanignaciosl opened this issue Jan 25, 2019 · 0 comments
Assignees

Comments

@juanignaciosl
Copy link
Contributor

Currently, ZCTA5 doesn't set names:

"zcta5": {
"plural_name": "ZCTA5s",
"description": "",
"short_name": "ZCTA5",
"census_code_description": "",
"census_description": "ZCTAs are approximate area representations of U.S. Postal Service (USPS) five-digit ZIP Code service areas that the Census Bureau creates using whole blocks to present statistical data from censuses and surveys. The Census Bureau defines ZCTAs by allocating each block that contains addresses to a single ZCTA, usually to the ZCTA that reflects the most frequently occurring ZIP Code for the addresses within that tabulation block. Blocks that do not contain addresses but are completely surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA; those surrounded by multiple ZCTAs will be added to a single ZCTA based on limited buffering performed between multiple ZCTAs. The Census Bureau identifies five-digit ZCTAs using a five-character numeric code that represents the most frequently occurring USPS ZIP Code within that ZCTA, and this code may contain leading zeros.\r\n\r\nThere are significant changes to the 2010 ZCTA delineation from that used in 2000. Coverage was extended to include the Island Areas for 2010 so that the United States, Puerto Rico, and the Island Areas have ZCTAs. Unlike 2000, when areas that could not be assigned to a ZCTA were given a generic code ending in \u201cXX\u201d (land area) or \u201cHH\u201d (water area), for 2010 there is no universal coverage by ZCTAs, and only legitimate five-digit areas are defined. The 2010 ZCTAs will better represent the actual Zip Code service areas because the Census Bureau initiated a process before creation of 2010 blocks to add block boundaries that split polygons with large numbers of addresses using different Zip Codes.\r\n\r\nData users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The ZCTAs process used primarily residential addresses and was biased towards Zip Codes used for city-style mail delivery, thus there may be Zip Codes that are primarily nonresidential or boxes only that may not have a corresponding ZCTA.",
"source": "U.S. Census Bureau: Geographic Terms and Concepts",
"summary_level": "860",
"census_notes": "",
"table": "zcta5",
"slug": "zcta5",
"name": "US Census Zip Code Tabulation Areas",
"cartographic": true,
"interpolated": true,
"weight": 8,
"fields": {
"geoid": "geoid10",
"aland": "aland10",
"awater": "awater10",
"name": null
}

As they're zip codes, using the id would be nice.

  • Use ids as names for zcta5.
  • Rerun hierarchy names task in order to add zip codes to the hierarchy.
  • Copy the geoid to the name column for US xyz table at those levels.
@alrocar alrocar self-assigned this Feb 7, 2019
@alrocar alrocar mentioned this issue Feb 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants