-
#### Description
Top and bottom coded values should be grey for selected and comparison area and both time points in change over time
[Example here]( https://factfinder-staging.planninglabs.nyc/ex…
-
#### Description
This could just be a rounding thing but worth checking, the change percent MOE is different when you have a single geog vs the aggregate of geogs that make up that single geog:
[Exam…
-
#### Description
If estimate for either or both time points (or selected area vs comparison area) is 0, change over time/difference shouldn't be calculated (seems it slipped through on the last updat…
-
#### Description
Under 18 years – PopU181: showing all zero values in both 18-22 and 06-10 data, despite correct values in spreadsheet
[Example here](https://factfinder-staging.planninglabs.nyc/ex…
-
### Description
Difference/change of 0 should be shown in grey (only happens sometimes on my end so not sure if it’s a true issue or not)
[Example here](https://factfinder-staging.planninglabs.nyc…
-
### Ticket
[Issue 16067](https://dev.azure.com/NYCPlanning/ITD/_workitems/edit/16067)
[Workflow branch strategy](https://github.com/NYCPlanning/labs-factfinder/issues/1134)
#### 2018-2022
##### ADD …
-
#### Description
- Census Blocks and Community District selections are showing zero values for all Detailed Race and Ethnicity groups with the 2020 Census data source
- "Cohabiting" is spelled inc…
-
Use this Issue to track work related to gathering requirements and creating Issues for the upcoming PFF ACS data updates.
Based on a discussion with Data Engineering, it sounds like there are three m…
-
### For tasks within [Issue 16067](https://dev.azure.com/NYCPlanning/ITD/_workitems/edit/16067), use a workflow inspired by trunk-based development
#### All application developers will use the sa…
-
### Ticket
[Issue 16067](https://dev.azure.com/NYCPlanning/ITD/_workitems/edit/16067)
[Workflow branch strategy](https://github.com/NYCPlanning/labs-factfinder/issues/1134)
#### Task(s)
- [ ] Run …