Happy Friday! Part of the reason for our requesst that you participate in our testing period is to gather feedback on ways to increase the value of Census API service to you. I saw in another thread a mention of using SAIPE rather than ACS for Jan's app. It would be helpful to know which datasets are your highest priorities. Please respond here to suggest which datasets would be most valuable to you as we extend API ...more »
As a developer, I think an API to describe and search for SF1 variables will be very useful. Sample API: http://thedataweb.rm.census.gov/data/2010/sf1/desc/(parameters) Usages: 1. http://thedataweb.rm.census.gov/data/2010/sf1/desc/all returns a JSON array of all SF1 variables and their descriptions. 2. http://thedataweb.rm.census.gov/data/2010/sf1/desc/P0010001 returns information about P0010001 (its name, concept, ...more »
I am trying to make something for all block groups in a county and noticed that I have to make separate requests for each tract. A block group looks like: ?get=P0010001&for=block+group:*&in=state:2+county:170+tract:000101 but it would be nice if we could request: ?get=P0010001,GEOID&for=block+group:*&in=state:2+county:170 so without specifying the tract. The added GEOID (just like NAME) would make make each record unique. ...more »
Any chance of getting this through the API? I'm mashing up Census data with FEC campaign contribution data, and it would be really interesting to have access to attributes on education, income, etc. at the ZIP level.
I have used an XML reader to put the ACS variables into a tree structure. However, because the variables in the XML file are not in order (after the first level), it is not particularly easy to find the variable you want--particularly when there are over 60,000. Am I missing something?
It would be nice to be able to pass in an optional parameter like &coordinates=1 and have the latitude and longitude points of each result returned in a new variable. For example, a state (or block group, tract, etc) would have a coordinate field with the array of lat/lon points of the state outline. Yes it would be a larger amount of data being returned, but it's optional. To save size, the coordinates could be ...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"
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 »
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.
I'm working on a project that would be greatly enhanced by offering the ability to query the database for the number of disabled individuals in a given area.
This data can be found by clicking through the census site, so I wonder why it's not available via the API?
I wish I didn't have to tell users they needed to do their own clicking on this, I'd much rather grab that data for them automatically.
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.
Have reviewed access to the ACS 2011 data by school district. Looks good. Very much need the same for ACS 2010 and Census 2010 SF1 (particularly the single year of age by gender tables iterated by race/origin, but pretty much all of it).
Thanks to all of you who have been working to make the API resources available.