javAPRSlib
javAPRSlib copied to clipboard
Java APRS Parser Library
Probably worth calling it itemName whilst you're in there :)
https://github.com/ab0oo/javAPRSlib/blob/2eb8c81ee4a1a9b0e6c1eb8ef15065403ddbe342/src/main/java/net/ab0oo/aprs/parser/MessagePacket.java#L39
I'm unhappy with the data structures we're using for the base APRSPacket. Hear me out: I've been working on adding weather data parsers. It's not too complex, but it highlights...
https://github.com/ab0oo/javAPRSlib/blob/34e930a3e7b7fc382955fea762708a98f5374cc6/src/main/java/net/ab0oo/aprs/parser/PositionParser.java#L506 @ge0rg Do you have any idea what's missing here? I've made a note not to leave myself vague TODOs in the future...
Would it be possible to add support for high-precision positions based on the APRS DAO extension (as defined in http://www.aprs.org/datum.txt)?
@hessu is maintaining a nice piece of data/code at https://github.com/hessu/aprs-deviceid/ which can be used to provide additional data about the sender of a packet. Would be great to include that.
Hi, i encountered a strange behavior and investigated a little. It seems to me that the PositionPacket is sent out without a timestamp (and can therefor not be received correctly...
As reported in https://github.com/ge0rg/aprsdroid/issues/76, the spec allows the removal of whitespace in the longitude according to the ambiguity defined in the latitude, e.g.: ``` 4903.__N/07201.75W- ``` This should be supported...
One example. KA7MYM>APRS,TCPIP*,qAC,AMBCWOP-2:@081706z4322.78N/12416.81W_187/000g002t...r000p028P028h...b10295L063AmbientCWOP.com"