> I have noticed that GDirections works according to the map data > displayed (or that's my explanation for it anyway), which is a problem
GDirections uses a road network database at Google's servers. It doesn't matter what map you display, it will use the same database. There is no way to force it to use something else. It's not the same as the database used by maps.google.com, which presumably is at present "better" in some way, whether that's because it includes MapMaker info or some other updated dataset. I think you'll just have to live in hope that the more detailed data eventually makes its way into GDirections. You could also try the v3 API Directions service, it may or may not be more in line with maps.google.com -- 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.
