Thanks for the info and yes it was a problem with javascript string handling. I simply used the addslashes() php function to fix the problem. Its sad that the one mentioning the pitfalls, his own utility doesnt produce the right code.
Any from google on how to encode the encoded levels string? On Oct 29, 10:40 am, Andrew Leach <[email protected]> wrote: > On Oct 29, 1:39 am, Jay Philips <[email protected]> wrote: > > > I've been trying to wrap my head around this problem for some time now and > > my conclusion is that google maps encoding feature has some major flaw in it > > which is causing encoded polygons to not appear as they are supposed to. > > cqdzCecqqIjEnB\MpB{FaEaCyCzG > > No, it's not a flaw. It's a feature of HTML checkboxes and Javascript > string handling. > > > I tried > > <http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/encodeFor...> > > to have it do the encoding and it didnt get past encoding the first > > point. > > You didn't > findhttp://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/pitfalls.... > > http://groups.google.com/group/google-maps-api/search?group=google-ma... -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
