You can also have routes in here, they're formatted kind of as a hybrid between tracks and waypoints. They're similar to tracks in that you have a high-level RTE called out with a name and the route is top-to-bottom in the array. They're similar to waypoints in that each point has a lat/long, name, comment, symbol, elevation, etc. Code: ≤rte≥ ≤name≥Example Route≤/name≥ ≤rtept lat="40.389079995" lon="-106.635330060"≥ ≤name≥Beginning≤/name≥ ≤cmt≥First Route Point (1/3)≤/cmt≥ ≤sym≥Flag, Blue≤/sym≥ ≤/rtept≥ ≤rtept lat="40.387669334" lon="-106.618745322"≥ ≤name≥Middle≤/name≥ ≤cmt≥Second Route Point (2/3)≤/cmt≥ ≤sym≥Flag, Blue≤/sym≥ ≤/rtept≥ ≤rtept lat="40.55697978" lon="-106.5962596"≥ ≤name≥End≤/name≥ ≤cmt≥Last route point (3/3)≤/cmt≥ ≤sym≥Flag, Blue≤/sym≥ ≤/rtept≥ ≤rte≥ You can copy/paste values, chunks of data, or even find/replace text to convert a list of waypoints to a route and vice versa as long as you keep the appropriate formatting. Again, you're really just editing a text file. I like GPSBabel (available for Mac/Win/*nix) for validating GPX files - Where LoadMyTracks and Google Earth either puke errors or simply don't load the file, GPSBabel tells you what line number the problem's at. Usually you're missing an open/close tag there. That answer your question?