FlightInfoEx method not returning originCity destinationCity

I am using the most basic of php scripts to call the flightinfoex method. Can someone verify if they are or are not getting originCity and destinationCity in the output.

Code:


<?php
$options = array(
                 'trace' => true,
                 'exceptions' => 0,
                 'login' => 'my username',
                 'password' => 'my password',
                 'proxy_host' => 'my proxy',
                 'proxy_port' => 'my port',
                 );
$client = new SoapClient('http://flightxml.flightaware.com/soap/FlightXML2/wsdl', $options);

$params = array("ident" => "N37413", "howMany" => "15", "offset" => "0");
$result = $client->FlightInfoEx($params);

$arrayOfFlights = array($result->FlightInfoExResult->flights);  //FLIGHT AWARE CALL
  print_r($arrayOfFlights);  //OUTPUT OBJECT WITHOUT MODIFICATIONS
?>

This is the abbreviated output:


Array
(
    [0] => Array
        (
            [0] => stdClass Object
                (
                    [faFlightID] => UAL1411-1396935229-airline-0229
                    [ident] => UAL1411
                    [aircrafttype] => B739
                    [filed_ete] => 03:08:00
                    [filed_time] => 1396935229
                    [filed_departuretime] => 1397166480
                    [filed_airspeed_kts] => 343
                    [filed_airspeed_mach] => 
                    [filed_altitude] => 0
                    [route] => 
                    [actualdeparturetime] => 0
                    [estimatedarrivaltime] => 1397178360
                    [actualarrivaltime] => 0
                    [diverted] => 
                    [origin] => KBWI
                    [destination] => KIAH
                    [originName] => Baltimore/Washington Intl
                    [originCity] =>
                    [destinationName] => Houston Bush Int'ctl
                    [destinationCity] =>
                )

            [1] => stdClass Object
                (
                    [faFlightID] => UAL1011-1396935228-airline-0237
                    [ident] => UAL1011
                    [aircrafttype] => B739
                    [filed_ete] => 02:46:00
                    [filed_time] => 1396935228
                    [filed_departuretime] => 1397152260
                    [filed_airspeed_kts] => 388
                    [filed_airspeed_mach] => 
                    [filed_altitude] => 0
                    [route] => 
                    [actualdeparturetime] => 0
                    [estimatedarrivaltime] => 1397162820
                    [actualarrivaltime] => 0
                    [diverted] => 
                    [origin] => KIAH
                    [destination] => KBWI
                    [originName] => Houston Bush Int'ctl
                    [originCity] => 
                    [destinationName] => Baltimore/Washington Intl
                    [destinationCity] =>
                )

            [2] => stdClass Object
                (
                    [faFlightID] => UAL1187-1396848938-airline-0102
                    [ident] => UAL1187
                    [aircrafttype] => B739
                    [filed_ete] => 03:26:00
                    [filed_time] => 1396848938
                    [filed_departuretime] => 1397041200
                    [filed_airspeed_kts] => 355
                    [filed_airspeed_mach] => 
                    [filed_altitude] => 0
                    [route] => PARKE J6 BWG MEM DHART J180 SWB TXMEX1
                    [actualdeparturetime] => 0
                    [estimatedarrivaltime] => 1397054160
                    [actualarrivaltime] => 0
                    [diverted] => 
                    [origin] => KEWR
                    [destination] => KIAH
                    [originName] => Newark Liberty Intl
                    [originCity] => 
                    [destinationName] => Houston Bush Int'ctl
                    [destinationCity] =>
                )


We have confirmed that a recent data source import has caused the city name to be blank in some responses. We’ll be refreshing our database to resolve this soon.

We believe this is fixed now.

Thank you, everything is up to date.