Leading zeros missing in RMC about nmea0183 HOT 4 CLOSED

Would

if ( !NMEA0183Msg.AddLatitudeField(Latitude,"08.3f") ) return false; 
if ( !NMEA0183Msg.AddLongitudeField(Longitude,"09.3f") ) return false;

or changing default format for bool AddLongitudeField(double Longitude, const char *Format="09.3f");
work?

from nmea0183.

Ha!! ;-)
I had just effectively done exactly that and compiled and it seems to work!
But I modified the definitions in NMEA0183Msg.h

// Add Latitude field. Also E/W will be added. Latitude is in degrees. Negative value is W. E.g.
    // AddLatitudeField(-5.2345); -> ,5.235,W
    bool AddLatitudeField(double Latitude, const char *Format="%08.3f");
    //original bool AddLatitudeField(double Latitude, const char *Format="%.3f");

   // Add Longitude field. Also N/S will be added. Longitude is in degrees. Negative value is S. E.g.
    // AddLongitudeField(-5.2345); -> ,514.070,S
    bool AddLongitudeField(double Longitude, const char *Format="%09.3f");
    //Original:  bool AddLongitudeField(double Longitude, const char *Format="%.3f");

Result:
$GPRMC,184345.00,A,5047.453,N,00100.094,W,0.4,0.0,100724,,*22
I was just logging on to Git hub to advise you!! but you got there first!

Have a great evening..
Dagnall

from nmea0183.

To close: the leading zero issue was (I believe) the root cause of this fault, where a Standard Horizon VHF was getting RMC from a (converted) N2000 Gnss (shown correctly in upper picture.
Its arguable if the Standard Horizon should have interpreted the ddmm. as dddm. - which is what it seems it did to give 120degrees! but having the leading zero always present to make dddmm. should prevent all arguments!

from nmea0183.

I pushed the fix. Fixed also crossing comment.

from nmea0183.