On Apr 7, 9:07 pm, ibgpsn <[email protected]> wrote: > OK, thanks. I had a way to decode the lat/lon and wondered what the zoom > string was buying me.
Basically - nothing except extra bulk. The poly itself contains every point unless point reduction is applied separately. > The lat/lon compression is about a factor of 3 for Appalachian Trail etc. but > you have to add in zoom string. > 5 digits after decimal point is OK for most topo map applications, unless > you're calling in a laser guided ordnance. I agree. It is accurate to approximately ten feet which is similar to the accuracy of civilian GPS. For building outlines and/or property boundaries, it is not enough. However, I doubt anyone would be using encoded polys for building outlines and/or property boundaries. -- 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.
