Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


 

Messages - sherlok11

Pages: [1]
1
Routes / Transam in Montana: best route...
« on: January 20, 2012, 12:01:30 pm »
On the crossing on US 12 with US 93 (N46 45.407 W114 04.942) there are two possibilities: going North on 12 to Missoula, MT or south on 93...
Connection is on Twin Bridge on SR 287/SR 41
http://www.easpices.com/vanilla-beans

What you think is the best choice?

2
This is a step-by-step guide to using the new Streets and Trips 2005 program with the Adventure Cycling GPS data.  It may be included as an addendum to the GPS User Guide one day, but for now, here it is in one long post.  I'd be happy to answer any questions this may provoke.  (And by the way, I don't work for ACA or MS [shudder].  I'm just a member planning a trip.  Since I had to work this out for myself, I thought I'd share it in case anyone else was heading down the same road.)
http://www.easpices.com/cocoa-beans

This procedure uses Microsoft Streets & Trips 2005 with the Adventure Cycling Association waypoint data.  While there may seem to be many steps, it really isn’t too complicated.  Once you get it going, this makes it a breeze to plan your route right on an interactive map, customizing your ride with any points of interest or stopovers you desire, while also retaining all the original ACA points of interest.

Streets & Trips 2005 in Windows 98SE (Should work for XP, too)
This information pertains to the 2005 edition of Microsoft’s Streets & Trips (S&T) mapping software.  Older versions may fail at some stage of this process, but I haven’t tested them.  The other software used in this method are the freely available EasyGPS (http://www.easygps.com/) for working with the ACA waypoint data and transferring them to/from the GPS unit, g7towin (http://www.gpsinformation.org/ronh/) for converting the data into a format S&T can read, and st2gpx (http://gpsbabel.sourceforge.net/st2gpx/st2gpx.html) for converting Streets & Trips files back into EasyGPS format.

Building Routes
This is a suggested procedure for selecting the waypoints and building a route for a day’s ride.  You may wish to use it as a starting point for developing your own methods.

1.  Create a file of all the waypoints along the part you’ll ride:  It’s easiest to make this file cover about one map section.  In EasyGPS, open the waypoint files (File > Open) of the map sections you need, for example, NT04v001.gpx.  If your ride spans map sections, however, some copy-and pasting is necessary.  Open a new file (File > New).  Referring to your paper maps and the Comments in the waypoint descriptions, copy waypoints from the master files—their names appear on tabs at the bottom of the window—to the new file.  Delete the routes that exist in the file already; we’ll make our own, and these will just get in the way later.  Save the new file (File > Save > Save as type: GPS Exchange File) with a useful name, like “waypoints for section 1.gpx”.  Continue to copy from the master files and paste into your new file until your area is covered.

2.  Convert the new waypoints file to a “comma-separated values” (.csv) file:  Run g7towin and open the new waypoint file you made in Step 1 (File > Open).  View the waypoints (Waypoints > View).  Save the list as a comma-separated values file (File > Save As).  Give it an appropriate name and save it as type “Comma Separated Values File (*.csv)”.  You may move onto Step 3 now, but one more tweak will make the importing easier later.  Open the new .csv file in a text editor.  (Right-click on the file, select Open With, and select Notepad or Wordpad from the list.  You may uncheck the box next to “Always use this program to open this file” if you wish.)  Delete the first lines that tell g7towin what kind of file it is, so that the new first line begins “Type”,”Name”,“Lat”, etc.  Save the file and exit the text editor.

3.  Import the waypoints into S&T:  Run S&T and click on Import Data Wizard (in the Data menu or from the button near the top of the screen).  Select files of type “Text Files” and select your new .csv file of waypoints.  The Import Data Wizard will begin.  On the first screen, select Comma as the separator character, then click Next.  If you performed the tweak of the file at the end of Step 2, S&T will see that the first line contains the column headings.  It knows how to read the name, latitude, and longitude of each waypoint.  I recommend changing the Name column to Name 2 and marking the Comment column as Name in the Data Type dropdown.  This way, the description of the waypoint will show when you click Show Name later.  Click Finish, and enjoy the neat graphics as the waypoint data are converted into S&T pushpins.  Move on to Step 3.

If you did not tweak the .csv file at the end of Step 2, you will have to tell S&T how to read the data.  Find the column that contains the Latitude and select Latitude from the Data Type dropdown.  Indicate the column for Longitude in the same manner.  For the name, I like to set the Comment (e.g. “Circle Dr/Main Av”) as Name and the Name (e.g. H07070) as Name 2.  Click Finish, and enjoy the neat graphics as the waypoint data are converted into S&T pushpins.

3.  Save a map template:  This step is optional, but to do it now will save the time of converting the same set of waypoints each time you want to use them to make a route.  Adjust the map view to your liking.  (E.g. font size or map style)  You may also want to change the look of the pushpins.  In the Legend and Overview pane, double-click the new pushpin set.  Here you may choose a different look for the waypoints.  (They are now pushpins in S&T.  I will refer to them as waypoints or pushpins interchangeably when dealing with them in S&T.)  You can also indicate which fields you want displayed when you double-click on one on the map.  When the map looks the way you like, save it as a template.  (File > Save As, choose Map Template as the type, then name it and save it with your other data for the current map section.)  You now have a map to use as a base for the routes of this section.

4.  Make a route:  If you saved a template in Step 3, open it up.  Otherwise, use the map with the imported data from Step 2.  Make a driving route in S&T by marking the points along the desired route.  Start by right-clicking the pushpin for the day’s start, probably a hotel or campsite, and choosing Route > Add as Start.  You have begun, and it’s only Step 4!  Select the next waypoint on your journey and add it as a Stop, making sure it gets numbered with the next number.  (Sometimes S&T will attempt to help you design a route by changing the order of the waypoints you enter, based on proximity to the previous one.  If it puts one out of order, you can correct it in the Route Planner panel by selecting the stop and clicking the Move Up or Move Down button.)  Continue to select waypoints along your route, which you’ll most likely choose by following the ACA map narrative.  All turns, significant road bends, and other points of interest will be already be on the map waiting for you to include them as part of the route if you want.  You can also view selected Points of Interest included with S&T by choosing View > Show or Hide Places.  You can add these to your route in the same way as you add the pushpins.

When the day’s route is complete, you can let S&T complete its route-making by telling it to Get Directions (Route > Get Directions), but this is not necessary.  (A word on distance is in order here.  When S&T makes a route by connecting many waypoints, it will begin to overestimate the distance traveled.  If the route contains a section that S&T thinks is impassable by car, it may take a long way around.  If a waypoint is recognized as being on the wrong side of a divided highway or just off the road, there will be a diversion in the route.  And so on.  All of these discrepancies add up to driving distances that may be far off the actual biking distance.  Know that now.  If you want to get a better estimate of riding distance, use the info from the ACA maps and supplement it with any intentional diversions you plan.  You can also use the convenient Measure Distance Tool in S&T.  If you want, you can even try opening another instance of S&T and attempting to force it to replicate the chosen route.  You should use the Avoid Area feature and try to use as few points as possible at all the right intersections to make it describe the right route.  The distance it shows then may be fairly accurate.)  The route described by S&T will not be saved or wind up in your GPS.  What will make it to the unit is the data for every Stop along the route (as waypoints), the order of the waypoints (as route legs), and the pushpins (as waypoints).  So any point you add to your route as a Stop, be it a pushpin, part of the ACA route, an address, or simply a bend in the road will become a waypoint in your GPS later.  Here’s how.

5.  Save your route as a S&T map file:  File > Save As.  Choose type Streets & Trips (not Map Template), name it uniquely, and save it with the data for the current map section.  The new file will end with the extension .est.

6.  Convert the map to .gpx format for use with EasyGPS:  This is where the beauty of st2gpx shines through.  This simple utility will read the information contained in the saved .est file and convert it to a .gpx file, which can be opened by EasyGPS.  Users should familiarize themselves with the usage of this program before continuing.  The instructions and FAQ should get you up and running.  Although the latest version (05, as of this document) will claim to have some difficulty in the conversion process and will also produce a null file, it works just fine.  (You can delete the null file that will be left over after a conversion.)  Once you have created the new .gpx file from your .est file, place them both with the other files for the current map section.  Rename the files as you wish.  I like to call the .est and .gpx files by the same names, using the riding day number and the endpoints.  (E.g. “17 Bogalusa to Easleyville.est” and “17 Bogalusa to Easleyville.gpx”)  Open the new .gpx file in EasyGPS.  It will contain the day’s route and all the waypoints for the section, as well as any new waypoints created for this route in S&T.  For the sake of convenience later, I like to delete all the points in the top pane now.  (The saved route will contain the waypoint data for all of its stops, and we’ll add the complete set of ACA waypoints back in later, so it’s safe to delete the listed waypoints now.)  (Right-click on one of the waypoints, press Control and A to select them all, then press the Delete key.)  Also, I like to edit the route info to make it easier to sort them later.  To do so, right-click on the route name in the bottom pane, and choose Edit Route.  I name the route with the riding day number, and then describe the start and end towns in the Description box.  Save the file with the changes.  (It’s time for another note on distance.  The distance given by EasyGPS will not be an accurate riding distance, either.  It will be the distance between the waypoints as they would be connected by straight lines, so necessarily shorter than the riding distance.)

7.  Continue to create routes for each day by repeating Steps 4 through 6.

8.  Send the data to your GPS:  You have a few options here.  You can upload each route individually using EasyGPS, and then separately upload the waypoints-only file you created way back in Step 1.  If you’d like to create a single .gpx file that contains every route in the section along with all the waypoints, just upload all the appropriate routes and the waypoints as just described above, then open a new EasyGPS file and receive the routes and waypoints back into the new file.  Save it, wrap it in foil, label it, and put it in the freezer until you’re ready to ride.

Thanks to James Sherring for helping with st2gpx and Ron Henderson for helping with g7towin.  Their tiny utilities make all of this possible.

ACA member Seth Copans wrote this document in September 2004.  He is solely responsible for its content.

Pages: [1]