Waypoints probably don't need any further discussion, they work like waypoints do in just about every other GPS.

People familiar with newer Garmin products will also understand POIs (Points of Interest). POI's are like waypoints in that they identify a location like a restaurant or a mountain summit but they cannot be modified or created on the GPS. Garmin's maps typically include millions of POI's but they also provide a POI Loader which can be used to create and load custom POI's on the Oregon.

The Oregon also adds special handling for waypoints which are geocaches which is discussed in more detail on the Geocaching page. Geocaches are distinct from Waypoints on the Oregon. They are visible through separate lists and are managed differently. Geocaches cannot be modified (except for marking them as found, DNF'ed, etc) or deleted but they do contain information specific to geocaches like cache type, terrain/difficulty ratings, container size, hints and the full cache description.

Waypoints

W2.) Is there a fast way to mark a waypoint on the Garmin Oregon?

No. The only way to mark a waypoint on the Oregon is to use the Mark Waypoint tool on the Main Menu.

Users are also able to create waypoints directly from the Map Page. When viewing the map, tap a location and an information button will appear at the top of the map. This button shows the location of the point you selected in addition to distance and heading from your current location. Pressing this button will take you to a new screen that has a button at the bottom allowing you to save this location as a waypoint. You will need to open the waypoint manager to rename it.

W3.) How do I navigate to a set of coordinates?

Select WhereTo?->Coordinates and enter the coordinates.
Select Main Menu>Mark Waypoint>Save and Edit>Change Location and edit the coordinates. By default these coordinates will be the location of where you marked the waypoint.

W4.) How do I edit/delete/project/reposition a waypoint after I have created it?

You can only perform these operations on a waypoint through the Waypoint Manager Tool on the Main Menu. Selecting a waypoint from the WhereTo? Tool will only allow you to view the waypoint on a map and navigate to it.

W5.) How I do delete waypoints?

There are three ways:

Select a Waypoint and tap the edit button (pencil icon) will allow you to select Delete Waypoint
Main Menu>Setup>Reset>Delete All Waypoints will delete all waypoints.
Main Menu>Waypoint Manager>[search/select waypoint]>Delete Waypoint will allow you to delete individual waypoints.

W6.) How do I know how much of my 1000 waypoint memory I've used?

Go to Main Menu>Setup>Reset and the Delete All Waypoints button will tell you the percentage of waypoint memory used.

W7.) I can't see any waypoints (or Custom POIs) on the map screen. Can I fix this?

Yes. Waypoints are visible on the map based on your zoom level. Normally the more you zoom in the more detail you will see. You can change the zoom level settings by following the instructions below.

Select Main Menu>Setup>Map>Advanced Map Setup>Zoom Levels>User Waypoints><n> Miles, where <n> is the zoom level below which you want waypoints to show up. Note this setting will also change the Zoom Level where you can see custom POIs

W8.) What's that little blue pin symbol that keeps showing up on the map screen?

The blue pin is the destination of your current or last navigation.

W9.) Why can't I see all of my waypoints in the nearest waypoints list or the Waypoint Manager?

The Oregon, like other Garmin handhelds, will display only the 150? closest waypoints in these lists. There are two ways to display these "hidden" waypoints:

Spell out the name of the waypoint you are searching for by selecting "abc" button and spelling out part of the waypoint name.
Recenter the origin of your searches by going to WhereTo and selecting the "target" button to select a new "search from" location. The 50 closest waypoints to this new origin will be visible in the lists.

Note: Garmin has increased the limit from 50 to at least 150. Need to test how many are visible at one time.

W10.) What is waypoint "000"? I do not remember creating it.

Waypoint 000 is a special waypoint used by the Oregon when you pan a map screen to a location, tap the map and start navigation to this point. The Oregon automatically creates this waypoint and navigates to it.

W11.) How many characters are supported in the Oregon's Waypoint name and description/note field?

The waypoint name supports 30 characters and the description/note fields supports 49 characters on the Oregon.

W12.) What are the little numbers/letters next to each Waypoint/Geocache/POI on the list page? How come they change to little red arrows sometimes?

This is the bearing to each of these points from your current location. Depending on your heading configuration (Setup>Heading>Display) you will see either cardinal directions (Directional Letters), bearing in degrees (Numeric Degrees) or bearing in Mils (Mils). If you are moving faster than 3-5mph this field will change to a little red bearing arrow.

W13.) How do I project a waypoint using the Garmin Oregon?

Goto Main Menu>Waypoint Manager>[select waypoint]>Project Waypoint and enter the distance and bearing. If you want to project a waypoint from your current location mark a waypoint first and then follow the procedure above.

W14.) Can I average waypoints on the Garmin Oregon?

Yes. As of 2.96 the Oregon now supports waypoint averaging. GPSFix has screen shots showing the feature and Garmin has posted some interesting information on how to use the waypoint averaging feature.

Tip: Use a Satellite Visibility Prediction Service to determine the best time to average a waypoint for a specific location and date.

W15.) What is waypoint "MOB"? I do not remember creating it?

Waypoint MOB is a special waypoint used by the Oregon when you use the the Man Overboard function.

W16.) How can I get the direct distance or bearing between two Waypoints (or POIs) when neither point is my current location?

thanks oystercatcher for the tip

To measure the distance or get the bearing between two points first select the starting point:

WhereTo?>"Target Button">A Waypoint>[select a starting point]

You will be returned to the WhereTo? menu where you can select

Waypoints>[select an end point]

After this you will see a map page with a status bar at the top. The status bar will have the distance and bearing from start to end.

POIs

P1.) Are POI name, description, category, address, email and phone fields supported? How many characters are supported in each of these fields?

POI name, description, category, address, email and phone fields are supported and can contain up to 1023, 1023, 14, 150, 150 and 150 characters respectively. The Oregon automatically prefixes the phone and email field text with "Phone".

The limitation on the name and description field length may not be a Oregon limitation -- it appears to be a limit imposed by the POI loader when using CSV files. Users are reporting that the Oregon can display much more information than 1023 characters using GPX files.

Verify: Copied from Colorado FAQ, assumed to be the same for Oregon.

P2.) Can I load geocaches as POI's? Can I create custom POI databases using GSAK on the Oregon?

Yes. Although you cannot use the Geocaching mode features of the Oregon with POIs, you can bypass the 2000 (or 5000 in case of the Oregon x50) geocache limit by using a custom POI database. The easiest way to do this is use the procedure developed by pilotsnipes for Nuvi's as documented on his site. There is also an active thread on the groundspeak forums that shows screen shots of the Colorado in action using his GSAK-based tools. The Oregon works the same.

There is also an advanced Nuvi POI GSAK macro written by jjreds for managing POIs on the Nuvi which applies to the Oregon (and Colorado). The download page for the macro is here and there is a groundspeak thread for support of the macro is here. Note the advanced version of the macro can be used to created custom POI databases for just about anything you can get into GSAK including waymarks, red light cams, speed cams, etc.

Spoiler photos associated with a cache can be displayed as a POI. Information on how to do this can be found here.

P3.) Where are custom POI databases kept on the Garmin Oregon?

The POI Loader installs the .gpi files into [OR drive]:\Garmin\POI. By default it installs a file called poi.gpi.

P4.) What if I want more than one custom POI database, can I do that?

Yes. Just use the POI Loader to download the first poi.gpi file and rename the file so that the next download doesn't overwrite the first file. For more details see this FAQ.

Once custom POIs are loaded onto the Oregon they are visible under WhereTo?>Extras.

P5.) I can't see POIs on the map screen. Can I fix this?

Yes. POIs are visible on the map based on your zoom level. Normally the more you zoom in the more detail you will see. You can change the zoom level settings for POIs by following the instructions below.

For custom POIs select Main Menu>Setup>Map>Advanced Map Setup>Zoom Levels>User Waypoints><n> Miles, where <n> is the zoom level below which you want custom POIs to show up. Note this setting will also change the Zoom Level where you can see waypoints.

For built-in map POIs select Main Menu>Setup>Map>Advanced Map Setup>Zoom Levels>Map Points><n> Miles, where <n> is the zoom level below which you want map POIs to show up.

P6.) Is there a maximum number of .gpi files (POI files) that I can load on the Garmin Oregon?

Yes. The maximum number of files that is supported is 20.

P7.) Can I create POI Proximity Alerts for Geocaches loaded to my GPSr?

Yes. See this Geocache Proximity Alert POIs tutorial so you never have to worry about accidentally missing another geocache again!.

Issues

Bugs

[x50] The dates in waypoint file names are derived using Zulu time not the local time zone. For example, in EDT (GMT-4) if I create a waypoint on 7/8 at 8:01pm the unit creates a file called Waypoints_09-JUL-09.gpx for this waypoint. Note the timestamps in route file names appear to be correct. (2.10)
[x50] Malformed GPX file is created after deleting a photo included in a waypoint. Take a photo, create a waypoint, edit the waypoint and "Change Photo" to add the photo to the waypoint. Goto the Photo Viewer and delete the waypoint. In USB Mass storage mode open the Waypoints gpx file associated with the new waypoint. The waypoint entry has a bogus "/" before the wpt tag. There is also still a link to the deleted photo which should probably be cleaned up. (2.10) For example:
- </<wpt lat="42.592734" lon="-71.328666"><ele>80.654160</ele><time>2009-06-12T22:05:38Z</time><name>003</name><link href="DCIM/1000GRMN/DSC00125.JPG"/><sym>Trail Head</sym></wpt>
[x50] GPX files are not loaded (waypoints or geocaches) from the SD drive. If you copy a file into [SD drive]:\Garmin\GPX the contents of these files do not show up on the Oregon 550t. (2.10)
From the WhereTo?>Extras list the unit displays heading arrows for each custom POI category. This doesn't make sense and is not consistent with how lists are displayed under map POI's which have sub-categories. (2.99)
Selecting a waypoint and POI at the same location on the map page does not activate the multi-object selector, you can only select the waypoint. Select a POI and tap the save as waypoint button, exit and goto the map page. Select the location of the POI/waypoint and note that only the waypoint is selectable from the map page (2.98)
During symbol entry for a waypoint it is not possible to determine the currently selected symbol by looking at the screen. Selecting Change Symbol should highlight the symbol currently used until the user makes a selection. (2.98)

Missing features

There is no way to clear the Recent Finds list without performing a master reset. (60csx, CO) (2.98)
Newly created waypoints should immediately show up on the Recent Finds list to make them easy to locate for subsequent navigation (a very common operation) (60csx) (2.98)
WhereTo?>Search Near should list All POIs as an option or alternately from any POI you should have the ability to "Search Near Here" (60csx) (2.98)
No support for custom waypoint symbols (60csx) (2.98)
Search and delete by waypoint symbol is not supported (60csx) (2.98)
Waypoint symbols are not visible in list views (e.g. recent finds) (60csx) (2.98)
After selection a navigation destination (i.e. Waypoint, POI, Geocache) the type of point and the symbol should be displayed in the summary box at the top of the screen with the green Go button (not just on the map). (60csx) (2.98)
On the Waypoint/Geocache/POI list views when you select the ABC button to start a spell search you should not have to enter any characters to get an alphabetical listing of all Waypoints/Geocaches/POIs. Currently you have to enter at least one character which means getting a filtered list of points and they are not in alphabetical order. You shouldn't have to enter any characters and should be able see the entire list sorted alphabetically. In some cases when a point is over 20 miles from your current location this is the easiest way to search when you don't remember the name. (60csx) (2.98)

New feature requests

Add the ability to see the "cmt" field of waypoints imported from gpx files. Particularly with geocaching child waypoints this field is used to describe the waypoint and it would be nice to be able to see this information on the detailed waypoint screen.
[x50] When selecting "Change Photo" from a waypoint edit it is not obvious which photo is selected (if there is one)
Add the ability to disable the proximity alerts that display when arriving at a destination. Alternately, make the alerts smaller (like the 60csx) so that the entire screen is not covered.
The UI design for the edit waypoint screen is very poor. In order to edit a waypoint you should immediately see all of the waypoint parameters (not just the name) and fields rather than having to select each to view it and determine if it needs to be changed. In 2.6 coordinate entry improved.
Add support for a special Home waypoint and shortcut to goto Home.
Add support for a set of high priority "core waypoints" (on Nuvis this is "My Favorites") that can be loaded and managed separately from all other waypoints. Frequently I want to have a "core" set of waypoints always loaded on my GPS: Home, Work, Friend's House, etc. I'd like to be able to delete all other waypoints on the unit (ie. those more temporary waypoints related to Geocaching for example) without deleting the core set.
When you mark a new waypoint you should be given the option to navigate to the waypoint without having to go back to WhereTo?>Waypoints.
The special cursor movement mode visible when editing waypoint fields should be eliminated and incorporated into the other data entry screens to reduce keystrokes and jumping between modes, similar to how coordinate entry works now.
Waypoint symbol pages should be alphabetized, it is difficult to remember whether you need to scroll right/left to find a particular symbol.
Change Symbol should land you immediately on a page that contains the most recently used set of symbols.
Editing the coordinates of a waypoint could be optimized, the touch pad should be look like this:
1 2 3 Up
4 5 6 Down
7 8 9 ^/v
< 0 > >>
The number scheme is well known and easier to use, the two empty button fields may be used for ">>" jump to next number field (from degree to minutes from minutes to second etc.) and "^/v" jump to first/second line.

Editing Names

There are some points which could be improved concerning editing waypoint (or track) names
• the used character for a space looks like a hyphen, this should be changed
• there is no possibility to insert characters (insert/overwrite mode or just inserting spaces)
• multiple tipping necessary to get the cursor to the end/start of a text line
• no possibility to enter special chars with accents etc.

These things could be done without compressing the actual user interface, here are some screen shots demonstration this (personally I find, that a "single" window containing the cursor/edit buttons would look better than the seperated buttons):

Needs Verification

Resolved

[x00] (3.20) Fixed potential shutdown related to drawing 32-bit map points. Believed to be same as item below.
[x00] (3.13) Fixed potential shutdown with custom POIs with custom symbols. Sometimes in automotive mode the unit will shutdown on the map page when navigating to a custom POI or with custom POI's visible on the map screen. (3.12)
[x00] (3.12) Fixed issues with back button not appearing when editing a waypoint. Edit a waypoint and modify a parameter like "Location". After completing the edit of the parameter there is no red "X" in the lower left corner to return to the main menu. Selecting View Map allows you to return to main menu. (3.12)
(2.97) Fixed lockup when a search returns no results. Introduced in 2.96.
(2.96) Added Waypoint Averaging application. No support for waypoint averaging (60csx) (2.94)
(2.96) Increased the number of waypoints viewable from the Waypoint Manager and Where To?>Waypoints
(2.95) Added POI subcategories. Map POIs should support the ability to filter by category, currently the Oregon only supports filter by database. Note 2.85 added support for databases and categories on custom POIs but not map POIs (Colorado, 60csx) (2.94)
(2.94) Added ability to edit a waypoint from the waypoint review. Should be able to edit a waypoint without having to enter the Waypoint Manager. For example you should be able to edit a waypoint selected from the WhereTo?>Recent Finds, WhereTo?>Waypoints lists or by selecting the waypoint from the Map Tool. (CO) (2.93)
(2.93) No Garmin specific release notes. The Spell feature under WhereTo?>Custom POIs is confusing. If you enter a letter which is contained in one of the database names you will get a list of database names to select from. If enter a letter/sequence which is not contained in one of the database names you can search all Custom POIs. Search should probably do one or the other not both. (2.93)
(2.93) No Garmin specific release notes. Under WhereTo?>Custom POIs>All Databases no POIs are displayed ("No Results Found") even if there are multiple databases containing POIs (2.86)
(2.86) Improved Custom POI spell search.
(2.86) Improved Custom POI database organization. Loading a single custom POI database does not work properly. Using POI loader (2.5.3) to load a single gpx file as a custom POI database results in a single entry under WhereTo?>Custom POIs which when selected appears like a waypoint in the middle of the Atlantic (link). POIs in the database are only visible during a "Spell Search" of the database. (2.85)
(2.86) Added distance and bearing to point when reviewing a Custom POI.
(2.85) Fixed some scan points not working properly with Garmin GB Discoverer maps
(2.85) Added support for Custom POI database and category selection. This resolved the issue for Custom POIs, however Map POIs are still do not display categories. The Oregon should have the ability to narrow POI searches by selecting POI categories. POI categories are not visible on the Oregon. (CO, 60csx) (2.6)
(2.6) Fixed issue when marking waypoints in the W Malayan RSO position format.
(2.6) Added GDA 94 datum.
(2.6) Added NAD 83 datum.
(2.6) Added 'Coordinates' option to the 'Where To?' menu. Support direct entry of coordinates as a destination under WhereTo?>Coordinates (Zumo/Nuvis) (2.5)
(2.6) Improved user interface for waypoint location editing. When entering UTM coordinates (Waypoint Manager>[Waypoint]>Change Location) there is no space between the easting and northing (2.5) The notation in the coordinates is confusing because a 2-digit degree number has a "-" in the leading position which looks like a negative sign. When there is no character the position should be blank. Entire set of coordinates should be visible when editing the coordinate field of a waypoint. At a minimum there should be a confirmation page where the entire set is displayed before accepting the changes. (60csx) (2.5)
(2.4) Fixed issue with duplicate waypoint names. User now gets a warning if they try to create waypoints with the same name. Create two waypoints with the same name "Test". The second waypoint will not be renamed and there is no warning that the waypoint was not renamed. (2.3)
(2.3) Improved handling of naming a waypoint the same as an existing waypoint. This does not fix the issue above. (2.2)
(2.3) Fixed creating invalid gpx files after projecting a waypoint. Projected waypoints have corrupted <desc> fields that cause current.gpx to be unreadable by Mapsource. From the Main Menu select the Waypoint Manager Tool and select an existing waypoint. Project a waypoint and save the newly created waypoint. Connect the Oregon to a computer and open current.gpx in Mapsource. You will receive an error "There was a problem communicating with the device" because the projected waypoint has garbage characters in the <desc> field. Opening the gpx file in a text editor reveals that the waypoint <desc> tag has bad characters. Deleting the waypoint fixes the problem. (2.2)
(2.3) Improved feedback when typing an invalid character into the keyboard. The keypad available for various characters in the coordinate string should be optimized to only show the characters valid for that location. For example the keypad needs only N, S, E, W when entering the lead character for latitude or longitude. Invalid character entry results in a beep and the character is highlighted red. Note: This fix actually prevents invalid characters from getting entered as well. (2.2)
(2.3) No specific Garmin release note. Sometimes during coordinate entry the display gets confused when entering numeric data. The result is the numeric entry pad is displayed on the symbol selection grid. Use the Mark Waypoint tool to create a waypoint and select Save and Edit. Select Change Symbol and select a different symbol for the waypoint, then select Change Location and hit the check mark to exit cursor move mode. The number grid will be displayed on top of the grid used for symbol entry. (2.2)
(2.3) Improved feedback when typing an invalid character into the keyboard. It is possible to modify the coordinates of a waypoint such that Mapsource will fail to import current.gpx from the GPS. Using the Mark Waypoint function create a new waypoint and then select Save and Edit>Change Location. Edit the longitude of the location to be E-180 00.002 and save these changes. When connected to a computer Mapsource will fail to import waypoints from the Oregon indicating a "There was a problem communicating with the Garmin device". Deleting the waypoint in the Waypoint Manager fixes the issue. The code below shows the illegal longitude value in the current.gpx file. The edit waypoint user interface should prevent the user from entering invalid characters or coordinates. (2.2)
```
<wpt lat="42.592850" lon="180.000002">...</wpt>
```
(2.3) Fixed Custom POIs not being removed from Recent Finds after the Custom POI database was deleted (2.2)
(2.3) Fixed issue where the Oregon would temporally stop responding after a spell search. Similar to issue seen on Colorado where Geographic POI searches would hang the display for several minutes. (2.2)