[OZAPRS] How to stop excessive digipeating?

[Dave Ingram]

Hi all,

I've been looking at some of the SEQ activity this afternoon, and there
are
some strange happenings.

Firstly, why are digipeater beacons set with a path of WIDE,WIDE? Surely
if
you can't hear the digi directly it isn't much use knowing that it is
there?
For example, there is VK4RAI-3, which is in a good location in Ipswich:
2007-10-18 06:59:40 16:59:40R VK4RAI-3>APNU19,WIDE,WIDE Port=1 <UI C
Len=70>:
!2730.13SU15235.50E_IRLP & Echolink Available On 439.325 MHZ Mt Knobby
I can hear this directly.

2007-10-18 06:59:41 16:59:40R VK4RAI-3>APNU19,VK4GME-3*,WIDE Port=1 <UI C
Len=70>:
!2730.13SU15235.50E_IRLP & Echolink Available On 439.325 MHZ Mt Knobby
VK4GME-3 at Griffith Uni has a shot at digipeating it

2007-10-18 06:59:44 16:59:44R VK4RAI-3>APNU19,VK4RTW-3*,VK4GME-3* Port=1
<UI C
Len=70>:
!2730.13SU15235.50E_IRLP & Echolink Available On 439.325 MHZ Mt Knobby
Finally VK4RTW in Toowoomba digipeats again. This is all a big game of
ping-pong (west to east, east to west and then west to east again).

VK4RIL-7, VK4RMM-3, VK4RTW-3, VK4RGO-3 and VK4RAI-3 are doing similar
things
and might not be helped with paths of:
  VK4RGO-3>APNU19,WIDE,WIDE
  VK4RAI-3>APNU19,WIDE,WIDE

VK4RMM-3 is collecting the set with WIDE,WIDE.
VK4RMM-3>APNU19,VK4RTW-3*,VK4GME-3*
VK4RMM-3>APNU19,VK4RTW-3*,VK4RAI-3*
VK4RMM-3>APNU19,VK4RTW-3*,VK4RGO-3*

Is this something that the digi operators can discuss and come to some
arrangement about?


Dave.
-- 
David Ingram (VK4TDI)
Real email: dave at ingramtech dot com
Brisbane, Queensland, Australia
http://www.ingramtech.com/
MGRS: 56J MQ 991583    Maidenhead Grid Square: QG62lm
_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs