With Places API, it provides the ability to add new places. How much are we sure that Google does not use these custom added places for their own marketing and research purposes. What if you want to keep these new places private to your applications. The Add Place section does not talk anything about this.
Does anybody have any information around Google privacy policy around adding new places?
As per the documentation:
By adding a place, you can supplement the data in the Google Maps
database with data from your application. This allows you to:
Instantly update the data in Google's database for your users.
Submit
new places to a moderation queue for addition to the Google places
database.
This means that places added via the Places API are reviewed and, if approved, added to the global places database that is accessible for all users. They will not be kept private to your application.
UPDATE
The Place Add has been deprecated on June 30, 2017 and will stop working on June 30, 2018. So you cannot use this method anymore. For further details please refer to the corresponding geo blog post.
Related
I wonder if I can get working places for all users from organization using calendar API. Coworkers from my organization uses google calendar to mark if they work from home or office. I attach screen to show what I am talking about.
I've searched many endpoints from calendar API but did not find suitable one. Is it possible to get those information from API?
It is not yet possible to retrieve those information from the API.
But Google already documented it (tutorial, API reference) and it should come at some point in the (hopefully) near future.
Here is the related issue in their tracker : https://issuetracker.google.com/issues/199918380
using the google classroom api i am able to modify attachments
and everytime i call the method
courses.courseWork.studentSubmissions.modifyAttachments
but the attachments just concatenate to the previously attached files.
my question is how can i remove an attachment that i accidently added or that i want to replace?
just like the classroom UI enables you to remove an attachment after you added it
Google classroom UI
Unfortunately there is no feature available to remove attachments with Google Classroom API . This is a product limitation for the API and can be promoted for future development [1]. Your idea will then be available for other members of the community to browse and vote on. Depending on the business impact Google product engineers typically roll out into production.
[1] https://developers.google.com/classroom/support#missing_features
I am many errors on my Maps API Console.
I am the website owner, not the developer or webmaster.
Got an email from Google about new pricing. Below is the email.
Today we are announcing important changes, including our new name - Google Maps Platform, a simplified product structure, pay as you go pricing for all, and more. Please take a few minutes to review the announcement to familiarize yourself with the upcoming changes.
We would like to highlight a few updates that may impact your implementation. Beginning June 11th, we are launching our new pricing plan and providing all users access to support. We’ll continue to offer a free tier — all developers will receive $200 of free monthly usage of our core products.
How does this affect your current account(s)?
Based on your usage over the last 3 months and our new pricing plan, we estimate that your monthly cost will exceed the current $200 free tier.
I am trying to figure out why I have so many API calls.
I am seeing in the console, that in the "Google Places API Web Service" I have alot of "Zagat content in the Places API" calls, and they all result in error.
I am trying to figure out how this is happening, but not finding any info online. I see that the "zagatselected" parameter was discarded May of 2017. I can not figure out what is causing these errors.
Everything has been working fine, I have my own API key, and have for a long while. The only reason I am really looking into this, is because Google will now start charging me monthly.
Is it possible you expose your Maps API key to the client, don't have any restrictions on it, and someone else is calling the API/raising those errors?
If you have a snippet of code like this....
<script src="https://maps.googleapis.com/maps/api/js?key=[APIKEYHERE]&libraries=geometry,places&callback=initialize">
...on a public web page, it would be easy for someone else to take the API key and use it themselves, unless you add a IP or referrer restriction to only allow it to be used client-side from your website. You can set up restrictions on who can use your API key following these instructions.
I suspect that the new Google Maps and Places API pricing scheme (which significantly lowers the number of free Places API calls) might cause some less ethical users to use keys they can scrape off websites.
A recent Ars Technica article rekindled my interest in WebOS so I was looking at the Services API (because I'm interested in building a replacement calendar app). I discovered the following text at the top of the calendar services API documentation:
Note: To prevent unauthorized use of
private user data, this API provides
access only to records created by your
application; that is, you cannot
access records owned by another
application.
What is the point of even having an API if you can't access data created by other applications? At that point there would be no reason for me to use their API rather than building the data storage myself. Am I missing something? Can any WebOS developers weigh in on this?
P.S. If they named their os "WebOS" you would think they'd know something about sane URLs. Check out that ridiculous calendar api doc url!!
The reason for the limited access is because of security, but not just that. Some services have agreements that limit how their data can be used. For example, having an API that would let a random webOS app access your Facebook calendar data would be working around the FaceBook terms of service that control how that data can be used. The same applies to LinkedIn, Google Calendar, and any other service from which the system is pulling information.
If you just need to post an occasional event, there's a better API to use that lets you cross-launch the calendar app with data that the user can accept into their own calendar. That way, you don't create your own bucket, but the user has to manually accept the event.
The reason to use the calendar APIs is to expose your own data to the user of the device. FlightView, for example, uses it to publish a calendar to the user of upcoming flights that he or she is interested in, and if those get rescheduled, it can automatically change them. The Fandango app uses this to push movie times for theaters the user likes into their calendar view. There's lots of possibilities.
I'm using Google Apps for my domain, and trying to enable access to the calendar on my website.
The problem is that I get This feed is read-only error every time I try to add an event to the calendar. Here's where I post to: Link (dead link)
You're using the basic feed, which according to the documentation is always read-only. Use a feed URL ending in private/full or private/full-noattendees instead.
(Disclaimer: I work for Google, and as part of implementing the calendar side of Google Sync I've had some experience of working with the GData APIs, but anything I write here must be taken to be the views of a private individual rather than as official Google policy etc :)