Assigned
Status Update
No update yet.
Comments
ra...@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?)
ra...@google.com
Making popular times available by day of the week would be awesome
bs...@cargas.com
It already is Jeffrey, you can toggle by day on mobile or desktop
bs...@cargas.com
We have continued to receive reports of this, were you able to review the fiddle example that was provided and do you have any updates on this?
bs...@cargas.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
bs...@cargas.com
Checking back in for an update again. This issue persists.
ch...@epix.net
We are experiencing same thing everyday on our tablets. Geo coordinates are routing my drivers WAY out to get to the dropped pin location. Your prompt attention would be appreciated to rectify this issue. Thanks. Chad.
mi...@acerobbins.com
Ace Robbins has had this issue for the last month and a half. Has this been fixed yet? Our drivers are still experiencing these issues.
Mike
Mike
il...@cargas.com
Would be extremely helpful to have access to this data directly via the API. Is it maybe available via another API?
mi...@apaq.dk
No update on here for a while now... Any news on making this available ?
mi...@apaq.dk
By chance I stumbled upon a comment mentioning that when using geo: in the intent, the coordinate can be supplied with a title.
Example (don't ask me about the syntax because it seems totally undocumented):
geo:0,0?q=<lat>,<lon>(<title>)
This actually works like in our iOS counterpart integration. We can supply the coordinate we have, but even if the coordinate we have is a few meters off in comparison to Googles, we still get the correct address shown instead of fx the neighbor house or a range of addresses.
Only thing is: It is not documented at all, so will it be supported in the future also? 🫣
Example (don't ask me about the syntax because it seems totally undocumented):
geo:0,0?q=<lat>,<lon>(<title>)
This actually works like in our iOS counterpart integration. We can supply the coordinate we have, but even if the coordinate we have is a few meters off in comparison to Googles, we still get the correct address shown instead of fx the neighbor house or a range of addresses.
Only thing is: It is not documented at all, so will it be supported in the future also? 🫣
09...@gmail.com
09...@gmail.com
News? it would be awesome :)
ra...@gmail.com Restricted+
Restricted+
Comment has been deleted.
Description
===========================================================================================
#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
===========================================================================================
What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. Launch navigation via google.navigation intent in Android. Example intent: google.navigation:q=34.876454,-78.65783
2. The primary destination does snap to the desired geocode, but the alternate routes resolve elsewhere and often deviate quite far from the intended location.
3. Intermittently, the Maps pin will occasionally drop to the alternate route as well and can result in incorrect navigation. (see attached)
4. Reports of this started the week of 9/26-9/30 and prior Maps versions reportedly handled this without issue.