Revision as of 11:24, 15 October 2015 view source Par (talk \| contribs) Bureaucrats, Administrators 1,003 edits No edit summary ← Older edit		Revision as of 13:24, 14 March 2017 view source Teegan.Burke (talk \| contribs) Bureaucrats, Administrators 430 edits No edit summary Newer edit →
Line 46: \|"-shp"\|\| The output format will be the ArcGIS Shapefile format. This can be opened directly in ArcMap, QGIS or SAGA (and most GIS software) \|- \|"-vector" or "-arrows"\|\| The output will contain arrows as polygons to display vector data (eg. velocities and unit flows) in GIS. Must be used with the -mif or -shp option. \|- \|"-t<output time>"\|\| Converts the data at the specified timestep, for example -t2 to convert output time 2 hours. If this switch is omitted the utility will display a list of available times and prompt for an input. Use -t99999 or -max to convert the maximums. Line 54: \|"-max" or "-t99999"\|\| The maximums will be converted. The maximums must have been written to be able to convert using the -max or -t99999 switch. See the .tcf file command (Store Maximums and Minimums == ON MAXIMUMS ONLY). \|- \|"-sf<scale factor>"\|\| Scale factor to scale the size of the arrows. The default is sf = 1, which means ~~either:~~the cell size of the first 2D domain in the .tcf file is equivalent in length to an arrow of 1m/s for _V.dat files or 1m<brsup>3</sup>/s for _q.dat files. * if grid is not specified the cell size of the first 2D domain in the .tcf file is equivalent in length to an arrow of 1m/s for _V.dat files or 1m<sup>3</sup>/s for _q.dat files. * if grid is specified, the grid <dist> value is used instead of the cell size of the first 2D domain to scale the arrows.<br>For example, if the first 2D domain has a cell size of 10m, by default, a 1m/s velocity arrow will be 10m long. If sf0.5 or grid5, is specified the 1m/s velocity arrow will be 5m long. \|- \|"-2dm <.2dm file>"\|\| To explicitly specify a .2dm file. By default TUFLOW_to_GIS assumes the .2dm file has the same name as the .dat file. Must be a space between -2dm and “<2dm_file>”. Line 177 ⟶ 175: <li><tt>TUFLOW_to_GIS.exe -shp -vector -grid2 -b -t2 M01_5m_003_q.dat</tt></li> <u>Description:</u> Convert to a ArcGIS shapefile ("-shp"), using vector outputs ("-vector") on a regular 2 metre grid ("-grid2") using batch mode ("-b") and converting at time 2 hours ("-t2") for the unit flow results '''M01_5m_003_q.dat'''.<br> * Convert output time 2 to a MapInfo vector file on a regular grid of 4m spacing:<br> <li><tt>TUFLOW_to_GIS.exe -mif -vector -sf0.5 -grid4 -b -t2 -typeV M01_5m_003.xmdf t</tt></li> <u>Description:</u> Convert to a MapInfo format ("-mif"), using vector outputs ("-vector") on a regular 4 metre grid ("-grid4") and half-size arrows ("-sf0.5"), using batch mode ("-b") and converting at time 2 hours ("-t2") for the velocity results '''M01_5m_003.xmdf'''.<br> == Calibration Points and Longitudinal Profiles ==

TUFLOW to GIS: Difference between revisions