NYCPlanning / NYCPlanning/data-engineering
CSCL - GeoSupport Integration Tests
Open
Nobody has claimed this yet.
db-cscl
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Bit of a stub to be flushed out
- do the outputs work in geosupport? As in literally, does code run without issue
- do any small changes (center of curvature for example) create problems in geosupport? Do we have changed behavior
etc
Largely or entirely being handled by GSS. Leaving this issue here in case we need to document anything.
From my understanding, GSS is running GRID generation using our etl outputs and comparing to "prod"
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
The issue does not name repository files or tests; start by reviewing the ETL outputs and GSS's GRID-generation comparison against production. Confirm whether the outputs run in Geosupport and whether small changes alter behavior, then document any findings if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100