next_page_token

[percy3d]

The places documentation mentioned you can get a next_page_token to point to the next 20 results. I'm just wondering how I can do this to get all the search results.

[deecodameeko]

pagetoken is not returned when configure, neither is opennow.

nearbySearchKeys: ['name', 'reference', 'vicinity', 'geometry', 'place_id', 'formatted_address', 'photos', 'pagetoken', 'opennow'],

after line 8 in angularjs-google-places.js add

var pagination ='';

~ line 32 there is this line

response.map(function ( result ) {

immediately after place

var obj = { next_page_token: pagination.H, hasNextPage: pagination.hasNextPage };

~ line 60 change

function callback( results, status ) {

to

function callback( results, status, pagetoken ) {

and add the line

pagination = pagetoken;

immediately after

now you will find the next_page_token added to every result. Not ideal sorry, real hack'y but I am open to a better way.

[dmgallardo]

Hi @badbod,
I just added all those changes, but how I can retrieve the next page ?

If I add pagetoken to the query parameters it didn't work.
And calling to the google places js api method "pagination.nextPage();", it didn't work either.

I can't process the callback from google.

I tried this google js example, and it worked:
https://developers.google.com/maps/documentation/javascript/examples/place-search-pagination

But when I try to integrate in angularjs, I cant make it work.

Thanks.

ahh, yes, you do get the token this way, as inefficient as it is, but still cant use it. like types. I have had to move to server side for this. That has it's own world of problems, mostly solved by cash to google.

Seems you might not get this if your not sending a API key. I dont think you get these details with the API key. Work it out.

be careful with the API key, I wasted through the free allowance (100,000?) in a day on a single dev server, single developer.

each place request costs 20 points, each places search is one point. 20 results requiring a 20 point lookup for details. 401 points for each places search that wants the details.

Average dev will refresh around 5 times a minute (more for good devs), scaling down as code and display is debugged. Initially over two thousand points per minute. In one hour that is over 100, 000 points.

If you half the points on the details lookup, then you get 2 hours to make it work.