Release Notes

PathAway GPS 3 for Windows Mobile


Revision History

Version 3.01b52 - Nov 4 2005

- Added: Garmin Data Transfer for GPSMAP 276C and 60C

Version 3.10.50 - July 23 2005

- Changes made to avoid tracking interruption after 15-60 minutes using Bluetooth GPS Devices.
- FIXED: Route Dialog context menu duplicated route as a track.

Version 3.10.48 - June 14 2005

- FIXED. With a "Follow Reverse" Route Active, Insert point was inserting in the wrong place.
- Fixed crash when selecting Show All Tracks or Routes
- Fixed map unreadable in cases where the map name is greater than 32 characters.

Version 3.10.47 - May 31 2005

- FIXED. Scale Zoom Out displayed points, routes and tracks at the bottom of a map in the wrong position. The larger the map (in pixels) the greater the error.

Version 3.10.46 - Feb 28 2005

- Fixed memory leak (lead to eventual crash after many hrs of running prog).

Version 3.10.45 - Feb 20 2005

- Fixed unexpected GPS disconnect while tracking.

Version 3.10.44 - Feb 2 2005

- Rebuild and localization updates.

Version 3.10.42 - Dec 23 2004

- FIXED. Zoom Hard keys not working after "Connect to GPS".

Version 3.10.40 - Nov 23 2004

- FIXED. Adjust location position saves using W not -. Affects only localized versions
- NEW: Auto Detect Baud rate in GPS Configure dialog.
- NEW: Expanded Debug Output log capabilities (GPS Configure).
- NEW: VGA PPC's. Maps now display in full VGA resolution.
- FIXED: Screen not refreshing properly when switching between landscape and portrait mode.
- FIXED: "New" from Points Dialog not saving Editted Data.
- FIXED: Time now displays in Local time.
- NEW: Added "System" to GMT Time Zone Offset. Means use the System Setting.
- Map Manager 3.10.21, PWDBLib.dll: Fixed: Could not send to Winmobile device from a Windows 98/ME PC.

Version 3.10.35 - Oct 18 2004

- Fixed: Date error on "Get from GPS" (download track data)
- Map Manager 3.10.21: Fixed Error converting between Lat/Long Degrees and UTM, with a Datum other than WGS 84.

Version 3.10.33 - Oct 7 2004

- NEW: Added Europe 1950 (Spanish and Portugal) datum
- NEW: Added option to set UTM Time offset in .5 (1/2 hr) increments
- FIXED: Possible data corruption when adding route points.
- FIXED: Simulate not working when set to Garmin protocol. - FIXED: Error Europe 1950 Datum conversion.
- NEW: Added Customizable Hard Key settings in Preferences.
- NEW: Added "GPS Configure->Advanced" Section, option to "Apply SIRF GGA Altitude Correction to calculate Elevation". See Explanation for details.

Version 3.10.30 - Sep 23 2004

- Fixed: Add to route problem when adding existing points to route. distance est error.

Version 3.10.29 - Sep 16 2004

- 3.10.29 updated. Map Manager build had an improper DLL. Upload to WinMobile would not work.

Version 3.10.29 - Sep 15 2004

- Move to... All Map Databases fixed.
- Point View. Selection of Database Types fixed.

Version 3.10.28 - Sept 13 2004 (pre-release)

- Pre-Release Version. Pocket PC 2002, 2003 ARM processors

As of the latest version, the following features displayed in the application are still incomplete:
- Automatic PathAway DB File list refresh on Card Change.
- Beam
- Transportation Mode Icons and Settings
- Points - Sort
- Show/Hide Toolbar


Apply SIRF GGA Altitude Correction to calculate Elevation

NMEA rule says, elevation in $GPGGA is either uncorrected
ellipsoidal(WGS84) elevation, or if a correction table is included
with the GPS Receiver, then the corrected (near geoidal)
elevation is given, plus, right behind, the value is noted, by
which this corrected elevation differs from the ellipsoidal (WGS84)
altitude.

But, SIRF does not stick to that rule:
They give the uncorrected ellipsoidal elevation as altitude plus
the correction value right behind. So using a sirf II chipset
user may end up with a wrong elevation constantly.
Here it is quite exactly about 50 Meters, i. E.
elevation reported is 707.7 meters, actual elevation
(seen from DEM or MAP or other receivers) is 649 meters,
correction value is 48.0 meters.

example:
$GPGGA,144347.099,4806.9547,N,00834.8330,E,1,06,1.8,707.7,M,48.0,M,0.0,0000*75

Note: This correction value can be negative (-) thus, finally adding up to
the elevation given. This problem applies to PALM as well as PPC

The entire story:
http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=10915