You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we think about integrating the output of census-data-downloader to be an input into the census-data-aggregator, is it possible to include the jam value information in the headers of the processed files?
For example, in the household income table the column name "10_and_under" would be replaced with "2499_10." The convention of having the headers in units of 1000s makes the 2499 representation a bit awkward though.
The text was updated successfully, but these errors were encountered:
update: I don't think what I initially proposed is necessary anymore. The headers for the lowest and highest bins are fine. A user could optionally provide a jam value for the census aggregator to give a more informative NA for the median if it lives in the lowest/highest bin. However, in the tables that may be downloaded by the downloader that represent medians themselves, the jam values may show up. I think this is connected to the *** annotations, but I need to investigate further.
As we think about integrating the output of census-data-downloader to be an input into the census-data-aggregator, is it possible to include the jam value information in the headers of the processed files?
For example, in the household income table the column name "10_and_under" would be replaced with "2499_10." The convention of having the headers in units of 1000s makes the 2499 representation a bit awkward though.
The text was updated successfully, but these errors were encountered: