-
**Is your feature request related to a problem? Please describe.**
There are a number of data sets that have latitude and longitude of specific sites in them -- such as eAMLIS data (https://amlis.osm…
-
### Overview
Comparing neighborhoods by the number of requests when each neighborhood council differs widely in population size can be misleading.
### Action Items
- [x] Research ways to joi…
-
**Description**
Investigate measures of home foreclosure rates that are available at the census tract level.
Some leads:
* https://www.huduser.gov/portal/NSP2datadesc.html
* http://www.th…
-
This issue seeks to address "donut holes" in our DAC map. This will involve the following:
1. For all census tracts that have at least one DAC neighbor, calculate the share of neighbors that are DACs…
-
We are going to move forward with adding race/ethnicity and age to the UI. Reports are the ultimate solution for additional demographics.
-
Hi,
block groups don't seem to work anymore. I think this is related to changes in the Census API described [here](https://github.com/uscensusbureau/api-geoHierarchy-changes/blob/master/changes.md)…
-
Should we change our output variable names to be: `census_block_group_id_2010` instead of `fips_block_group_id_2010` ? (and `census_tract_id_2010` instead of `fips_tract_id_2010` ?)
In `st_census_t…
-
I think we need to have a starting point for the data schema for this project.
For each census tract, what attributes/fields that we want? Some initial thoughts:
1. GEOID
2. County
3. Tract numb…
-
Dear all,
I struggle with the error
Error in 1:nrow(x) : argument of length 0
I was hoping that tximport can help here.
Specifically, I imported a shapefile for block groups that include censu…
-
I don't have any issues with `census.geo = "county"` but when I switch to `census.geo = "tract"` I get a data access failure error.
```
probabilities %
predict_race(surname.only = FALSE,
…