[aprssig] Traffic Info via APRS
stoddard at pobox.com
Fri Mar 15 19:30:48 EDT 2013
Glad to see you clarify that. Why is it people assume a firehouse will simply get pushed over a straw without a second thought.
On Mar 15, 2013, at 14:37, John Gorkos <jgorkos at gmail.com> wrote:
> My intent would be for this to be a piece of code that runs on the digi
> controller. Here in ATL, we're making a concerted effort to standardize
> all our high-HAAT, wide area digis on APRX running on Rasp Pis or some
> other embedded linux box, and they (will) all have direct internet
> connections. The code I'm talking about would periodically pool the RSS
> feed over the internet, and each digi would have a well defined zone they
> are responsible for broadcasting traffic incidents for. If an incident
> shows up in the RSS feed that occurs in that DIGIs zone, it would then
> create and transmit the object, probably with no digi path (I.e. No
> rebroadcast of the object). We'd coordinate the zones to have maybe 2 or
> three miles of overlap on the boarders. This way, APRS-IS is completely
> out of the loop: the digi gets the info directly from RSS and it goes
> directly to RF.
> John Gorkos
> On 3/15/13 2:10 PM, "Jason KG4WSV" <kg4wsv at gmail.com> wrote:
>> On Fri, Mar 15, 2013 at 11:47 AM, Shawn Stoddard <stoddard at pobox.com>
>>> The big question is does it clutter the map too much?
>> No, the big question is does it clutter the _network_ too much.
>> Code should be carefully written to be aware that it's on a shared
>> 1200 baud channel (overall TX rate checks, packet length, distance,
>> utility to the users, etc).
>> It's potentially a great service, but there's also a non-trivial
>> chance for disaster when you tie the internet to RF.
>> aprssig mailing list
>> aprssig at tapr.org
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig