3
$\begingroup$

What's the difference between an APRS "item" and an APRS "object"?

A kenwood manual says Objects have timestamps, items do not. What does that mean, and how should it be used?

Also in general: What is a good resource for learning about APRS? aprs.org is not one, since it only has angry rants about implementations doing it wrong, and no explanations about what's right.

$\endgroup$
6
$\begingroup$

Per the spec, which unsurprisingly is found at aprs.org, objects are intended for moving or animate objects of the same nature as a station beacon (people, vehicles, storms, etc.) while items are meant for permanent points of interest (they may come and go, but they're not expected to move) such as hospitals. However, there's no real difference between them, other than the fact that, as Kenwood says, object reports contain timestamps. In practice, clients seem to display them and age them out identically.

Both of them are almost completely equivalent to ordinary position beacons (which can have a timestamp or not), except that an object or item has a name which is different from the callsign of the originating station.

| improve this answer | |
$\endgroup$
  • $\begingroup$ Yeah I read the spec. Sorry, should have added that to my question. I think you confirmed my vague understanding though: It's a layer violation in the protocol standard, and really shouldn't have been distinct types at the protocol layer. (though this is my opinion and you don't have to agree). I was thinking they had to be actually different, but no, not really. $\endgroup$ – Thomas Apr 7 at 18:03
  • $\begingroup$ @Thomas I do agree, it seems unnecessary to have reserved different object types for them. APRS is kind of simultaneously overengineered and underengineered :) $\endgroup$ – hobbs - KC2G Apr 7 at 18:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.