From: "D. Cooper Stevenson" <cstevens@gencom.us>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Grid To Hex Conversion
Date: Wed, 01 Dec 2004 18:58:00 -0000 [thread overview]
Message-ID: <200412010532.29152.cstevens@gencom.us> (raw)
In-Reply-To: <20041130183417.73373.qmail@web13123.mail.yahoo.com>
On Tuesday 30 November 2004 18:34, you wrote:
> Hey Coop!
>
> Eric and I have been wondering if you knew what you
> were getting into when you offered to host XConq,
> we've had 2500+ hits in the last two weeks on the
> sf.net site, alone.
I'm thoroughly enjoying Xconq's continued success. I'm really happy to see the
project going so well.
Eric's cranking out new revisions like there's no tomorrow, you've brought in
an artist and are actively pursuing good game design, and Matt's come out in
force with the terrain imaging!
For my part, it turns out that Xconq uses an "oblique cartesian coordinate
system" for displaying tiles. The Xconq manual does an excellent job of
documenting this:
"However, if you take a rectangular array of data and just wrap an area
(terrain ...)) form around it, then everything will appear to be tilting to
the left...
The coordinate system is Cartesian oblique, with the y axis tilted to form a
60-degree angle with the x axis, so it can be difficult to relate typed-in
characters to the final appearance."
This means exactly what it says: I you try to overlay a rectangular land use
grid over Xconq it's going to lean to the left. A screen image of what this
looks like upon request. The solution is to "...have your program map the
cell at x, y in the rectangular array to x - y / 2, y before writing."
I continue to work on this. Here's some links to give you a better idea.
Here's a link to the input file. Each number represents a hex on the Xconq
map. "42," for example, represents a hex of forest type I believe:
http://wiki.xconqgis.org/map_files/landcover_ascii.txt
Here's the script that converts from the input file to the Xconq file:
http://wiki.xconqgis.org/map_files/ascii_to_xconq.sh
Here's the output:
http://wiki.xconqgis.org/map_files/earth-gis.g
On the plus side, I have found a comprehensive GIS Landcover, DEM, and road
dataset for the entire globe!
Here it is:
http://www.mapability.com/index1.html?http&&&www.mapability.com/info/vmap0_index.html
And here for more information:
http://earth-info.nga.mil/publications/vmap0.html
By the way, the 3D work based on the global VMAP0 data was already written for
us a' la FlightGear:
http://www.terragear.org/docs/vmap0/
Note that global VMAP1 data (1:250,000) scale is declasiffied but is not yet
completely available for download:
http://www.mapability.com/index1.html?http&&&www.mapability.com/info/vmap1_index.html
-Coop
> Anyway, I had a new idea for a
> poll:
[snip]
Okay! I'll post tomorrow!
-Coop
next parent reply other threads:[~2004-12-01 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041130183417.73373.qmail@web13123.mail.yahoo.com>
2004-12-01 18:58 ` D. Cooper Stevenson [this message]
2004-12-03 3:01 ` Eric McDonald
[not found] <Pine.LNX.4.21.0411111834140.11520-100000@diamond.ansuz.sooke.bc.ca>
2004-11-12 5:17 ` 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=200412010532.29152.cstevens@gencom.us \
--to=cstevens@gencom.us \
--cc=elijahmeeks@yahoo.com \
--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).