I am not sure what you mean by "Traffic Hording" .
Are you referring to his station "always winning the race to an APRS-IS server"?
This should NOT be a competition to 'most packets posted on APRS-IS'.
The imnportant point is good consistent coverage.
There are only a few factors that influence this:
1. First to receive
??? Closer to the transmitting station is typically 'first to receive' as the RF reaches it first.
??? Most often intermediate DIGIs would be the largest factor here.? So literally, closest (no DIGI required) would win.
? ? ?? In most cases, this is related to highest, or most coverage area.
??? >>> Another factor here
is overlapping DIGI coverage.? If the TX hits several DIGIpeaters and
?????????? is
retransmitted over the same area, thos in the overlap area may get interference from the others and
?????????? miss part of the packet
2. Quickness to decode
??? If a station is slow to decode (error correction may be a factor), this may give another station time to win the race.
??? However, the error corrcection may make the more packets availble quicker to the APRS-IS server.
??? So you would win when the closer stations doesn't get a clean packet.
3. Internet access to the APRS-IS server(s)
?? a) ISP speed at the IGATE site is probably the biggest factor.
?? b) DNS servers used by your provider and DNS settings may influence how fast they resolve the APRS-IS server.
?????? EXAMPLE: you send noam.aprs2.net and the DNS server sends back an IP address for one of the 'pool' servers.
?? a) Since most clients use a 'pool' address for APRS-IS, it is hard to ensure you have the shortest route to an APRS-IS server.
?????? There are some network settings that may help this, but I have never tried to optrimize this.
As far as "too busy" is concerned, any IGATE is almost defintely RF limited.? If the data is on RF and heard, it can be IGATEd.
