-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NTA MOE should not appear for top-coded values #759
Comments
@EricaMaurer this is a problem on production too, afaict: https://popfactfinder.planning.nyc.gov/profile/599/economic?reliability=true Does this issue block the new data release from happening? |
I'd love for it to not appear, but good to push through the new data release and tackle this at another point if it's not an easy fix. |
@EricaMaurer I don't think it'll be too bad but I'd like to reduce the # of "variables" in terms of debugging. I think one thing should happen, sniff test, then the other. Sounds like we're cool with tackling this after. |
Makes sense. Don't want it to get lost in the list of issues, but happy to tackle this after releasing the data. |
For NTA geographies (from database) MOE should not appear for top-coded values. Showing in PFF as 0, showing in database as null. Value should be null in PFF. This is not an issue for aggregate geographies.
Example: BK09 https://factfinder-staging.planninglabs.nyc/profile/840/economic?comparator=3&reliability=true
The text was updated successfully, but these errors were encountered: