english:

 

 

                                 

 

     Another modeling option change that will be discussed here is switching between flat and elevated terrain modeling.  As noted earlier, the model assumes flat terrain, i.e., all receptors are assumed to be at the same elevation as the base elevation for the source as the default mode of operation.  If the user wishes to model receptors on elevated terrain, then the TERRHGTS keyword must be included on the CO pathway.  This keyword, which is described in more detail in Section 3.2.3, accepts one of two possible secondary keywords, either FLAT or ELEV.  Their meaning should be obvious.  Note that the input runstream image:

CO TERRHGTS   FLAT

18

has the same effect as having no TERRHGTS keyword at all.  If the user elects to perform FLAT terrain modeling for a particular application, the model will ignore any elevated terrain height information given on the RE pathway.  Processing will continue as flat terrain, and warning messages will be generated to warn the user that elevated terrain heights were present in the file, but ignored for processing.  The advantage of this approach is that if an application is setup for elevated terrain modeling, a simple change of the secondary keyword on the TERRHGTS card from ELEV to FLAT is all that is needed to run the model in flat terrain mode.  The terrain height information does not need to be removed from the input file.

 

151 - 152 - 153 - 154 - 155 - 156 - 157 - 158 - 159 - 160 - 161 - 162 - 163 - 164 - 165 - 166 - 167 - 168 - 169 - 170 - 171 - 172 - 173 - 174 - 175 - 176 - 177 - 178 - 179 - 180 - 181 - 182 - 183 - 184 - 185 - 186 - 187 - 188 - 189 - 190 - 191 - 192 - 193 - 194 - 195 - 196 - 197 - 198 - 199 - 200

 

     Flag of Portugal 

 castellano:     italiano:     

 

 français:    português:  

 

deutsch:

 

  APLICACIONES castellano: DIS CUS DES  RAD   english: DIS CUS DES RAD  

 

 português: DIS CUS DES RAD   italiano:   DIS CUS  DES RAD

 

français:  DIS CUS DES RAD