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

using count in isochrone api #356

Closed
Azema opened this issue May 22, 2014 · 1 comment · Fixed by #1220
Closed

using count in isochrone api #356

Azema opened this issue May 22, 2014 · 1 comment · Fixed by #1220

Comments

@Azema
Copy link

Azema commented May 22, 2014

Hi guys,

I've a problem with API journeys:

Sorry for my English, I prefer the French ;-)

Say hello to everyone for me

@antoine-de
Copy link
Contributor

you are right, this api does not seems correctly paginated (the ``count` should be used for that).

Beware that you did not give a to param to your journey, thus you don't call the classic 'journey' API but the 'isochrone' API (hence the many journeys returned).

We don't use often this API yet, hence the mistake on the pagination.
Thanks for the issue, we'll try to correct that as soon as possible!

@TeXitoi TeXitoi changed the title Mistakes in API journeys using count in isochrone api Oct 24, 2014
antoine-de added a commit to antoine-de/navitia that referenced this issue Oct 19, 2015
close hove-io#356 as count fill max_nb_journeys when provided
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants