NYCPlanning / NYCPlanning/data-engineering
PLUTO QA improvements
Open
Nobody has claimed this yet.
db-pluto
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Follow up to this.
TBD if the following will become GH issues:
- a note somewhere (steamlit page?) that all source data, including zoning and DTM, shouldn't change between builds unless there is a source data issue. Applies to both major and minor
- add new QA flow to wiki
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 comment in issue #1183 and review the repository wiki for the existing QA flow. Clarify whether the source-data note and new QA flow are in scope, then document the agreed behavior and add the corresponding wiki guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering, documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100