Assigned
Status Update
No update yet.
Comments
ca...@google.com
Yes please :) Along with a more specific definition of how the Popular Times are determined (how much history? done by mobile device activity? check ins?)
pi...@gmail.com
Making popular times available by day of the week would be awesome
co...@gmail.com
It already is Jeffrey, you can toggle by day on mobile or desktop
dr...@gmail.com
Hello, following up on this. Please let us know when we can expect pagination for "Places API (New)." Thanks
te...@lingtual.com
@r22, I think Jeff is referring to the ability to split popular times by day of week in the information released by the API, not the currently existing web GUI.
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
fr...@gmail.com
Agree with the comments above. Please make this available..
th...@gmail.com
Would love to see this feature implemented soon
em...@gmail.com
Would like to migrate to the new api, as it enables search with more than one type such as restaurant, cafe etc. However because no pagination is available I am not sure whether I should migrate to the new API. 20 results is not something I, as a developer, would prefer to show to my users. For now, seems better to stick to the old API. I request pagination just like the comments above.
is...@gmail.com
Would be extremely helpful to have access to this data directly via the API. Is it maybe available via another API?
sa...@gmail.com
No update on here for a while now... Any news on making this available ?
sa...@gmail.com
Definitely need an pagination option for nearby search(New) api. Please add this feature .
an...@gmail.com
Pagination for nearbyPlaces(new) should be implemented asap. Without it is useless.
at...@gmail.com
News? it would be awesome :)
dr...@gmail.com
This would be great, we could use for some cool analytics applications...
im...@gmail.com
Would be great to see this opened up so we could use it in app development in iOS and Android.
ap...@gmail.com
Hi, those data would be definitely usefull to enable new services like shopping day optimizer and many more.
sa...@gmail.com
Any updates?
dr...@joinpoppet.com
Would be great!!
an...@cartodb.com
Hi Project Team, any updates? We'd love to use that in our apps and systems. It's a VERY powerful piece of data
jo...@gmail.com
Can we please see it as an Api for other apps to use.
se...@gmail.com
Hi Project Team, any updates? Thanks a lot!
fm...@gmail.com
Please build it...we will come!
md...@gmail.com
Don't build it, keep the data for yourself its very valuable
dr...@gmail.com
Very valuable feature that would get much use and increase spend on places api calls
lu...@inudev.com
Also hoping for this to be implemented
ow...@gmail.com
Would love to see this API exposed
ic...@gmail.com
How has this been an issue for almost a year? I can't believe a company as large as google would neglect a feature as important as pagination. I hope that you manage to get this feature added soon but since no one has responded to any chats I'm guessing its going to end up taking forever.
ad...@usach.cl
waiting to get popular times info from Google Places API
vi...@gmail.com
Comment has been deleted.
gi...@mbark.me
Comment has been deleted.
gi...@gmail.com
Hey folks, unless I'm misunderstanding what people want to do here, I think the functionality is there, just not very clearly documented (imho).
It looks like you need to pass "nextPageToken" as one of the X-Goog-FieldMask:https://issuetracker.google.com/issues/343942714
Doing that returns nextPageToken in the results, which you can then pass as the pageToken parameter in the following request.
It looks like you need to pass "nextPageToken" as one of the X-Goog-FieldMask:
Doing that returns nextPageToken in the results, which you can then pass as the pageToken parameter in the following request.
k2...@gmail.com
The new searchNearby API returns 400 error when 'nextPageToken' is included in X-Goog-FieldMask.
URI:https://places.googleapis.com/v1/places:searchNearby
I got this error:
{'code': 400, 'message': 'Request contains an invalid argument.', 'status': 'INVALID_ARGUMENT', 'details': [{'@type': 'type.googleapis.com/google.rpc.BadRequest ', 'fieldViolations': [{'field': 'places.id ,places.location,places.googleMapsUri,places.displayName,places.shortFormattedAddress,places.primaryType,places.primaryTypeDisplayName,places.types,places.rating,places.userRatingCount,places.priceRange,nextPageToken', 'description': "Error expanding 'fields' parameter. Cannot find matching fields for path 'nextPageToken'."}]}]}
URI:
I got this error:
{'code': 400, 'message': 'Request contains an invalid argument.', 'status': 'INVALID_ARGUMENT', 'details': [{'@type': '
ac...@gmail.com
Would be very usefull
ga...@gmail.com
It would be extremely helpful to get this information to make amazing apps. Please OPEN THIS for us!
da...@wegotrip.com Restricted+
Restricted+
Comment has been deleted.
fa...@gmail.com
Indeed, would be great if you could include this endpoint within your next update! Thanks
ii...@gmail.com
Would love to get access to this data!
am...@gmail.com
I agree - please add to API.
lo...@nobu.sh
The only thing missing in the Places API! Too bad it was not added with the latest Google I/O batch of changes
an...@gmail.com
I join the chorus of people requesting this feature.
Be...@gmx.de
[Comment deleted]
ev...@gmail.com
Any updates on this? This is quite important
ky...@gmail.com
I too join the chorus for requesting this feature.
mi...@gmail.com
And me... But I fear it is too valuable in aggregate to expose back to the masses. We can hope...
in...@homicity.com
Google, can you please fix this issue? We're paying for a service that is useless....
ju...@gmail.com
Adding to the earlier request(s) for the Places API to provide Popular Times.
zp...@netdoer.com
Joining the chorus for requesting this feature!
Description
This service is currently in the Preview launch stage. Google provides no SLAs or technical support commitments for Preview products. Unless stated otherwise by Google, Preview offerings are intended for use in test environments only.
To learn more about the Preview launch stage, see
This template is *not* intended to be used for reports concerning the Text Search method for the service “Places API” (“
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
Feature Request
-----------------------
What would you like to see us add to this API?
To improve the API, I would love to see the ability to retrieve more than 20 results per request through pagination
or batching.
(This Feature Request is about the Text Search endpoint for the service “Places API (New)” (“