Sign up ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I do not succeed in importing waypoints from Ozi files (extension .wpt). I tried both converting through GPS-Babel to XML (.gpx) and importing in QGIS with the GPS-tool. Both times set to WGS 84, as is the setting in Ozi.

What should I do?

share|improve this question
Could you describe how the import process fails? – whuber Jun 1 '12 at 14:45

3 Answers 3

Global Mapper will convert WPT to SHP

OziExplorer Waypoint (WPT), Route (RTE), and Track (PLT) Files

Description: The OziExplorer waypoint (WPT), route (RTE), and track (PLT) file formats are used to store user waypoints, routes, and track logs from GPS devices by the OziExplorer application. The WPT and TRK files can be loaded into Global Mapper v6.00 and above, and the RTE files can be loaded into v9.01 and above.,_Route_RTE,_and_Track_PLT_Files

ESRI Shapefiles you can use a trial version to test it.

share|improve this answer

If you try to import from a GPS... You can try DNRGarmin! It takes several files (.gpx, .kml, shp, txt, etc) and can convert them to .shp files. Hope that helps.

share|improve this answer
While very capable and a mainstay of GPS users for many years, DNR Garmin (now DNRGPS) doesn't know how to handle Oziexplorer files. However gpsbabel which is bundled with DNRGPS does. Get to it from File >> Launch GPSBabel menu. (but OP already said GPS babel doesn't work on their files) – matt wilkie Oct 16 at 15:59

is very capable, and used under the hood by many programs. It can be hard to sort out just what options to use even with the gui that's now included. I suspect for the original poster an incorrect combination of parameters was being passed, though we can't rule out internal file data corruption.

In any case, at this point you need to go to the source and use GPS Babel directly, to get a more direct view of what is going on and possible error messages.

Step 1: use a tool to help determine the right combination of command line options.

I like the online free GPS Vizualizer service. What I particularly like about gps-viz, aside from being available without installing and instant viewing gratification, is that it shows the command line used to use as templates in your own scripts.

GPS Vizualiser conversion dialog

The following GPSBabel command was executed:
gpsbabel -w -r -t -i ozi -f "2011 Auriol Moose.plt" -o gpx -F "2011 Auriol Moose.gpx"

Step 2: use the command line to inspect error messages directly

In the event the problem was unresolved in Step 1, use the command line from it in your own local console. Prepend -D n to increase the verbosity of debugging messages, with 0 meaning none. The debugging info is format specific (some don't add very much extra detail). The following is level 3:

gpsbabel -D 3 -w -r -t -i ozi -f "2011 Auriol Moose.plt" -o gpx -F "2011 Auriol Moose.gpx"
GPSBabel Version: 1.4.4
options: module/option=value: ozi/snlen="32" (=default)
options: module/option=value: ozi/wptfgcolor="black" (=default)
options: module/option=value: ozi/wptbgcolor="yellow" (=default)
options: module/option=value: ozi/proximity="0" (=default)
options: module/option=value: ozi/altunit="feet" (=default)
options: module/option=value: ozi/proxunit="miles" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: gpx/snlen="32" (=default)

Step 3: follow up on errors

Follow up on the error messages, with many round trips to the fine manual, and questions here on GIS Stack Exchange as needed. The more research and info you put into your questions the better and faster results (low effort on this question meant 3.5 years before an effort-ful answer).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.