On Dec 1, 11:43 am, Anton Bulgakov <[email protected]> wrote: > Hello! > > I have a suggestion to increace accuracy class in encoding algorythm > for EncodedPolylineData. > > For now it is 1e5 : > > "The steps for encoding such a signed value are specified below. > 1. Take the initial signed value: > -179.9832104 > 2. Take the decimal value and multiply it by 1e5, rounding the > result: > -17998321 " > > its not very nice for me. i need accuracy class minimum 1e8
Version 2 is now deprecated and is extremely unlikely to be changed to such a large extent. Or did you mean to post this to the Version 3 Group? The earth is 40075km around the Equator, so an accuracy of 1e-5 degrees is a real distance of 1m maximum -- it's less as you go nearer the poles. 1e-8 provides a distance of 1mm at the Equator -- and 0.3mm at your latitude. Do you really need that level of precision in a map? It's highly likely that the tiles themselves aren't positioned with that level of accuracy. What is more likely to have an effect on the line is the [Douglas- Peucker] algorithm which works out which points not to show -- and that's not changed by increasing the accuracy of the points themselves. Your encoded string has a very odd character at the start, which isn't going to be very useful. The encoding is designed to produce characters in the low ASCII range. -- 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.
