Originally Posted by Russ
Ya in most cases what you say is true but NOT in Homeport. You CREATE a track and a route on the Homeport program. Hence the rub, Homeport treats a track differently than things like CE, or The CAPN. No offense but you haven't used Homeport I guess
. Remember Homeport is ONLY
a planning software
. Once the Homeport route/track is loaded on the Garmin chart plotter things are different, then what you say applies.
That's the question I am asking how is Homeport different in the way it treats a track and a route. Why chose to plan using a track vs a route
On the contrary. I had Homeport open and was checking what I was posting
as I did it.
It's not only
"planning software". In addition to route
(not track) planning, I use it both as a trip archive and as a post-race analysis tool after importing tracks
from a GPS
The simple anwer to "why chose to plan using a track vs a route" is: Don't! Routes are designed for planning. Tracks are not.
The fact that HP lets
you create a track manually by clicking on points and also edit tracks doesn't alter anything I said. (That's why I started off with the word "generally"). Such a track has limited use as a planning tool. Unlike a route, you can't put in the other variables required for planning such as speed, fuel
FWIW, I regularly import
tracks from my handheld Garmin into HP and use HP for route planning - exporting the routes to the handheld once I have them fully planned.
Creating a track for planning purposes in HP is like using a hammer to insert a screw. You can
do it, but it's not the right tool for the job and the end result will not be as good.