Pynmeagps

What's Changed
* RELEASE CANDIDATE 1.0.35 by semuadmin in https://github.com/semuconsulting/pynmeagps/pull/56

FIXES:

1. Fixes & simplifies the derivation of NMEA `NS` and `EW` values when creating `NMEAMessage` objects (e.g. GNGLL) using individual keyword arguments. `NS` and `EW` will always be derived from the sign of the provided signed decimal `lat` and `lon` values and need not be provided explicitly. When creating an `NMEAMessage` using a single payload argument (_which is effectively what happens when parsing incoming serial data streams_), the value of `NS` and `EW` in the payload will determine the sign of the decimal `lat`/`lon` values in the `NMEAMessage` object.

**Full Changelog**: https://github.com/semuconsulting/pynmeagps/compare/v1.0.34...v1.0.35

What's Changed
* RELEASE CANDIDATE 1.0.34 by semuadmin in https://github.com/semuconsulting/pynmeagps/pull/53

FIXES:

1. Add missing Trimble PASHR Proprietary Pitch and Roll sentence Fixes [52](https://github.com/semuconsulting/pynmeagps/issues/52).

**Full Changelog**: https://github.com/semuconsulting/pynmeagps/compare/v1.0.33...v1.0.34

What's Changed

1. Add planar formula in `nmeahelpers.py` to calculate approximate planar distance between two sets of coordinates. Complements the haversine formula at smaller scales.

* Rc 1.0.33 by semuadmin in https://github.com/semuconsulting/pynmeagps/pull/51

**Full Changelog**: https://github.com/semuconsulting/pynmeagps/compare/v1.0.32...v1.0.33

What's Changed
* Rc 1.0.32 by semuadmin in https://github.com/semuconsulting/pynmeagps/pull/50

1. Update pynmeagps.NMEAReader to cater for NMEA streams with LF (b"\x0a") rather than CRLF (b"\x0d\x0a") message terminators.

**Full Changelog**: https://github.com/semuconsulting/pynmeagps/compare/v1.0.31...v1.0.32

What's Changed
* RC 1.0.31 by semuadmin in https://github.com/semuconsulting/pynmeagps/pull/48

1. Extend range of permissible NMEA header sequences in `NMEA_HDR` to include all known Talker IDs (not just the previous "GNSS" range of $G & $P). Supported message types remain as defined in `nmeatypes_*.py` but these can now be associated with any Talker ID from any device.
1. Minor Internal streamlining.

**Full Changelog**: https://github.com/semuconsulting/pynmeagps/compare/v1.0.30...v1.0.31

What's Changed
* RC 1.0.30 by semuadmin in https://github.com/semuconsulting/pynmeagps/pull/47

1. Cater for 'IN' (Integrated Navigation) Talker ID.

**Full Changelog**: https://github.com/semuconsulting/pynmeagps/compare/v1.0.29...v1.0.30