We really need polyline/gon editing, for our backend, tho we might as well keep v2 for the CMS and v3 for the front-end for now, still, its an extremely valuable tool to create content. Since Google maps is trying to slowly progress to a GIS it should have facilities to create the content you want to display. Therefor, it needs editing in my opinion.
2010/5/26 polylib <[email protected]> > On May 26, 12:31 am, "Thor (Google Employee)" > <[email protected]> wrote: > > > Encoded polylines was really useful too. > > > > Good to know. Please add to the Issue Tracker. > > The poly encoding algorithm is poorly designed but if it is to be > perpetuated, please make the "zoom string" optional. > > -- > 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]<google-maps-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-api?hl=en. > > -- Bjorn Brala ---------------- www.GeoStart.nl/english/ - Google maps - Swis Webdesign www.twitter.com/bbrala -- 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.
