My tracks for Central New York Chapter of the North Country Trail Association is going to be easy to merge and I have it high and low elevations anyways. So, I moved ahead and got the NCT GIS Repository tracks for Pennsylvania organized by chapter. Then I started working on the Allegheny National Forest. I went out on a limb and tried to merge it's 95 miles at once, but the GPX file came back with errors.
I always work in the westbound direction, so I started numbering it's tracks 00 - 54 at that point. I had changed GPSVisualizer's settings so that it would convert to GPX and not merge. This time, the reordered tracks showed the correct mileage on the output. But when I went to merge, there were still errors.
Like I mentioned, it's on a limb. The proper proceedure at that point is to determine what direction the tracks are heading in and edit their names with Eb or Wb. Once I get done with that, I'll choose whether its easier to merge eastbound or westbound, put one in a folder and save to the hard drive. The use GPSVisualizer's "reverse tracks" feature for GPX output to get them all facing the same direction.
Afterwards, I'll import them to Google Earth and replace the tracks that are in the wrong direction, save that file and run the GPX conversion set to "connect all segments" and "merge tracks." Usually that does it. But if it still gets errors, I'll need to go back over the raw track segments again to confirm that they're in the correct direction.
If they aren't, then I'll have to reverse the affected segment and repeat the process. But if they're right, then that means that there is a bad track somewhere. The fix to this is to overtake and trace the track by hand, extending the terminators of one of it's neighbors... then delete the bad track. Once that's done, go back through the GPSVisualizer GPX merging process.
No comments:
Post a Comment