Is there a possibility to set the manhole floor level X below the lowest connected invert? That would be great!
Is there a possibility to set the manhole floor level X below the lowest connected invert? That would be great!
You should be able to do this with a nested IIF statement. Essentially you would have the following ranges:-
Range 1: V<2m/s OR D*V<3m2/s
Range 2: Partial damage: V>2m/s AND 3m2/s<D*V<7 m2/s
Range 3: Destroyed: V>2m/s AND D*V>7 m2/s
IIF(Range 1, No Damage, IIF(Range 2, Partial Damage, IIF(Range 3, Destroyed, Other)))
Each range would need to be defined in the IIF statement.
Is there an SQL term that gives the genuine subcatchment (polygon) area? I am trying to write an audit SQL that identifies all subcatchments where the total runoff area is greater than the total subcatchment area, but I want to use the genuine area of the subcatchment - not the value which has been entered in the "total area" field (which may not equal the actual area)? So something along the lines of:
CLEAR SELECTION;
Subcatchment.area < area_absolute_1 + area_absolute_2 + ... + area_absolute_12
As an unrelated second query, I am also trying to write an SQL to identify all objects in the model which contain a specific flag - "OP" (optioneering). So far, I have:
CLEAR SELECTION;
SELECT FROM [All Nodes] WHERE flags.value="OP";
SELECT FROM [All Links] WHERE flags.value="OP";
SELECT FROM [Subcatchment] WHERE flags.value="OP"
For the rest of the object types, would I have to add new lines for each object type? Or are there any other group terms available, along the lines of [All Polygons], [All Lines] or even simply [All Objects]?
Last edited by Jason_Kulsdom; September 3, 2018 at 08:33 AM. Reason: second query added
Does anyone use a query to set the manhole floor elevations by means of its connecting conduit? If so, I'd be very interested. Thanks!
I know that there is a quirk with ICM, whereby if you select a few pipes and use the inference to interpolate invert levels, but at the same time you do not select the intermediate nodes, then the chamber floor level of those nodes will not be updated based on the connected pipe invert levels, despite them still being flagged #D. This issue can be avoided by making sure you include all intermediate nodes before using the inference. Or it can be resolved by changing the chamber floor flags away #D, then back to #D. Or just be validating the model, at which point all fields flagged #D will re-calculate themselves.
Hi,
Is there an SQL query to split a long conduit by adding nodes with equal intervals?
Thank you!