GPSFix» – GPSFix

Custom Symbols on the Garmin Oregon 450 and 550

Scott — Thu, 11 Mar 2010 14:30:16 +0000

Ever since the Colorado arrived two years ago without this feature, Custom Symbols has been on the The Most Wanted List for the newer State-named units, especially since the older 60csx had this capability. Today Garmin fixed that for some Oregon owners by announcing Custom Symbol support in their latest 450/550 beta. The Custom Symbols feature allows you to add completely new waypoint symbols to your GPS or override the default waypoint and geocache symbols assigned by Garmin. Based on Garmin’s instructions on the trail-tech blog I’ve been playing around with the new feature and here is what I’ve found you can do with Custom Symbols:

Override a preinstalled waypoint symbol by creating a bitmap file named .bmp in \Garmin\CustomSymbols\. The new symbol will replace the Garmin default symbol on the Change Symbol page, map page and waypoint lists — places where waypoint symbols are normally visible
Add a new waypoint symbol by creating a bitmap file called .bmp in \Garmin\CustomSymbols\. These symbols appear on two new pages called “Custom” under Change Symbol when editing a waypoint.
Override a preinstalled geocache symbol by adding a symbol file called .bmp in \Garmin\CustomSymbols\. You can only associate symbols based on Groundspeak’s “geocache type” field, other cache attributes such as size, state, etc. are not supported (but wouldn’ t THAT be cool).

A Custom Symbol file needs to meet certain basic requirements according to Garmin:

24-bit Windows-style bitmap format (Windows Paint supports this format)
Saved in \Garmin\CustomSymbols\ in either internal memory or SD card, both seem to work simultaneously
Bitmap can be no larger than 32 pixels in either width or height
Limited to a total of 56 Custom Symbols per GPS (this happens to be the space available in the two new Custom pages under Change Symbol).
Replacement waypoint symbols files need to have the same prefix as the element does for the waypoint in a GPX file (i.e. Summit.bmp)
Transparent pixels can be created in the symbol by setting the pixel color to magenta (RGB = 255, 0, 255).
Symbols will draw centered around a waypoint by default. To create an offset symbol include the offset in pixels from the upper-left corner in the filename (i.e. Summit.10×20.bmp)
An enumerated symbol ID can be associated with a symbol by including the ID in the filename (i.e. Summit.1234.bmp). This will only be of interest to developers.
Garmin provides a list of waypoint and geocache symbol names on their developer site.

Based on my limited testing, Custom Symbols seem to be working as expected except for the fact that BaseCamp does not support Custom Symbols — neither displaying them nor allowing you to select them. And as with many new features I kept thinking of improvements (some of which are already on the Oregon wiki feature request list) that would make this an even more powerful feature:

Search and delete by symbol in the Waypoint Manager (please!)
Enhanced custom symbols for geocaches. A way of overriding or augmenting symbols based on cache size, enabled status, contains travel bugs, solved mystery cache, difficulty, attributes, etc would be useful.
The currently selected symbol for a waypoint should be highlighted when you select Change Symbol
Pages under Change Symbol should wrap when you scroll to the end. With the addition of two Custom pages it takes even longer to get from one end to the other when scrolling back and forth.
Recent Finds should display symbols like other lists.

I’ve added a page to the Oregon wiki for Custom Symbol FAQ’s .

Availability of this feature on the Dakota, Oregon x00 and Colorado is unclear at this time. The Dakota and Oregon x50 do have some special capabilities in this area, they share support for both 24×24 bitmap symbols and UserDataSync that is not available on the older units. Time will tell if these features are prerequisites in order to support Custom Symbols or not.

If you don’t like making your own symbols I’ve found two sites that have small symbol libraries here and here. If you find others please post and let us know!

The command is executed on the F120 via SSH from the SC. It’s an expect script that further passes the control over to the active SAM. The SAM runs through a list of slot numbers and for each it issues the “clia boardreset” command. The order is: 4-13, other SC, this SC, other F120, this F120.

Garmin to Add Custom Symbols and Tracklog Improvements to Oregon x50

Scott — Wed, 10 Mar 2010 19:00:25 +0000

Update: Garmin has released beta 3.26 for the Oregon x50 available here. I would highly recommend backing up your entire /Garmin/GPX directory before using this beta since your current tracklog will get modified and moved into daily/weekly archives if you enable that feature.

Here’s something bound to make Garmin Oregon 450 and 550 owners happy. Two new posts from Garmin on their trail tech blog indicate upcoming support for custom waypoint and geocache symbols and improved tracklogs. While the beta software doesn’t seem to be available yet the posts look promising. Here’s a summary:

Custom Symbols

Create your own bitmap symbols, up to 32 pixels wide by 32 pixels high
Override built-in waypoint or geocache symbols
Add up to 56 new waypoint symbols

Tracklog improvements

Configure daily or weekly track archives
Change the color of the current tracklog
View archived tracks on the GPS
Use the stopwatch to start and stop archive tracks
Mark archived tracks as favorite saved tracks so they can be navigated, viewed, etc
Archive your favorite saved tracks

No word on whether either of these features will be available on the Dakota, Colorado or Oregon 300/400. Once the beta software is available I’ll be posting tips on how to use both new features.

GPSFix Twitter Weekly Updates for 2010-03-07

Scott — Sun, 07 Mar 2010 22:00:00 +0000

Garmin Colorado 400i, 400c and 400t discontinued? No longer show up on Garmin's US site (CO 300 does) #
Garmin Colorado 400's are on the discontinued list: https://buy.garmin.com/shop/shop.do?cID=167 Wonder how the 300 will stay? #
Boyd's free detailed New Jersey map for Garmin Oregon/Colorado/Dakota http://tinyurl.com/yg6w64s #
Garmin Oregon 450t finally in stock at Amazon, hopefully it'll last longer than last time (still no 450's) http://bit.ly/9CV2te #

GPSFix Twitter Weekly Updates for 2010-02-28

Scott — Sun, 28 Feb 2010 22:00:00 +0000

Reading GPS Tracklog: Handheld GPS 101: Routes http://tinyurl.com/ydfo7g9 #
Garmin Oregon 450 shows up as in stock at Amazon for ~$375 http://bit.ly/arbBlH #
RT @gpstracklog Raytheon wins contract to improve GPS OCX (advanced control segment) http://bit.ly/bRWUXN #

GPSFix Twitter Weekly Updates for 2010-02-21

Scott — Sun, 21 Feb 2010 22:00:00 +0000

http://twitpic.com/13gou8 – #Garmin Oregon's "Are we there yet" mode – great with a 6-year old. Wish my Nuvi had this large data field. #
Garmin Oregon 450/550 3.13 beta. Fixes custom map colors and demo mode http://www8.garmin.com/support/download_details.jsp?id=4743 #
#Garmin Dakota 10/20 2.61 beta. Fixes custom map colors and demo mode: http://www8.garmin.com/support/download_details.jsp?id=4751 #
RT @gpsreview Putting the orbit altitude of GPS satellites into perspective: http://www.gpsreview.net/satellite-perspective/ #
RT @gpstracklog I started a new series of posts this a.m. – GPS 101: Waypoints http://bit.ly/9VIU3p Me: Great for new GPS users #
RT @gpstracklog GPS File Depot has added new search options http://bit.ly/dx7nqu and a #Garmin custom map index http://bit.ly/bnAWTT #
Tip: Create daily tracklog archives from #Garmin Oregon, Dakota, Colorado tracks using GPSBabel http://tinyurl.com/ydy5doc #
New #Garmin Oregon x50 and Dakota releases = beta + GB Discoverer fix. OR: http://tinyurl.com/ykfo3b2 DK: http://tinyurl.com/m63mkz #

Garmin Oregon 450/550 and Dakota Beta Fixes Bugs

Scott — Tue, 16 Feb 2010 00:21:08 +0000

For those of you who don’t follow me on Twitter, Garmin has posted new beta software for both the x50 Oregon and Dakota which includes fixes for the following two issues:

* Fixed issue with units getting stuck in demo mode.
* Fixed color issues with GB Discoverer and Custom Maps.

Both have been reported on the Oregon and Dakota wiki boards although it isn’t clear to me why they are releasing these updates as a beta – something which has normally been used when Garmin introduces new features.

On my Oregon 550t it looks like they have addressed both problems and I haven’t seen any problems updating to the new release.

GPSFix Twitter Weekly Updates for 2010-02-14

Scott — Sun, 14 Feb 2010 22:00:00 +0000

Oregon vs Dakota comparison page added to the Dakota wiki http://garmindakota.wikispaces.com/Dakota+vs.+Oregon #
Via FGT: Using Mobile Atlas Creator to create #Garmin custom maps http://tinyurl.com/yjegkmt #

GPSFix Twitter Weekly Updates for 2010-02-07

Scott — Sun, 07 Feb 2010 22:00:00 +0000

RT @allory_d MapInstall software version 3.13.5 (Windows) http://www8.garmin.com/support/download_details.jsp?id=3291 #
Garmin Oregon 450 and 450t owners manual available. Also covers the 550 and 550t. http://tinyurl.com/ykhodw6 (PDF) #
RT @allory_d MapSource software version 6.15.11 http://www8.garmin.com/support/download_details.jsp?id=209 #
RT @gpstracklog GIS Data For US National Parks And Monuments: http://bit.ly/8Zyyit #
TopoFusion Pro 3.97 released. Rolls up previous beta releases into official version. http://tinyurl.com/ya85xfa #
RT @gregorypleau #Garmin Colorado v3.1, 3.2 annoying how 3rd party maps cover all waypoints. Could you fix before EOLing the firmware! #
RT @gpsreview Appalachian Trail GIS and GPS Data: http://bit.ly/cWehPP #
RT @JakesJournal Garmin has some February fun with Vancouver cityXplorer http://bit.ly/azHDGH Me: CX works on handhelds too. #
Quick tutorial on how to change Maps on your Oregon/Dakota/Colorado. Covers other Garmin GPS's too. http://tinyurl.com/yz3uspx #

Garmin Releases “Do-Over” for Oregon and Dakota

Scott — Sat, 06 Feb 2010 15:13:21 +0000

After making new releases available for the Oregon x00, Oregon x50 and Dakotas just weeks ago, Garmin has quickly followed up with a fix-up release that addresses several common complaints.

The new software lineup made available on January 28th includes Oregon x00 version 3.6, Oregon x50 version 3.1 and Dakota version 2.6. All of these releases can be downloaded to your GPS using Garmin’s WebUpdater. The release notes from Garmin include:

Increased the map drawing range to allow maps to draw farther south.
Corrected issue with route line sometimes not drawing.
Corrected issues with marine POI.
Corrected issues with GB Discoverer maps.
Corrected issues with possible corrupted profile showing on the Profile Change page. (only listed for the Oregon x50)
Corrected issue with project waypoint bearing sometimes not showing the input value .

Unless you are below latitude south 60 degrees (where the first issue might be your most important fix!) the second item, a missing routing line, was an issue that generated a lot of user complaints. A quick perusal of the discussions for the new firmware reveals there are still some issues to be sorted out:

GB Discover maps don’t update properly during driving
Custom maps color scheme is lighter and (in my opinion) more washed and harder to read

Note for Oregon 450 and 450t owners: it appears that the Oregon 550 and 450 share exactly the same firmware. New 450 users are reporting that the Webupdater is upgrading them to version 3.1.

GPSFix Twitter Weekly Updates for 2010-01-31

Scott — Sun, 31 Jan 2010 22:00:00 +0000

Garminconnect still can't split tracks if you forget to reset odometer before starting a activity on your Oregon, Dakota, Colorado. #
Anyone got their hands on a #Garmin Oregon 450 or 450t yet? #
Appearance of custom maps different in newest Garmin Oregon/Dakota beta. Most feel it is worse now http://tinyurl.com/yesv8gf #
Reading @geeks2null Garmin Oregon 450 Test (German) http://bit.ly/betgaW Me: Display is not much better than 300 similar to 550 #