Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone Issue #266

Open
azampagl opened this issue May 19, 2021 · 1 comment
Open

Timezone Issue #266

azampagl opened this issue May 19, 2021 · 1 comment

Comments

@azampagl
Copy link

I'm running into issues on trips with locations that don't have an official IATA and the app is pairing the city to the wrong time zone.

Scenario:
I tried entering the airport KHCR, but it does not have an official IATA code, which is fine. So I provide the city "heber" but the app thinks it is in the timezone PDT when it is really in MDT (therefore showing the wrong duration of the flight).

Is there anyway to manually specify the timezone without setting the airport code or city?

On AirSegment I've tried entering all combinations of the following.

  • timezone and utcOffset on the StartDateTime and EndDateTime objects. API seems to ignore this.
  • setting the latitude and longitude and setting start_airport_latitudeSpecified, start_airport_longitudeSpecified, etc. to true. Api seems to ignore this.
  • Setting the duration. Api seems to ignore this.
@julsat
Copy link

julsat commented May 20, 2021

hi @azampagl
I was able to create a flight segment with Heber, UT as destination which is mapped to a correct timezone MDT. Please use full city name including state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants