Feature Requests

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 »

Voting

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 »

Voting

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.

Voting

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?

Voting

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 »

Voting

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"

Voting

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 »

Voting

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.

Voting

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.

Voting

The App Gallery shows Easystats using the API operations. Easystats is presently the only source of ACS 2011 1 year data for 113th Congressional Districts. Can those same data be available to us via API calls? If so, 1) the same scope of ACS 2011 1 year items should be available minimally for the US 010 & states 040 (not supported by easystats) and 2) there needs to be a minimal expansion of another 50-60 subject
...more »

Voting

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 »

Voting

This is a request to simplify the school district API call structures to have only one replacing the three separate calls for unified, secondary and elementary.
The school district codes are unique within state irrespective of the type (U, S, E). Most users are interested in a few districts by name/id, all districts in a state/region or all districts in the U.S. Also, just having the state+district code provides
...more »