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

iata-arrivals-cli Timezones #7

Open
graememilne opened this issue Jan 1, 2024 · 1 comment
Open

iata-arrivals-cli Timezones #7

graememilne opened this issue Jan 1, 2024 · 1 comment

Comments

@graememilne
Copy link

graememilne commented Jan 1, 2024

Just discovered your program the other day,which i think is fantastic.
Wish I had known about this years ago.

The web page mentions this below

 --- IMPORTANT! -----------------------------------------------
   • All times shown are in the timezone of your computer!
   • Do not attempt to run these queries in rapid succession,
     as your IP might get blocked by the API providers.
 --------------------------------------------------------------

This works fine if looking for info in the country you are in, UK. But when looking for info from an airport in a different country, I noticed this.

In Sched, ETA it gives the local time in the country you are in UK, but Status gives the correct time in the country you are looking for info on airport in for example: Amsterdam, Schiphol, AMS.

I notice in the To do list from 2018:

Add "-t" CLI flag for time-zone (TZ) times used for API vs. local airport TZ.

  • Does this mean when looking for airport info in another country, the above will show correct times for that airport?

For example I am in the UK, and I want to see info from ./arrivals.py -t AMS.

  • The Sched, ETA will show the correct times for AMS instead of my local time?

If so, what is the time line for implementing this important feature.
Hope you can implement this sooner than later?

@E3V3A
Copy link
Owner

E3V3A commented Oct 21, 2024

@graememilne
Hi Milne,
I'm looking to make a complete update and review. It's still a useful tool, but a lot have changed in the python environments in the last few years. Also need to check that the API's are working as expected. Unfortunately I have no ETA for this.

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