Received: from hpindck.cup.hp.com by opus.hpl.hp.com with SMTP (1.37.109.8/15.5+ECS 3.3+HPL1.1) id AA17317; Tue, 13 Dec 1994 16:24:48 -0800 Return-Path: <kenb@hpindck.cup.hp.com-DeleteThis> Received: from hpindkb.cup.hp.com by hpindck.cup.hp.com with SMTP (1.37.109.11/15.5+IOS 3.20+cup+OMrelay) id AA188824682; Tue, 13 Dec 1994 16:24:42 -0800 Full-Name: Ken Brown Message-Id: <199412140024.AA188824682@hpindck.cup.hp.com-DeleteThis> To: wind_talk@opus.hpl.hp.com-DeleteThis Subject: Re: Tide Data In-Reply-To: Your message of "Tue, 13 Dec 94 16:14:41 PST." <Pine.3.89.9412131628.A8792-0100000@netcom15> Date: Tue, 13 Dec 94 16:24:41 -0800 From: kenb@hpindck.cup.hp.com-DeleteThis
shrEd wonders:
> Just curious whether anyone actually uses tide data for anything? I
> usually rely upon current data (slack, peak ebb and peak flood times)
> rather than high/low tides. Except for places like Palo Alto, which
> becomes inaccessible, or Third Ave, which sometimes becomes a bit muddy,
> I don't usually use the tide data for anything. Does anyone else?
Well, I'd say that, with the exception of Coyote, CandleStink, and Oyster,
every place I sail on the Peninsula *is* unsailable, or at least prone to
fin-eating sandbars, at some tide levels that occur during the season.
I definitely factor tide level into my choice of launch site. So I'd
cast a vote for making the tide level, as well as current, available.
*******************************************************************************
Ken Brown /\ SnailMail: Hewlett-Packard
kenb@cup.hp.com-DeleteThis /\ ..... /\ 19420 Homestead Road
Voice: (408) 447-3089 //\\ @_/ ..... /\ MS 43LT
Fax: (408) 447-3660 //\\ ./K .... //\\ Cupertino CA 95014
|| l\... //\\ USA
^-~-~^ ||
***************** "Who needs some stupid quote here, anyway?" *****************
This archive was generated by hypermail 2b29 : Mon Dec 10 2001 - 02:28:26 PST