Assigned
Status Update
Comments
an...@google.com <an...@google.com> #2
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?)
an...@google.com <an...@google.com>
yu...@google.com <yu...@google.com>
an...@google.com <an...@google.com>
as...@google.com <as...@google.com>
sh...@google.com <sh...@google.com> #3
Making popular times available by day of the week would be awesome
sm...@gmail.com <sm...@gmail.com> #4
Comment has been deleted.
sh...@google.com <sh...@google.com> #5
Thanks for your post.
The engineering team will look into the issue and explore if there are feasible ways to resolve it as soon as possible.
We will let you know as soon as additional updates are made available.
The engineering team will look into the issue and explore if there are feasible ways to resolve it as soon as possible.
We will let you know as soon as additional updates are made available.
as...@google.com <as...@google.com>
iv...@google.com <iv...@google.com> #6
@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
Description
-----------------------
What would you like to see us add to this API?
simple, non secure, traffic for IOT devices
Issue report
----------------
What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. program any IOT device to call
2. It fails because no SSL was used
3. ALL IOT devices are not powerful enough and do not have enough memory to have the SSL library onboard.
Please enable simple and non-secure data for IOT devices.
ideally combine info from
and
Best regards
Dean