Thanks Chad.

I will investigate V3 API. I would like to confirm that the
discrepancies are actually caused by the key in v2, correct?

Thanks
Chen

On Jun 14, 1:02 pm, Chad Killingsworth
<[email protected]> wrote:
> For any type of mobile development, you really should be using the v3
> API - it's designed for that. Also v3 doesn't require API keys.
>
> Chad Killingsworth
>
> On Jun 14, 11:27 am, Chen Song <[email protected]> wrote:
>
>
>
> > Hi
>
> > I am developing an iPhone app which needs to call Google Map V2
> > Javascript API to get routing information. The app is using JSON to
> > generate the request and parse the response. What I observed is that
> > the response from Google Map is changing and not consistent over time.
>
> > For example, below is a snippet that is part of the response processed
> > by JSON. As you can see, the value of the root node for the routing
> > information is "B". But as times goes on, the root node may change its
> > value to "A". I have found such changes happened several places in the
> > response and there is no pattern how the keys are changing themselves.
>
> > B =     {
> >         Distance =         {
> >             html = "2,884&nbsp;mi";
> >             meters = 4641558;
> >         };
> >         Duration =         {
> >             html = "1 day 21 hours";
> >             seconds = 163819;
> >         };
> >         End =         {
> >             coordinates =             (
> >                 -121.07983,
> >                 37.705488,
> >                 0
> >             );
> >         };
> >         Steps =         (
> >                         {
> >                 Distance =                 {
> >                     html = "85&nbsp;ft";
> >                     meters = 26;
> >                 };
> >                 Duration =                 {
> >                     html = "2 secs";
> >                     seconds = 2;
> >                 };
> >                 Point =                 {
> >                     coordinates =                     (
> >                         -74.00615,
> >                         40.71436,
> >                         0
> >                     );
> >                 };
> >                 descriptionHtml = "Head <b>southwest</b> on
> > <b>Broadway</b> toward <b>Chambers St</b>";
> >                 polylineIndex = 0;
> >             },
> >                         {
> >                 Distance =                 {
> >                     html = "0.4&nbsp;mi";
> >                     meters = 635;
> >                 };
> >                 Duration =                 {
> >                     html = "1 min";
> >                     seconds = 87;
> >                 };
> >                 Point =                 {
> >                     coordinates =                     (
> >                         -74.00632,
> >                         40.71416,
> >                         0
> >                     );
> >                 };
> >                 descriptionHtml = "Take the 1st <b>right</b> onto
> > <b>Chambers St</b>";
> >                 polylineIndex = 2;
> >             },
> >             ...
>
> > When calling Google Map V2 API from iPhone, I used a Google Map API's
> > key which is not generated by Google but just an arbitrary character
> > sequence. My question is as below:
> > 1) Is the API' key the root cause of the issue I observed in my iPhone
> > app?
> > 2) If so, can I resolve the issue by requesting a key officially from
> > Google? I tried to sign up for a key but it needs me to provide my
> > homepage URL. As I am using the key in an mobile application instead
> > of in a website, I don't know how I could request the key without an
> > website URL.
>
> > Thanks for you time on my question.
>
> > Regards,
> > Chen

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-maps-api?hl=en.

Reply via email to