From: David S. <on...@gm...> - 2011-04-29 22:57:06
|
On Sat, 30 Apr 2011 02:12:49 +0900 sangho park <gou...@gm...> wrote: > as basic concept, route information can be acquired by service, not > local data. > we can extend route for shortest path using local backing store, but > it's just option. > yes..yes.. it'll be very good feature that uses local map and route > data, but we should overcome so many license issues. Personally I think it's absolutely critical to be able to do local routing. That's my main use case, navigating out in the wild when I have no data connection. "Semi manual" routing is OK, that's even a desired feature. Pick out a few waypoints, draw some route segments, tell it to follow this road or river from waypoint C to waypoint D, but keep the A to B to C and D to E segments... Perhaps, if we have to, precalculate route segments when there is a data connection, store them; then manipulate them later, adding or removing them to a particular route. /me does not want to be stuck out in the middle of nowhere with no routing ability. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. |