Revision as of 05:16, 4 March 2015 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,786 edits →Input Flags (switches) ← Older edit		Revision as of 05:26, 4 March 2015 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,786 edits →Input Flags (switches) Newer edit →
Line 94: ! width=90% \| Description \|- \|"-cp<cp_file>"\|\| For appending the value from a .xmdf or .dat file to a .mif or .shp file. ~~'Note:~~The ~~requires~~cp_file contains points representing locations where results are extracted from TUFLOW. The file format includes two attributes. The first attribute is a ~~space~~numeric ~~after~~field ~~-cp~~containing ~~and~~the ~~use~~recorded ~~quotes~~value. ifThe ~~spaces~~second ~~existing~~field ~~within~~is a char(100)text field containing the ~~filename~~cp name. The cp_file is also used to find calibration points near any longitudinal profile.' 'Note: requires a space after -cp and use quotes if spaces existing within the filename.' \|- \|"-cpsd<sd>"\|\| The search distance for finding calibration points near a longitudinal profile. Line 100 ⟶ 101: \|"-lpmd<md>"\|\| The distance between LP chainage markers along a longitudinal profile. \|- \|"-lp<lp_file>"\|\| For longitudinal profile output. The lp_file contains polyline(s) representing the lp alignments(s). The first and only attribute within the file is a char(100) containing the lp name. One <lp_name>.csv file for each polyline is produced. ~~'Note: requires a space after -lp and use quotes if spaces existing within the filename.'~~ 'Note: requires a space after -lp and use quotes if spaces existing within the filename.' \|- \|"-fso"\|\| Free Surface Only, sets 1D water levels in pipes to the obvert/soffit level if running full

TUFLOW to GIS: Difference between revisions