Bug 1080831

Summary:	nmea dataset always invalid when converting from gpx
Product:	[Fedora] Fedora	Reporter:	Frank Büttner <bugzilla>
Component:	gpsbabel	Assignee:	Douglas E. Warner <silfreed>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	19	CC:	itamar, rc040203, rhbugs, silfreed
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 20:05:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Frank Büttner 2014-03-26 08:33:46 UTC

Description of problem:
When try to convert an gpx file to nmea, the result file will only contains GGA positions marked as invalid and an incomplete RMC data sets

Version-Release number of selected component (if applicable):
gpsbabel-1.4.4-5.fc19.x86_64

How reproducible:
every time

Steps to Reproduce:
1. gpsbabel -i gpx -f foo.gpx -o nmea -F foo.nmea

Actual results:
All GGA positions are marked as invalid, because the field for signal status are set to "0" and not "1,2 or 6".
The RMC data set are only complete until field date, the following fields are invalid,because the last part for signal status are complete missing.
  


Expected results:
An valid nmea file.

Additional info:
Sample output(real position replayed by X and Y):
$GPGGA,140252.755,XXXXX.YYYYYY,N,XXXX.YYYY,E,--->0<---,00,0.0,80.000,M,0.0,M,,*56
$GPRMC,140252.755,V,XXXX.YYYY,N,XXXX.YYYY,E,0.00,0.00,121013,,---><---*17
Sample of an correct nmea data set(from the English wikipedia site):
$GPGGA,092750.000,5321.6802,N,00630.3372,W,--->1<---,8,1.03,61.7,M,55.2,M,,*76
$GPRMC,092750.000,A,5321.6802,N,00630.3372,W,0.02,31.66,280511,,,--->A<---*43

I have mark the problematic position with ---><---.
The gpx file are ok, because I can open it for example with QLandkarte an the positions are showed correct.

Comment 1 Fedora End Of Life 2015-01-09 21:15:42 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 20:05:56 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.