Thanks Antohny for pointing out a solution, and to Mike for rewrtiting his code. I figured out the first solution with feeding the last accumulated distance to the funtion, but that new implementation is much nicer.
Case closed :-) On 28 Nov., 18:58, Mike Williams <[EMAIL PROTECTED]> wrote: > Wasn't it Anthony who wrote: > > > > >It looks like the EPoly code is really only meant for use with one > >distance (i.e. one function call). You should be able to speed it up > >significantly (from O(n^2) to O(n), I would think) if you rewrite it > >to find multiple intervals. > > That sounds like a plan. I've now added GetPointsAtDistance() to > EPoly.js. It does go quite a bit faster. > > http://econym.org.uk/gmap/epoly.htm > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
