Scenery:Texmapper.cfg File - Revision history

Thomas: /* DEM data */

2010-01-09T22:14:18Z

DEM data

← Older revision		Revision as of 22:14, 9 January 2010
Line 189:		Line 189:
	pri = 1		pri = 1
	}		}

	dem_dir {		dem_dir {
	path = /data/geodata/srtm30		path = /data/geodata/srtm30

Thomas: /* Input data section */

2010-01-09T22:14:09Z

Input data section

← Older revision		Revision as of 22:14, 9 January 2010
Line 154:		Line 154:
	coosys = +proj=utm +zone=30 +datum=WGS84		coosys = +proj=utm +zone=30 +datum=WGS84
	}		}

	image_dir {		image_dir {
	path = /data/geodata/images/lores/		path = /data/geodata/images/lores/

Thomas: /* Flags */

2010-01-09T22:13:41Z

Flags

← Older revision		Revision as of 22:13, 9 January 2010
Line 140:		Line 140:

	shadows = false		shadows = false

	This parameter can be disabled if you are using aerial imagery containing real shadows in them.		This parameter can be disabled if you are using aerial imagery containing real shadows in them.

Thomas at 22:12, 9 January 2010

2010-01-09T22:12:50Z

← Older revision		Revision as of 22:12, 9 January 2010
Line 131:		Line 131:
	=== Flags ===		=== Flags ===

	This section controls some on/off features of the texture mapper. One important feature is the mipmap generation. If you enable this, each texture file will contained downscaled versions of itself to use as [[http://en.wikipedia.org/wiki/Mipmap\|mipmaps]].		This section controls some on/off features of the texture mapper. One important feature is the mipmap generation. If you enable this, each texture file will contained downscaled versions of itself to use as [http://en.wikipedia.org/wiki/Mipmap mipmaps].

	mipmaps = true		mipmaps = true

Thomas at 22:11, 9 January 2010

2010-01-09T22:11:40Z

← Older revision		Revision as of 22:11, 9 January 2010
Line 83:		Line 83:
	tile_size_e = 3648		tile_size_e = 3648

	Now, since the tiles are parallell with the longitude lines, the width varies over the tile. This means that the tile_size_e parameter is only correct at the given ''reference latiude, ref_lat''.		Now, since the tiles are parallell with the longitude lines, the width varies over the tile. This means that the tile_size_e parameter is only correct at the given ''reference latiude, ref_lat''. If no reference latitude is given, we use the equator (0 degrees).

	ref_lat = 50		ref_lat = 50
Line 89:		Line 89:
	In this case, the tile width is correct at 50 degrees latitude. Further north, the tile will be narrower, further south the tile will be wider.		In this case, the tile width is correct at 50 degrees latitude. Further north, the tile will be narrower, further south the tile will be wider.

	The tile start location (south ~~east~~ corner) is given by:		The tile start location (south west corner) is given by:

	start_n = 45.0974		start_n = 45.0974
Line 102:		Line 102:

	For performance, we recommend keeping the tile size around 4km.		For performance, we recommend keeping the tile size around 4km.

			Another way to specify the tiling, is to specify the start coordinates (SW corner) and end coordinates (NE corner) and number of tiles. The tile size is then determined by these parameters and should not be specified. For example

			start_n = 60
			start_e = 10
			end_n = 62
			end_e = 14
			num_tiles_n = 32
			num_tiles_e = 32

			This would make a scenery block of 2x4 degrees with a tile size of about 3.5km. Here we have not given any reference latitude, so in this case at 60 degrees north, the longitudes are half the distance apart relative to the latitude lines and we have made the block twice the size in EW-direction to compensate.

	=== Texture mapper section ===		=== Texture mapper section ===

Thomas: /* Flags */

2010-01-09T21:57:31Z

Flags

← Older revision		Revision as of 21:57, 9 January 2010
Line 120:		Line 120:
	=== Flags ===		=== Flags ===

	This section controls some on/off features of the texture mapper. One important feature is the mipmap generation. If you enable this, each texture file will contained downscaled versions of itself to use as [http://en.wikipedia.org/wiki/Mipmap\|mipmaps].		This section controls some on/off features of the texture mapper. One important feature is the mipmap generation. If you enable this, each texture file will contained downscaled versions of itself to use as [[http://en.wikipedia.org/wiki/Mipmap\|mipmaps]].

	mipmaps = true		mipmaps = true

Thomas: /* Flags */

2010-01-09T21:57:05Z

Flags

← Older revision		Revision as of 21:57, 9 January 2010
Line 126:		Line 126:
	This should normally be left on. It will produce slightly bigger files, but if you don't enable it, you will get frame rate stuttering on certain graphics cards since these mipmaps must be calculated at run-time.		This should normally be left on. It will produce slightly bigger files, but if you don't enable it, you will get frame rate stuttering on certain graphics cards since these mipmaps must be calculated at run-time.

	The next parameter is shadows. If you generate textures from synthetic imagery, you may want to add some shading to the textures. This is done by doing a simple raytrace of a terrain model to add shadows. If you enable this feature, you must also add some elevation data in the data input section. Also remember to set the dem_resolution parameter (see below)		The next parameter is shadows. If you generate textures from synthetic imagery, you may want to add some shading to the textures. This is done by doing a simple raytrace of a terrain model to add shadows. If you enable this feature, you must also add some elevation data in the data input section. Also remember to set the ''dem_resolution'' parameter (see below)

	shadows = false		shadows = false

	This parameter can be disabled if you are using aerial imagery containing real shadows in them.		This parameter can be disabled if you are using aerial imagery containing real shadows in them.

	=== Input data section ===		=== Input data section ===

Thomas at 21:56, 9 January 2010

2010-01-09T21:56:34Z

← Older revision		Revision as of 21:56, 9 January 2010
Line 151:		Line 151:
	}		}

	The first block is the highest priority (pri = 2) and will be used whenever possible. If this data set is not available, or the pixel data is 0,0,0 (black), a lower priority data set is used. The data set is read from the directory /data/geodata/images/aerial and all its subdirectories (recursive = true), and only files with the extension .tif are considered.		The first block is the highest priority (''pri = 2'') and will be used whenever possible. If this data set is not available, or the pixel data is 0,0,0 (black), a lower priority data set is used. The data set is read from the directory ''/data/geodata/images/aerial'' and all its subdirectories (''recursive = true''), and only files with the extension ''.tif'' are considered.

	==== Projections ====		==== Projections ====

Thomas at 21:55, 9 January 2010

2010-01-09T21:55:10Z

← Older revision		Revision as of 21:55, 9 January 2010
Line 163:		Line 163:
	Some data are given as regular .tif or .jpg files with a so called "world" file, with the extension .tfw or .jgw. In this case, the projection is not given, and if you use these types of files, and the coordinate system is not lat/lon, you will need to specify the coosys.		Some data are given as regular .tif or .jpg files with a so called "world" file, with the extension .tfw or .jgw. In this case, the projection is not given, and if you use these types of files, and the coordinate system is not lat/lon, you will need to specify the coosys.

	The format of the coosys parameter is the same as for the PROJ.4 tool, see [[http://trac.osgeo.org/proj/]] for further info.		The format of the coosys parameter is the same as for the PROJ.4 tool, see http://trac.osgeo.org/proj/ for further info.

	==== DEM data ====		==== DEM data ====

Thomas at 21:54, 9 January 2010

2010-01-09T21:54:37Z

← Older revision		Revision as of 21:54, 9 January 2010
Line 163:		Line 163:
	Some data are given as regular .tif or .jpg files with a so called "world" file, with the extension .tfw or .jgw. In this case, the projection is not given, and if you use these types of files, and the coordinate system is not lat/lon, you will need to specify the coosys.		Some data are given as regular .tif or .jpg files with a so called "world" file, with the extension .tfw or .jgw. In this case, the projection is not given, and if you use these types of files, and the coordinate system is not lat/lon, you will need to specify the coosys.

	The format of the coosys parameter is the same as for the PROJ.4 tool, see [http://~~proj~~.~~maptools~~.org/] for further info.		The format of the coosys parameter is the same as for the PROJ.4 tool, see [[http://trac.osgeo.org/proj/]] for further info.

	==== DEM data ====		==== DEM data ====