Can Chrome extension name include Google product name?
For example: "YouTube Hello"
If your product is compatible with a Google product, make reference to that Google product by using the text "for", "for use with", or "compatible with", and be sure to include the ™ symbol with the Google trademark. Example: "for Google Chrome™"
Learn More
https://developer.chrome.com/webstore/branding#description
Related
In the google maps place API web service doc it says for nearbySearch for name "One or more terms to be matched against the names of places, separated with a space character."
But I'm not sure how to do this. I've tried the following
https://maps.googleapis.com/maps/api/place/nearbysearch/json?key=AIzaSyDi9shpQeCKw2VyelOJrawc****&location=41.8369,-87.6847&radius=50000&name=alinea%20yusho
but it returns no results even though google definitely has entries for both alinea and yusho. What exactly do they mean by "separated with a space character"?
Try to use pipe symbol instead. I tried it and it worked!
name=alinea|yusho
I have the Place Id of a place on google maps in my app. Is there a way to put the place Id in a URL and have it directly link to the page? Or does it have to be done through the URL?
I can't seem to find anything detailing this in the docs. I've tried below, but it just gets me the standard google maps page:
https://maps.google.com/maps?placeid=ChIJN1t_tDeuEmsRUsoyG83frY4
Recently, in May 2017, Google launched the new Google Maps URLs API. You can read about this API in the official documentation
https://developers.google.com/maps/documentation/urls/guide
So, from now on you can construct a URL for Google Maps using the place ID. In your particular case this URL will be
https://www.google.com/maps/search/?api=1&query=Google&query_place_id=ChIJN1t_tDeuEmsRUsoyG83frY4
Hope this helps!
Not directly, using the placeID you can get a variety of information in JSON or XML format, among them there are also the lat lng of the place and its address with which you can easily locate the map
google developer doc
The URL for a specific Google Place is returned by the places details API endpoint.
If for example you query:
https://maps.googleapis.com/maps/api/place/details/json?placeid=ChIJV2BQ4laeekgRFauLvdXbFXE&key=YOUR_API_KEY
You will see that in the returned JSON there is a key 'url' which points to https://maps.google.com/?cid=8148660811851344661
The correct format, at this time, to produce a general link that goes directly to correct google place is: https://maps.google.com/?cid=[place_id]&t=[maptype]
The map type parameter "t" is apparently necessary. Without it, google maps seems to perform a more general search when the link opens that is sometimes successful and sometimes not. With it, maps opens to correct place each time whether it opens in browser or in app on mobile.
Set this parameter to "m" for a street map and "k" for a satellite map.
A lot of answers on SO show the following syntax which often pulls unwanted results if two locations of the same name are nearby e.g.:
https://www.google.com/maps/place/Starbucks/#43.088554,-88.06579,17z/
If you are already using google places api, then you have the place_id, so i recommend using it to avoid ambiguity.
When I search something using the standard Drive interface, the resulting page have an url which encodes the search terms, for example (basic search):
https://drive.google.com/a/mydomain.com/?tab=mo#search/toner
or, as an alternative:
https://drive.google.com/a/mydomain.com/?tab=mo#advanced-search?q=fogna&view=2&visibility=2
Where can I find a reference on how this url is built (query parameter syntax)?
I understood the following empyrical;
"?tab=mo" seems somehow required
"visibility=2 searches all the documents in my domain (for Business Apps)
"advanced-search?q=" is alternative to basic search
"view=2" or "view=1" seem the same thing
I haven't experimented different combinations until now.
I am trying to integrate a custom search box in one of our Sites, in order to provide the user with results from the Drive contents (this is not possible using the standard search function in sites).
Unfortunately I can't answer your question but I can share that I'm looking for exactly the same thing. Since Google retired iGoogle the built in Google Docs/Drive search gadget within Google sites no longer returns a result. Creating a dialogue box that returns a custom URL for search would be the most straight forward method to perform a basic search.
It seems that as a minimum the base URL for a search is ...
https://drive.google.com/a/mydomain.com/#search/
Appending the search term requires %20 to replace spaces
e.g.
https://drive.google.com/a/mydomain.com/#search/my%20document will return a search for 'my document'
Good luck Massimo, hopefully some can assist
The drive SDK has includeSubscribed for drive.changes.list. Is there an equivalent in Documents List ?
There is no equivalent according to my current knowledge.
When adding more than one phone number in the "Main Phone" field of Google Places' uploaded bulk file, I'm having the formatted phone number validation message. I don't want to add the alternative phone under the "Alternative Phone" field because this field is not retrieved through the Google Places API!
The link to the missing data problem is found at:
A Missing Data Issue in Google Places API
So is there a way to upload the bulk file having more than 1 pone number under the "Main Phone" attribute??
Thanks!
There is no way to add more than one phone number in "Main Phone" field as this is not supported by Google Places. You must conform to the formatting rules when uploading bulk places as specified here: http://support.google.com/places/bin/answer.py?hl=en&answer=1722104
As the formatting guide states: "Phone numbers must be valid in the country where your listing is located.", adding more than one number into the "Main Phone" field is not classified as a valid listing.
Your only option is to use just one phone number as returned by the Google Places API or wait until the feature request for the Google Places API to return more than one phone number has been filled: http://code.google.com/p/gmaps-api-issues/issues/detail?id=3905
For anyone else interested in seeing this feature added to the Google Places API please click the 'star' icon to be notified of future changes, and to let us know you are interested in seeing it resolved.