I am working on a page drawing data from the 1990, 2000 and 2010 SF1 and noticed a lot of differences between them. Most importantly for me: - the variables that can be drawn from the Geographic header varies a lot, in 2010 only the Name, in 1990 and 2000 a whole slew of variables, including a very useful AREALAND, but NAME for one is missing in 1990 - in 2010 the list of available geographies is a lot longer than in ...more »
are there any plans to add support for the 1980 Census and the ACS 2005-2009 5-year estimates? Any timeline on these data sources? They would be a great addition to the API.
Following up on my request of 10 months ago ... it does not appear that any urban population or housing unit items are populated at the block level.
This is a request for Census to populate those few 2010 SF1 urban/rural update fields for all summary levels.
Provide developers with tables of valid state and county codes and any other data used as a parameter for queries
My specific request would be for api access to the statewide non-metropolitan geographic level (need the medians so I can't back into a value). However, I realize this has to be a pretty low priority for most api users. Do the developers have a goal of adding more of these types of geos or should I expect that I'll be going to factfinder for this type of request for years to come? (Extremely happy with the current ...more »
Is there any chance thay data from the 2005-2009 ACS might be included via the API anytime soon? (Or, barring that, is there some sort of anticipated timeline moving forward?)
Perhaps its obvious, but not taking chances ... this is a request to have ACS 2012 1 year and ACS 2012 5 year datasets available when released or soon thereafter. The ACS 2011 scope of geography would be great. 113th congressional districts should be available with the 1 year estimates. It is requested that ACS 2012 (and 2011) 1 year and 5 year subject matter be extended by adding the demographic profiles (dp2 ... ...more »
The ACS API includes geographic summary levels above the state level, the SF1 and SF3 API do not. I would like to see those levels added.
Since United States is a diversity country. People speak different languages over here. Different language represent different culture, and different market. We need language speaker map.
Having used these APIs for a while, I find them very useful and working well. Thank you. Among needed additions/extensions are these items ... APIs structured somewhat like these to access the underlying data as used in the new Census "Americas Economy" app is very much needed ... with as much geographic drill-down as feasible. The two geographies most needed for ACS are CBSAs and school districts. Is it feasible ...more »
In another thread I read about an updated version of the available ACS tables. It would be very handy if table restrictions and Block Group availability would be included in that list. (As in Appendix E of the technical documentation http://www2.census.gov/acs2010_5yr/summaryfile/ACS_2006-2010_SF_Tech_Doc.pdf). In the XML document those restrictions could be attributes of the "concept"
Requesting these additional data be made accessible via the API:
1 -- QuickFacts city and county
2 -- federal state coop program population estimates incrementally updated county and metro; annual components of change & age-gender-race/origin
Appears Census 2010 school districts not among data enhancements. Can these data be made accessible? Thank you.
This adds to my note re the need for 113th Congressional District data (minimally from ACS 2011 1 year data corresponding to easystats). Since all but 2 MSAs are included in the ACS 1 year estimates, most users would benefit from having most recent (ACS 2011 1 year) data for MSAs, unless comparing the MSA with subMSA geography. This is a request to add MSA ACS 2011 1 year (also ACS 2010 and Census 2010 even better) ...more »
It would be nice if the API query could capability include SUMLEV 101 place fields. The Census SF1 documentation does include place fields for SUMLEV 101, but I assume the API only has a subset of 101 implemented.
These 2 API queries do NOT work.