- DOH! I knew that. I remember testing that now. I had recently looked at my General Setting and specifically the range and let it direct me down the wrongMessage 1 of 18 , Oct 3, 2011View SourceDOH! I knew that. I remember testing that now. I had recently looked at my General Setting and specifically the range and let it direct me down the wrong thought.Thanks!Fred, N7FMHFrom: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Monday, October 03, 2011 13:30
Subject: Re: [aprsisce] TCP/IP Local Server?
On 10/3/2011 11:52 AM, Fred Hillhouse wrote:
> I have APRSIS32 set for a/75/-168/15/-50 which is basically North America.
> My client sends r/43/-71.5/1000. I thought this should limit the view in my
> clients to 100 miles. I am seeing packets from further out than expected.
> This is one example: WD8GEO-9 at ~500 from the client's filter parameter.
Your r/... filter is for 1000 kilometers. The 1/10 mile thing in
Configure / General's Range is an APRSISCE/32 convenience for ... well,
ME which is who I wrote the thing for back when that was done. See the
first entry at http://www.aprs-is.net/javaprsfilter.aspx All ranges in
the raw APRS-IS filters are in kilometers.
> Now that I have recently added calculating the direction and distance this
> has become more apparent. I had not really looked at this before. I also had
> a shorted range in APRSIS32 previously.
> Is APRSIS32 using my client filter within its own filter currently?
Yes, it should be. If you correct it as described above and it still
gives you stuff that's far away, please let me know so I can look into
it. Also, you can test your filters with Control-G in the server and
see what your client should be seeing. You'll see a dramatic difference
between r/..../1000 and r/..../160 (100 miles as kilometers).
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32