-
### What happened + What you expected to happen
```
Traceback (most recent call last):
File "chicago_taxi_fare.py", line 25, in
dataset_transformed = chained_pp.fit_transform(dataset)
Fi…
-
**Describe the bug**
A couple of times the census tract feedback button has been not highlighted during the public engagement demos. I'm asking if we can get usage numbers but in the mean time, and s…
-
## Question
What % of California (and Californians) has (open to the public) transit coverage in GTFS?
## Metrics
By area:
* The % of non-water area of Californian that is within 1/4 mi of a…
-
I ran into a bug that was somewhat hard to track down, even though you caveated it in the documentation:
First, the code snippet:
```
geoHierarchy: {
state: '08', // correct, state is 'ab…
-
Linguistic isolation should not be used in the formula to identify DACs for Puerto Rico.
-
# Purpose
People are not clear that they need to zoom in and they are not clear that they can select non DAC tracts. We removed the first instruction for.... reasons but we should address these usabi…
-
Hi Kyle,
I have a census tract (`120100`) at origin (2015) with NA value in the `B25077_001` variable (median home value). The same census tract in 2020 is almost a perfect fit (i.e. no real chang…
-
**Is your feature request related to a problem? Please describe.**
When importing block group data using `getcensus`, the variables `tract` and `blockgroup` are not formatted correctly. The variable …
-
Using:
```
metadata_config = kubeflow_dag_runner.get_default_kubeflow_metadata_config()
runner_config = kubeflow_dag_runner.KubeflowDagRunnerConfig(kubeflow_metadata_config=metadata_config, tfx_i…
-
Perhaps I am misunderstanding the docs here. The description of the `census.geo` argument indicates it is optional, and that users can instead pass in a `census.data` object so the census API need not…
aridf updated
2 years ago