NYCPlanning / NYCPlanning/data-engineering
COLP Housenums have invalid values
Open
Nobody has claimed this yet.
db-colp
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
In version 23v2, per @croswell81:
"HNUM was normalized from "=-T" to "T" - Not sure if this should just be blank?"
An Example
| UID | BBL | ObjectID |
|---|---|---|
| 115cf001a411021a802468dab4924f3b | 4161000175 | 1121 |
It's not urgent, and can be addressed prior to the next COLP release
cc @AmandaDoyle
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
Locate the COLP v23v2 transformation or source that produces HNUM, then trace how the example BBL 4161000175 is normalized. Confirm the intended handling of the "=-T" value with the issue context, and verify that the resulting HNUM value matches the agreed behavior before the next COLP release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100