Comments on: GAT - Ground Altitude File

By: Fabs

Fabs — Sat, 14 Jan 2012 07:21:43 +0000

Shinryo makes a lot of sense though. In my project I am reading it as an unsigned int. Remember that the format is little-endian, so there is no difference between reading an int and a byte unless the number represented grows larger than 255.

By: nevelis

nevelis — Sun, 02 Oct 2011 20:21:42 +0000

@Shinryo - the last 3 bytes are probably just padding for alignment.

By: Shinryo

Shinryo — Tue, 22 Feb 2011 10:42:30 +0000

Is the last header information really correct with 3 bytes? Kinda hard to believe. If I’m not wrong, the tile type should be at least unsigned short, resulting the last value also beeing a short value. But as far as this weird format goes, I would even say that the tile type is an unsigned long.

By: Ximo(Offline)

Ximo(Offline) — Mon, 02 Oct 2006 10:49:51 +0000

Thanks, i’ll fix it in a minute

By: VCL

VCL — Sun, 01 Oct 2006 18:56:59 +0000

And the ‘???’ at offset 17 is 3 bytes, not 4 bytes.

By: VCL

VCL — Wed, 14 Jun 2006 18:44:03 +0000

I believe we have a more correct specification of the GAT file format, at http://www.openkore.com/wiki/index.php/Field_file_format
I’m not sure whether your description of the first 4*4 bytes in the Tiles structure is more accurate than ours, but I’m pretty sure that our description (and the offset) of the type field is more accurate, based on the tests I’ve done.