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

Bug: Routes return is missing airports #3

Open
danshev opened this issue May 12, 2022 · 1 comment
Open

Bug: Routes return is missing airports #3

danshev opened this issue May 12, 2022 · 1 comment

Comments

@danshev
Copy link

danshev commented May 12, 2022

Making a call to /routes

GET => http://aviation-edge.com/v2/public/routes?key=MY_API_KEY&departureIata=BOS ... Barcelona (BCN) not in response
GET => http://aviation-edge.com/v2/public/routes?key=MY_API_KEY&departureIata=BOS&arrivalIata=BCN ... BCN in response

Edit: the return for larger airports (BOS, ORD, ATL, NRT) is consistently exactly 300 rows ... is it possible there's an inadvertent limit on the return?

I need the /routes endpoint to provide all possible destinations from an origin airport -- is there anything that can be done to fix?

@danshev
Copy link
Author

danshev commented May 15, 2022

Solution: specify a high limit query string parameter, e.g.:

http://aviation-edge.com/v2/public/routes?key=MY_API_KEY&departureIata=BOS&limit=5000

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

1 participant