Currently, the package allows you to get information about the latitude / longitude direction only for coordinates saved in the DD format. Formatting longitude / latitude to GPS / DMS format cuts out direction information, or rather tells you to read the longitude symbol as East and the latitude symbol as North, which may not necessarily be true. It may happen that some services may want to receive GPS coordinates immediately in GPS / DMS format, and these formats require the delivery of a direction sign.
My suggestion is simple and could be included in the program code. However, I think that the packet responsible for parsing NMEA frames should provide complete information about each of the supported frames, even those that are theoretically easy to obtain.
Coverage remained the same at 100.0% when pulling 52da6e28594c29e5bb76b3c444d16d809eac9f69 on krawczyk87:pr-direction-sign into 236848d9189c561b285fbcb8f2d02bb6f68f51a8 on adrianmo:master.
Currently, the package allows you to get information about the latitude / longitude direction only for coordinates saved in the DD format. Formatting longitude / latitude to GPS / DMS format cuts out direction information, or rather tells you to read the longitude symbol as East and the latitude symbol as North, which may not necessarily be true. It may happen that some services may want to receive GPS coordinates immediately in GPS / DMS format, and these formats require the delivery of a direction sign. My suggestion is simple and could be included in the program code. However, I think that the packet responsible for parsing NMEA frames should provide complete information about each of the supported frames, even those that are theoretically easy to obtain.