Forge viewer with google map extension - autodesk-forge

seems google map API is no longer free, error message -> You must enable Billing on the Google Cloud Project at console.cloud.google.com/project/_/billing/enable.
is it true? any workaround?

We can't speak for google's billing plans, for development, please try creating one more google account and then a trial version of google maps access perhaps.

Related

Google Maps API error: Google Maps API error: ApiNotActivatedMapError

I am trying to use google maps distance matrix api in my project to get distance between 2 places. I have also enable this api in google developer console. But I am continuously getting error ApiNotActivatedMapError.
I am using sample code provided by google as distance-matrix .
When you use a library or service via the Maps-Javascript-API, and use a key, you only need to activate the Google Maps JavaScript API .
When you get the particular error with the linked example you obviously didn't activate the Google Maps JavaScript API for your project.
Update:
since June 22, 2016 you need also to activate the related API(Webservice) for new applications when you want to use the following features:
geocoding service
directions service
distanceMatrix service
elevation service
places library
Old question.. But.. I had n similar issue recently with a ApiNotActivatedMapError using geocoding but Konerak's comment helped me get to this really nice post.
Basically, you can activate your API's here: https://console.developers.google.com/apis/library
Activating Google Maps JavaScript API along with the already activate Geocoding API solved my problem.
Hope it helps someone in a similar position :)
This link is enabled API https://console.developers.google.com/apis/library. For default emulator and in iOS its disabled, but in this console you can active this API.

Google Drive APi and Google Maps in the same application

I'm using Google Maps API in my application. I want to use Google Drive too. Do I need to create a new key and project in google developer console, or just enable Google Drive?
Just enabling Google Drive would be fine.
According to the console help docs:
a project is a collection of settings, credentials, and metadata about the application or applications you're working on that make use of Google Developer APIs and Google Cloud resources.
So in other words, one project == one app.
https://developers.google.com/console/help/new/?hl=en_US#managing-projects-in-the-developers-console
Hope this help!

API Console for Maps For Businesses

Is there a way to use the API Console instead of the Enterprise portal of Google Maps for Business to check my quotas and billable limits?
I created a project with the same account i use to enter the enterprise portal but im not sure they are both linked.
Maps for Work (Enterprise) billing and quotas are available in the API Console only for the Google Places API, the Geolocation API, the Roads API, Maps SDKs for Android and iOS.
https://developers.google.com/maps/premium/previous-licenses/previous-faq#google_maps_api_services
Just FYI, all new projects renewed or created after january 1st of 2016 are using the developer console which is much simpler than the old site.

Is there an issue tracker for Google Drive Realtime API?

I am facing a bug with Realtime API of Google Drive SDK and I like to know if there is an issue tracker where I can check if that issue is registered and eventually fill a new one.
There are no official bug trackers for the Google Drive service.
There is this page, which lists the known issues encountered using Google Drive :
http://support.google.com/drive/bin/static.py?hl=en&page=known_issues.cs
And this other one that links to Google Drive service's forum, where yo can actually report an issue (look at the proposed categories):
https://productforums.google.com/forum/m/#!forum/drive

Understanding the authorization flow with Google Drive and Google Play Services

I have gone through Quickstart with Google Drive and I have also used Google Play Services. The docs for Google Drive outline the process of how the authorization flow works. The docs also indicate that developers should not use Drive initiated authorization although it appears that the Quickstart sample app does exactly that. I am left with the impression that Google prefers that the developer handle all the details of authorization.
Yet after trying out sample code that uses Google Play Services (but not for Google Drive), I am left with the impression that Google wants developers to use Google Play Services to handle all the authorization. It seems that Google Play Services simplify the authorization process significantly. Although the docs don't say this, I found elsewhere online that GoogleAuthUtil.getToken manages how access and refresh tokens are retrieved, especially after they expire.
Basically, the issue I am struggling with to understand is whether the Google Drive docs for the API are out of date and Google wants us to rely upon Google Play Services. There seems to be a lot of complexity in the Google Drive authorization process that Google Play Services has eliminated. At the same time, the docs for Google Drive API has been available for over half a year, so it makes me question why Google hasn't updated these docs to show any reflection on how Google Play Services are used with it.
Any insight into this would be appreciated.
The recommended approach for authorization on Android is using Google Play Services. The Android quickstart guide on the Google Drive SDK documentation covers exactly that:
https://developers.google.com/drive/quickstart-android
The Google Drive docs are out of date and Google should really update them. Retrieving tokens and authenticating users should be done using Google Play Services. The only thing you should be using the Google Drive API for is accessing the Google Drive service. Google Play Services handles all the details of authenticating users, retrieving access and refresh tokens and handling all the errors that can arise.