Dear Support,
It appears there is an extraneous “:” on the leading side of the timezone string in JSON results when making AirportInfo calls. The extra colon is inside the string itself. This didn’t exist before (that I remember), but exists in every one I check now. I was able easily compensave by doing a replace function on that field, but I thought you might like to know about it (see snippet below for example).
AirportInfo?airportCode=KSAT produces the following results:
{“AirportInfoResult”:{“name”:“San Antonio Intl”,“location”:“San Antonio, TX”,“longitude”:-98.46905710000000056,“latitude”:29.533957999999998378,“timezone”:“**:**America/Chicago”}}
Best Regards,
Jason Cook