New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix acs 2010 2014 #611
Fix acs 2010 2014 #611
Conversation
('geoidsl', input_['tiger'][self.geography + '_{}'.format(self.year) + GEOID_SUMLEVEL_COLUMN]), | ||
('geoidsc', input_['tiger'][self.geography + '_{}'.format(self.year) + GEOID_SHORELINECLIPPED_COLUMN]), | ||
('geoidsl', input_['tiger'][self.geography + '_{}'.format(self.tiger_year()) + GEOID_SUMLEVEL_COLUMN]), | ||
('geoidsc', input_['tiger'][self.geography + '_{}'.format(self.tiger_year()) + GEOID_SHORELINECLIPPED_COLUMN]), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
line too long (123 > 120 characters)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Point to 2015 geographies to keep retrocompatibility and save disk space, even if it is wrong to do so.
Ok, so this change always bound ACS data to the last Tiger geometries, right? I guess that you considered bounding them to the "right" ones. What made you dismiss that option?
tasks/us/census/acs.py
Outdated
@@ -35,6 +35,7 @@ | |||
CBSA, PLACE] | |||
YEARS = ['2010', '2014', '2015', '2016'] | |||
SAMPLES = [SAMPLE_5YR, SAMPLE_1YR] | |||
MINIMUM_TIGER_YEAR = 2015 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really minor: maybe there might be a YEARS
array at tiger.py
and this could get the first one. that way it'd would also document the available years.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a nice idea. The years belong to tiger indeed.
In the current dump (April 2018), we have the 2010 and 2014 data bounded to 2015 geometries. This patch keeps this behaviour even if its incorrect. Main reason is that the 2014 and 2010 tiger is not at the source we use currently for tiger 2015/2016 (some S3 bucket), so including the geometries means developer effort as well as loading time and bigger dumps. Since it's something that has been broken forever, I don't think it's worth it to fix it now. |
|
Tests are failing, and it seems to be related:
|
Those tests are also broken in master and I've got no idea why. I'll try to see what's happening before merging this. |
('region_name_sl', input_['geoids']['{}_{}{}'.format(tiger_geo,TIGER_YEAR,GEOID_SUMLEVEL_COLUMN)]), | ||
('region_name_sc', input_['geoids']['{}_{}{}'.format(tiger_geo,TIGER_YEAR,GEOID_SUMLEVEL_COLUMN)]), | ||
('region_name_sl', input_['geoids']['{}_{}{}'.format(tiger_geo, TIGER_YEAR, GEOID_SUMLEVEL_COLUMN)]), | ||
('region_name_sc', input_['geoids']['{}_{}{}'.format(tiger_geo, TIGER_YEAR, GEOID_SHORELINECLIPPED_COLUMN)]), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
line too long (121 > 120 characters)
Point to 2015 geographies to keep retrocompatibility and save disk space, even if it is wrong to do so.