I wanted to describe in more detail, what I suggest what should be done to optimize the
usage of waypoint and routes:
Of course first of all, I want to remember what I already posted here: http://www.usglobalsat.com/forum/index.php?topic=973.msg1756#msg1756
But there was one item, I wanted to specify in more detail (my favorite item):Route definition:
1. To be sure what we are talking about:
* A "Route" is considered a sequential ordered number of waypoints.
* A "Route" is needed to use the full functionality of the navigation tools of GH-625.
* Currently there is no way to load a route into the GH-625 via PC software.
* The method of creating a route with the buttons of the watch is "no fun".
2. Of course, the best solution would be to have a "Load" function for routes,
like we already have for tracks and waypoints. Routes can aldready be created via TG 2.1
(the sequential ordering of waypoints is already there !). The only thing missing is the
communication protocol/software for loading these few numbers into the watch.
It's really a pitty !
Maybe Geoffrey can check again with his team, if there is a possibility to implement this !
3. If this is not possible, I would suggest a workaround, which seems to be rather easy.
It consists of two steps:
a) First it has to be maded sure, that during waypoint definition in TG 2.1, the waypoint
naming is done in alphanumerical order, like A001, A002... A050.
This could be done either by the user himself. Or even better: By a software option
for automatical naming. This could ask for a name pattern like "A###", when first
waypoint is created. All following waypoints would be named automatically with up
b) After loading the waypoints into the watch, the route has to be created.
What has to be done manually in the moment, could be done by the watch itself
with an automatic route creation, which just orders all waypoints according to their
alphanumerical names into a route.
I think this is a simple function and I'm sure, GlobalSat can do that !
c) When I said, the auto-route function should order "all" waypoints to combine a route,
that means, it will only work fine, when "all" waypoints belong to one single route only.
If you want to keep waypoints for more than one route inside the watch, the conecpt
needs a litte extension:
For more than one route, you should start with giving them different names,
like "A001, A002,... A050" for route "A" and "B001, B002, ... B050" for route "B".
After importing the waypoints into the watch, the auto-route function could ask for
a start and end point and after selecting "B001" and "B020" it will create a route
by combining all waypoints in this band.
This is a little extension to b), but it's still not too complicated.
From my point of view, these modifications could solve the problem of route creation.
Of course any feedback is welcome !