Re: Problem using array of strings for display of multiple encoded polylines

Yes it is, for now. BTW, it looks like v3 doesn't use encoded
polylines, but instead uses arrays of points comprising a polyline.
I'm very new at this - just started looking 2 days ago and completed
my first map with the help of this group yesterday - is it likely that
google will maintain encoded polylines in v3 or has it definitely been
left behind? Also, how long should I assume v2 API to be supported/
allowed before having to redo this map.

Thanks again for your help!
Jeff

On Nov 2, 9:52 pm, "geocode...@gmail.com" <geocode...@gmail.com>
wrote:
> On Nov 2, 7:40 pm, Jeff <jeff.ti...@gmail.com> wrote:
>
> > Here is my "final" in case anyone is interested later. I'm also
> > interested in hearing from others who may be doing similar maps.
> > Jeff
>
> >http://www.azimotion.com/myTripShotMaps.html
>
> Looks to me like you have a default (red) marker over top of a
> (smaller) blue marker.  Is that on purpose?
>
>   -- Larry
>
>
>
> > On Nov 2, 11:41 am, Jeff <jeff.ti...@gmail.com> wrote:
>
> > > Andrew - thank you!  My mistake was in confusing the array string
> > > declaration as you noted - didn't need to be enclosed in quotes.  I
> > > removed the escaped quotes and now see multiple polylines displayed.
>
> > > Thanks to all (and especially to the original responder John who had
> > > tried to gently guide me down the right path based on missing the
> > > escaped backslashes in the points).
>
> > > And yes, the references you guys provided were very helpful beyond the
> > > original documentation.
>
> > > I appreciate it,
>
> > > Jeff
>
> > > On Nov 2, 11:30 am, Andrew Leach <andrew.leac...@googlemail.com>
> > > wrote:
>
> > > > On Nov 2, 5:16 pm, Jeff <jeff.ti...@gmail.com> wrote:
>
> > > > > OK, those last two replies turned some lightbulbs on, thanks.
> > > > > Following is the code I now have with escaped quotes and double-
> > > > > escaped backslashes in the encoded polylines. Unfortunately, I see
> > > > > only the markers, but none of the polylines displayed by the browser
> > > > > (Firefox).
>
> > > > Why do you have escaped quotes in the strings? The strings of
> > > > characters must not contain quotes, only valid characters.
>
> > > > To get a Javascript string containing the characters ABCDEFG, you put
> > > > that in quotes, either single or double. These are equivalent, and
> > > > contain strings of seven characters:
> > > > var mystring= "ABCDEFG";
> > > > var mystring= 'ABCDEFG';
>
> > > > That is not the same as these, which are also equivalent:
> > > > var mystring="'ABCDFEG'"
> > > > var mystring="\'ABCDEFG\'"
> > > > because in these statements, the strings really contain the quote
> > > > characters. The strings are nine characters long.
>
> > > > Regarding the levels string, Google's example page, encoding function
> > > > and documentation are (ahem) sub-standard. Prof McClure's is far
> > > > better and produces results which do the job that encoding is intended
> > > > to do.
>
> > > > Andrew- Hide quoted text -
>
> > - Show quoted text -

--

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