This question is old, but I figured I’d add to it in case anyone else is having this issue. restricting types to ‘address’ unfortunately does not achieve the expected result, as routes are still included. Thus, what I decided to do is loop through the result and implement the following check: result.predictions[i].types.includes(‘street_address’) Unfortunately, I was … Read more
There’s no documentation on the specific length, but the max I have seen is length 255. This corresponds to address 488 Srinagarindra Rd., Suan Luang, Bangkok, 10250. You can check the place id here. FYI the place id is: ErwBNDg4IOC4luC4meC4mSDguKjguKPguLXguJnguITguKPguLTguJnguJfguKPguYwg4LmB4LiC4Lin4LiHIOC4quC4p-C4meC4q-C4peC4p-C4hyDguYDguILguJUg4Liq4Lin4LiZ4Lir4Lil4Lin4LiHIOC4geC4o-C4uOC4h-C5gOC4l-C4nuC4oeC4q-C4suC4meC4hOC4oyAxMDI1MCDguJvguKPguLDguYDguJfguKjguYTguJfguKI
The parameter should be pagetoken, not “next_page_token”. Try this: https://maps.googleapis.com/maps/api/place/nearbysearch/xml?location=42.9825,-81.254&radius=50000&name=Medical%22Clinic&sensor=false&key=[KEY GOES HERE]&pageToken=[NEXT PAGE TOKEN GOES HERE]
Unfortunately you can’t get more than 60 results from the Google Places API; at least not without breaking the terms of service: Unless you have received prior written authorization from Google (or, as applicable, from the provider of particular Content), you must not: (d) use the Products in a manner that gives you or any … Read more
As of now (2016-12-15), no, as can be found at https://developers.google.com/places/web-service/details#PlaceDetailsResults. There’s no other API for that information. You could use the API ratings return to do something alike, but still not the same. You can track the existing requests for the feature (and star & bump it) at https://issuetracker.google.com/issues/35827350.
Edit: The sensor parameter is no longer required, and will now be ignored if it’s used. The parameter doesn’t impact the results. It’s a parameter that Google is required to collect for Google’s data providers who charge differently based on whether the request uses a sensor or not. see Google docs