Hi, I want to get the current location based on this link but I can't find any python example to do that. I want to create a general code to get the current location. I used this part of code but it didn't work.

import googlemaps
gmaps = googlemaps.Client(key='my_key')
loc = gmaps.geolocate()
print(loc)

Thanks.

I tried the basic example code... but I'm stuck with this:

/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:79: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
Traceback (most recent call last):
  File "get_times.py", line 6, in <module>
    geocode_result = gmaps.geocode('1600 Amphitheatre Parkway, Mountain View, CA')
  File "/usr/local/lib/python2.7/dist-packages/googlemaps/geocoding.py", line 68, in geocode
    return client._get("/maps/api/geocode/json", params)["results"]
  File "/usr/local/lib/python2.7/dist-packages/googlemaps/client.py", line 205, in _get
    raise googlemaps.exceptions.TransportError(e)
googlemaps.exceptions.TransportError: [Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

I can't see any way in the library API to point to the certificate. Where should I get this certificate and how to make the library see it?

Hello, I found that traffic_model="optimistic" sometimes takes longer than traffic_model="best guess". I don't know if this is because of the library or because of Google Maps, but I thought I'd ask, because it makes me question the results using "optimistic" more generally. That is, maybe the results using "optimistic" are not reliable in general.

The graph plots the travel time using the three traffic_model options, for all departure times on a particular day (in the future). Note how during the night the "optimisitic" is slower than the other two.

Also, here is code that generates this for a particular leaving time.

Code output:

['Travel time from: 12.979572,80.25271 to 12.921726,80.230478']
['Departure time (local): 16 Dec 2015 03:42:02']
['Time, no traffic, minutes: 12.566666666666666']
['Time in traffic, minutes: 9.45']
['Time in traffic (optimistic), minutes: 10.45']

Code:

__author__ = 'Gabriel Kreindler, [email protected]'

'''
This code shows that the traffic_model option sometimes generates counter-intuitive results.
The option traffic_model="optimistic" sometimes generates longer travel times compared to "best_guess" or "pessimistic".
(The latter is not shown here.)
'''

import googlemaps
import time
import calendar

# client
client = googlemaps.Client(key='KEY HERE')

# origin and destination
orig="12.979572,80.25271"
dest="12.921726,80.230478"

# query time
t1 = time.strptime("15 Dec 2015 22:12:02", "%d %b %Y %H:%M:%S")
nsec1 = calendar.timegm(t1)

# get offset
timezone_offset = client.timezone(orig, timestamp=nsec1)
timezone_offset_sec = timezone_offset['rawOffset']

# nice local time
t1_loc = time.gmtime(nsec1 + timezone_offset_sec) # local time
dep_time_local = time.strftime("%d %b %Y %H:%M:%S", t1_loc)


# get duration in traffic
dist = client.distance_matrix(orig, dest, departure_time=nsec1, mode="driving")

# parse
temp = dist["rows"][0]["elements"][0]
assert temp["status"]=="OK"
dist_output = temp["distance"]["value"]
dur_output = temp["duration"]["value"]  # duration
dur_intraffic_output = temp["duration_in_traffic"]["value"]

# get duration in traffic
dist = client.distance_matrix(orig, dest, departure_time=nsec1, mode="driving", traffic_model="optimistic")

# parse
temp = dist["rows"][0]["elements"][0]
assert temp["status"]=="OK"
dur_intraffic_opt_output = temp["duration_in_traffic"]["value"]

print(['Travel time from: ' + orig + ' to ' + dest])
print(['Departure time (local): ' + dep_time_local])
print(['Time, no traffic, minutes: ' + str(dur_output/60)])
print(['Time in traffic, minutes: ' + str(dur_intraffic_output/60)])
print(['Time in traffic (optimistic), minutes: ' + str(dur_intraffic_opt_output/60)])

I read the following doc

The duration in traffic is returned only if all of the following are true:

1. The request includes a valid API key, or a valid Google Maps APIs Premium Plan client ID and signature.
2. The request does not include stopover waypoints. If the request includes waypoints, they must be prefixed with via: to avoid stopovers.
3. The request is specifically for driving directions—the mode parameter is set to driving.
4. The request includes a departure_time parameter.
5. Traffic conditions are available for the requested route.

For condition 2, how do I prefix via: to the waypoints. I have a list of coordinates.

Thanks for stopping by to let us know something could be better!

PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Some of the paths that I send to the road snap API do not come back as I would expect.

If for instance I pass in X number of coordinate pairs (interpolate is on, btw), and I receive Y pairs back, where Y > X, I may not receive all of my originalIndex pairs back.

So, I may have on the return: [{originalIndex: 0}, new_0, new_1, new_2, {originalIndex: 3}, ...]

What does this behavior mean? And what should I do with the pair(s) that are not returned from the API?

Add support for reverse geocoding by place_id in addition to existing lat/lng. Doesn't change interface, just checks for a string that begins with something other than a digit or a +/- sign. Treats such strings as place_ids, otherwise behaves like current code.

The library keeps retrying requests that are rejected by the REST API with the following. I think this is not correct behavior. It masks what exactly is happening from the the python API developer and it does not matter how long you retry it will keep failing until the next day.

{u'status': u'OVER_QUERY_LIMIT', u'rows': [], u'error_message': u'You have exceeded your daily request quota for this API.', u'destination_addresses': [], u'origin_addresses': []}

Geocode endpoint accepts a place_id param as an alternative to geocode Google docs: https://developers.google.com/maps/documentation/geocoding/requests-places-geocoding

Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [ ] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [ ] Ensure the tests and linter pass
• [ ] Code coverage does not decrease (if any source code was changed)
• [ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [ ] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [ ] Ensure the tests and linter pass
• [ ] Code coverage does not decrease (if any source code was changed)
• [ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

If an end-user of the library wants to override _DEFAULT_BASE_URL (e.g. in order to use a proxy), this makes it easier. The user can simply run

googlemaps.client._DEFAULT_BASE_URL = 'http://my_proxy_dns'

in their server/script's startup code.

Without this change, the default value for the parameter gets "baked" into the function definition and is harder to change.

(Obviously a module's internal implementation details are subject to change, and this PR doesn't construe a guarantee that overriding _DEFAULT_BASE_URL will continue to work in the future).

Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [x] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [x] Ensure the tests and linter pass
• [x] Code coverage does not decrease (if any source code was changed)
• [x] Appropriate docs were updated (if necessary)

Fixes #467 🦕

Thanks for stopping by to let us know something could be better!

PLEASE READ

If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.

Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.

If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.

Check for answers on StackOverflow with the google-maps tag.

Is your feature request related to a problem? Please describe. I would like to be able to filter place reviews by newest, rather than just the default.

Describe the solution you'd like I would like to be able to pass a simple parameter to filter for the newest reviews for a place.

Describe alternatives you've considered There is no alternative, other than using the default filter.

Additional context Add any other context or screenshots about the feature request here.

Google Maps API Find Place requests now support a location restriction parameter which limit results to a specified area. This is unlike the location bias parameter which prefers results in a specified area. The location restriction parameter can be set by specifying either a radius plus lat/lng, or two lat/lng pairs representing the points of a rectangle.

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [x] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [x] Ensure the tests and linter pass
• [x] Code coverage does not decrease (if any source code was changed)
• [ ] Appropriate docs were updated (if necessary)

Fixes https://github.com/googlemaps/google-maps-services-python/issues/464 🦕

The Google Maps API now supports a locationrestriction parameter for Find Place requests, which can restrict results to a certain area. This is unlike the locationbias parameter, which prefers results in a certain area.

See: https://developers.google.com/maps/documentation/places/web-service/search-find-place#locationrestriction

https://github.com/googlemaps/google-maps-services-python/blob/5b952d73f8374baac876b4d845fd46cebec6ed7e/googlemaps/addressvalidation.py#L47 currently only accepts a limited number of arguments - see https://developers.google.com/maps/documentation/address-validation/reference/rest/v1/TopLevel/validateAddress#postaladdress

Our use case is that we know the US state, and want to pass that to the API as hint (in administrativeArea)

Can easily be solved by adding **kwargs

Triggering the retry mechanism on invalid requests due to inconsistent behavior in Google Maps API, which is described in issue #366.

The side effect is that if wrong parameters are provided request won't fail on the first try but will go through a retry mechanism.

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [x] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [x] Ensure the tests and linter pass
• [x] Code coverage does not decrease (if any source code was changed)
• [x] Appropriate docs were updated (if necessary)

Fixes #366 🦕