129
edits
TerraGear Documentation: Difference between revisions
Jump to navigation
Jump to search
→Toolchain
No edit summary |
|||
| Line 78: | Line 78: | ||
| -m ''or'' --minnodes||50||smallest number of nodes to produce. For a mostly flat tile, more nodes are wasteful. | | -m ''or'' --minnodes||50||smallest number of nodes to produce. For a mostly flat tile, more nodes are wasteful. | ||
|- | |- | ||
| -x ''or'' --maxnodes||1000||largest number of nodes to produce. | | -x ''or'' --maxnodes||1000||largest number of nodes to produce.<br /> | ||
For a very complex tile, limiting this will reduce the detail of the resulting mesh. | |||
|- | |- | ||
| -e ''or'' --maxerror||40||While picking points, and we have at least minnodes, but not yet maxnodes, the mesh will be completed if any of the remaining points maximum elevation error drops below this value. | | -e ''or'' --maxerror||40||While picking points, and we have at least minnodes, but not yet maxnodes, the mesh will be completed<br /> | ||
if any of the remaining points maximum elevation error drops below this value. | |||
|- | |- | ||
| -f ''or'' --force|| ||If you have an already fitted work directory, and want to regenerate with different parameters, be sure to use force. | | -f ''or'' --force|| ||If you have an already fitted work directory, and want to regenerate with different parameters, be sure to use force.<br /> | ||
Otherwise, the work directory is checked for updated height data and merged with current data | |||
|} | |} | ||
| Line 105: | Line 108: | ||
| --line-width||50||for line data, this is the width in meters the generated polygons will be. | | --line-width||50||for line data, this is the width in meters the generated polygons will be. | ||
|- | |- | ||
| --line-width-column||''none''||for line data, this optional field can be used to retrieve the width from the database row, under the given column. | | --line-width-column||''none''||for line data, this optional field can be used to retrieve the width from the database row, under the given column.<br /> | ||
If data is present in the row, it overrides the line-width parameter. | |||
|- | |- | ||
| --point-width||500||for point data, this is the 'width' of the square generated. Both width and height will be this large. | | --point-width||500||for point data, this is the 'width' of the square generated. Both width and height will be this large. | ||
|- | |- | ||
| --point-width-column||''none''||for point data, this optional field can be used to retrieve the width from the database row, under the given column. | | --point-width-column||''none''||for point data, this optional field can be used to retrieve the width from the database row, under the given column.<br /> | ||
If data is present in the row, it overrides the point-width parameter. | |||
|- | |- | ||
| --area-type||Default||This string is used to define the type of landclass the generated polygons will be saved under. | | --area-type||Default||This string is used to define the type of landclass the generated polygons will be saved under.<br /> | ||
In tgconstruct, the landclass priorities file is used to determine the priority of each landclass. higher priorities are 'on top' of lower.<br /> | |||
The name given here must match a landclass type in your priorities configuration file. | |||
|- | |- | ||
|} | |} | ||