This is great news. I was wondering if there is a plan to expand this library to include more standard computational geometry functions in, such as intersect, hittest etc in? Since it is treated a separate lib to load, it's size probably is a less concern that the core. Also, I assuming even it is specified in the bootstrap code, it will still loaded afterwards (i.e. won;t not increase the startup time)?
On Jan 5, 1:20 am, "[email protected]" <[email protected]> wrote: > I just saw the neat API V3 Geometry Library > > http://code.google.com/apis/maps/documentation/javascript/geometry.html > > he documentation seems a little thin right now. Some questions: > - What units do computeLength and computeDistanceBetween return their > results in? > (I assumed meters, and that loooks to be correct) > - Is there anyway to change those units? > > - Does computeLength take a "path" an array of latlng objects (it > doesn't seem to, how do we use it? > It says this: You may instead use computeLength() to calculate the > length of a given path if you have several locations > > - Does computeArea take a path? Will it work on a google.maps.Polygon? > > The examples don't include the length or area methods. > > Thanks, > Larry -- 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.
