Badges [ 7 ] [-]
Activity Stream [+]
Ideas Contributed [ 30 ] [+]
... seems very slow. Can we expect this speed or is it just today ... or maybe something else?
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.
An ACS 2013 CBSA "name" in the API call is "for=metropolitan+statistical+area/micropolitan+statistical+area"
That does not work for summary level 314.
What is the spelling of the "name" for a metropolitan division? Guessing,
"for=metropolitan+division" does not work.
Can you please provide a full sample? complete with a MD code.
this applies to block groups, but others as well ... '+county:*+tract:*' with acs5 is not set to operate with the * wildcarding (using the above selects the first BG in each county only) but would be immensely valuable if county and tract can accept wildcarding rather than specific values. For most users, looking up a tract code is infeasible and generally not desireable (multi tracts being the norm). Thank you and ...more »
The acs5 at state level uses a gnis coding in query. maybe others do also. It is suggested that only FIPS codes, census codes (places, tracts etc), and OMB codes (cbsa etc) be used. folks are far more familiar with FIPS codes and it willl reduce a) confusion and b) Census resources to maintain a additional layer of geocodes. it might be that gnis is going to be a national standard, maybe, but we are not there now.
This is intended to be positive & helpful ... to Census: the scope of tables/items is insufficient to build "real" generalized applications. Too many key tables are missing (for typical users) and many of those included are relatively infrequently used. To make this "catch" with the broad developer community, the subject matter data needs expansion. For ACS 5 year data, consider first all of those tables that are ...more »
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 »
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.
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 »
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 »
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 »
Need code list for AIA. The SF1 identification section shows this field -- American Indian Area/Alaska Native Area/ Hawaiian Home Land (FIPS) AIANHHFP 5 81 A/N 00001–89999 American Indian area, Alaska Native area, or Hawaiian home land This is apparently the code field required by the API (both SF1 and ACS). Geography division cannot locate this file. most all references are now 4 digit ANSI codes (includiing ...more »