Status Update
Comments
op...@gmail.com <op...@gmail.com> #2
ca...@google.com <ca...@google.com>
ca...@google.com <ca...@google.com> #3
op...@gmail.com <op...@gmail.com> #4
ca...@google.com <ca...@google.com> #5
Thank you for your message.
Kindly see below for the additional information that we may need from you:
-
Sometimes I throw a lot of latitude and longitude but api returns different amount. - Please provide a sample request on the issue with both the expected correct result and incorrect results.
-
But late I reload the api page , api returns the same amount. - Please provide a screenshot or screen recording on how and when you are encountering this issue.
Also note that using place IDs is preferred over using addresses or latitude/longitude coordinates. Using coordinates will always result in the point being snapped to the road nearest to those coordinates - which may not be an access point to the property, or even a road that will quickly or safely lead to the destination. Using the address will provide the distance to the center of the building, as opposed to an entrance to the building.
op...@gmail.com <op...@gmail.com> #6
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
Description
But late I reload the api page , api returns the same amount.
I think it's a bug.
Please fix it.