BackpackGearTest
Google
Web BackpackGearTest.org
  Home Guest - Not logged in 
 
 » Register
 » Login
Gear Reviews
Documents
Tools
 » Contact

Reviews > Navigation and Map Gear > GPS > Magellan SporTrak Topo 2003 > Andy Mytys > Field Report

Magellan SporTrak Topo GPS

Field Report

Reviewed By:Andrew Mytys
Email:amytys@gmail.com
Date Published:July 14, 2004
Update History:None


Product Information:
Manufacturer:Thales Navigation
Item:Magellan SporTrak Topo GPS (http://www.magellangps.com)
Item Number:980616-39
Product Number (physical unit):800480-10
Year of Manufacture:2004
MSRP:$399.99
Listed Weight:6.1 oz (173 g)
Weight as Delivered:6.3 oz (179 g), including:
  . SporTrak Topo GPS, 4.5 oz (128 g)
  . 2 AA Energizer Batteries, 1.7 oz (48 g)
  . Wrist Strap, 0.1 oz (3 g)
Size:5.6 x 2.2 x 1.15 in (14.2 x 5.6 x 2.9 cm) [h] x [w] x [d]
Display:2.2 x 1.33 in (5.59 x 3.88 cm) [h] x [w]
Display Resolution:160 x 104 pixels
Power Source:2 AA Batteries (included)
Availability:North America
Warranty:One year from original purchase date, extended to original purchaser
only. Repaired or replaced products are warranted for 90 days from
the date of return shipment, or for the balance of the original warranty,
whichever is longer.
Warranty Extension:Within 90 days of purchase, customers can extend the base warranty to three years for a cost of $39.95.

The information in this Field Report of the Magellan SporTrak Topo GPS is to be taken in addition to my Initial Report, where I summarized the basic functions inherent to the SporTrak Topo GPS.



Product Description:

A handheld, 12 channel WAAS/EGNOS enabled recreational GPS unit that provides location accuracy to within three meters (10 ft). The SporTrak Topo comes pre-installed with a complete set of topographical data for the United States, including the lower 48 states, Hawaii, and 80% of Alaska. This data includes details such as topographic contouring and elevation, highways, major roads, waterways, and coastlines. There are eight customizable navigation screens that can be used to represent output in a variety of ways, allowing the SporTrak to meet the demands of many different applications. The SporTrak also comes with MapSend Topo software, giving PC users the ability to exchange track and waypoint data between their computer (Win95, 98, XP, NT only) and the GPS via a serial-based interface cable (also included). Additionally, the MapSend software contains a greater level of map detail for the United States. The SporTrak accepts up to 20 MB of regional data for upload, providing the consumer an even finer level of navigational feedback.


Testing Approach and Field Conditions:

In general, my approach to testing can be defined as the desire to objectively evaluate the Magellan SporTrak Topo GPS in terms of its usefulness as a tool for navigation. I have evaluated the bulk of its built-in features, as well as its ability to interface with external tools such as the MapSend Topo software included with the SporTrak. I also gained some experience with interfacing the SporTrak with other mapping software titles such as DeLORME's Topo USA and National Geographic's (hereafter referred to as NG) state series of PC-based USGS topographic maps. I have used the GPS in the field as a stand-alone tool in navigation, as well as an enhancement to traditional map-and-compass orienteering.

My field-testing thus far has centered on two basic types of terrain - developed city infrastructures and backcountry travel, both on and off the trail. In terms of topography, I've been able to test the GPS in areas where the unit had both low and high degrees of relief, and have compared the accuracy of the GPS' results with those of paper-based maps, in addition to what I've been able to visually observe.

The questions that my evaluation of the SporTrak Topo addresses are as follows:

  • Can the SporTrak reliably determine my current position?
  • Can the SporTrak lead me to where I want to go?
  • Do the SporTrak's built-in topographic and street maps accurately represent reality?
  • Can the SporTrak help me to determine the most efficient and safest route to travel in?
  • Does the SporTrak present its data in a manner that's meaningful to me?
  • Does the SporTrak provide enough data to meet all my navigation needs?

In addition to these questions, I will be commenting on my experience in terms of general GPS performance, as it pertains to the SporTrak Topo's many features. Where does the unit shine, and where can improvements be made? How useful are all the features of this GPS, and how easy is it to gain proficiency with the SporTrak?

Finally, there's lessons learned. Based on the results of my testing, what's the best way to utilize the SporTrak, and in what cases may additional resources be necessary?


Can the SporTrak reliably determine my current position?

Sort of. The SporTrak will give the coordinates of your current position, as reported by a bunch of fancy satellites orbiting overhead. If you were to give those coordinates to another individual who also had a GPS, or a GPS compatible map and compass, they would be able to find your position to within about fifty feet, depending on the strength of their GPS signal and/or their map reading abilities.

Manistee River/NCT loop maps

However, as you can see in the image to above, the positions that the SporTrak's built-in maps display the the GPS' position to be in isn't always accurate. This is, in most cases, due to the fact that the coordinate system used to create the maps varies from the coordinate system used to communicate with the satellites. The result is a skewed position. For example, in the image at the far left depicting the SporTrak's LCD panel, which was taken during a recent hike, it is reported that at one point in time the GPS was in the middle of a lake. Rest assured that this wasn't the case.

SporTrak startup dance Upon arriving home from my hike, I synched the GPS with NG's Topo! program for Michigan, and the MapSend program that came with the SporTrak. The panel in the center, left position displays the NG program's result, and the panel at center, right displays the result from the MapSend program. Both of these images show a similar route, although the level of detail with respect to topography is far greater in the NG example.

The curious detail to note is that the location of the track on the LCD panel and MapSend program are different. This is because the MapSend based maps, while similar to those pre-loaded in the SporTrak, are not the same. Once I used the MapSend program to upload the region I hiked into the SporTrak, the LCD's map suddenly matched what I saw on my PC (see image at far right). Note how the lake suddenly takes a natural shape, rather than looking like a crashed B-2 Spirit Stealth Bomber.

The SporTrak seems to have issues with settling on its current position within a narrow margin of error across sequential power-up's. This is not a new phenomenon to GPS technology, but the SporTrak's variance in position between one power-up and the next can deviate by a lot. The image to the left depicts a track, made by standing in one position and just turning the SporTrak on and off, then on and off again. This was repeated a few times. Each time I stood in the exact same place. According to the scale, my position throughout this exercise is moving by as much as 150 feet (45 m).

Of course, the GPS first has to catch a signal before it can report on any position. I find that my unit is slow in finding and capturing its initial satellite feed, and even slower in collecting the data from these satellites once a signal is captured. I've come to this conclusion by monitoring the GPS Status messages in the Position Screen. I feel that this may be an issue with my individual unit, and not with the SporTrak line in general. I've hiked side by side with a fellow BGT tester who's evaluating the color version of the SporTrak, known to contain the same antenna technology as the SporTrak Topo, and his GPS is ready to navigate within a few seconds. My unit likes to take MINUTES, even after its initialization process has been repeated. It's slow to the point of being embarrassing. After standing around a clearing for five minutes and still not locking onto the requisite number of satellites, I just give up and start hiking. Eventually, the SporTrak gains a signal during my hike.

Sometimes the SporTrak likes to pull my leg, with the Satellite Screen reporting that a full strength signal has been acquired from five or more satellites. Still, it does not toggle to the Map Screen and display my position. In addition, it fails to display any satellites "in view" across the sky and horizon. This is curious, as the SporTrak should only have to capture three signals in order to be able to compute my location and four or more satellite signals to report in "3D" mode (in addition to location, elevation is also computed).


Can the SporTrak lead me to where I want to go?

A map of Andy's neighborhood

The answer to this question is a mixed bag. My experience is that, as with the current position example from above, if someone were to give me the GPS coordinates of my destination, using a GPS of their own to determine said coordinates, I'd have a pretty good chance of getting exactly where I wanted to go. However, if I were to use coordinates derived by using the MapSend software to perform an "Address Lookup", or I were to simply find the location using either the SporTrak's built-in maps or the maps supplied with the MapSend software, I could have difficulties navigating to the desired position. In the example to the right, my "Home" point is located on the map in the middle of Fairfax Dr. However, my position on the detailed map I uploaded to the SporTrak shows my as being on Fonville Dr, an easy 150-feet (45 m) to the south. All of this is caused by a disconnect between the coordinate system used in creating the map and the coordinates that the GPS is using for current location and tracking purposes. This is not a big issue in the city, especially when the GPS includes a map showing all surrounding streets relative to the current position. However, such a deviation in the backcountry could result in a swamp, steep cliff, or some other natural obstacle being located between the GPS and the desired destination. Clearly, there are issues with relying purely on the SporTrak system for navigation.

Take a look at the image on the right. The red line represents a route plotted directly on the built-in maps provided with the SporTrak. The yellow line represents the GPS track - the route I actually walked - along the physical streets in the neighborhood that corresponded to the planned red route. The SporTrak was set up to capture a track at the greatest level of detail possible. The green line represents a GPS route that I plugged into my SporTrak using the NG software. Finally, the blue line represents a shortcut, which I'll come back to when discussing routes, below.

The small map offset in the corner is an actual satellite shot of my neighborhood, courtesy of the U.S. Geological Survey. I have taken the liberty of tracing the route that I walked in red. Note that neither the SporTrak/MapSend based route, the NG based route, nor the track that the GPS captured while I walked look identical in shape to what's actually on the ground. The fact that the GPS incorrectly logged a simple 90-degree turn (Fonville Dr to Carl St) troubles me. This may be another indication that there is something wrong with my test unit, yet the degree to which the overall track corresponds with the general layout of the neighborhood has me thinking the GPS is tracking as best as it can. Of all the tracks, the NG (green) route comes closest to my track. In fact, had I not limited the green route to 20 waypoints "evenly distributed" along the course of the route, the NG map would be mimic the shape I traced in the satellite image perfectly. Also, if I were to open the NG software and upload my plot of the route, it would line up with the streets correctly - the NG streets are in a completely different location than those in the maps provided by Magellan, and I find them to be a more accurate representation of reality. Why is this the case? Because NG uses USGS maps as their source. The downside of this is that the maps are updated less frequently, so, for example, the neighborhood just to the north of mine is still a cornfield. The SpotTrak/MapSend data might not be as accurate at the NG maps, but in terms of man made objects it is more up to date.

Another topic I'd like to touch on is that of routes. In the figure above, you'll note that the green line has a series of waypoints along it. I instructed the NG mapping program to produce 20 evenly-spaced waypoints over the course of the route. I then activated that route, and had the SporTrak navigate me along its course. When I arrived at "TR6", I continued walking straight, along the blue line, taking a shortcut. Routes in the GPS are set up in such a way that the user has to come within a certain distance of the current waypoint in the sequence in order to have the GPS advance navigation to the next waypoint. By taking the shortcut, the GPS continued to attempt to navigate me towards waypoint "TR7", even though I was making advanced progress towards the final waypoint in the route - it did not simply skip forward and navigate me towards "TR15." I find this to be acceptable as long as I pay attention and monitor my progress (though I do wish there was an option for shortcut recognition), as the SporTrak allows me to manually set the current "leg" of the route being navigated. Where this becomes a true issue is when a route plotted using the MapSend software is far off of its mark. In the image below, waypoint "3" is located near the lower-right corner of the route. As you can see by my yellow track, I walked in reverse through points "2", "1", and "Home," bypassing points "3", "4", and "5" in the process. Actually, I walked the route in the correct direction and along it's path, but due to the differences in map and GPS coordinates the GPS didn't know this. As I moved further along the route, the GPS kept trying to navigate me to waypoint "3". If I were in the woods, in an area where the SporTrak provided little topographic information, I might think that I somehow got off track and go through all sorts of obstacles to get back "on track," when all along I could just be moving in a direction that eventually forces me to backtrack.

You'll also notice that the ends of the track line do not meet. This is entirely due to GPS position error - I actually ended in the same position where I started.

Another walk in Andy's neighborhood

The lesson here is that the GPS' ability to navigate the user is only as good as the source of the coordinates. If that source happens to maps made using an alternate coordinate system than what the GPS is using, or if a weak satellite signal is being relied upon, there may be some issues encountered in locating the final destination. The MapSend PC-based maps, as well as the SporTrak internal maps, should not be relied on when navigation is of utmost importance.


Do the SporTrak's built-in topographic and street maps accurately represent reality?

Maps depicting the Appalachian Trail in PA, along segment 12 just east of Pine Grove Furnace State Park

Once again, this depends entirely on how good the source maps are for the area the GPS is reporting on. In some cases, particularly those instances where there is a large amount of topographic relief, the results are excellent. Take for example the two images shown above. The cutouts depict the Appalachian Trail, PA section 12, near the side trail to Pole Steeple. The map on the left shows the detail available on the SporTrak (I've chosen to use the MapSend software as my source for the sake of appearances). The map on the right is a close-up of the official Appalachian Trail map for this section, compiled and published by the Potomac Appalachian Trail Club, or PATC (colors enhanced for the purposes of this report). While it's difficult to make out here, the SporTrak map does have labeled contour lines for 750, 1000, and 1250 feet. These maps are US based, so elevation information is limited to feet. From Pine Grove Road, located near the top of each map, there is approximately 700 feet (213 m) of relief depicted here. Contour lines and other details, while not as accurate as those on the PATC map, are acceptable and fall in line with the general terrain features - certainly good enough for me to use for navigation purposes. Also, note the depiction of the AT itself. On the SporTrak-based map, the yellow line represents my GPS track, the actual route that I walked. On the PATC map, the AT route is supplied by the PATC. While there are slight differences, I find the results given by the GPS to be acceptable.

Pinckney Rec Area detail, using Magellan's MapSend software Pinckney Rec Area detail, using DeLORME's Topo USA software

When the GPS finds itself in areas of limited relief, however, the story changes. To illustrate my point, I've included three maps depicting the terrain found in Michigan's Pinckney State Recreation Area. The map above (right) represents the detail available on the SporTrak using the MapSend software as a source. The map to the left is this same area, created using DeLORME's Topo USA program. Unlike the detail given along the Appalachian Trail, these maps have only a few contour lines depicting the lay of the land.

Pinckney Rec Area detail, using National Geographic's Topo! software When one looks at a USGS map of the same area, however, it is clear that there is a lot more subtleties in topography present than the SporTrak's built-in map would lead one to believe. Furthermore, this topography, due to its "rolling" characteristics, cannot be dismissed when it comes to making navigational choices. The SporTrak map makes the terrain look like one big mesa - once at the top, the land is flat. The USGS map, supplied by the NG Topo! program, tells the whole story and allows the hiker to make intelligent choices in terms of route planning. This is extremely important, as the thick vegetation and rolling nature of the landscape does not allow one to view the terrain for more than a few feet in any given direction. The location of every ridge counts, especially as the area in question is a bit swampy. Without appropriate levels of detail, the "best" route is masked, and getting from point-a to point-b becomes an exercise in trial and error, having to backtrack one's steps every time the route suddenly finds itself leading into impassable terrain. Of course, fitting this level of detail for the entire country in the SporTrak's current memory would not be possible. It would be nice, however, if Magellan could treat this issue like it does that of roads - provide a "base" amount of data in the SporTrak's memory, then allow users to upload additional level of detail for any given area of interest.

It all comes down to accuracy and detail, and the race to deliver it to the consumer in a hand-held, flexible, and friendly format. I think that, for readers hiking in mountainous regions of the US, the SporTrak excels. For use in backcountry navigation in the mid-western US and areas of similar topography, a paper map may still be necessary.


Can the SporTrak help me to determine the most efficient and safest route to travel in?

The answer to this question goes hand in hand with the question of the SporTrak's ability to accurately depict reality. Were I traveling off-trail in regions such as in my Pickney State Recreation Area example, there's no way I would allow myself to rely solely on the SporTrak's maps. My experience shows that, due to the lack of detail shown in the SporTrak's topo maps, intelligent choices in terms of "which way is best" cannot be determined. The SporTrak does allow me the luxury of being a little sloppy with my paper map, not really having to pay attention to where I am. Having the SporTrak at hand allows me the ability to turn it on, receive a signal, and be shown my current location in proximity to a set of physical features common to both the SporTrak's built-in maps and a "real" map. Once I've established my location to some degree of accuracy, I can then narrow down my exact position by looking at the landscape around me and comparing it to what's depicted on the paper USGS topographical map. I can then plan my route, again using the USGS map, and continue to use the GPS as a crutch should my navigational abilities fail me.


Does the SporTrak present its data in a manner that's meaningful to me?

On some of its screens, the SporTrak does a fine job in conveying meaningful and accurate information. On other screens, I find the information to be of less use. The same can be said for the various types of data that can be customized across the SporTrak's screens. All told, the SporTrak Topo boasts eight different navigation screens, most of which contain customizable data fields that can hold any of 17 different types of data. Screens that are infrequently used can be turned off so that the process of switching from one navigation screen to another is more efficient. Indeed, I found little use for a few of the screens, either due to the data content or duplicity of function, and turned them off.

First, I'd like to whittle down the SporTrak's functionality, as I view it, by eliminating the screens that I find less than useful.

  • Data Screen: This screen displays six customizable data fields on the screen. In addition, there is a graphical "strip" compass displaying 50° to either side of the user's current heading.

    I've disabled this screen. There really aren't six available types of data that I'm interested in seeing at the same time, and the "strip" compass provides a sliver of the information found on the Compass Screen. In addition, I'm more accustomed to working with a full, 360-degree compass housing, which is graphically depicted on the Compass Screen.

  • Large Data Screen: This screen simply displays the contents of four customizable data fields. Without any other information, more screen space and larger fonts can be used in displaying data than on other user screens.

    This screen doesn't really offer anything new that's not available on other screens, and I have turned it off as well. With its large fonts, I could see using this screen with the GPS mounted in a prominent position where a driver or captain could quickly reference it for feedback on speed, bearing, CTS, XTE, etc. As a hiker though, I'd rather not flip to another screen to see information that could be displayed on the screen I'm already on, and I certainly can't see myself hiking with this screen being my primary choice - not enough bang for the buck, so to speak.

  • Speedometer Screen: This screen displays a graphic of a speedometer, similar in style to what's found in a car. The scale dynamically changes based on the speed of travel, so while walking the high-end of the scale may be 6 MPH (10 KPH), while when driving down the expressway it may be 100 MPH (160 KPH). There is an odometer that can be set on the screen as well, in addition to four customizable data fields.

    I've also elected to turn this screen off. It offers four customizable data fields, like other screens do. I find that the speedometer is only accurate when traveling at speeds higher than a walking pace (my car's speedometer works fine, thank you), and the odometer that falls short in its calculation of distance traveled.

  • Road Screen: This screen represents the user's route as if they were traveling on a road. Waypoint and destination icons, in addition to those for the sun and moon, are displayed relative to the current position as they come into view. Above the road there is a graphical compass displaying 20° to either side of the user's current heading, in addition to four customizable data fields.

    The idea behind the Road Screen is to deliver a graphical depiction of the selected route in the form of a road, allowing the user to look at the screen while moving, following the road to the destination. When turns are needed, the road will curve to the left or right. Should the user get off course, arrow icons are presented indicating what direction needs to be moved in to get back on the "road." There are a number of ways to create the "road" - it can be a straight line, leading from a given position to a destination, or based on a route. The source data for the route could be a set of manually input waypoints, a route marked on a map and uploaded to the SporTrak using software such as MapSend, or a backtrack, using tracks of previous travels held in the SporTrak's memory. The problem with using MapSend to create routes is that many of the maps do not directly overlay the physical locations that they represent. As shown in the neighborhood walk example, above, the yellow track (actual route walked and traced by the GPS) never really followed the road coordinates built into the SporTrak system (the red track). Following the road would mean walking off course. In a suburban neighborhood context, this might mean being a street or two off, or walking on private property. In the backcountry, following the road might take one over a cliff, or through a lake. If the Magellan supplied map data was used as a basis for creating a route of manually entered waypoints, similar issues would occur. The only type of route that the road would accurately represent would be one who's source was a track created in the field with the GPS, such as a backtrack or saved route using waypoints taken in the field on a previous hike. Likewise, one could get waypoints from an external source such as a friend, or magazine. The caveat is the waypoints really should be taken in the field. I've basically found that I can't sit down, fire up MapSend, waypoint a bunch of intersections or landmarks, upload those waypoints as a "route," and expect the Road Screen to lead me in the down an acceptable path. I can, however, drive out to someone's house with the GPS on and use the Road Screen to follow my backtrack, being shown every turn necessary to return to my staring point.

    Assuming I have waypoints that will work with the Road Screen, there's another issue. The Road Screen is built to be used on a route created with considerable distances between direction changes, such as when driving in a car. Due to its resolution, I find the road screen extremely difficult to follow if used to "Backtrack" a route I have walked, or when maneuvering in a car in small areas, such as when driving in an office complex where turns are in close proximity to one another. For driving on the highway, however, it excels... but once again only when used on a course plotted using satellite signals and a GPS. I find that plotting a course using the MapSend maps is of little use.

The remaining screens contain the meat of the SporTrak, and my evaluation of them is as follows:

  • Satellite Screen: This screen graphically displays which satellites are in view, their location relative to the user's position, and which satellites are being used to compute the current position. The relative strength of each signal being received from any given satellite is also displayed. There is also a graphic on this screen that gives the user an idea of how much power is left in the installed batteries.

    I find this screen useful. It lets me know what's occurring during the satellite acquisition phase. I can see what satellites are being tracked across the sky and horizon, the strength of signals being received, etc. If I lack strong signal reception, I know that I may need to find an area that's more open than the one I'm currently in. The experience can be like watching a pot boil, however, and can be especially frustrating when three or more satellites are shows as having had their signals captured at full strength, yet the GPS is still not ready to navigate (See Position Screen for more details). Truth be known, this screen could also be eliminated if I wasn't such a satellite voyeur. The Position Screen could supply similar information, but without the nice graphical representation.

  • Position Screen: The position screen shows the current position using whatever geeky coordinate notation the user has configured the GPS to calculate in (e.g. 42° 26.876N 083° 12.456W). The current elevation, if available, is also displayed, as is the time of day. There is an odometer that can be set on the screen as well, in addition to two customizable data screens. GPS status messages are also displayed. Lastly, this screen allows the user to project a waypoint from the current position by a fixed distance and bearing.

    This screen gives me a more detailed picture of what the GPS' current status is. It displays the current position and elevation, if known, as well as the time of day. It also gives me a textual description of the GPS' communication with the satellites overhead, be it in the process of acquisition, calculating the margin of error for a given satellite, resolving the current EPE, etc. Having two customizable data fields in addition to all the other information that's given is just icing on the cake. Note that the screen's odometer falls far short of actual distance traveled. I'll get into accuracy of distance, speed, and elevation a little later in this report.

  • Map Screen: This screen displays the user's current position and the direction in which they're heading. Topographic, street, and other information is also represented on the screen. In essence, a little map is shown. Using the arrow button, the map can be scrolled around in the window, giving the user an idea of what lies ahead. The cursor can be moved to any position within the covered area (48 states, + Hawaii and 80% of Alaska) for closer inspection, and a waypoint can also be created if desired. The map can be viewed in a variety of scales, showing anywhere from approximately 400 feet to 6500 miles of data across the screen (125 m to 10,500 km). There are also two customizable data fields on this screen.

    The map screen has two basic types of information - street and topographical. The street detail in the GPS' permanent memory includes only major roads. For example, the main roads making up the square mile around my neighborhood are present, but the streets within the grid these major streets make up are not. To get detailed street level information, a region or set of regions needs to be defined and selected for GPS upload using the MapSend software. Uploading takes time and eats battery power, so some thought should be given to upload requirements before the actual upload occurs. In addition, an upload will overwrite and erase any street detail that has been previously uploaded to the GPS. To be able to use both new and old street level regions, the superset of information needs to be defined and uploaded to the GPS. The SporTrak does have a large block of internal memory reserved for this purpose, however, and an entire state's worth of information can be sent to the SporTrak and still not fill its memory.

    I find that the detailed street level information is difficult to use until the GPS is within a quarter mile or so (~0.4 km) from the destination - at greater distances, the zoom range on the GPS screen needs to be pulled back to a level where the detailed street information simply isn't visible. For purposes of general navigation, the Compass Screen is the way to go!

    The Map Screen also contains topographic information, but as I have already shown its usefulness entirely depends on how much topographic detail is present for your location. In areas with a high degree of relief, the Map Screen is sufficient for navigation. In areas that one would consider flat or rolling, the maps may be of less use.


  • Compass Screen: This screen displays a compass and shows the direction in which the user is heading. There are also icons that display the position that the sun and moon are in, relative to the user. If a destination point has been identified, its location relative to the user will also be displayed. There are four customizable data fields on this screen.

    The Compass Screen is the "classic" GPS screen found on many GPS', from basic to advanced models. It displays a graphical compass that shows where north is relative to the direction of travel and, if a GOTO point is active, shows where that location is relative to the GPS' current position. Typically, I have one of the user-defined fields display the Distance to the target position. Between knowing what direction the destination is in and how far I am from it, I can make decisions such as what exit to get off of on a highway, how important it is that I turn towards the destination (unless I'm less than a mile from my destination, I'm only interested that I'm moving in the general direction), etc. Typically, if I'm using the GPS for navigating while driving, I just "wing it" until I get to within a quarter mile (0.4 km) to my destination, and then toggle over to the map screen and make more informed and detail-based decisions. While the SporTrak does boast a lot of snazzy features, I find that this single screen is the one I use most frequently.

    One of the nicest uses I found for the Compass Screen was when traveling in Europe. I turned the GPS on at my hotel, captured a signal, and created a waypoint. Then I turned the GPS off, put it in my pocket, and went wandering around, exploring a strange city. I didn't worry about dragging around a city map, keeping track of where I was. Narrow, cobble-stoned streets curved in all directions, and my curiosity had me running every which way. Eventually, it was time to start heading back to the hotel. I found myself a clear area, outside of the narrow canyon-like streets, and turned the SporTrak on. Once I had my position displayed, I simply instructed the GPS to "GOTO" the hotel. The compass screen showed me approximate distance and direction, and I went about wandering down whatever street seemed to lead me in the direction the Compass screen showed my hotel to be in. I never lost my signal, even when walking down narrow streets with multi-level homes to either side. The impromptu nature of my route had me moving down streets I had not yet explored, and any interesting points I saw along the way were way-pointed, so that I could return and explore further the next day. Lacking detailed street information, or any street information in this case (European streets are not covered in the US version of the SporTrak), was not an issue at all. In fact, it was probably a plus!

Data available for reporting in screen-based customizable fields:

  • Speed: The speed at which the GPS is moving across the ground.
  • Heading: The direction that the GPS is moving in, relative to north, expressed in degrees 1-360.
  • Elevation: Current elevation of the GPS above sea level
  • Time: The current time of day.
  • Date: The current date.
  • EPE (Estimated Position Error):This value represents the average margin of error in the reported position, given as a distance, based on the current satellites and signal strength being used to compute position. If the GPS reports that you are within 30-feet (9 m) of your destination, for example, and the EPE is 90-feet (27 m), than you can be standing at the actual destination, at a point 120-feet (36 m) away, or anywhere in between.
  • Avg. Speed: The average speed of movement given the distance traveled.
  • Max Speed: The maximum speed the GPS has traveled at since it was powered on and established a fix.

Data available for reporting in screen-based customizable fields, where values will only be displayed when a route or GOTO point is active on the GPS:

  • Bearing: The direction that's needed to travel from the current position to the selected destination, expressed in degrees 1-360.
  • Distance: The distance from the current position to the selected destination, measured in a straight line.
  • VMG (Velocity Made Good): The component of the velocity that is towards the destination.
  • CTS (Course to Steer): The direction you should be traveling in order to return to the course while proceeding towards the destination. It is a “compromise” course bearing that projects from the current position to a point on the courseline midway between a point perpendicular to the current position and the destination waypoint, expressed in degrees 1-360.
  • ETA (Estimated Time of Arrival: The estimated time of arrival at the selected destination. The ETA is based on the distance of a straight line between the GPS' current position and the destination, given the current speed.
  • ETE (Estimated Time Enroute): The time remaining before reaching the destination. As with ETA, the ETE is based on the distance of a straight line between the GPS' current position and the destination, given the current speed.
  • XTE (Cross Track Error): The perpendicular distance between the present position and the courseline, reported as being left or right of the courseline.
  • Turn: Indicates to the user what direction (left/right) and by how many degrees they need to turn in order to return to the course.
  • Total Dist: The Total Distance of the active route or, if a GOTO is active, the distance between the start point and the destination waypoint.

While walking, I find that the speed calculated by the SporTrak is grossly off. With each step I take, the needle can fluctuate anywhere from 1 to 4 mph (1.6 - 6.4 kph), even though my pace seems to be rather constant. In a car, the speedometer falls in line with the vehicle's speedometer. As I use the GPS primarily for walking, any speed related calculations are suspect and hence I pay little attention to them. This includes Speed, Average Speed, Max Speed, and Velocity Made Good.

Likewise, distance is off while walking with the GPS. For example, on one of my walks along a flat city surface, the GPS reported a distance traveled of 1.67 miles, or 2.69 km (odometer reading, cleared before staring walk). Once I uploaded my track to the PC, the distance of the track was reported as 1.85 miles (2.98 km) - one would have expected the odometer and track distances to coincide. The same route, with the course plotted using the MapSend software, has a projected distance of 2.02 miles (3.25 km), A measuring wheel used to measure the same route reported a distance of 2.18 miles (3.51 km). Deviations between the GPS' perception and reality increase as GPS use moves off of city streets and into the woods. For validation of my measuring wheel, I benchmarked it against a 100-meter surface. It proved to be accurate. I do not hold stock in values given for Total Distance as a result. The value for Distance, however, becomes more accurate as the GPS approaches its destination. I depend on this figure to let me know when I can switch to the Map Screen, and get acceptable street-level results using a detailed view.

Given that both speed and distance traveled have proven unreliable, figures such as ETA and ETE become suspect.

I also find reported elevation to be inaccurate. Once again, I look to my neighborhood walk. The GPS will report that my walk varied from 628 to 801 feet (191 - 244 m). When the course is plotted using the MapSend software, the elevation is projected to vary from 683 to 708 feet (208 - 216 m). Based on visual signals, such as being able to see objects a quarter mile away that appear more or less at the same level as similarly sized objects next to me, I estimate that the actual elevation variance is closer to the MapSend figure, but even less severe. By no means is there almost 200 feet (61 m) of elevation change across my test route. The elevation reported by the SporTrak closely matched topographic data found on my paper map while I was hiking along the AT. In areas where the overall variance in elevation was less than 100 feet (30 m), I had the least accurate results. While hiking in Michigan's Pinckney State Recreation Area, for example, it was not uncommon for the SporTrak to report elevation as increasing as I walked downhill, and decreasing as I moved uphill.

 Profile of my planned route, as projected by the MapSend software - 2.02 miles (3.25 km), with elevation
 ranging from 683 to 708 feet (208 - 216 m)
Profile of my planned route, as interpreted by the MapSend software
 Profile of the SporTrak's reflection of my actual track (walk), 1.85 miles (2.98 km), with elevation ranging
 from 628 to 801 feet (191 - 244 m)
Profile of my actual route, with elevation as reported by the GPS


Does the SporTrak provide enough data to meet all my navigation needs?

I think it's clear, based on the observations I've noted above, that the SporTrak Topo GPS cannot be relied on as the sole tool for successful orienteering and navigation decision making in the field. It is certainly a powerful tool, but there are still holes in GPS technology that could have a negative effect on my hike. I believe that these shortcomings are not so much in design, as much as in the fact that GPS technology in general, particularly on the receiving end, is still at an early stage of evolution.


Other Considerations:

  • Durability: To date, I have had no durability issues with the SporTrak Topo GPS. Having only been dropped once, it has had little physical abuse. I also have opted to protect the SporTrak by purchasing the optional belt-clip carrying case. I typically attach this case onto the webbing found on the outside of my pack's shoulder straps.

  • Ergonomic Design: The SporTrak fits comfortably in the hand, and its buttons are very easy to use without looking. I do find the process of swapping batteries to be a chore, as the battery compartment is held onto the SporTrak with a screw. On the plus side, this screw, along with the gasket surrounding the top of the battery housing, ensures a watertight fit. I certainly wouldn't want to compromise that in favor of a little convenience.

  • Screen Clarity: The screen's contents are always easy to make out, and I find that I never have to adjust existing contrast levels to compensate for the sun's glare. At night, the lowest backlight level has proven to suffice for all my needs, though there is a brighter level of backlighting available.

  • User Interface: I find the SporTrak's functions were very intuitive and hence easy to learn. I have had a few difficulties, but the source of these were centered around errors in the user manual that led me in the wrong direction. For example, the user manual states that to activate or deactivate a route, "Enter" should be depressed after the desired route has been selected. Actually, "Menu" needs to be pressed in order for the user to be shown further options for the route, amongst which is Activate/Deactivate. There have been a few instances where I've been a little confused on how to use a GPS function while out in the field, and I have attempted to resolve these questions using the SporTrak's built-in help screens. Unfortunately there is no topic listing or index set up for the help system. Basically, the help that's provided is nothing more than a compilation of tips, divided into eight categories - there's very little in the way of "how-to" that's included. Users advance from one tip to the other via the "previous" and "next" buttons. There's no way of knowing if the answer one needs is actually in the help system - users need to just start reading and hope for the best.

  • Waypoint Creation: I also wanted to make sure I mentioned an issue I had with waypoint creation. With detailed map information loaded for a given region, any address within that area can be looked up by the GPS, with the option of creating a waypoint at its location. For auto-based travel, this has proved to be a very handy feature indeed. Basically, a user can lookup an address by selecting a region uploaded to the SporTrak's internal database and selecting "Address." At this point, the SporTrak will query for the street name. As the user enters in letters, the GPS will "guess" at the street, by completing the street name based on "like" matches in the database. If the guess is wrong, the user simply continues entering letters. When a street name has multiple hits, due to, for example, the street finding itself across multiple zip codes within a city or within multiple cities, an entire list of matches will appear. As these choices are scrolled though, additional details about each entry, such as the city and zip code, is given at the bottom of the GPS' screen. The bearing and distance from the GPS' current position to the highlighted street are also given. The problem is that some city names are too long, and the zip code gets truncated. For example, I see two entries for Washington Ave. in Ann Arbor, MI. One is for zip code "4810" and the other is also for zip code "4810." It should read "48104" and "48108". I have to view this information on the next screen, and if I guessed wrong, come back and try again. I really don't see the value of knowing the bearing and distance to this street before I've even established that it is indeed the street that I'm looking for. I'd rather that the lower line was reserved for the zip code and street number range (e.g. 500 - 15680).


Next Steps:

In the final stage of my testing, I will continue to evaluate the various functions of the Magellan SporTrak Topo GPS, and their accuracy and usefulness in the field. Also, there are many functions that I have not yet touched upon in this field report - I will be discussing these new functions, as well as providing additional insights with respect to the features I've covered in this Field Report.


Personal Biographical Information:
Reviewer:Andrew Mytys
Email:amytys@gmail.com
Homepage:Andy's Lightweight Backpacking Site
Location:Michigan
Age:33
Gender:Male
Height:6'1" (185 cm)
Weight:165 lb (75 kg)

     Backpacking Background:

I live in Michigan and have been hiking seriously for 15 years, although I've camped since I was 6 years old. I consider myself a lightweight hiker. I carry the lightest gear I can get my hands on which will provide a comfortable wilderness experience and adequately support the goals of my trip. Unless my goals are time/distance oriented, my pace is always slow. I rarely exceed 1.5 miles (2.4 km)/hour. I rest frequently, hike long days, and enjoy whatever nature throws my way.




Read more reviews of Magellan gear
Read more gear reviews by Andrew Mytys

Reviews > Navigation and Map Gear > GPS > Magellan SporTrak Topo 2003 > Andy Mytys > Field Report



All material on this site is the exclusive property of BackpackGearTest.org.
BackpackGearTest software copyright David Anderson