Vote up to Idea More consistency between the Decennial API's Vote down to Idea More consistency between the Decennial API's

Rank149

Idea#146

This idea is active.
Feature Requests »

More consistency between the Decennial API's

I am working on a page drawing data from the 1990, 2000 and 2010 SF1 and noticed a lot of differences between them. Most importantly for me:

- the variables that can be drawn from the Geographic header varies a lot, in 2010 only the Name, in 1990 and 2000 a whole slew of variables, including a very useful AREALAND, but NAME for one is missing in 1990

- in 2010 the list of available geographies is a lot longer than in 2000 and 1990. For my page I am especially missing county subdivisions in 1990 and 2000.

- If I ask for a list of states, Puerto Rico is included in 2010, not in 1990 and 2000

- State IDs have a leading zero in 2010, not so in 1990 and 2000. Maybe other ID's as well, I didn't test that. The API seem to work both with and without the leading zero.

Having more consistency in geographies and geographic header variables would be very helpful, the different table numbers and setups is hard enough to deal with.

Comment

Submitted by Jan Vink 1 year ago

Comments (1)

  1. Jan,

    I will address each point.

    (1) Good ideas. We'll look into getting AREALAND (et al.) for 2010 SF1 and NAME for 1990 and 2000.

    (2) We are currently exploring what it would take to make additional geographies available for 1990 and 2000.

    (3) This is related to #2; we're looking into this.

    (4) You're right. FIPS codes should be consistent. I'll look into getting this fixed.

    Thanks for the feedback. This was very helpful.

    Dave

    1 year ago

Events

  1. The idea was posted
    1 year ago