Bugs / Problems

invalid json

For this particular api query to acs5 I receive invalid json. I confirmed this with jslint. I suspect one of the fields aren't escaping properly or something.

http://api.census.gov/data/2012/acs5/profile?get=DP04_0088E,DP02_0100E,DP02_0104E,DP02_0105E,DP02_0106E,DP02_0107E,DP02_0108E,DP02_0109E,DP02_0111E,DP02_0112E,DP02_0113E,DP03_0019E,DP03_0020E,DP03_0021E,DP03_0022E,DP03_0023E,DP03_0024E,DP03_0025E,DP02_0090E,DP03_0004E,DP03_0005E,DP03_0006E&for=place:*&in=state:*&key={key}

Tags

Submitted by

Stage: Active

Feedback Score

1 vote
1 up votes
0 down votes
Idea#214

Idea Details

Vote Activity

  1. Upvoted

Similar Ideas [ 4 ]

Events

  1. The idea was posted

Comments

  1. Comment
    jporter ( Idea Submitter )

    Any updates on progress with this? I just checked with jsonlint again and it's still got an error of:

    Parse error on line 760687:

    ... null, nullnull, nu

    ----------------------^

    Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '['

    It seems to me that one of those null's isn't adding the needed comma. In fact when I used find in my browser and typed "nullnull" I got over 500 results. At the end of those results you can see that two groups of two null columns are not separated by a comma as I would assume they need to be.

  2. Comment

    Yes, we've confirmed the bug and we're working on it. We'll post back here when the patch is tested and deployed.

  3. Comment
    jporter ( Idea Submitter )

    Any eta on the patch going out? If you have a staging area I could help test.

  4. Comment

    We've patched the bug. Please test and report back if you have any problems.

    And, thanks again for the bug report!

Add your comment