Pyrtcm

What's Changed
* RELEASE CANDIDATE 1.0.18 by semuadmin in https://github.com/semuconsulting/pyrtcm/pull/54

FIXES:

1. Fixes issue with parsing of IGM05/IGM06 SSR message payloads e.g. 4076_025, 4076_066, etc. Output can be verified using caster products.igs-ip.net:2101/SSRC02IGS1.

**Full Changelog**: https://github.com/semuconsulting/pyrtcm/compare/v1.0.17...v1.0.18

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

ENHANCEMENTS:

1. Add proprietary IGS SSR 4076 messages, as defined in https://files.igs.org/pub/data/format/igs_ssr_v1.pdf. NB not fully tested as available NTRIP sources only cover a subset of the 4076 subtypes defined.

**Full Changelog**: https://github.com/semuconsulting/pyrtcm/compare/v1.0.16...v1.0.17

What's Changed
* RELEASE CANDIDATE 1.0.16 by semuadmin in https://github.com/semuconsulting/pyrtcm/pull/49


1. PRN SIG mapping streamlined - id2prnsigmap() helper method replaced by dictionary PRNSIGMAP.
1. Various minor internal refactoring.

**Full Changelog**: https://github.com/semuconsulting/pyrtcm/compare/v1.0.15...v1.0.16

What's Changed
* RELEASE CANDIDATE 1.0.15 by semuadmin in https://github.com/semuconsulting/pyrtcm/pull/48

CHANGES:

1. MSM GNSSEpoch field now parsed into appropriate datafield(s) e.g. GLONASS GNSSEpoch = {"DF416": "GLONASS Day Of Week", "DF034": "GLONASS Epoch Time (tk)"}.
2. MSM Extended Satellite Information field parsed into appropriate datafield e.g. DF419 for GLONASS, ExtSatInfo for other GNSS.


**Full Changelog**: https://github.com/semuconsulting/pyrtcm/compare/v1.0.14...v1.0.15

What's Changed

1. Minor internal streamlining of RTCM 1230 message processing.

* Rc 1.0.14 by semuadmin in https://github.com/semuconsulting/pyrtcm/pull/45

**Full Changelog**: https://github.com/semuconsulting/pyrtcm/compare/v1.0.13...v1.0.14

What's Changed
* Rc 1.0.13 by semuadmin in https://github.com/semuconsulting/pyrtcm/pull/44

ENHANCEMENTS:

1. Enhance MSM signal attribute labelling to support either frequency band (e.g. "L1") or signal RINEX code (e.g. "1C"):
- The `labelmsm` keyword argument in `RTCMReader` and `RTCMMessage` is now an integer rather than a boolean, with values 0 = no label, 1 = label with signal RINEX code (the existing default behaviour), 2 = label with frequency band
- `cell2prn` helper method - new optional parameter `sigcode` 0 = use frequency band, 1 - use signal RINEX code (existing default behaviour)


**Full Changelog**: https://github.com/semuconsulting/pyrtcm/compare/v1.0.12...v1.0.13