blankblank blank


Archive for the 'Magellan' Category

Android: The Future Of Consumer GPS – Part II

After yesterday’s magnum opus about how Android will transform the consumer GPS industry, today’s shorter post is a few random thoughts on how the big three handheld GPS makers might be affected by Android, and how they might respond. Personally, I think it’s going to be tough for them to adapt. Up until recently, handheld GPS units have been a fairly limited specialty market, allowing manufacturers to control interfaces and map data, and charge exorbitant prices due to limited competition. In most consumer electronics fields, prices drop even as capabilities increase; that really hasn’t been the case for handheld GPS. Android has the capability to turn GPS into a commodity market, meaning less control and more competition, leading to lower prices. And this is an environment that the old-school GPS vendors may have trouble with.

Magellan: Magellan is still struggling to overcome the disastrous premiere of their Triton line in 2008: decent hardware with capabilities unique at the time (raster imagery, 3-axis compass) sabotaged by horribly buggy software. Most of these problems got fixed, but too late to make a difference. Magellan was acquired late in 2008 by MiTAC (parent company of Mio, and they’ve just recently announced a new series of Explorist models, due out this fall.  For standard GPS models, the specs on these look pretty good, and the prices are very competitive. But in the long run, I don’t see how they can compete with more-capable Android models that are likely to sell in the same price range or even lower.  Putting someone else’s Android unit into a Magellan body with a better antenna and waterproof/field-rugged design might be a better way to go. They already have some experience using that approach with their new case for the iPhone, which enhances the iPhone’s GPS abilities while offering better protection against the elements; they just have to do it more cheaply.

DeLorme: DeLorme has moved into second place for handheld GPS units with their PN series, the first consumer models with raster/aerial imagery, and the first models with an affordable subscription plan for this imagery. They’ve also come out with a new model recently, the PN-60, with an upgraded interface and the ability to interface with SPOT communicators for satellite text messaging. But $400 for a GPS with a 2.2” display? No touchscreen? No apps? Their $250 xMap software lets you upload GIS data (raster and vector) to their PN models, but you can already put raster imagery on Android models, and GIS vector data can’t be too far behind. I don’t see this proprietary hardware line as having much of a future, and they don’t have much experience with alternative hardware.

Garmin: Garmin seems to develop an OS for their GPS units, and then use it as long as they can. The OS developed for their eMap model in 1999 was adapted and upgraded for most of their handheld models through 2006, culminating in the classic 60/76Cx series. These were probably the best-selling handheld consumer GPS series of all time, and four years later are still among their most popular units. They’re only 2.5 years into their next-gen GPS OS, the one that powers the Colorado/Oregon/Dakota/62/78 series, and they’ve certainly released a ton of variant models in these lines. The question is whether they can move past their own proprietary hardware and software designs and move quickly to an Android platform, using their strong GPS expertise to bring additional features that will differentiate their models from the rest of the market.

I’d like to think so – I’ve been a Garmin fanboy for 10 years now, and even now that I own a Droid X, you’ll have to pry my 60Cx out of my cold dead hands. But their recent history isn’t encouraging. Their first attempt to move Garmin technology to a cellphone platform, the nuvifone, was universally despised by reviewers. Their second effort, the Garminfone, was based on the Android platform, and received much more favorable reviews; the car navigation software of the Garminfone is generally considered to be the best Android car navigation system so far. If the phone had come out in the latter half of 2009 as originally scheduled, it could have been a huge success. But instead, it was first released in June 2010, and was crippled by:

  • Older software; it ran Android 1.6 when every other phone being released at the same time ran Android 2.1
  • A custom interface that makes it very difficult to upgrade to more recent Android versions
  • Slow processor
  • 3 MP camera
  • A screen pixel count 1/4 of its similarly-priced competitors, and a smaller screen
  • Garmin car navigation software on competing models that, while not as good, was free
  • Lousy battery life
  • No headphone jack

In short, simply not competitive with other Android phones. A month-and-a-half after being introduced for $199.99, it was already discounted by $70, and was part of a “buy one, get one free” package from T-Mobile. Even with that, it’s only sold about 20,000 units, which Garmin themselves acknowledged as a disappoint performance in their latest quarterly report..

If Garmin is going to survive in the consumer market, they’re going to have to move faster than that in developing products. And they’re going to have to give up control of the overall interface in favor of Android’s standard, putting their interface into just their applications. And they need to leverage their GPS engineering capabilities and map data into advantages that make  their units stand out. If they don’t, they’re going to have a tough time surviving in this new market.




Handheld GPS Units – Beyond The Manual

It’s no secret that the manuals many GPS makers puts out with their handheld GPS units aren’t always ideal. They can be very confusing, give cursory explanations of more complicated functions, and often leave out any mention at all of advanced functions. Plus, as firmware gets updated and features get added/dropped, the printed versions become out-of-date, and even the online PDF versions lag in adding descriptions of new features. Here are some online resources to help plug the info gaps for these units.

GPSFaqs.Org: Contains comprehensive FAQs for the following Garmin models -

If your eTrex model or GPSMap isn’t listed above,  you may find the answer you’re looking for in the FAQ for a different but comparable model, since most of these models share a similar OS/interface.

GPSFaqs.Org also has FAQs for Magellan GPS units; coverage is strong for Explorist models, but cursory for Triton models.

Yahoo Groups: A number of active groups for the GPSMap series (60Cx/60CSx and 76Cx/76Cx), as well as eTrex models (general and the Legend). Not a lot of action in the Triton or DeLorme forums.

Groundspeak GPS And Technology Forum: Free registration required. Regular postings/discussion on GPS units from a variety of manufacturers, mainly Garmin and DeLorme.

DeLorme Community Forum: Probably the best source for info about the DeLorme PN series of GPS receivers.

TritonForum: By far the best source of info for the Magellan Triton series.

GPSFix Wikis: Created by Scott at GPSFix.Net, an exceptionally strong resource for info about modern Garmin units in the following series:

gpsinformation.net: Tons of general info about GPS, and pages about specific units from a wide variety of makers, some dating back to the 1990s! May take a bit of hunting to find the info you’re looking for.

<!–wsa:Moagu-banner–>




Archive Of Old GPS Firmware And Software Updates

If you ever feel the need to roll your GPS back to an older version of the system firmware, you likely won’t find it on the manufacturer’s website; they typically only have the latest version. The Garmin Software Archives has a pretty extensive collection of  older firmware updates that covers most Garmin units released over the past dozen years, as well as some for other makers as well (Bushnell, deLorme and Magellan). The collection is most comprehensive for handheld units (need an update for your 12XL?), but includes some marine, aviation and automotive units as well. The archive also had older software updates for Garmin programs like MapSource, Basecamp, WebUpdater, POILoader , nRoute, even the old USB programmer for Garmin’s proprietary memory card format. Some programs (e.g. MapSource) don’t let you downgrade to an older version, so you’ll need to uninstall your current version, then install a valid older version from one of your map discs before using one of the updaters from the archive.

Almost forgot: there’s a link at the archive to a great Garmin PDF from 2005 on using your GPS with paper maps; also includes a page of map tools that you can print on a transparent sheet and use with USGS 1:24K topo maps (map grid for UTM and compass rose, and two scale rulers).




A Review Of The Garmin Oregon 450t GPS For Field Work: Part I

A few weeks ago, I did a post called “In Search Of The Perfect Fieldwork GPS”, a list of the features I’d like to see in a handheld GPS unit designed for serious fieldwork and mapping. The Magellan Triton 2000 GPS unit, which I reviewed last year, had some but not all of these features, and while it’s a decent GPS it’s just not good enough for fieldwork. Recently, Garmin was nice enough to send me one of the latest models in their Oregon line of GPS units, the Oregon 450t, for review:

This post will look at the basic hardware and GPS performance of this unit, comparing it with the Magellan Triton 2000 and my old-school Garmin 60Cx. Tomorrow’s post will be a review (rant?) of the Oregon’s touchscreen interface.

The Oregon 450 series, another touchscreen model, is a follow-on to the Oregon 550 models introduced in mid-2009, and the successor to the Oregon 400 series. The biggest difference between the 400 and 450 series is the tri-axial compass on the 450, which works at any angle; the compass on the 400 requires you to hold the unit horizontally. Comparing the 450 to the higher-end 550 units, the 450 models don’t have the built-in 3 MP digital camera found in the 550s. I think a camera is a useful add-on for a fieldwork GPS; while the 3 megapixel sensor is a bit small, I’ve heard that you can focus from two inches to infinity with this camera, making it useful for both closeup and distance shots. A “t” at the end of a model number indicates that it has a 1:100K-equivalent US topographic map dataset pre-loaded into the unit; non-“t” models have a simple basemap installed, plus an elevation database that lets them display shaded terrain relief and 3-D views.

At 2.25” x 4.25”, the Oregon is substantially smaller than either the Triton or 60Cx, and fits comfortably in my hand. I think I would have liked to have seen a bit more texturing on the outer surface to help with the grip, since the unit only has the power button to break the surface continuity. Still, the “rubbery” edge of the unit shouldn’t make hanging on to it too difficult, even in wet conditions. There’s a lanyard hole at the bottom of the unit, but no lanyard is included; instead, a carabineer clip can be slid onto the back, letting you clip it onto your belt or pack. I’d personally prefer a lanyard, and buy a separate belt case/clip. While the unit is small, it weighs just slightly less than the Triton or 60Cx, so it actually feels heavier than those units even though it’s not (weight vs. density).

Documentation: Only a quick-start guide was included in the package. You can download a PDF user manual from the Garmin website, but even it is seriously lacking in basic information about the unit. I can’t recommend the Garmin Oregon GPS Wiki enough as a far more complete documentation source for the Oregon line than anything Garmin puts out.

Software: None included.  Unlike the 60Cx model, the Oregon does not come with Garmin’s MapSource program, which allows you to manage and upload vector mapsets to your Garmin unit; you have to either pay for a Garmin mapset that includes this program, or beg/borrow/steal a copy from someone else. A recent update to Garmin’s Basecamp software added the ability to upload mapset data, but I find this program far inferior to MapSource for this purpose. This is nickel-and-dime stuff; for the price you’re paying for this unit, a copy of MapSource should be included.

Computer interface: Mini USB plug, and thank God it’s USB 2.0; older Garmins had USB 1.0, which made large map transfers painfully slow. One annoying feature is that the only way to use USB for power only is to have the USB interface set to Garmin Spanner; in other interface modes, the GPS unit display is turned off automatically. On the flip side, you have the option of an NMEA serial interface through the USB connection, which is useful for those programs that only work with NMEA connections.

Battery life: I got a respectable 15-20 hours out in the field from the recommended NiMH rechargeable batteries, far better than the Triton, slightly worse than the 60Cx.

Display: The 3” diagonal, 65K-color 240 x 400 display is gorgeous when viewed under the right lighting conditions and angle. When the first Oregon units were released, many people complained about display visibility, especially in sunlight conditions. I don’t have an older model for comparison, but I can say that this Oregon’s display is very usable in sunlight conditions, far better than the Triton. Outdoors under reduced light (cloud or shade), the display is less than ideal unless you turn the backlight on at full intensity; even then, it’s not great. Terrain shading on maps looks great in screenshots, but in the field, you’ll get better results by turning it off. Oddly enough, the Triton display is better under those conditions when the backlight is turned on. The Garmin 60Cx is far better than either of those in all lighting conditions, at the cost of reduced color depth and resolution; still, a low-color display you can see is better than a high-color one you can’t.

One final problem with the display: since it’s a touchscreen, it’s going to get covered with fingerprints pretty quickly, and these can degrade screen visibility, especially in sunlit conditions.

GPS Satellite Reception: The Oregon units have small ceramic path antennas, which require you to hold the unit horizontally for optimal reception. I wish Garmin had stuck with the larger, omni-directional quad helix stub antennas found on their 60Cx and Colorado units; while they might break up the “clean” look of the unit, you’d get better reception at all angles. And there’s no connector on the Oregon for an external GPS antenna that might improve reception. I consistently acquired more GPS satellites on my old Garmin 60Cx than on the newer Oregon model. Still, outdoor reception with the Oregon for the regular GPS constellation is acceptable under most usage conditions, even holding the unit at an angle, and is superior to the Magellan Triton. I also liked the unit’s ability to store GPS satellite data to increase acquisition speed the next time you turned it on. WAAS reception was very problematical; even under wide open skies, with no terrain blockage and two WAAS satellites high in the sky, picking up a WAAS signal could take as long as half an hour, and the WAAS signal frequently dropped out. Even when a WAAS signal was received, not every GPS satellite signal had the “D” indicator showing that the GPS position was being properly corrected. Not a huge problem now while the sun is currently in a quiet phase, but that will change as the sun moves towards a more active phase over the next few years; Garmin needs to fix this issue ASAP. Neither the Garmin 60Cx or Magellan Triton had similar WAAS signal problems.

Positional accuracy: For a quick qualitative analysis of positional accuracy, I loaded high-resolution calibrated aerial imagery onto both the Garmin Oregon and Magellan Triton, and tested them under fully open skies (no terrain or tree blockage). Both were equally excellent in positional accuracy; while the displayed error estimates were on the order of 5 meters for both units, the actual error based on the aerial imagery was on the order of 1-2 meters.

One thing the Oregon has that is sorely lacking on the Triton is waypoint averaging; for good waypoint accuracy for serious field work, this is essential. Garmin suggests returning to a specific point several times to do waypoint averaging that takes into account errors due to satellite geometry; I’d suggest to Garmin that they include Dilution of Precision (DOP) in the display, letting people know how good the current satellite geometry is.

average

Compass: I’ve used GPS units with built-in compasses before, and always wound up turning them off. Accuracy was always questionable; direction readings tended to be “jerky”, jumping around continuously; the need to hold the unit horizontally limited the utility. The compass on the Oregon 450t has none of these problems; it’s the best GPS compass I’ve ever used, by far. Accuracy is outstanding when you follow the simple calibration procedure; readings are smooth and solid; the “tri-axis” functionality lets you hold the unit at any angle and get an accurate reading. It’s not a complete substitute for a good handheld compass, but it’s not that far off, either. A+ for Garmin on this one. If they could only add a feature that would let you measure the angle from level at which you hold your unit, it would be fantastic for combined angle/direction measurements like slope and dip/strike.

Compass screen:

compass

Maps: Every standard vector map I tried on the Oregon unit worked perfectly, including custom maps with standard feature types. I tested some custom maps with custom feature types, and they worked as well, but there’s no guarantee with those that all of them will work. As I mentioned above, terrain shading looks great with some of these maps when you do screenshots, but doesn’t work that well in real-life, and I turned it off right away. In terms of map variety and availability, Garmin blows Magellan away completely; in addition to Garmin’s own proprietary maps, a search on this website and others like GPSTracklog will bring up many sources of free Garmin maps (e.g. the GPSFileDepot).

Last year, Garmin added the capability to display raster maps on the Colorado/Oregon/Dakota series, and included the capability for you to create your own maps for free. I give Garmin major props for that, as no other GPS maker has done that. deLorme requires you to pay $200 for a copy of xMap in order to put your own raster data on their GPS units. Magellan has never released any official way to put your own raster maps on their Triton units, limiting your official choices to maps sold by them (though there are now free unofficial options for generating Magellan Triton raster maps, like TritonRMP Maker, RMP Creator and Mobile Atlas Creator).

Having said that, though, there are currently too many limitations on raster map functionality on the Oregon for it to be fully useful right now. No map segment can be larger than one megapixel in size (1024 x 1024 pixels square), requiring either downscaling or tiling of larger raster images. Garmin hasn’t issued any tools for creating, managing or uploading such raster maps; you have to use either Google Earth or one of the many 3rd-party tools that have popped up to aid in creating raster imagery (like G-Raster or Mobile Atlas Creator). You’re limited to 100 active map segments in total on your unit; since you can’t turn raster image files on and off, that means a total of 100 map segments is all you can have. And you can’t have different types of raster imagery, say aerial photos and topo maps, for the same area; since you can’t turn one type off while leaving another on, only one type can be displayed. The Magellan Triton is far superior in this respect; raster images can be up to 18000 x 18000 pixels in size, you can put as many into your unit as you have memory for, and you can turn raster image mapsets on and off at will. In order for this capability to be fully functional, Garmin needs to:

- Increase the total number of map segments that can be active

- Give you the ability to turn raster mapsets on and off.

Sample raster map (USGS topo in this case):

raster

Memory: The 450t comes with 1 GB of built-in memory, and the ability to add 4 GB of additional memory with a microSD card that fits into a slot behind the batteries. With the current limitations on raster maps, 5 GB is more than enough space; if Garmin fixes those issues, then I can see where this might not be enough storage space. However, memory cards are cheap and easy to swap out, so that’s not a big problem.

3D View: With a built-in elevation basemap for the US, the Oregon 450t can give you a 3D view of the terrain; with the built-in compass, it changes the view to match the direction you’re facing in. Initially a very cool feature, but IMO it has limitations that limit its usefulness:

- While it will overlay vector map features on top of the terrain view, they’re not labeled. So, for example, if there’s a hill/mountain in the 3D view, its name won’t be displayed.

- Waypoints and tracks are not displayed in 3D view; without that, 3D View’s utility in navigation is limited (although it will display a navigation track).

- Raster maps are not overlaid

3dview

Waypoints: Maximum of 1000 waypoints, the same as older units. But I think you’d have to work hard to come up with a scenario that requires that many waypoints; you can always download and archive waypoints on your computer for future uploads. The touchscreen interface makes entering the waypoint name a lot faster than with rocker switches.

I was going to complain about the lack of custom waypoint symbols, but Garmin recently added that as a beta feature; now they only need to add support for that in their MapSource and Basecamp software.

Tracks: Far better support for track data than earlier Garmin units. Up to 200 tracks can be saved on a unit, and tracks you save now include time data, useful for geotagging photos. Up to 10,000 points in a track, and if you run over that limit on your current track, the Oregon automatically saves the first part of the track in GPX format, and then truncates the current track to free up room for subsquent track points. See the Oregon Wiki track section for full details.

Custom POIs: I’ve posted about these before; they’re a useful way to store points and related data on your unit without having to use up waypoint space. The Oregon units support these, though they annoyingly hide them in the Where To => Extras folder; what’s up with that name, Garmin? Older Garmin units limited POI names to 40 characters, and associated data to 80 characters; Oregon units increase those to 1023 characters, and add some extra data fields (Oregon Wiki has full details). Using the techniques in this post, and taking advantage of the extra data space, you could associate several hundred words of data with each POI; this could be very handy for field work.

There are a host of other features that I’ll skip, like geocaching support, calendar, stopwatch, alarm, etc., since these aren’t really relevant to what I’d want to use this unit for: navigation and data collection. Except for the WAAS issues, which I really hope they fix soon, I found a lot to like in the feature set and basic functions of the Garmin Oregon 450t unit. What I didn’t like, in fact actively dislike, is much of the touchscreen interface; I’ll deal with that in Part II of this review.




Raster Maps For Garmin And Magellan GPS Units, And Mobile Phone Apps, With Mobile Atlas Creator

Mobile Atlas Creator (formerly TrekBuddy Atlas Creator) is an open-source program that downloads map tiles from a variety of sources, and converts them into a large number of formats compatible with mobile phone mapping apps, some Garmin and Magellan GPS units, and OziExplorer. Written in Java, it comes with a Windows executable and Linux shell script to start up the program; I don’t have a Mac, but I’d guess there’s some way to get it to work with Macintosh computers as well. Map sources currently built into the program include:

Continue reading ‘Raster Maps For Garmin And Magellan GPS Units, And Mobile Phone Apps, With Mobile Atlas Creator’




Online Resources For Magellan Triton GPS Owners

The huge number of online support resources for Garmin handheld GPS units dwarfs the number of comparable sites for info and data for the Magellan Triton GPS line. Still, there are a few very useful sites to bookmark if you own this raster-compatible GPS unit.




TritonRMP Helper Upgraded To Version 2.0

I posted version 1.0 of my utility TritonRMP Helper on this site a few weeks ago, an aid to creating custom raster maps for the Magellan Triton GPS series. It re-projects a GeoTiff to geographic/WGS84 coordinates (if necessary), then extracts out the calibration data needed by the program TritonRMP Maker to convert the TIFF file into a Triton-compatible RMP file. I’ve added a few enhancements to it, and voila, version 2.0. Check the original post for basic info, but here are the improvements:

  • The biggest change is in exporting calibration data to TritonRMP Maker. In 1.0, you had to manually copy the coordinates of calibration points into the program. Version 2.0 of TritonRMP Helper now creates a “gmap” file containing all the calibration data needed by TritonRMP Maker; no more manual copy-and-paste required, which cuts the time and work required a lot. Load the gmap file into the Maker program with the File => Map => Import Maps command. You can load multiple gmap files at the same time to combine maps, or different zoom levels, in the final RMP output. The name of the gmap file is displayed at the top of the program, along with the GeoTiff file associated with the calibration data:

Helper_2

  • Version 1.0 allows rescaling of GeoTiff images down to smaller sizes, for use at lower zoom levels, but this sometimes fails without warning for very large images. Version 2.0 checks for this failure, and gives you an error message. You can sometimes get the rescaling to work by exiting the program, then starting it up and trying again.
  • Version 1.0 came with no install program, just a zipped folder containing the executable and associated files. Some people were reporting issues with the “comdlg32.ocx” ActiveX control being missing on their system, and some would probably prefer to have a regular program install. So the program is now available in two versions: an executable for a full install, and a zipped folder version for those who don’t want the full install.

Standard disclaimer, i.e. use it at your own risk, and double-check any maps you produce for accuracy. And report any bugs you find to me via my Contact link.




Put Rasterized OSM Maps On The Magellan Triton GPS Using RMP Creator

For a while, there were two programs you could use to calibrate and convert raster map images into Magellan-Triton-GPS-compatible maps, TritonRMP Maker and RMP Creator (website in German). The author of RMP Creator apparently decided to remove the custom map calibration and conversion functions in favor of those in TritonRMP Maker, but did keep the program active for one very cool function: converting rasterized Open Source Mapping (OSM) data into Triton-compatible map formats.

It’s a Java WebStart program; here’s a direct link to the program launcher. Run the program, and zoom in to your desired geographic area:

osmmapnik

Based on the map zoom level, the program will automatically choose which output zoom levels will be available, and you can select/deselect them by checking the boxes at the bottom. You have the choice of basic OSM street maps as above, or the OSM Cycle Map which includes topographic contours:

osmcycle

Specify the output filename in the ResultFiles box, click on the “Execute Conversion” button, then wait a while as the program downloads map tiles for multiple zoom levels, combines them, and converts them to a single RMP file for use in the Triton GPS unit. Once completed, you can install the map file into your Triton with Vantage Point, or copy it directly to the Map_data folder on the SD card used with the Triton. They’re not vector-map sharp, but do show streets and street names clearly enough:

osm