Welcome to your new IdeaScale community! Your community/forum has now been created. We look forward to all your ideas, comments and discussions.
I had already created a thematic map application that gave information about the uncertainty surrounding ACS estimates (move your mouse over the counties). This website generates the map using API data requests. A future expansion will include parsing the variables XML file.
I have an API request where the get argument that works is "P0030001,P0030002,P0030003,P0030004". However, I wanted to get all available names in that concept, which in total is a list of 8 elements "P0030001,P0030002,P0030003,...P0030008".
This request fails with error "unknown variable 'P0030005,P0030006,P0030007,P0030008"
Is there a limit on the length for the GET argument?
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 »
returns a JSON array of all SF1 variables and their descriptions.
returns information about P0010001 (its name, concept,... more »
Is there any support (yet?) for congressional districts and other lower-level geographies in the ACS API? States and counties work fine, but I run into problems as soon as I start to go a little deeper into the hierarchy. Are most of these other area types only supported for the SF1 data?
I get the following response:
["1","620","620","620","620","Block Group 1","02","170","000101"]]
Note that the order of the variable names and... more »
A block group looks like:
but it would be nice if we could request:
so without specifying the tract.
The added GEOID (just like NAME) would make make each record unique.... more »
New geography resources posted to the Geography section of the website at www.census.gov/developers/
I'm glad to see JSON as the response format for the API, but structure makes it really hard to use. I also haven't seen this list-of-lists format for individual records before.
What would work much better would be one of the following:
a) an array of objects. Within each object, each field name is a key, each value is the value associated... more »
Let's take P012B049: African American female 85 years and over. It's extremely tedious to tease apart that this is the combination of three variables: race, sex, and age group. One of the great features of XML is its hierarchical structure, which makes it easy... more »
Please take a look at the source.
Given the dearth of other live examples, I felt like I should post something, though I haven't been able to do a lot of necessary cleanup and polish. It was nice to be able to pull something like this together with just a few hours of work via the Census API, though.
For a given ACS sub-table (anything with an _002E or higher suffix), I'm calling the data for all US counties and dividing... more »
In all of the "sex by age" sets the "85 years and over" label is duplicated for female. I think the first instance is actually just "female".
variable name="P012A026" concept="P12A. Sex By Age (White Alone) ">Female: !! 85 years and over
variable name="P012A049" concept="P12A. Sex By Age (White Alone) ">Female: !! 85 years and over