Re: Metroguide, Vista C and routes.
From: Nacho (ncc1701zzz_at_hotmail.com)
Date: 11/27/04
- Next message: Randy: "Re: Which one?"
- Previous message: Fred Hiltz: "Re: multi use gps"
- In reply to: Stuart Middleton-White: "Re: Metroguide, Vista C and routes."
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 27 Nov 2004 16:41:40 GMT
Hi!
Thanks for your long explanation!
I will play with different options and save the same route in several
ways to play with.
I have seen that a track will all the viapoints is too long, when I
upload it to the GPS, it says that the track will be trunked.
But the option of convert an auto-generated route to a route with hidden
via points seems to be very nice...
Best regards.
Stuart Middleton-White wrote:
> Nacho <ncc1701zzz@hotmail.com> wrote:
>
>
>>I have tried WinGDB and it works just fine!
>>Have you any personal experience with the different methods?
>
>
> Yes. In order to understand how WinGDB/Routetool operate you have to
> know how routes are stored in MapSource GDB files.
>
> Routes consist of waypoints (that appear in the MapSource waypoint
> list) added by the user, via's (don't appear in the waypoint list but
> are visible on the screen) which are created when you drag'n'drop the
> route line in MapSource, and invisible via's which MapSource adds
> (based on the map data) and stores in a route. MapSource typically
> adds many of these invisible via's so the route follows the road. The
> problem with later Garmin units is that they discard these invisible
> via's on the assumption that the route will be recreated based on
> autoroutable maps. If you don't have any loaded then the route is just
> a (small) number of straight lines between the waypoints/via's.
>
> WinGDB gets around this by converting point types based on the users
> preference. Thus
>
> "Convert routes to tracks with all points"
> uses *all* point types in the route to create a track. The problem
> with this is that long routes create very large tracks. Most Garmin
> units have a 10,000 point limit in the active log so it may be
> desirable to reduce the number of points (BTW MapSource has a feature
> to reduce the number of track points).
>
> "Convert routes to tracks with via points only"
> I think (not 100% sure) that this just ignores invisible via's when
> creating tracks from routes.
>
> "Convert auto-generated route via points to user waypoint vias"
> This option converts the invisible via's to normal (visible) via's
> creating a new route (not track). This makes the route follow the road
> as per MapSource. However the GPS has a limited number of points per
> route (250 for the 60C/76C series). Again on long routes too many
> points can be created.
>
> "Convert auto-generated route via points to hidden via points"
> Does the opposite of the option above (I think). I'm not sure what use
> it is.
>
> "Convert tracks to routes with user waypoint via's"
> Makes a route from a track using normal via's.
>
> "Convert tracks to routes with hidden via points"
> Similar to the last but invisible via's are used.
>
> I suggest you play with the different options and look at the results
> in MapSource. It should become clearer then ;-)
>
> ---
> Don't feed trolls--it only makes them grow!
- Next message: Randy: "Re: Which one?"
- Previous message: Fred Hiltz: "Re: multi use gps"
- In reply to: Stuart Middleton-White: "Re: Metroguide, Vista C and routes."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
