Google Places API and Radar Search Requests in iOS - objective-c

I would like to find all places (max 200) near current location, depend on types (supported types) and the distance radius (max 50 000 meters). I'm working with Google Places API in Objective-C language.
A Radar Search request is an HTTP URL of the following form:
https://maps.googleapis.com/maps/api/place/radarsearch/output?parameters
Example URL:
https://maps.googleapis.com/maps/api/place/radarsearch/json?location=48.859294,2.347589&radius=5000&types=food|cafe&keyword=vegetarian&key=API_KEY
Now I need to put name these finding places to NSString array. I must make loop which return NO when names of places in array are completly. Could you help me or give me links how to working with JSON and fetch data from JSON format?

Related

What is the best way to send String input to Google Text-to-Speech?

I have a few paragraphs that needs to be put through the Google TTS API for conversion. Some of these sentences have Dynamic words in them (eg: username). By simply passing the entire text to the API, it's taking around 8-9 secs for the Google API to respond (since some of these sentences are significantly larger in size)
What is the best strategy for converting these sentences?
I was hoping I could first convert the Static part of the sentences and store it somewhere and then convert the Dynamic part, and somehow insert the byte response of the Dynamic word. But I am not sure if this can be done at all.
For eg:
Hi, User how are you?
I was hoping to store the byte responses for "Hi," and then "how are you?" and then insert the byte response for "User" in the appropriate position

PHP: Google Translate 5000 characters limit

I'm using this library for translating:
https://github.com/dejurin/php-google-translate-for-free
It's possible to translate more than 5000 characters with this library?
Or save the translated text to a txt and change from text translate to docs translate?
I mean this:
https://translate.google.com/#view=home&op=docs&sl=en&tl=lb
Based on what Google says, it is not possible to send more than 5,000 characters per request. Moreover, Google recommends that you send less than 5,000.
You can find it here under technical questions : Google Translate FAQ
Regarding the second question, ii is possible.
According to the website of the library the result of the translation is returned in the form of an array, so first of all you must do is convert the array into a string, separating each element of the array by what you decide (here I separate it by a blank space):
$arrayToString = implode(' ', $result);
Here $result is the array returned by the library. Now we just have to save the string in a txt file.
$file = 'path/to/file/filename.txt';
file_put_contents($file, $arrayToString);
Regards

Error 414 -The requested URL is too large to process

I am using Google Chart API in my Application and generating graph using URL "http://chart.apis.google.com"
I am getting error "The requested URL is too large to process", when I provide large set of parameters to this URL.
What I can do in this situation?
The Google Charts API FAQ offers this advice:
Is there a limit on the URL length for the Google Chart API? What is the maximum URL length?
The maximum length of a URL is not determined by the Google Chart API, but rather by web browser and web server considerations. The longest URL that Google accepts in a chart GET request is 2048 characters in length, after URL-encoding (e.g., | becomes %7C). For POST, this limit is 16K.
If URL length is a problem, here are a few suggestions for shortening your URL:
If you are using a text encoding data format, remove leading zeros from numbers, remove trailing zeros after decimal points, and round or truncate the numbers after decimal points.
If that does not shorten the URL enough, use simple (1 character) or extended (2 character) encoding.
Sample data less frequently; i.e., reduce granularity.
Remove accoutrements and decorations, such as colors, labels, and styles, from your chart.
also found this but there doesn't seem to be an answer/solution.
http://groups.google.com/group/google-chart-api/browse_thread/thread/b47c1588b39d98ce
In case it is a browser error - browsers have their maximum URL length limitations (IE 6/7 has 2,083 limit):
What is the maximum length of a URL in different browsers?
I'm getting HTTP 414 but my URL length is not an issue (it is 1881 characters), and I have tried both GET and POST. My guess is that Google will also return this error when the chart you are requesting is too "expensive" to generate.
A method that worked well for me was to divide all values by 10 or 20 and converting the results to int (no commas), but I kept the numbers on the axis. This way, it's a little less accurate but reduces the amount of characters used in the URL.
Code example:
$newSalesrank = $rank/20;
$rankdata .= intval($newSalesrank);
This solved my problem, I got no more "url too long" errors and it still looks good on my charts - because it still looked the same, the numbers just were simply scaled down.

How to change Geo information to real name

Is there a way to convert Geo information to real place name? For example, I take a photo on "137-159 New Montgomery St San Francisco, CA 94105", the Geotagging information is :
geo:37.786971,-122.399677
when I type the geo in google map, it can show the place name to me. Does google provide API to get it? Thanks in advance.
Yes, the Google Maps API GeoCoder GClientGeocoder.getLocations() provides reverse geocoding as well:
The term geocoding generally refers to translating a human-readable address into a point on the map. The process of doing the converse, translating a point into a human-readable address, is known as reverse geocoding.
The GClientGeocoder.getLocations() method supports both standard and reverse geocoding. If you pass this method a GLatLng object instead of a String address, the geocoder will perform a reverse lookup and return a structured JSON object of the closest addressable location. Note that the closest addressable location may be some distance from the original latitude and longitude values of the query, if the supplied GLatLng is not an exact match for any addressable locations.

Using Google Weather API with Lat and Lon - how to format?

I want to use the Google Weather API - by passing lat and long values. I am storing these values, however it seems Google needs these values in different format.
i.e. For the town of McTavish I have values of 45.5 and -73.583
This works here: http://api.wunderground.com/auto/wui/geo/WXCurrentObXML/index.xml?query=45.5,-73.583
But when I use these data for Google API, it does not work: See: www.google.com/ig/api?weather=,,,45.5,-73.583
Any help appreciated. I would prefer to use the Google Data.
UPDATED ANSWER:
I have just noticed some OTHER irregularities with Google's Weather API. In ANY case, you need to have 8 numerical digits, in addition to the negative sign, if it applies. See the following code block (Java-based) for proper formatting. (Not the perfect algorithm, but just a quick example so that you can see the results)
lat = lat.replace(".", "");
while(lat.length() < 9)
lat = lat.concat("0");
if(lat.contains("-"))
lat = lat.substring(0, 9);
else
lat = lat.substring(0, 8);
ORIGINAL RESPONSE:
Paul, the trick about Google's Weather API is that you don't use the coordinates as received by traditional latitude/longitude. Instead, you parse out the decimal points. Additionally, a "fun quirk" of Google's Weather API seems to be a requirement that the data come in as a 7- to 8-digit string. So, for instance, 45.5 should really be 45.50000, and -73.583 should really be -73.58300. This length of 7-8 digits does NOT seem to include the negative sign (-) in front of any negative coordinates.
So, your 45.5(0000) becomes 4550000, and your -73.583(00) becomes -7358300. So the final URL would be:
http://www.google.com/ig/api?weather=,,,4550000,-7358300
Note that again, 7-8 digits means 4550000 or 45500000 would be acceptable, as would -7358300 or -73583000.
I only found out about the 7-8 digit length when I saw your question--I tried entering the data into my weather parsing program, and found that 455,-73583 does not yield proper data.
Note that this is by my unofficial experimentation, and not by official documentation, so there may be other quirks to be discovered.
It's much simpler - latitude & longitude should be multiplied by one million
In my opinion longitude an latitude must be coded in _e6 format (six last digits must be the decimal part of the lon/lat string passed to the API). Then you must adjust first decimals to a length of six, you add 0s if you have fewer than six decimals, and you clip it to 6, if you have more. For the int part if you have just one character you must add a zero first, for two or three digits, you don't need to do anything.
Examples:
1.1234 must be coded as: -01123400
112.2345 must be coded as: 112234500
34.123456 must be coded as
Here you have a explanation with examples and a the php source code (the blog is written in Spanish).
As Miguel said it is the last 6 digits that should be the decimal places. So the correct code is as simple as....
string.Format("http://www.google.com/ig/api?weather=,,,{0:0},{1:0}",
(latitude * 1000000),
(longitude * 1000000));