andyvan-trabus

Question: Reasonable approach to constructing an editor

2

I have written an editor using PyCrate and PySimpleGUI that works well for editing existing fields in an object. It uses get_val_paths() to go through a message and construct a...

Question: General guidelines for contributors?

2

I'd like to contribute, but I've looked around and have failed to find some minimal set of instructions. What I'd like to know when constructing pull requests: What version of...

ais.h #define LIBAIS_VERSION_MAJOR 0 #define LIBAIS_VERSION_MINOR 15 ais/__init__.py __version__ = '0.17'

Parsing using the tag_block queue can result in an exception: > python test_239.py > Traceback (most recent call last): > File "test_239.py", line 9, in > queue.put(line, line_no) > File...

I noticed that messages that decode when I call ais.decode don't decode when I use the tag_block interface. I've traced it to the following: > Parse('!ANVDO,1,1,,Y,E>k`?g@VWW:3WVRak`?g@VWW:3WVRak`?g@VWW:3WVRa

Timestamp not decoded ("\\c:1628097600")

1

I'm seeing quite a few lines that have the timestamp ("\c:") present, but with an extra backslash. I'm not familiar enough with the standard to know whether this is valid...

KeyError: 'decoded' in DecodeTagMultiple

1

I saw the following exception: > python3 test_234.py > Traceback (most recent call last): > File "test_234.py", line 9, in > queue.put(line, line_no) > File "/home/avanpelt/git/TMP/FORK/libais-fork/ais/tag_block.py", line 171, in put...

Add parsing support for 8:367:23, 8:367:24, 8:367:25, 8:367:33.

3

This adds support for parsing the USCG 23, 24, 25, and 33 messages. I've tested this with live messages, and have added one each of those live messages as a...

Handling of N/A values could be improved

1

The current processing of values that need to be scaled or offset to yield "useful" values introduces some hardships for code that's trying to use the returned values. Example AIS...

I noticed the following name in the code for AIS8_1_26_SENSOR_WX: DictSafeSetItem(rpt_dict, "**air_pressor_type**", rpt->air_pressor_type); This seems to be the field which is "Air Pressure Sensor Data Description" in a similar section...