Vote up to Idea Error when querying with census tract blocks Vote down to Idea Error when querying with census tract blocks

Rank50

Idea#22

This idea is active.
Bugs / Problems »

Error when querying with census tract blocks

Hi,

I'm trying to run the following query:

http://api.census.gov/data/2010/acs5?key=[key]&get=B00001_001E&for=block:2001&in=state:04+county:015+tract:954900

I get the error message, "There was an error while running your query. We've logged the error and we'll correct it ASAP. Sorry for the inconvenience."

If I run the same query but just use the census tract, it works, but if possible I would like to be able to be as specific as the tract blocks. Is there any workaround for this/will it be fixed soon?

Comment

Submitted by Community Member 1 year ago

Vote Activity

  1. Approved
    1 year ago
  2. Approved
    1 year ago

Events

  1. The idea was posted
    1 year ago

Comments (5)

  1. This geography appears to be invalid for the ACS 5 year dataset. It is however valid for the Summary File 1 dataset.

    Valid geographies for ACS are noted at http://www.census.gov/acs/www/data_documentation/geography/

    Our documentation on this particular survey is incorrect, and I will attempt to have this corrected.

    Thanks for reporting it.

    1 year ago
  2. There is no data on blocks in the ACS; the lowest level of geography for the 5-year ACS is block group. Maybe the error message could be improved the user that this is an invalid geography and not an error that needs fixing by the Census Bureau.

    1 year ago
  3. Indeed, as a side note, using the Summary File 1 data does go down to the block level, and might have the data you are looking for.

    1 year ago
  4. since there are a myriad of these types of errors, it might be preferred that Census not spend resources on bullet proofing. Maybe better to focus on issues such as expanding the scope of subject matter tables/items, adding datasets, being ready for ACS 2011, and extending geocode wildcarding. just some thoughts.

    1 year ago
    1. Bullet proofing is all we can do here, most of what you are asking needs to be changed by the data owners themselves, and cannot be altered by the API developers.

      I have however added a suggestion for geographic wildcard expansion.

      1 year ago