hi! thanks for the heads up - its a known issue, and we're gunning to have this rectified ASAP.
On Wed, Mar 10, 2010 at 9:51 AM, Don Park <super...@gmail.com> wrote: > Hi, > > Some of the tweets are causing my JSON parser (Json-Lib) to throw > "JSON does not allow non-finite numbers" exception. Looking at the > tweet, only likely suspect is the new Geo Location field > 'bounding_box'. > > "bounding_box": { > "type": "Polygon", > "coordinates": [ > [ > [ > 1.79769313486232e+308, > 1.79769313486232e+308 > ], > [ > -1.79769313486232e+308, > 1.79769313486232e+308 > ], > [ > -1.79769313486232e+308, > -1.79769313486232e+308 > ], > [ > 1.79769313486232e+308, > -1.79769313486232e+308 > ] > ] > ] > }, > > JSON verifiers say they are valid so it's kinda confusing. > Nevertheless, I thought Twitter API team should be aware that some of > the JSON parsers are barfing on tweets like above. > > Best, > > Don Park > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi