NYCPlanning / NYCPlanning/data-engineering
CPDB: Re-evaluate what to do with non-mapped projects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Only ~30% of projects in CPDB are mapped. To increase this number, around 7 years ago DCP asked other city agencies to help map unmapped projects, and this dataset was manually created. This dataset is becoming out of date and the quality isn't great: for example, bin column has invalid non-numerical values.
At some point, we should meet with the Capital Planning and Support team to re-evaluate how we can map more projects.
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 products/cpdb/data/dcp_cpdb_agencyverified.csv, especially the bin column and the current mapping coverage described in the issue. Then identify the CPDB mapping workflow and coordinate with the Capital Planning and Support team to define the replacement approach. Done requires an agreed way to improve unmapped-project coverage and address the dataset's quality issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100