[aprssig] Objects on APRS

Thu May 3 12:57:02 EDT 2007

> The best place for the object is local RF.  An IRLP, 
> Repeater, Echo Link, in Billings, MT are only good 
> to the local APRS travelers n RF in the local community. 
> Therefore they need to be sent out on local RF. If 
> they appear on the APRS-IS it should be from being 
> received from RF.

Agree completely.  But requiring 10,000 non-APRS sysops and
owners of ILRP and ECHOlink nodes to invest in a separate 144.39
TX and a TNC to generate the object is never going to happen
(though a few did).

When solved this by asking the IRLP and ECHOlink systems to
simply generate the objects onto the APRS-IS so that the objects
at least existed from a reliable source, and then they can
piggyback on the existing TNC and existing TX of the local
Igate.  Done...

> To ask an Igate Owner to constantly watch and update the 
> gateway to consistently put these on RF is adding to his 
> work load.  The work load should be from the person or 
> station generating the Object.

To provide a local RF service, the Igate should not just be a
plug-and-forget.  The SYSOP should be kept informed of the local
RF domain and the local IRLP and ECHOlink sysops should request
that the local Igate have these two local objects passed-to-rf.

I see these local resource sysops working and talking together
so that the APRS map display in each area does represent to the
local community, what the leaders in the local community feel
are important RF assets.

The burden is not just on the Igate (though he has to make the
entry to activate the object).  The other observers need to keep
these sysops informed of any major change in the local assets
that would need to be reflected in the Igate settings.

> This is true of Hospital, EOC, Police, Fire and other 
> objects.

No, these are not RF assets, and they do not have changing
STATUS that is of immediate need to local RF operators.  None of
these objects are initiated on the APRS-IS anyway.  Anyone in
the area that activates an EOC or a Firestation forsome
immediate event, is responsbile himself for placing it on the
map.

The only APRS-IS initiated objects to my knolwedge that fit the
category of needing to be added to the local Igate pass-to-RF
list are the desired local IRLP and ECHOlink nodes.

> I would not like to receive a call about all the
> objects I am gating to RF.

I agree completely.  No one should be transmitting -routine-,
inanimate, non-RF objects to RF.  I see far too much of that and
it is a waste of resources.  Especailly, since built into APRS
was the feature to QUERY for EOC's, Query for hospitals, or
anything else so that they couild be tranmistted on demand, but
no one wants to see these objects all the time.
But we are only asking for two local objects in the coverage
area of any given Igate.  That is, the active IRLP and ECHOlink
objects.

> It makes better sense for the local stations to generate 
> the RF information.

Better sense, true, but will never happen.  That's 10,000 TNC's
and 10,000 radios someone has to buy and it simply wont happen.

I think we may be talking apples and oranges.  Here are my key
points:

1) No one likes to see routine objects of no immediate RF value

2) We are never going to get local IRLP and ECHO nodes to
generate their own

3) It is so simple to generate them in real time on the APRS-IS
straight from the IRLP and ECHO central database so that the
object reflects the real-time status of the node.

4) All we are expecting is for the Igate operator to be
knowledgible of the RF assets in his community and to assist the
local are in putting these out by adding them to his pass-to-RF
list.

Hope that helps
Bob, WB4APR

> 
> > -----Original Message-----
> > From: Robert Bruninga [mailto:bruninga at usna.edu] 
> > Sent: Tuesday, May 01, 2007 9:27 AM
> > To: 'TAPR APRS Mailing List'; n7vr at arrl.net
> > Subject: RE: [aprssig] Objects on APRS
> > 
> > 
> > The way it is supposed to work (I think) is that the IRLP
and
> > the ECHO link "systems" centrally put out objects into the
> > APRS-IS.  From there, any local Igate is supposed to know
those
> > IRLP's and ECHO link nodes in their immediate area and put
them
> > in the special gate-to-RF list.   If this is not how it is
> > working, can someone summarize it for all of us?  Thanks Bob
> > 
> > > -----Original Message-----
> > > From: aprssig-bounces at lists.tapr.org 
> > > [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Eric
> > Goforth
> > > Sent: Monday, April 30, 2007 1:10 AM
> > > To: n7vr at arrl.net; TAPR APRS Mailing List
> > > Subject: RE: [aprssig] Objects on APRS
> > > 
> > > One thing that can be an option though is to contact your
> > nearby iGate
> > > operator and request that they push the posit out for you.
> > > 
> > > Here in the Palm Springs, CA area, my iGate (K6KIT-11)
watches
> > for the
> > > IRLP3180 (AK6E-15) and pushes it out via a single hop
through 
> > > the local
> > > digi (INDIO).
> > > 
> > > Eric J. Goforth, N6GOF
> > > www.APRSDEPOT.com
> > > 
> > > 
> > > -----Original Message-----
> > > From: aprssig-bounces at lists.tapr.org
> > > [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Jim
> > Fuller (N7VR)
> > > Sent: Saturday, April 28, 2007 11:29 AM
> > > To: aprssig at lists.tapr.org
> > > Cc: nwaprssig at nwaprs.info
> > > Subject: [aprssig] Objects on APRS
> > > 
> > > Hi Guys,
> > > 
> > > I would like to remind everyone that IRLP, Voice Repeater,

> > > Etc. Objects
> > > that
> > > are put on an APRS Gateway node are great. But to put them

> > > out when your
> > > only connection is to the APRS-IS system is counter
> > productive. I have
> > > been
> > > noticing a few in the northwest have been doing this, 
> > > thinking an Igate
> > > will
> > > pick them up and put them out. 
> > > 
> > > Hope everyone has fun at Dayton.
> > > 
> > > Jim Fuller
> > > AAR8NY - ARMY MARS
> > > N7VR - http://www.fuller.net/n7vr.html
> > > ARRL Montana Section Emergency Coordinator -
> > http://www.mtares.org
> > > International TCP/IP Gateways Robot Operator --
> > > http://www.ampr-gateways.org
> > > montana.aprs2.net Server Operator -- http://www.mtaprs.net
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > aprssig mailing list
> > > aprssig at lists.tapr.org
> > > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> > > 
> > > _______________________________________________
> > > aprssig mailing list
> > > aprssig at lists.tapr.org
> > > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> > > 
> > 
> 
> 