Assigned
Status Update
No update yet.
Comments
mi...@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?)
zu...@gmail.com
Making popular times available by day of the week would be awesome
mi...@google.com
It already is Jeffrey, you can toggle by day on mobile or desktop
zu...@gmail.com
Specific search queries would not help elaborate my current predicament, because our system does not search for a specific point, but rather for a collection of points in a given region(region could be a city, county, state, country etc.) and it uses location names for it's search(not my idea), so it is important to have a unified 'language' in our data sets. And most of the time it seems that only the most precise region names cannot be translated. For instance "Senamiesčio seniūnija", which is basically a small district, would not be saved to our datasets, because it's search would require special characters, in which case that point would be described in a larger region's search results, which in this case would be "Vilnius", "Vilnius County" and so on. And ant least for our system purposes there would not be much difference between translation and transliteration, as we simply need point descriptions without any special characters.
mi...@google.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
[Deleted User] <[Deleted User]>
What I would like to see is a way to force all results to be on the local language of the place. We save the result of the geocoding on our database and having the language change between users makes it harder to filter and group the data. Also forcing to a specific locale (e.g. english) would make all non-english speaking country users addresses incorrect.
[Deleted User] <[Deleted User]>
The workaround for this is to do a reverse geocoding on each of the results specifying the official language of the result (not always easy to know as some countries have different languages for different regions).
Seehttps://stackoverflow.com/a/43887567/980933 for some more ideas on that.
See
Description
Example:
...
{
"long_name": "Vilniaus apskritis",
"short_name": "Vilniaus apskr.",
"types": [
"administrative_area_level_1",
"political"
],
"lang": "lt"
},
{
"long_name": "Vilnius County",
"short_name": "Vilnius County",
"types": [
"administrative_area_level_1",
"political"
],
"lang": "en"
},
...