search

NYCPlanning / labs-factfinder

New York City Census Reporting Tool
Other
40 stars 12 forks source link

NTA MOE should not appear for top-coded values #759

Open EricaMaurer opened 4 years ago

EricaMaurer commented 4 years ago

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

image

allthesignals commented 4 years ago

@EricaMaurer this is a problem on production too, afaict:

Screen Shot 2020-03-04 at 6 54 22 PM

https://popfactfinder.planning.nyc.gov/profile/599/economic?reliability=true

Does this issue block the new data release from happening?

EricaMaurer commented 4 years ago

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.

allthesignals commented 4 years ago

@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.

EricaMaurer commented 4 years ago

Makes sense. Don't want it to get lost in the list of issues, but happy to tackle this after releasing the data.