JaVaWa GPS-tools
JaVaWa RTWtool
version: 4.0 / date: 2015-04-09
downloaded 22,161 times
Available for:
Available for Mac OS XAvailable for Windows
Click here to download


JaVaWa RTWtool

JaVaWa RTWtool is a program that allows various conversions of routes, tracks and waypoints. There are options to 'unflag' routes, convert routes to tracks and vice versa, convert a collection of waypoints to a track or direct route.

Routes and tracks can be filtered to limit the number of points per route/track, and they can be split if they exceed a specified length. Tracks can be joined together.

Tracks and waypoints can be enriched with elevation data, and tracklogs can be cleaned up.

Route points accidentally put off road can be corrected automatically.

Routes and tracks can be converted to a series of waypoints in a POI file; optionally in a form like the Hermanizer.

Furthermore, routes and tracks can be converted to courses for the Garmin Edge, with the ability to automatically generate course points which warn you for changes in directions in a track or for turns in a route. Waypoints can also be converted to course points.

Finally, there are conversion options for TomTom, Google Earth, a Web map, extensive options for text files (CSV/TXT) and support for "geocoding" en "reverse geocoding" (finding coordinates using addresses and vice versa).

Routes, tracks and waypoints can be separately converted and/or processed, and both the input and the result can be displayed on a map.

File formats

JaVaWa RTWtool not only supports GPX files, but a variety of different file formats.
The following file formats can be read:

1) uses two different GPX formats; one of them isn’t compatible with Garmin devices. JaVaWa RTWtool supports both and saves them always in the Garmin-compatible format.
2)The GDB format has certainly some advantages (compact, suitable for large amounts of data, fast processing in JaVaWa GMTK), but it's somewhat outdated: it doesn't support non-announced via points, or things like cadence or heartbeat. In most cases it is better to use the GPX format.
3)When you've got a corrupt FIT file, most of the times JaVaWa RTWtool can read it. It will be indicated when a file is not complete.
4)Some KML or KMZ files don't contain (or just a few) placemarks and/or paths, while Google Earth shows them all. In that case the file contains "Network Links". Network links are references to other KML/KMZ files (usually) on the internet. JaVaWa RTWtool downloads and processes these Network Links automatically.
Network Links pointing to locally stored files won't be processed; open the original files instead.
5)Because CSV (and similar) files aren't standardised upon import you will get a dialog where you can select the list separator and the field order. More info in the manual.
6)Shapefiles often use another coordinate system than WGS84. JaVaWa RTWtool supports several transformations: Dutch Grid, Lambert 2008, Lambert 72 (both used in Belgium), Ordnance Survey National Grid and Universal Transverse Mercator (UTM) to WGS84. Upon import of a shapefile you will get a dialog where you can select the transformation, the text encoding (usually Windows-1252) and which shape fields need to be connect to which GPX fields.
7)JaVaWa RTWtool supports only ASCII DXF; no binary DXF. The remark above about transformations also applies to DXF files.

JaVaWa RTWtool can write to the following file types:

8)A FIT file always contains a single course. When converting several courses simultaneously, the first file will get name that you have specified, the others will have a sequential letter appended to the name.

When importing and converting additional attributes like cadence, heart rate and temperature will be processed too.


Export toItemExport asOptional modifications
Garmin file (.gpx/.gdb),
Device (Garmin)
RoutesRoutesSplit, Filter, Split & Filter, Add via points, Reverse
Direct routesSplit, Filter, Split & Filter, Only via points, Reverse
TracksSplit, Filter, Split & Filter, Reverse, Add elevation data
Unflagged routes-
WaypointsAt fixed intervals, On via points, On direction points
TracksTracksCorrect track logs, Split, Filter, Split & Filter, Reverse, Join, Add elevation data
Direct routesSplit, Filter, Split & Filter, Reverse
WaypointsAt fixed intervals, On track points, On direction points
WaypointsWaypointsAdd elevation data, Add warning distance
Direct routeSplit, Filter, Split & Filter
TrackSplit, Filter, Split & Filter
Garmin POI fileRoutesWaypointsOnly direction points, Only route points, Direction & route points
TracksWaypointsOnly direction points, Only track points, Direction & track points
WaypointsWaypointsAdd warning distance
Course File (.tcx/.fit),
Device (Courses)
RoutesCoursesAdd course points
Reversed coursesAdd course points
TracksCoursesAdd course points
Reversed coursesAdd course points
Course points-
TomTom (.itn/.ov2)RoutesRoutes-
Reversed routes-
WaypointsAt fixed intervals, On via points, On direction points
Reversed routes-
WaypointsAt fixed intervals, On track points, On direction points
Google Earth (.kml/.kmz)RoutesTracksAdd animation data
TracksTracksAdd animation data
Web map (.html)RoutesRoutes-
Text fileRoutesWaypointsAt fixed intervals, On via points, On direction points
TracksWaypointsAt fixed intervals, On track points, On direction points
WaypointsWaypointsAdd elevation data, Add warning distance
ESRI ShapefileRoutesTracks-
TracksTracksTrack points to point shape
DXF fileRoutesTracks-

Additional modifications

A right click (or Ctrl-click on the Mac) in the input list will show a menu with some additional modifications, depending on what is selected:

a single itemchange name
a single courseconvert course points to waypoints
one or more routes or trackschange colour
one or more waypointschange symbol
assign or change category
add addresses using reverse geocoding.
one or more itemsdelete

Text files


There is no standard for waypoints in a text file with list separators; therefore the layout can be very different. Also differences in coordinate format, list separator and text encoding will occur.
JaVaWa RTWtool can handle (almost) every combination; it requires more user interaction than other file formats though.
Upon import JaVaWa RTWtool will show a dialog box where you can set the following parameters:

Next you will see a text box with the first ten records from the file; the table below that will show the records split into fields (with the proper settings). When you click a column header, you will get a menu for assigning a waypoint element (e.g. coordinate, name) to a column.
At the end of this menu there are two special options: "Name>Phone number" and "Name@Speed". These are for fields that contain two separate items, which will processed separately by JaVaWa RTWtool. The first one can occur in CSV files for TomTom; the second one in CSV files for Garmin POI Loader.

At the top of the dialog box there are three buttons with presets, and when the file contains field names JaVaWa RTWtool will check these and try to match them with known definitions upon opening the file.

Records that don't contain valid coordinates (according to the chosen settings) will be shown in red in the table. These won't be imported, unless they contain address data (and that is assigned to the following fields: Address, Suffix, City, State/province and/or Country). More about this here.


When exporting to a text file, after been asked for a file name, you will get a dialog box where you can select the list separator, decimal separator, text encoding and coordinate system. You can also select which fields you want in the exported file; you can reorder the items in the list on the right by dragging them to the right position.
This dialog has aslo some presets; "Simple" is for a Garmin POI Loader compatible format, and "POImaker" for a POImaker compatible format.

Automatic coordinate determination

When text files contain records without coordinates JaVaWa RTWtool can try to find these using address data through the Google Geocoding API.

POI files


When converting waypoints to POIs they can be subdivided into groups and subgroups. This can be accomplished in several ways:
  1. When all waypoints originate from a single file the waypoint category will be used for the group name (when converting routes or tracks to waypoints the name of the route or track is used instead)
  2. When loading a folder with multiple source files into JaVaWa RTWtool, the file name will be used for the group name and the waypoint category for the subgroup name.
  3. When loading a folder containing subfolders which on their part contain source files, the name of the subfolder will be used for the group name and the file name for the subgroup name.
  4. When waypoints don't have categories assigned and there is just a single source file the name of the POI file will be used as group name.

You can assign categories to waypoints with JaVaWa RTWtool or BaseCamp.


By default JaVaWa RTWtool adds the regular waypoint symbols to the POI file, but it is possible to use your own symbols. This requires a BMP file with an 8 bit colour depth (256 colours; other colour depths are not supported) and a max. size of 24 x 24 pixels (or max. 48 x 48 pixels for devices with a high resolution screen). Use the colour magenta (RGB: 255 0 255, Hex: FF00FF) for the transparent parts of the symbol. (When you need magenta as a visible colour in your symbol, use a different shade).

There are several methods to link a custom symbol file to your waypoints. In the list below you can see how, and in which order it will be processed (when option 1 isn't applicable, option 2 will be used, etc.)
  1. Using the link field of an individual waypoint.
  2. Using the category of a waypoint; the name minus extension of the BMP file has to be the same as the category name.
  3. Using the subfolder where the files with waypoints reside; the name minus extension of the BMP file has to be the same as the folder name.
  4. Using the file name of the source file with the waypoints; file names minus extension need to be the same. (Note: when files with identical names exist in subfolders, the first found symbol file will be used)
  5. When none of the above, the waypoint symbol will be used. Geochaches will be assigned the appropriate symbol, regardless the options mentioned above.


You can even add photos to POIs (a single photo per POI) by adding a link to a JPG file in the same way as described above for BMP files.


When creating a POI file with JaVaWa RTWtool the following limitation apply:  



Version Changes
  • Fixed bug in TomTom export.
  • Fixed bug in GPI export.
  • Added support for OZIexplorer files (import only)
  • Added support for OSM files (import only)
  • Added support for newer TomTom Rider devices.
  • Added validation of input (can be disabled)
  • Directe routes and tracks will be splitted in parts with an exact length.
  • Can show statistics when converting to Garmin POI files.
  • Fixed bug in filter routine.
  • Reading/writing elevation of waypoints from/to kml-/kmz files.
  • Optimized elevation routines.
  • Minor changes to waypoint symbols in certain conversions.
  • Fixed bug that caused the current settings not to be retained.
  • Added power support when reading TCX or FIT files.
  • Added option to split tracks based on the number of track points.
  • Added support for power registration in tracks.
  • Added support for (invalid) Mio GPX files.
  • When converting waypoints to course points they will be linked to the closest position on the track, even when there is no track point (a new one will be created when neccessary).
  • Fixed bug in conversion of course points to waypoints.
  • Some changes for BaseCamp compatibility.
  • Fixed bugs in elevation assignment to (border crossing) tracks.
  • Fixed problem with importing certain KML KMZ, GDB and OV2 files.
  • Minor adaption in conversion of waypoints to course points and vice versa (note field).
  • Fixed timestamp bug in reversed tracks.
  • Fixed bug in waypoint display (Info option).
  • Added support for transformation to/from Ordnance Survey National Grid.
  • Added support for "Digitaal Hoogtemodel Vlaanderen"
  • Made some changes for processing elevation sources.
  • Added support for photos in POI files.
  • Added support for text files without coordinates (will be determined using 'gecoding')
  • Added option to add addresses to waypoints ('reverse geocoding')
  • Fixed some minor bugs.
  • Optimized certain processes.
  • Imporoved CSV import.
  • Changed symbol selectors.
  • Added extended support for groups and subgroups in POI files.
  • Added option to web map to switch on or off via points, waypoints and waypoint labels.
  • Fixed decimal sign bug in CSV conversion.
  • Added new BaseCamp symbols.
  • Fixed bug in the Windows version where the processing of navigation directions from GDB files didn't work properly.
  • Import and export settings for text and shape files are stored separately.
  • Improved compatibility GPX files.
  • Fixed bug in export "track to point shape".
  • The elevation (Z) from polylineZ/polygonZ shape files will be processed too.
  • Added more configuration options for web maps.
  • Added option to view info in table form.
  • Last window position and size will be retained.
  • Added extra check to the processing of NMEA files.
  • Fixed bug in transformation from Lambert 2008 to WGS84.
  • New option: assigning/modifying waypoint categories.
  • New option: using custom symbols in POI files.
  • New option: view all info of routes, tracks snd waypoints.
  • Fixed bug that caused addresses in POI files not to be shown.
  • Fixed bug with certain phone numbers in GDB files.
  • Fixed bug in shapefile import.
  • Solved problem with downloading AHN elevation files.
  • Solved problem with special characters in POI files.
  • Solved problem in Hermanizer function i.c.w. OV2 files.
  • Added option to change colours and symbols of items.
  • Improved KML, OV2 and DXF import.
  • Added options for layer names (DXF export)
  • Some small bug fixes.
  • Fixed bug with units in feet.
  • Extra info will be added to course points.
  • Improved unglitch routine.
  • Added option to determine elevations using the "Actueel Hoogtebestand Nederland" (only for The Netherlands)
  • Fixed problem with POI files with more than 500 POIs.
  • Added support for importing polygons in KML/KMZ files.
  • Added support for importing GGZ files.
  • Improved the web map format.
  • Improved the preview.
  • Improved Shapefile support.
  • Added support for the DXF format.
  • Improved KMZ import.
  • Added option to export to the KMZ format.
  • Bugfix for csv files with variable number of fields per record.
  • When exporting to KML adding animation data is optional.
  • Added option to choose the line width for routes and tracks in KML and HTML files.
  • Support for UTM in Shapefile conversion.
  • More waypoint info on map (when available)
  • Extensive options for import and export of text files, like support for UTM, MGES and Maidenhead Locator, text conversions and more.
  • Separate POImaker optionhas been dropped (integrated in the import and export options for text files)
  • Adding phone numbers to OV2 files.
  • Fixed problem with negative coordinates and elevations.
  • Added support for POImaker files.
  • Some small bugfixes.
2.0New in version 2.0:
  • New interface.
  • Conversion to GPI-format (POIs).
  • Importing & exporting ESRI shapefiles.
  • The setting Course points is changed to Directions.
  • More filter options.
  • Placing waypoints on turns in routes/tracks.
  • Suport for Geocaching files.
  • Support for laps in TCX files (will be converted to separate tracks).
  • Broader support for importing CSV files: user-selectable field order, separators etc.
  • Option to rename items.
  • CSV files are saved a bit different (see manual).
  • Some small bugfixes.
  • Fixed bug that occurred when saving a route to a GPX file.
  • Added support for new features in GPX files.
  • Solved problem with adding elevation on western/southern hemisphere.
  • Fixed some minor bugs.
  • Solved problem with overwriting existing files.
  • Improved KML/KMZ support.
1.6JaVaWa RTWtool 1.6 has the following new options:
  • Joining tracks
  • Correct tracklogs
  • Integration of GetKML
And the following changes:
  • The routine for adding elevation can download data automatically (for the EU)
  • The routine for adding course points is improved.
  • Google Maps is replaced by an Open Source alternative.
  • Sending to a device is handled by a separate option in the drop down list instead of an option in the settings.
  • Minor change for compatibility Google Maps export with Internet Explorer.
  • New: option to add elevation data to tracks and waypoints.
  • Added option to write to a CSV file.
  • Added option to convert routes to direct routes using only via points.
  • Improved 'glitches' removal routine.
  • Small cosmetic changes.
  • Added option to define map size when exporting to Google Earth.
  • Changed from FIT to TCX format when exporting courses to Edge, because the Edge 800 cannot handle multiple files (= bug in device)
  • Fixed bug with NMEA import.
Contact Terms of use RSS Valid HTML 5
Copyright © 2008-2015 JaVaWa. All rights reserved.