when I request on google fit rest api the steps count the only steps I see are the value user_input, and then the Google Fit App write on google fitness store or not?
Related
I am trying to get users' objectives through the rest API, for Google Fit.
While I know this exists for Android: https://developers.google.com/android/reference/com/google/android/gms/fitness/GoalsClient
I am not aware (after browsing for hours) of such methods/entrypoint for the rest API.
Could someone point me to the right ressource/direction?
Thanks
I currently have an application which takes a a start and end point from a user and sends a request to the google maps directions API, for example: https://maps.googleapis.com/maps/api/directions/xml?key=my_key8&origin=M460PU&destination=NN36NW&sensor=false&mode=driving&units=imperial&departure_time=1501752779
We then display the estimated journey time for a given route. The user has asked if it's possible for us to include a link directly to Google maps so that they can see the route on the maps and make sure it looks ok.
I've seen previous questions such as this one: Link to Google Maps but that seems to be a solution for a simple Google Maps search, where as in my case I want to see a route from the directions API.
I'm trying to figure out if I there's a way I can take the data from the Directions API response and plug that in to a http://maps.google.com/maps URL that the user can click on. Has anyone ever had any success doing this?
As mentioned #geocodezip you should use Google Maps JavaScript API or Google Static Maps API in order to show exactly the same route as the output of Directions API.
There is also an option to open Google Maps web site or native app using the Google Maps URLs. You can have a look at the documentation to figure out how to create the URL:
https://developers.google.com/maps/documentation/urls/guide#directions-action
The only issue is that the Google Maps URLs doesn't provide any parameter for departure time, so you will always get routes for "Leave now" that might have discrepancies comparing to a web service that was requested for a different departure time.
Based on your question I think the Google Maps URL might be
https://www.google.com/maps/dir/?api=1&origin=M460PU&destination=NN36NW&travelmode=driving
Google Maps Javascript API is reporting that I'm over the limit, but I'm pretty sure I'm not. I get this error:
You have exceeded your daily request quota for this API. For more information on usage limits and the Google Maps Javascript API services please see: https://developers.google.com/maps/documentation/javascript/usage
My Google API dashboard gives these numbers for the past day:
Google Places API Web Service: 407
Google Maps Geocoding API: 70
Google Maps JavaScript API: 30
What could be causing this? How can I get this up and running again, it is killing my application?
I came across your question because I am in the same position, seemingly well below the quota limits according to the console.
In the developer's console, go to the Dashboard, then click on the Google Places API Web Service. Then in the Quotas tab, scroll to the bottom and you'll see the Requests per Day. Here I was clearly reaching the 1000 requests per day limit, hence explaining the blocking of the requests.
We now count Google Maps JavaScript API client-side requests towards
the daily limit of the associated web service API.*
So it's the libraries=places and associated api usage (e.g. autosuggest in the search box) that is triggering this.
I added places with the Google Places API (Web Service) some weeks ago.
How does the approval work and
how long does it take till a place has passed Google moderation and is approved?
How do I know if a place was declined?
I added an other place with the Google Maps Maker. This place was approved within a week. What's the difference?
There are some reasons why we are receiving 'REQUEST_DENIED'
* You have not activated the Google Places API Web Service in the Google Developers Console.
* The key parameter is missing from your request.
* The key parameter does not match the your API key in the Google Developers Console.
* Your API key has not been correctly set up in the Google Developers Console:
* The request was not sent as an HTTPS request, HTTPS is required for all Google Places API Web Service requests.
* The incorrect HTTP method was used to send the request:
Double check all listed above then try to execute your application.
The newly-added place is available to your app after a short time, and is added to a moderation queue for possible addition to Google's Places database and Google Maps. Places that pass moderation will be visible to all apps and on Google Maps.
When you add a place, you receive a place ID for the new place immediately. This place ID is scoped for your app only. The place then enters a moderation queue, awaiting approval for addition to the Google Places database. If approved, the place will receive a new place ID, available to all apps and on Google Maps.
Here are related stack overflow ticket: REQUEST_DENIED when using the Google Places API / Google Places API - REQUEST_DENIED
I would like to know:
Is GTFS-realtime data available from the Google Maps Directions API?
If not, are there plans to include GTFS-realtime data in the Google Maps Directions API?
I am a member of a team developing a web application that integrates Google Maps Directions API. The website provides a "Trip Planner" form in which the user enters From, To, Date, and time data to display trip options into the website. Our website visitors are specifically interested in Bus transit options.
The integration is working wonderfully. However, the data returned by the Google API does not contain GTFS-realtime data. We know that the realtime is known to Google through GTFS feeds provided by the transit provider, and we see the realtime data when doing an identical search via https://www.google.com/maps.
I looked at the "Transit Specific Information" that is returned in the Google Maps API DirectionsResult Object (https://developers.google.com/maps/documentation/javascript/directions#TransitInformation). There is no reference to real-time information in this documentation. Even if real-time information is supplied (and I suspect that it is not), there would be no way to distinguish between scheduled and predicted times.