StanfordMLOctave/machine-learning-ex6/ex6/easy_ham/0553.a2487df9e3ff8da0521a96...

81 lines
3.5 KiB
Plaintext

From fork-admin@xent.com Sun Sep 8 23:50:39 2002
Return-Path: <fork-admin@xent.com>
Delivered-To: yyyy@localhost.example.com
Received: from localhost (jalapeno [127.0.0.1])
by jmason.org (Postfix) with ESMTP id 3BBC216F1A
for <jm@localhost>; Sun, 8 Sep 2002 23:50:23 +0100 (IST)
Received: from jalapeno [127.0.0.1]
by localhost with IMAP (fetchmail-5.9.0)
for jm@localhost (single-drop); Sun, 08 Sep 2002 23:50:23 +0100 (IST)
Received: from xent.com ([64.161.22.236]) by dogma.slashnull.org
(8.11.6/8.11.6) with ESMTP id g88HOEC03926 for <jm@jmason.org>;
Sun, 8 Sep 2002 18:24:14 +0100
Received: from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
with ESMTP id 8EA012940F0; Sun, 8 Sep 2002 10:21:03 -0700 (PDT)
Delivered-To: fork@example.com
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
by xent.com (Postfix) with ESMTP id C03002940C4 for <fork@xent.com>;
Sun, 8 Sep 2002 10:20:34 -0700 (PDT)
Received: from [192.168.123.100] ([64.173.24.253]) by mta5.snfc21.pbi.net
(iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id
<0H240092BQYV6K@mta5.snfc21.pbi.net> for fork@xent.com; Sun,
08 Sep 2002 10:23:19 -0700 (PDT)
From: James Rogers <jamesr@best.com>
Subject: Re: whoa
In-Reply-To: <m2n0qsr1gf.fsf@maya.dyndns.org>
To: fork@example.com
Message-Id: <B9A05063.D7DA%jamesr@best.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
User-Agent: Microsoft-Entourage/9.0.1.3108
Sender: fork-admin@xent.com
Errors-To: fork-admin@xent.com
X-Beenthere: fork@example.com
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:fork-request@xent.com?subject=help>
List-Post: <mailto:fork@example.com>
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Sun, 08 Sep 2002 00:55:00 -0700
X-Spam-Status: No, hits=-9.2 required=7.0
tests=AWL,DATE_IN_PAST_06_12,EMAIL_ATTRIBUTION,INVALID_MSGID,
IN_REP_TO,KNOWN_MAILING_LIST,QUOTED_EMAIL_TEXT,
SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_ENTOURAGE
version=2.50-cvs
X-Spam-Level:
On 9/8/02 7:38 AM, "Gary Lawrence Murphy" <garym@canada.com> wrote:
> J> ... If you want a region of the globe mapped out to a very
> J> high resolution (e.g. 1-meter), they can scan the area with
> J> aircraft LIDAR and add it to the database, thereby making that
> J> region zoomable to the resolution of the database for that
> J> area.
>
> Can you give us an example of an application where 1-m resolution
> would be worth the considerable expense?
An example: Being able to model RF propagation in three dimensions for a
metro area when deploying wireless networks. By having every single tree
and building detail and similar, you can "see" even tiny dead spots due to
physical blockage and signal attenuation. Overlay this with fiber map data
for yourself and your competitors (when you can glean such data), which is
also useful at this resolution, and you have a very slick way of modeling
existing network deployments in excruciating detail and optimizing further
deployments to maximize coverage and bandwidth. Take that and tie it into a
slick geo-physically aware real-time network monitoring and management
system and you've really got something...
For many applications though, 5-meter data is probably adequate.
-James Rogers
jamesr@best.com