TopoFusion support forums
Archived - Use Search => Archived - Feedback and Comments => Topic started by: gpsdualsport on June 30, 2006, 07:29:40 AM
-
I've been using Topofusion for quite a while now and what to says tharnks to Scott M. and the rest of the team.
Props #1. The trail networking function is more robust now and generates less 'false intersections' than before. I don't understand how it works. In some sections it appears to be a true average of the tracks. In other sections it appears 'envelope' the tracks and take the shortest path around a turn. The end result are exactly what I need and I can live without understanding how it's coded.
Props #2. This year the the Southern California Ride for Kids dual sport charity event I was finally able to get my GPS data cleanly downloaded into the Magellan GPS units.
Magellan tracklog loading is always a major pain for me. All of my data collection and prep work is with Garmin hardware. Downloading this Garmin generated tracklog into Magellan GPS hardware has always been difficult in the past. The data on the Magellan has unusual additions between the track segments. The end results have been the tracklogs resemble a spider web on the Magellan displays. This year was the first time I could import the Garmin made GPX file into Topofusion then download this track into the Magellan Sportrak without errors. The track segements were not linked together.
I wanted to say Thanks for the continued improvements to Topofusion.
Sincerely,
Dan Yuknavage
AMA District 37 Dual Sport GPS geek, (the LA Barstow to Vegas district of the AMA)
-
Awesome Dan. Thanks for the props and positive feedback. It's always great to hear from people using the software, especially the network feature!
PS - We published the details of the network algorithm in an IEEE paper. It's all there! I admit that it's not easy to grasp what's going on though. That's part of what makes it an interseting problem for me. I hope to get some more time to improve it in the future.