NYCPlanning / NYCPlanning/data-engineering
PLUTO 26v4
Open
Nobody has claimed this yet.
data update
db-pluto
- 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
Start with the linked Data Update Workflow and Data Catalog wiki pages to understand the PLUTO update process and expected package destinations. Work through the checklist from source extraction through distribution, recording QA and publication progress. Done means every stage is complete and the resulting packages have been distributed.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100