Revision as of 18:32, 4 January 2019 view source Tuflowduncan (talk \| contribs) Bureaucrats, Administrators 1,210 edits →Method ← Older edit		Revision as of 18:33, 4 January 2019 view source Tuflowduncan (talk \| contribs) Bureaucrats, Administrators 1,210 edits →Method Newer edit →
Line 5: =Method= <li>Copy the contents of the '''Module_data\Module_02\2D_Development''' into the '''TUFLOW\model\mi''' folder. This folder contains the following two layers: <b>~~2d_ztin_M02_development_001~~2d_ztin_M02_development_001_R.mid</b>,and <b>2d_ztin_M02_development_001_P.mid</b>. <li>Open the layer '''~~2d_ztin_M02_development_001~~2d_ztin_M02_development_001_R''' within MapInfo and observe the polygon and its attributes. This polygon defines the area within which we wish to alter the zpt elevations. Any points falling within the polygon are used for creating the TIN surface. The attributes of this polygon have been left blank (are set to 0) as the elevations will be defined in a separate layer. <li>Open the layer ''''2d_ztin_M02_development_001_P''' within MapInfo and observe the points and its attributes. These points all have elevations assigned to the ‘Z’ attribute and will be used when generating the TIN. Note that none of the points are snapped to the polygon within the '''2d_ztin_M02_development_001''' layer. The elevations of the polygon’s perimeter will therefore be based on the current zpt values (i.e. the zpt values assigned by any prior commands). Later on in this tutorial, we will specify the command used within the tgc to associate the two GIS layers with each other. <br>

FM Tute M02 MI Define Elevations: Difference between revisions