JaVaWa GPS-tools
JaVaWa RTWtool
version: 3.1 / date: 2014-09-17
downloaded 15,525 times
Available for:
Available for Mac OS XAvailable for Windows
Click here to download
Changelog

Nederlands

JaVaWa RTWtool

JaVaWa RTWtool (the successor of MacGPX) 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 and extensive options for text files (CSV/TXT).

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)Geocaching.com 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 having 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) 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.

Conversions

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
WaypointsWaypoints-
Course points-
TomTom (.itn/.ov2)RoutesRoutes-
Reversed routes-
WaypointsAt fixed intervals, On via points, On direction points
TracksRoutes-
Reversed routes-
WaypointsAt fixed intervals, On track points, On direction points
WaypointsWaypoints-
Google Earth (.kml/.kmz)RoutesTracksAdd animation data
TracksTracksAdd animation data
WaypointsWaypoints-
Web map (.html)RoutesRoutes-
TracksTracks-
WaypointsWaypoints-
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
WaypointsWaypoints-
DXF fileRoutesTracks-
TracksTracks-
WaypointsWaypoints-

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: list separator, text qualifier, text encoding (90 different ones) and coordinate system (WGS84, Dutch Grid, Lambert 2008, Lambert 72, Universal Transverse Mercator coordinate system (UTM), Military Grid Reference System (MGRS) and Maidenhead Locator System).
You can assign columns to a large choice of waypoint items.

There are similar options for exporting to a text file.

 

screenshot

Changelog

Version Changes
3.1
  • 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.
3.0
  • 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.
2.9
  • 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.
2.8
  • 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.
2.7
  • 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)
2.6
  • 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.
2.5
  • Improved the web map format.
  • Improved the preview.
  • Improved Shapefile support.
  • Added support for the DXF format.
2.4
  • Improved KMZ import.
  • Added option to export to the KMZ format.
2.3
  • 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.
2.2
  • 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.
2.1
  • 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.
1.9
  • Fixed bug that occurred when saving a route to a GPX file.
1.8
  • Added support for new features in GPX files.
  • Solved problem with adding elevation on western/southern hemisphere.
  • Fixed some minor bugs.
1.7
  • 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.
1.5
  • Minor change for compatibility Google Maps export with Internet Explorer.
1.4
  • New: option to add elevation data to tracks and waypoints.
1.3
  • Added option to write to a CSV file.
1.2
  • Added option to convert routes to direct routes using only via points.
  • Improved 'glitches' removal routine.
  • Small cosmetic changes.
1.1
  • 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 XHTML 1.0
Copyright © 2008-2014 JaVaWa. All rights reserved.