NYCPlanning / NYCPlanning/data-engineering
KPDB on the M-drive
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
CAPS and Housing agree that there's a need to share KPDB data internally for DCP staff to see projections of housing development. Only aggregations by administrative boundaries should be shared to prevent oversharing of non-public records (like pre-certified ZAP applications).
todos
- ask GIS about M-drive standards for filetypes and metadata/documentation
- add (or confirm we already do) all aggregations we want to put on the M-drive
- get and incorporate Housing's feedback on columns and column names in outputs
- put latest build on M-drive and determine how it should be distributed there in the future
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 existing aggregation outputs and asking GIS for M-drive filetype and metadata standards. Confirm which administrative-boundary aggregations are ready, then incorporate Housing's requested columns and names. Done means the latest build is on the M-drive with an agreed distribution process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100