parse unknown message IDs

[semuadmin]

pynmeagps Pull Request Template

ENHANCEMENTS:

1. Enhance NMEAMessage to parse unrecognised* NMEA sentence types to a nominal <NMEA(TTXXX, NOMINAL, field_01=x...)> message structure if VALMSGID validation flag is not set, rather than raise a NMEAParseMessage error e.g.:

   A. with the VALMSGID flag not set (the new default behaviour):

   from pynmeagps import NMEAReader
   msg = NMEAReader.parse("$GNACN,103607.00,ECN,E,A,W,A,test,C*67\r\n")
   print(msg)

   <NMEA(GNACN, NOMINAL, field_01=103607.00, field_02=ECN, field_03=E, field_04=A, field_05=W, field_06=A, field_07=test, field_08=C)>
   

   B. with the VALMSGID flag set:

   from pynmeagps import NMEAReader, VALMSGID
   msg = NMEAReader.parse("$GNACN,103607.00,ECN,E,A,W,A,test,C*67\r\n", validate=VALMSGID)
   print(msg)

   pynmeagps.exceptions.NMEAParseError: Unknown msgID GNACN, msgmode GET.
   

   * unrecognised message types include those with unknown or invalid NMEA msgIDs (but valid payloads and checksums), or valid NMEA sentences whose payload definitions are not yet in the public domain (e.g. those currently commented-out in NMEA_MSGIDS).

2. Add NMEA ALF sentence definition.

3. Add validate argument to NMEAMessage and carry forward from NMEAReader

4. Add logger to NMEAMessage.

Testing

Please test all changes, however trivial, against the supplied pytest suite tests/test_*.py. Please describe any test cases you have amended or added to this suite to maintain >= 99% code coverage.

• parse tests updated

Checklist:

• I agree to abide by the code of conduct (see CODE_OF_CONDUCT.md).
• My code follows the style guidelines of this project (see CONTRIBUTING.md).
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• (if appropriate) I have added test cases to the tests/test_*.py unittest suite to maintain >= 99% code coverage.
• I have tested my code against the full tests/test_*.py unittest suite.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I have signed my commits.
• I understand and acknowledge that the code will be published under a BSD 3-Clause license.