Increase speed in data-access using "traffic" Payton-library

1 year 2 months ago #1668 by geoidee
Dear List

I am using the traffic-library (traffic-viz.github.io/index.html) to access the OpenSky Impala shell. Hope it is OK to ask a question here.

To retrieve flights arriving at a given airport, I query history with the given values:
  • startTime = 2019-02-01 00:01
  • endTime = 2019-02-01 23:59
  • callsign = <value from previous query, see remarks below>
  • icao24 = <value from previous query, see remarks below>
  • bounds = <box around the airport>

opensky.history(
    startTime,
    endTime,
    bounds = (5.0, 46.0, 11.0, 49.0),
    callsign = callsign,
    icao24 = icao24,
    count = False,
    return_flight = True)

Problem:
  • The call opensky.history() can take several minutes.
Question:
  • Is there an idea to speed up the query / call of opensky.history()?
Looking forward to any ideas and suggestions.

Best regards and thanks in advance,
Yvo

Remarks:
As a previous query, I retrieve the entire list of flights during an entire day for the given arrival-airport.
  • airport = <airport-code>

opensky.flightlist(
    start = startTime,
    stop = endTime,
    arrival_airport = airport)

Please Log in or Create an account to join the conversation.

1 year 2 months ago #1675 by dkovar
Greetings,

Traffic and pyopensky both sit on top of the OpenSky Impala shell or their live API and any speed issues are due to the OpenSky servers.

I need to download a -lot- of data and have tried Traffic, pyopensky, and ssh into the shell. They are all equally slow.

Server performance also varies based on load and has generally been getting worse.

-David

Please Log in or Create an account to join the conversation.

1 year 2 months ago #1676 by geoidee
Thank you very much for your replay. Good to know what the bottleneck is.

Please Log in or Create an account to join the conversation.

Powered by Kunena Forum
This website uses cookies to offer you the best experience of our services. By using this website you agree to our privacy policy!