Jump to content

dryad

Members
  • Posts

    4
  • Joined

  • Last visited

dryad's Achievements

  1. Thank you both for the response. With some investigation, I found that 'Edit line properties' gives an error 'The selected polylines are of unequal category' if one open line and one closed line are selected. This was what was stopping me using the method suggested to reassign. Is this by design? On your first point, when importing a shape file, the 'Polyline-attribute header specification' window allows the Elevation setting to be (disabled), so I would suggest that might allow you to automatically identify elevations to ignore. Typically I create elevation and roughness shape files separately. Thanks again for the help, Daniel
  2. When I import a shapefile roughness map (ESRI Shapefile maps) consisting only of roughness lines, mapeditor sets the Z values of the lines to 0. Setting the attribute header for Elevation to (disabled) has no effect, and the line is still assigned an elevation of 0. ESRI shapefiles can't have values of null or 'blank' in numeric fields, so I can't see any way of changing how this works. Alternatively I couldn't find a way to assign all elevations to null after importing. Any suggestions? Have I missed something? Thanks.
  3. Thanks for the response, Morten. The standard states 'The flow model shall be validated for the type of terrain', so this was really the point of my original question. Any further thoughts?
  4. Has either WAsP or WAsP CFD been validated for use as the flow model to determine if a site calibration measurement can be avoided? If so, can someone point to a reference? Thanks
×
×
  • Create New...