We've been using some of the 2010 census data (ACS5,SF1) by calling it using JSONP. After several months of functioning fine, it is throwing an error today. My code hasn't changed, is something broken on your end?
Bugs / Problems
I get an error when I try to return ACS5 Median Age data for places. The same query (URL) works for counties.
I have the following query strings for the sf1_2010.xml, sf1_2000.xml, and sf1_1990.xml respectively. All query strings are the same format, just different query values: 1) http://api.census.gov/data/2010/sf1?key=a8e19a47c9c91ffa82c63c0f383ebbe8d7b3fa55&get=P0070001,NAME&for=county:*&in=state:* 2) http://api.census.gov/data/2000/sf1?key=a8e19a47c9c91ffa82c63c0f383ebbe8d7b3fa55&get=EXTCITIN,NAME&for=county:*&in=state:* ...more »
I've had an API key for weeks and just got back to my project after doing some other work. I get this error when I make a query that used to work:
"A valid key must be included with each data API request.
You included a key with this request, however, it is not valid.
Please check your key and try again.'
I'm a first time user trying to request a Registration Key. I've tried several times today from both Explorer and Firefox browsers and keep getting the below error.
"The server encountered an internal error () that prevented it from fulfilling this request."
I have a problem accessing the registration form : http://www.census.gov/developers/tos/key_request.html
It says that "The server at api.census.gov is taking too long to respond."
what is this due to ?
are there some geographical restrictions ? (since i am not in the US).
I'm trying the following call and getting nothing. When I put it into the browser the page just hangs. The response says the server received it and then it stops. I'm calculating the average age of each city in the USA. Here is the request (note I removed my key) http://api.census.gov/data/2010/sf1?key=[yourkey]&get=PCT0120157,PCT0120158,PCT0120159,PCT0120160,PCT0120161,PCT0120162,PCT0120163,PCT0120164,PCT0120165,PCT0120166,PCT0120167,PCT0120168,PCT0120169,PCT0120170,PCT0120171,PCT0120172,PCT0120173,PCT0120174,PCT0120175,PCT0120176,PCT0120177,PCT0120178,PCT0120179,PCT0120180,PCT0120181,PCT0120182,PCT0120183,PCT0120184,PCT0120185,PCT0120186,PCT0120187,PCT0120188,PCT0120189,PCT0120190,PCT0120191,PCT0120192,PCT0120193,PCT0120194,PCT0120195,PCT0120196,PCT0120197,PCT0120198,PCT0120199,PCT0120200,PCT0120201,PCT0120202,PCT0120203,PCT0120204,PCT0120205,PCT0120206&for=place:36&in=state:99990 ...more »
I get error: the 'get' argument must be a comma separated list of variable names with the following query:
In the first 1990 census table, there is no variable for Amer Ind/Esk/Aleut Males 12-13 yrs. In the age by race and gender group, the variables skip from P0120131 to P0120133, so presumably P0120132 is the missing age range. Using the variable in the data call results in an unknown variable error.
I just wanted to share a labeling error we have run across in the 2010 SF1 API Variables XML. (http://api.census.gov/data/2010/sf1/variables.xml) Under renter occupied by race/ethnicity for each race/ethnicity (Asian householder as example) the xml:id="H016D0017" and xml:id="H016D0010" are both labeled: label="Renter occupied: !! 7-or-more-person household". When xml:id="H016D0010" is the total and should have a label ...more »
"$20,000-$34,999: 30 to 34 percent" (presumably H0500016) is missing. Variables jump from "$20,000-$34,999: 25 to 29 percent" to "$20,000-$34,999: 35 percent or more". Using the variable in the data call results in an unknown variable error.
In the 1990 sf1 data call, H0240001 (Spec Own-occ HUs:Agg Value) is currently returned as a regular integer. However, all the state values are the same - 2,147,483,647, which is the max value that can be stored in a regular integer, indicating that the variable should be stored as a big integer.
I've just started working with the API today. I started by using sample queries such as: http://api.census.gov/data/2012/popproj/pop?get=TOTAL_POP,RACE&SEX=1&YEAR=2012&key= It worked fine earlier today, but now I keep getting the "resource not available" error. EDIT - For clarification, it worked in the AM for a period of about 1 hour. I tried again about 6 hours later, and it didn't work for a period of about 1 hour. ...more »
This used to work for me — currently returns null for all values, but has data for other geographies. Temporary glitch?
I get the following error:
There was an error while running your query. We've logged the error and we'll correct it ASAP. Sorry for the inconvenience.
when running this query: