Awesome... I added a second backslash where I only had single
backslashes previously... et voila. Now it works.
Can I inquire further though about your comments on encoded level
strings and the purpose of encoded polylines? I thought that the
purpose of an encoded polyline was:
1) compact code
2) faster rendering times
3) ability to set zoom levels
How am I missing these benefits? I am using a string of Bs because
that is what the encoding utility gave me. The GMap doc example
seems to use all Bs as well:
var encodedPolyline = new GPolyline.fromEncoded({
color: "#FF0000",
weight: 10,
points: "yzocfzynh...@n}@o...@nzd",
levels: "BBB",
zoomFactor: 32,
numLevels: 4
});
map.addOverlay(encodedPolyline);
Please let me know what I am not doing correctly?
Thank you greatly for the assistance.
-mcslain
On Feb 16, 4:22 pm, "maps.huge.info [Maps API Guru]"
<[email protected]> wrote:
> p.s.
>
> Using an encodedLevels string of all B's renders any value you gain
> from encoding moot. There is absolutely no point in using encoded
> polygons/lines unless you also properly utilize the encodedLevels
> string as well.
>
> -John Coryat
>
> http://maps.huge.info
>
> http://www.usnaviguide.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
