public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: mskala@ansuz.sooke.bc.ca
To: "D. Cooper Stevenson" <cstevens@gencom.us>
Cc: Xconq Mailing List <xconq7@sources.redhat.com>
Subject: Re: GIS Update
Date: Wed, 22 Sep 2004 16:36:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0409212244001.28593-100000@diamond.ansuz.sooke.bc.ca> (raw)
In-Reply-To: <1095818641.27063.71.camel@localhost>

On Tue, 21 Sep 2004, D. Cooper Stevenson wrote:
>   1) We are not after satellite photos, we are after "Digital Elevation
> Models."

Well, depending on what you want to do with it.

A DEM is a height field.  It specifies the elevation at a bunch of points.  
If you are building a map that cares about elevation, then you want that
for sure, but you might want other kinds of data too.  For my Antarctic
map I also used the DEM to infer the surface type, because that seemed the
most useful thing to do, but that was something of a kludge adapted
specifically for the Antarctic map.  On other maps there are probably
other kinds of data that can provide better guidance as to the final "bin"
to put the hex in.

For instance, if we had multispectral data (like from a LANDSAT TM image)
we could use that to classify hexes by type of surface terrain - forest,
cropland, water, etc.  That could be useful.  LANDSAT TM is like an image
file with five or six channels of colour information (corresponding to
colour bands from visible into infrared, with some subtleties and
complications) at a resolution where each pixel is 15 to 25 metres.  I
don't know that we could get that for free, but I'm pretty sure we can get
AVHRR data (similar kind of thing, pixels are kilometres in size) for
free.  If we had "line coverages" of vector data for things like rivers,
it might be fun to try to convert those into border or connection terrain,
although the complexity of the algorithms to do that might get pretty
high.  Part of the fun is that there are lots of different kinds of GIS
data out there.

>   2) Because the data is in a raster format (as apposed to a regular
> image file),  I believe it is quite possible to automate the creation of
> new maps and smaller scale views of those maps

One thing to watch out for is that not all DEMs are really rasters.  Some
are just lists of points; others are complicated data structures called
Triangulated Irregular Networks or TINs, and even if they are rasters,
they may not be on the grid or projection you want.  GRASS has some pretty
sophisticated tools for manipulating the data into whatever grid you want,
so that shouldn't be a problem, but it'll be something to keep in mind.
-- 
Matthew Skala
mskala@ansuz.sooke.bc.ca                    Embrace and defend.
http://ansuz.sooke.bc.ca/

  parent reply	other threads:[~2004-09-22  2:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22  2:26 D. Cooper Stevenson
2004-09-22  2:59 ` Eric McDonald
2004-09-22 16:36 ` mskala [this message]
2004-10-02  1:29   ` Christopher Wood
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
2004-10-30 22:15       ` D. Cooper Stevenson

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=Pine.LNX.4.21.0409212244001.28593-100000@diamond.ansuz.sooke.bc.ca \
    --to=mskala@ansuz.sooke.bc.ca \
    --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).