Thank you very much for your effort in fixing up the trail data.
I was trying to unit eht 4200 sections into 33 (for 320k coords), and I ran into several problems myself. The biggest one was that the original kml didn't have the sections in right order, so I had to put them all in a set, and each time just pick up the next closest section to the one I am "holding" in order to concatenate the coords into one long list.
But then I realized the actual data was wrong, and not in the way you found out - there are some bits on the trail where the coords create a loop. It is probably just a glitch in the data, but I was wondering if it came this way from the ESRI files, or maybe something went wrong along the way.
Well, as I said, I didn't even know the data was a bit to the west, so thanks again for making it all that much more accurate. But you can see this loop problem at your section 37 (For example), about 0.08 miles east of Pierce Pond Lean-to. Just wondered if you have an idea as to why it happens (and it happens in several other places as well), and how to fix it.

I'd also love to hear how you managed to transfer the data into your sections.

Noam.