INT field not decoding negative numbers properly

[torriem]

RTCM Integer fields that are negative are not being parsed properly. Thus the ECEF values reported by message types 1005 and 1006 are incorrect. I have submitted a pull request to add twos complement parsing of integer numbers in RTCM3.py.

[alco1900]

I confirm Il gio 28 mar 2019, 20:48 torriem <notifications@github.com> ha scritto:

…

RTCM Integer fields that are negative are not being parsed properly. Thus the ECEF values reported by message types 1005 and 1006 are incorrect. I have submitted a pull request to add twos complement parsing of integer numbers in RTCM3.py. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ao-WE027gCuWMkHeFsJKXPyxSHi1oUZWks5vbRylgaJpZM4cRAOs> .

[pyrog]

Also the description of message type 1005 is wrong. Should be :

NAME: Stationary Antenna Reference Point, No Height Information
ID: 1005
UINT:12:2:Message Number
UINT:12:3:Reference Station ID
UINT:6:21:ITRF Year (Reserved)
UINT:1:22:GPS Indicator
UINT:1:23:GLONASS Indicator
UINT:1:24:Galileo Indicator (Reserved)
UINT:1:141:Reference Station Indicator
INT:38:25:ECEF-X
UINT:1:142:Single Receiver Oscillator Indicator
UINT:1:1:Reserved
INT:38:26:ECEF-Y
UINT:2:364:Quarter Cycle Indicator
INT:38:26:ECEF-Z
END:

Strangely, the description for message type 1006 is good (INT38 for ECEF-X Y and Z)