NYCPlanning / NYCPlanning/data-engineering
HDB 23Q2 CCD unit change summary file issue
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
HDB 23Q2 used 2023CCDs for aggregation, but joined census data (source for column cenunits20, no others) had information for 2013CCDs.
23Q4 will be with only 2023CCD data, as the source dataset from here has been updated, but we'll need to correct the exports for 23Q2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the 23Q2 export process and the linked 2020 Census source, then identify where cenunits20 is populated from the 2013CCD data. Compare the affected 23Q2 exports with the 2023CCD source and document which outputs require correction. Done means the 23Q2 exports consistently use the intended CCD units.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100