On Mar 15, 2:44 pm, bratliff <[email protected]> wrote: > > V3 does not support encoded polys.
Ha! I hadn't noticed that you cannot setPath(encoded), and I think it's curious because the DirectionsStep returns encoded_lat_lngs among other fields. >V2 encoded polys are confusing & > inadequate. I still think they'd be a better, more compact format to store than SVG, and the conversion utilities are readily available in various languages from Marc McClur's page. > I believe his application involves floor plans which > cannot be described with five decimal places of Lat/Lon precision. I > believe it uses a Euclidean (flat) projection. You can use any precision. You're not limited to 5 decimals. -- Marcelo - http://maps.forum.nu -- -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
