[aprssig] Weather Station Path/Rate Recommendations

[Mark Cheavens]

Could be a bit that reports if the station is "smart" or "dumb".

Mark
KC5EVE
At 02:11 PM 1/20/2009, you wrote:
>The problem:
>
>I'm a meteorologist that needs to know the conditions at station XYZ.
>I look it up, and see it hasn't reported in 25 minutes. Does this
>mean...
>
>1. the station does not have "smart weather reporting"?
>
>2. the station has "smart weather reporting" and conditions are stable?
>
>3. the station has "smart weather reporting" and conditions have
>changed, but the report was lost in transit due to channel congestion
>or other factor unrelated to weather?
>
>4. the weather at XYZ got so bad so suddenly the station was blown
>way, washed away, or otherwise trashed?
>
>You can't use the absence of data to make decisions unless you have a
>consistent reporting algorithm and completely reliable data delivery.
>Since neither is possible in the world of APRS, "smart weather
>reporting" is dumb ;-)
>
>Steve
>
>On Jan 20, 2009, at 3:00 PM, Steve Noskowicz wrote:
>
> >
> >
> >> 30 minutes is too slow for most situations. ...
> >> for other types of weather ...rates of five minutes are
> >> desired by many ...
> >
> > Sounds obvious to me.  This suggests a Wx station "Smart Beacon"
> > algorithm.  Wx condition change rate handled just like vehicle speed.
> >
> > No change -> 30 min _or more_
> > Rapid change -> 5 min.
> >
> > 73, Steve, K9DCI
> >
> >
> >
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
>
>
>_______________________________________________
>aprssig mailing list
>aprssig at tapr.org
>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig