Hi frnds, Can any one of you give me the code for putting arrows to show the directions on the polylines.
On Sat, Apr 25, 2009 at 10:16 AM, bratliff <[email protected]> wrote: > > On Apr 24, 8:36 pm, mark mcclure <[email protected]> wrote: > > I'm not really sure that I do anymore. Back when I first started > > making > > these maps, it was literally impossible to make a polyline with more > > than 500 vertices that didn't crash most browsers. At that time, > > encoding allowed you to make polylines with tens of thousands of > > vertices. It seems, though, that things have improved greatly for > > normal polylines, though. I'm thinking that maybe you can do a few > > thousand points without worrying about encoding and still have > > reasonable performance these days. > > > > Mark > > Basically, I agree unless your poly has never had point reduction > applied to it. On really clean polys like Mark's British Coast Line, > "Packer" cannot eliminate much. On really dirty polys like the U.S. > Census Cartographic Boundary files, "Packer" can do a lot of > reduction. Fewer points will improve performance. > > Trying to provide a good rule of thumb is futile. The API supports > four different poly rendering engines for the different browsers. > What works well in one browser may fail miserably in another browser. > Google has an undocumented "mapslt" / "mapsdt" facility. It blows > away all four of the GPoly rendering engines. Unfortunately, you have > to bend the TOS rules in order to use it. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
