Open jzadra opened 5 years ago
Correct -- the C tables are in a different ("Combined") format and so they can't be fetched the same. But nearly all are just assembled from data that can be found in other detailed tables.
-Ezra
On Thu, 14 Feb 2019 14:07:30 -0500, Andy Cochran wrote:
Is there a known issue with fetching "C" tables?
I'm having trouble getting C16001 for 2017 (and 2016 and 2015), although it used to work maybe a year ago for 2016. The table does exist for the year and span I'm looking for: censusreporter.org.
Here's the error:
acs::acs.lookup(table.number = "C16001", endyear = 2017) [1] NA Warning messages: 1: In acs::acs.lookup(table.number = "C16001", endyear = 2017) : acs.lookup for endyear>2015: using 2015 variable codes to access 2017 data. (See ?acs.lookup for details) 2: In acs::acs.lookup(table.number = "C16001", endyear = 2017) : Sorry, no tables/keyword meets your search. Suggestions: try with 'case.sensitive=F', remove search terms, change 'keyword' to 'table.name' in search (or vice-versa)
― You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.*
--
Ezra Haber Glenn, AICP
Department of Urban Studies and Planning
Massachusetts Institute of Technology
77 Massachusetts Ave., Room 7-346
Cambridge, MA 02139
eglenn@mit.edu
http://dusp.mit.edu/faculty/ezra-glenn
617.253.2024 (w)
617.721.7131 (c)
Thanks. Is this a limitation of the way the acs package makes the API calls, or is it that the API itself doesn't support C tables?
Unfortunately the B version (B16001) has a lot of missing data and geographies smaller than states due to how many categories there are so I can't use it to build the data that is in the C16001 table.
I think it's the package more, not the api.
The system for looking up variables and fetching data is actually a bit outdated, and sort of just hobbling along. I really haven't been able to spend the time to maintain and update, and have even started looking for someone else to take on the role of package maintainer -- so perhaps someday in the not too distant future...
--Ezra
On Thu, 14 Feb 2019 14:18:35 -0500, Andy Cochran wrote:
[1 <text/plain; UTF-8 (7bit)>] [2 <text/html; UTF-8 (7bit)>] Thanks. Is this a limitation of the way the acs package makes the API calls, or is it that the API itself doesn't support C tables?
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.*
--
Ezra Haber Glenn, AICP
Department of Urban Studies and Planning
Massachusetts Institute of Technology
77 Massachusetts Ave., Room 7-346
Cambridge, MA 02139
eglenn@mit.edu
http://dusp.mit.edu/faculty/ezra-glenn
617.253.2024 (w)
617.721.7131 (c)
Is there a known issue with fetching "C" tables?
I'm having trouble getting C16001 for 2017 (and 2016 and 2015). The table does exist for the year and span I'm looking for: censusreporter.org.
Here's the error: