From: Lincoln Peters <sampln@sbcglobal.net>
To: cstevens@gencom.us
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: GIS Update
Date: Thu, 28 Oct 2004 04:54:00 -0000 [thread overview]
Message-ID: <1098923706.26829.53.camel@localhost> (raw)
In-Reply-To: <200410271721.59236.cstevens@gencom.us>
On Wed, 2004-10-27 at 10:21, D. Cooper Stevenson wrote:
> On Wednesday 27 October 2004 05:46, Lincoln Peters wrote:
> > Do you think that this data map nicely to the terrain types in an
> > existing terrain module (plains, forest, desert, mountains, swamp,
> > shallows, sea), or does this call for a new terrain module to be of any
> > real interest? If at this point you're just dealing with landcover, I
> > could create a simplified spin-off of my proposed omniterr.g terrain
> > module toward that end (no coatings would be needed).
>
> Why didn't I think of that?!!?
>
> I think you've hit the nail right on the head. It would certainly be ideal to
> simply have a GIS terrain module that couples seemlessly with the NLCD 92
> data. This would deprecate the need for a conversion script.
I've already modified my "omniterr.g" module so that it is entirely
based on vegetation (I kept the original, of course). I'll see if I can
modify it to handle the different classes of land cover described in the
USGS page.
> Here is the specific landcover specification:
>
> http://landcover.usgs.gov/classes.asp
Looks like a total of 22 terrain types, unless I'm misunderstanding how
it's supposed to work.
> >
> > Elevation data, of course, is a fairly simple matter to import.
> > Although as far as I can tell, it only affects the isometric view code
> > and (sometimes) the fractal percentile terrain generator.
> >
>
> I think you're right. I can see that it will be increasingly important to use
> elevation as a determinate of such factors such as unit speed, engagement
> advantage and "who can see whom."
>
> This is known. The good news is that I think Xconq's engine can be extended to
> use elevation in these ways. I may be out in left field here; Eric or others
> may say, "Xconq already does read elevation."
Actually, there is one other thing I remember that elevation affects:
line-of-sight. I think that it lacks the ability to affect unit speed
or engagement advantage; the best you can do is create a bunch of
additional terrain types to represent different altitudes (way too much
work, if you ask me!).
---
Lincoln Peters
<sampln@sbcglobal.net>
If your happiness depends on what somebody else does, I guess you do
have a problem.
-- Richard Bach, "Illusions"
next prev parent reply other threads:[~2004-10-28 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 5:42 D. Cooper Stevenson
2004-10-27 17:17 ` Lincoln Peters
2004-10-27 17:25 ` D. Cooper Stevenson
2004-10-28 0:54 ` D. Cooper Stevenson
2004-10-28 4:54 ` Lincoln Peters [this message]
2004-10-30 22:15 ` D. Cooper Stevenson
-- strict thread matches above, loose matches on Subject: below --
2004-09-22 2:26 D. Cooper Stevenson
2004-09-22 2:59 ` Eric McDonald
2004-09-22 16:36 ` mskala
2004-10-02 1:29 ` Christopher Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1098923706.26829.53.camel@localhost \
--to=sampln@sbcglobal.net \
--cc=cstevens@gencom.us \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).