NYCPlanning / NYCPlanning/data-engineering
EDDE - 2025 Follow-on Work
Open
Nobody has claimed this yet.
db-edde
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
knock-on work for #1662 .
- Use dcpy.utils for geoparquet loading
- Rewrite the README, and add instructions for mapping Winnie's data to our build inputs.
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 reading issue #1662 and inspect the current geoparquet loading path and README. Determine where dcpy.utils should be used, then document how Winnie's data maps to the build inputs. Done means both checklist items are implemented and the README instructions are complete and usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100