NYCPlanning / NYCPlanning/data-engineering
COLP 2026-12
Open
Nobody has claimed this yet.
data update
db-colp
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Resources
Data Update Workflow and Data Catalog wiki pages
Stages
- source data extracted
- draft shared for QA
- draft passed QA
- draft published and packaged
- packages distributed to destination
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
Read the Data Update Workflow and Data Catalog wiki pages linked in the issue, then use their documented process to identify the source data and required package destinations. The work is complete when source extraction, QA, publication and packaging, and distribution are all confirmed in the checklist.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100