WORLD.DAT - Revision history

Spike: /* Relationship to Real World Geography */

2014-08-16T15:58:39Z

Relationship to Real World Geography

← Older revision		Revision as of 15:58, 16 August 2014
Line 39:		Line 39:

	A Y coordinate value of 720 (hex: D0 02) corresponds to 90°S latitude (the South Pole); a Y coordinate value of -720 (hex: 30 FD) corresponds to 90°N latitude (the North Pole).		A Y coordinate value of 720 (hex: D0 02) corresponds to 90°S latitude (the South Pole); a Y coordinate value of -720 (hex: 30 FD) corresponds to 90°N latitude (the North Pole).

			The coordinate system used in EU and TFTD is a form of geodetic coordinate system [http://en.wikipedia.org/wiki/Geodetic_coordinates].

	== Texture / Terrain Type ==		== Texture / Terrain Type ==

Hobbes at 04:32, 23 July 2013

2013-07-23T04:32:53Z

← Older revision		Revision as of 04:32, 23 July 2013
Line 85:		Line 85:
	*[[TEXTURE.DAT]]		*[[TEXTURE.DAT]]
	[[Category:Game Files]]		[[Category:Game Files]]
			[[Category:Enemy Unknown/UFO Defense]]

Zaimoni at 07:33, 23 August 2012

2012-08-23T07:33:51Z

← Older revision		Revision as of 07:33, 23 August 2012
Line 10:		Line 10:
	! Offsets !! Meaning !! Values		! Offsets !! Meaning !! Values
	\|-		\|-
	\| 0-1 \|\| First X coordinate \|\| 0 - 2879		\| 0-1 \|\| First X coordinate/longitude \|\| 0 - 2879
	\|-		\|-
	\| 2-3 \|\| First Y coordinate \|\| -720 - 720		\| 2-3 \|\| First Y coordinate/latitude \|\| -720 - 720
	\|-		\|-
	\| 4-5 \|\| Second X coordinate \|\| 0 - 2879		\| 4-5 \|\| Second X coordinate/longitude \|\| 0 - 2879
	\|-		\|-
	\| 6-7 \|\| Second Y coordinate \|\| -720 - 720		\| 6-7 \|\| Second Y coordinate/latitude \|\| -720 - 720
	\|-		\|-
	\| 8-9 \|\| Third X coordinate \|\| 0 - 2879		\| 8-9 \|\| Third X coordinate/longitude \|\| 0 - 2879
	\|-		\|-
	\| 10-11 \|\| Third Y coordinate \|\| -720 - 720		\| 10-11 \|\| Third Y coordinate/latitude \|\| -720 - 720
	\|-		\|-
	\| 12-13 \|\| Fourth* X coordinate \|\| 0 - 2879		\| 12-13 \|\| Fourth* X coordinate/longitude \|\| 0 - 2879
	\|-		\|-
	\| 14-15 \|\| Fourth* Y coordinate \|\| -720 - 720		\| 14-15 \|\| Fourth* Y coordinate/latitude \|\| -720 - 720
	\|-		\|-
	\| 16-19 \|\| Terrain Type/Texture \|\| 0-12		\| 16-19 \|\| Terrain Type/Texture \|\| 0-12

Volutar: Undo revision 36145 by MikeTheRed (talk) longitude=x latitude=y

2012-08-23T06:37:45Z

Undo revision 36145 by MikeTheRed (talk) longitude=x latitude=y

← Older revision		Revision as of 06:37, 23 August 2012
Line 1:		Line 1:
	The original XCOM file is 13320 bytes long, while TFTD is 14660 bytes long. However, each uses the same 20-byte record format giving the original 666 entries and TFTD 733 entries. This file describes the terrain on the geoscape screen using quadrilateral polygons and triangles.		The original XCOM file is 13320 bytes long, while TFTD is 14660 bytes long. However, each uses the same 20-byte record format giving the original 666 entries and TFTD 733 entries. This file describes the terrain on the geoscape screen using quadrilateral polygons and triangles.

	The first 16 bytes of file contain the points for the polygon. 4 sets of 2 short (2-byte) integers, designating the 'X' and 'Y' coordinate (or latitude ~~and longitude~~ if you prefer). If the last set has an x value of -1 then it is to be rendered as a triangle, otherwise it is a quad.		The first 16 bytes of file contain the points for the polygon. 4 sets of 2 short (2-byte) integers, designating the 'X' and 'Y' coordinate (or longitude and latitude respectively, if you prefer). If the last set has an x value of -1 then it is to be rendered as a triangle, otherwise it is a quad.

	The last 4 bytes in the record contain the terrain type. This could be a long integer or 2 short integers as the last 2 bytes in each record are 0.		The last 4 bytes in the record contain the terrain type. This could be a long integer or 2 short integers as the last 2 bytes in each record are 0.
Line 32:		Line 32:
	== Relationship to Real World Geography ==		== Relationship to Real World Geography ==

	As the 2880 possible ~~latitude~~ values range from 0 to 2879 (hex: 3F 0B) and the ~~longitude~~ values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)		As the 2880 possible longitude values range from 0 to 2879 (hex: 3F 0B) and the latitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)

	This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).		This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).

MikeTheRed: Thanks but longitude is first in the file

2012-08-22T15:07:43Z

Thanks but longitude is first in the file

← Older revision		Revision as of 15:07, 22 August 2012
Line 1:		Line 1:
	The original XCOM file is 13320 bytes long, while TFTD is 14660 bytes long. However, each uses the same 20-byte record format giving the original 666 entries and TFTD 733 entries. This file describes the terrain on the geoscape screen using quadrilateral polygons and triangles.		The original XCOM file is 13320 bytes long, while TFTD is 14660 bytes long. However, each uses the same 20-byte record format giving the original 666 entries and TFTD 733 entries. This file describes the terrain on the geoscape screen using quadrilateral polygons and triangles.

	The first 16 bytes of file contain the points for the polygon. 4 sets of 2 short (2-byte) integers, designating the 'X' and 'Y' coordinate (or longitude ~~and latitude respectively,~~ if you prefer). If the last set has an x value of -1 then it is to be rendered as a triangle, otherwise it is a quad.		The first 16 bytes of file contain the points for the polygon. 4 sets of 2 short (2-byte) integers, designating the 'X' and 'Y' coordinate (or latitude and longitude if you prefer). If the last set has an x value of -1 then it is to be rendered as a triangle, otherwise it is a quad.

	The last 4 bytes in the record contain the terrain type. This could be a long integer or 2 short integers as the last 2 bytes in each record are 0.		The last 4 bytes in the record contain the terrain type. This could be a long integer or 2 short integers as the last 2 bytes in each record are 0.
Line 32:		Line 32:
	== Relationship to Real World Geography ==		== Relationship to Real World Geography ==

	As the 2880 possible ~~longitude~~ values range from 0 to 2879 (hex: 3F 0B) and the ~~latitude~~ values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)		As the 2880 possible latitude values range from 0 to 2879 (hex: 3F 0B) and the longitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)

	This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).		This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).

Davorian: Correcting longitude/latitude terminology (get it the right way around!)

2012-08-17T12:52:17Z

Correcting longitude/latitude terminology (get it the right way around!)

← Older revision		Revision as of 12:52, 17 August 2012
Line 1:		Line 1:
	The original XCOM file is 13320 bytes long, while TFTD is 14660 bytes long. However, each uses the same 20-byte record format giving the original 666 entries and TFTD 733 entries. This file describes the terrain on the geoscape screen using quadrilateral polygons and triangles.		The original XCOM file is 13320 bytes long, while TFTD is 14660 bytes long. However, each uses the same 20-byte record format giving the original 666 entries and TFTD 733 entries. This file describes the terrain on the geoscape screen using quadrilateral polygons and triangles.

	The first 16 bytes of file contain the points for the polygon. 4 sets of 2 short (2-byte) integers, designating the 'X' and 'Y' coordinate (or latitude ~~and longitude~~ if you prefer). If the last set has an x value of -1 then it is to be rendered as a triangle, otherwise it is a quad.		The first 16 bytes of file contain the points for the polygon. 4 sets of 2 short (2-byte) integers, designating the 'X' and 'Y' coordinate (or longitude and latitude respectively, if you prefer). If the last set has an x value of -1 then it is to be rendered as a triangle, otherwise it is a quad.

	The last 4 bytes in the record contain the terrain type. This could be a long integer or 2 short integers as the last 2 bytes in each record are 0.		The last 4 bytes in the record contain the terrain type. This could be a long integer or 2 short integers as the last 2 bytes in each record are 0.

Davorian: /* Relationship to Real World Geography */

2012-08-17T12:51:13Z

Relationship to Real World Geography

← Older revision		Revision as of 12:51, 17 August 2012
Line 32:		Line 32:
	== Relationship to Real World Geography ==		== Relationship to Real World Geography ==

	As the 2880 possible ~~latitude~~ values range from 0 to 2879 (hex: 3F 0B) and the ~~longitude~~ values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)		As the 2880 possible longitude values range from 0 to 2879 (hex: 3F 0B) and the latitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)

	This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).		This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).

MikeTheRed: /* Relationship to Real World Geography */

2009-11-21T01:13:35Z

Relationship to Real World Geography

← Older revision		Revision as of 01:13, 21 November 2009
Line 32:		Line 32:
	== Relationship to Real World Geography ==		== Relationship to Real World Geography ==

	As the 2880 possible latitude values range from 0 to 2879(hex: 3F 0B) and the longitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30").		As the 2880 possible latitude values range from 0 to 2879 (hex: 3F 0B) and the longitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30"). (2880 = 360 x 8, and 720 = 90 x 8.)

	This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).		This implies that, at the equator, each possible map location on the Geoscape occupies a square that is 60 nautical miles (111 kilometres, 69 statute miles) on its side, or an area of 4,761 square miles / 12,321 square kilometres. This area would of course reduce with North or South latitude as you move away from the equator (and also the shape of the area will become progressively less square).

Zombie: /* Texture / Terrain Type */ Converted table into gallery of images.

2009-07-19T02:14:32Z

Texture / Terrain Type: Converted table into gallery of images.

← Older revision		Revision as of 02:14, 19 July 2009
Line 65:		Line 65:
	Although TFTD has three choices of underwater depth that can be associated with any given mission (plus a forth "depth" for surface missions), that value is not derived from this file. Most likely it's taken from the [[LOC.DAT]] record that points to the mission in concern.		Although TFTD has three choices of underwater depth that can be associated with any given mission (plus a forth "depth" for surface missions), that value is not derived from this file. Most likely it's taken from the [[LOC.DAT]] record that points to the mission in concern.

	{\|		<gallery widths="400" heights="225">
	~~\| [[~~Image:xcom_render2.gif\|~~360px]]~~		Image:xcom_render2.gif\|Rendering of the data in WORLD.DAT for the original XCOM. The colors are obtained by using offset 16-19 for each record. Click on the image to see the exact color key, generally speaking though it goes bright green to dark green for 0-5, and dark yellow to white for 6 - 12. Value 11 however is not used anywhere in the map.
	\|		Image:tftd_render.gif\|Rendering of the data in WORLD.DAT for TFTD. Colors again are obtained by using the same offset as before. They go from blue to white for 0 to 12.
	Rendering of the data in WORLD.DAT for the original XCOM. The colors are obtained by using offset 16-19 for each record. Click on the image to see the exact color key, generally speaking though it goes bright green to dark green for 0-5, and dark yellow to white for 6 - 12. Value 11 however is not used anywhere in the map.		</gallery>
	\|-
	~~\| [[~~Image:tftd_render.gif\|~~360px]]~~
	\|
	Rendering of the data in WORLD.DAT for TFTD. Colors again are obtained by using the same offset as before. They go from blue to white for 0 to 12.
	\|}

	<i>TFTD seems to have overlapping polygons at places whereas XCOM didn't (exception to the poles, which is probably because these polygons are rendered to a sphere, not a flat surface).</i>		<i>TFTD seems to have overlapping polygons at places whereas XCOM didn't (exception to the poles, which is probably because these polygons are rendered to a sphere, not a flat surface).</i>

Spike: fixing heading levels

2008-12-07T01:14:55Z

fixing heading levels

← Older revision		Revision as of 01:14, 7 December 2008
Line 30:		Line 30:
	<small><nowiki>*</nowiki> As mentioned above, the fourth coordinate could be (-1, 0) denoting a triangle</small>		<small><nowiki>*</nowiki> As mentioned above, the fourth coordinate could be (-1, 0) denoting a triangle</small>

	=== Relationship to Real World Geography ===		== Relationship to Real World Geography ==

	As the 2880 possible latitude values range from 0 to 2879(hex: 3F 0B) and the longitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30").		As the 2880 possible latitude values range from 0 to 2879(hex: 3F 0B) and the longitude values range from -720 to 720, the resulting map could be said to have a spatial resolution of one-eighth of a degree, both in latitude and in longitude (0.125° or 00°07'30").
Line 40:		Line 40:
	A Y coordinate value of 720 (hex: D0 02) corresponds to 90°S latitude (the South Pole); a Y coordinate value of -720 (hex: 30 FD) corresponds to 90°N latitude (the North Pole).		A Y coordinate value of 720 (hex: D0 02) corresponds to 90°S latitude (the South Pole); a Y coordinate value of -720 (hex: 30 FD) corresponds to 90°N latitude (the North Pole).

	=== Texture / Terrain Type ===		== Texture / Terrain Type ==

	The final value in each record points to the [[TEXTURE.DAT\|texture type]] to be displayed for that polygon. It also serves to determine the terrain type used when you start a battle in that area.		The final value in each record points to the [[TEXTURE.DAT\|texture type]] to be displayed for that polygon. It also serves to determine the terrain type used when you start a battle in that area.