To add to Mark's answer, the Surface Storage options available with the Implicit and SWMM solvers in SewerGEMS and CivilStorm provide an option to define with a depth-area curve, but you'll need to enter those values in the table. As you noticed, the Trex and Terrain model tools will populate node ground elevations. There are likely other programs that can extract a cross section from a TIN, which you could use to populate the depth-area table in CivilStorm or SewerGEMS.
↧
Forum Post: RE: Is there a way to model a surface above a structure in StormCAD
↧
Forum Post: RE: Export Shapefile of Network using WaterObjects
Bruce, I will check with some of our developers for ideas on why this is happening. In the meantime, it may help to try creating a smaller demo project for the shapefile export and get things working there first.
↧
↧
Forum Post: Hammer surge control
For surge control of pumping main pipeline , where I can define zero velocity valve and Air cushion valve. Is there any provision is there in Hammer software.
↧
Forum Post: RE: Hammer surge control
Hello, Here is the similar discussion on forum about modeling zero velocity valve in Hammer. About modeling air valves, the below technote you may find useful.
↧
Forum Post: How to name(number) the junctions and pipes to follow the general direction of water flow in WaterGEMS V8i?
I have designed a distribution network in WaterGEMS V8i for which pipe and junction data was imported from a .dxf file. During the import, the junctions (and pipes) were named randomly, where J-2 does not follow J-1. From the point of view of 'designing', this does not matter. But for execution and record-keeping on site, it is desired that J-1 be the first junction of the network just after Reservoir, J-2 be the next junction on line and so on. I understand that while importing data from .dxf, there is no way for WaterGEMS to know how to name the junctions, and thus it names them randomly. However, after the design is complete, WaterGEMS generates additional data - 'flow direction'. So how do I use these flow arrows to rename the junctions and pipes, so that J-1 is first junction after Reservoir and there is at least some order in the naming of remaining junctions? Of course, I am interested in an auto-assign method to avoid manually naming hundreds of junctions.
↧
↧
Wiki Page: Compatibility Chart [TN]
Applies To Product(s): WaterCAD, WaterGEMS, PondPack, StormCAD, SewerCAD, FlowMaster, CulvertMaster, Hammer, SewerGEMS, CivilStorm Version(s): Various Environment: N/A Area: General Subarea: N/A Original Author: Shahzaib Bukhari, Bentley Technical Support Group Compatibility Chart WaterCAD & WaterGEMS XM & V8i Version 08.11.05.61 (SS5) 08.11.04.57 08.11.04.58 (SS4) 08.11.04.50 (SS4) 08.11.03.16 08.11.03.17 08.11.03.19 (SS3) 08.11.02.31 (SS2) 08.11.01.32 (SS1) Date Released 8/4/2014 7/1/2013 5/6/2013 7/8/2011 11/24/2010 10/26/2009 O/S compatibility * = certified Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Note: Windows XP is no longer supported. Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows XP SP3 (32-bit)* Windows 2008 Server R2 (64 bit only)* Windows 2008 Server (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows 7* Windows XP SP2 or later Windows XP SP2 or later (64-bit) Windows Server 2003 SP2 or later Windows Vista Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows Vista SP2* Windows XP SP1/SP2 Windows XP (64 bit) Windows Vista SP0 Windows 2008 Server Windows 7 Supported AutoCAD Versions (*= basic testing only) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit) 2011 (64 bit)* 2011 2010* 2010 2009* Certified MicroStation versions (older versions also supported) 08.11.09.459(SS4) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 08.11.09.xx (SS3) 08.11.07.xx (SS2) 8.11.7.443 (SS2) 08.11.09.xx (SS3) 8.11.7.443 (SS2) 8.11.7.x ArcGIS versions in WTRG 10.2 10.2.1 10.2 10.1 SP1 10.0 SP5 10 SP5 10.1 SP1 9.3.1 SP2 10 (Certified in 10 only) 9.3 10 9.3 9.3 SP1 Version of .NET needed 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 + SP1 PondPack v10 & Pondpack V8i compatibility chart Version 08.11.01.56 08.11.01.54 08.11.01.51 10.01.04.00 Date Released 3/8/2012 12/16/2010 10/26/2009 11/7/2008 O/S compatibility * = certified Windows Vista SP2* Windows XP SP3 (32/64 bit)* Windows XP SP2 or later Windows XP SP2 or later (64 bit) Windows Server 2003 SP2 or later Windows 7 Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3 (32/64 bit)* Windows 7 Windows XP SP2 or later Windows XP SP2 or later (64 bit) Windows Server 2003 SP2 or later Windows Vista SP2* Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3 (32/64 bit)* Windows Vista SP2* Windows XP SP2 or later Windows XP SP2 or later (64 bit) Windows Server 2003 SP2 or later Windows 2008 Server Windows 7 Windows 2008 Server R2 Windows XP SP1-SP3 (32/64 bit)* Windows Vista SP1 (32 bit)* Windows Vista (64 bit) Windows Server 2003 (32/64 bit) Supported AutoCAD Versions ( * = basic testing only) 2012 (32 bit)* 2011 (32 bit)* 2011 2010 2010 2009* N/A Certified MicroStation versions (older versions also supported) 8.11.7.x and 8.11.9.x 8.5.xx.xx /8.11.7.xx 8.11.5.x N/A ArcGIS versions in Pondpack N/A N/A N/A N/A Version of .NET needed 3.5 SP1 3.5 SP1 3.5 SP1 1.1 StormCAD V 8i compatibility chart Version 08.11.05.58 (SS5) 08.11.04.54 (SS4) 08.11.03.83/84(SS3) 08.11.03.77(SS3) 08.11.02.75(SS2) 08.11.02.38(SS2) Date Released 5/8/2015 6/3/2014 7/15/2013 1/7/2013 11/7/2011 12/16/2010 O/S compatibility * = certified Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP* Windows Server 2003* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Wndows Server 2003 x64* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows 8 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows Vista SP2* Windows XP SP3* Windows 7 (32/64 bit)* Windows XP SP2 or later (32/64 bit) Windows Server 2003 SP2 or later Windows Vista Windows 2008 Server (32/64 bit) Windows 2008Server R2 (64 bit only) Supported AutoCAD Versions ( * = basic testing only) 2016 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit) 2011 (32/64 bit) * 2011 2010 2009* Certified MicroStation versions (older versions also supported) SS3 08.11.09.357 (SS3) 08.11.7.443 (SS2) 08.11.09.357 (SS3) 08.11.7.443 (SS2) 8.11.09.357 (SS3) 8.11.7.443 (SS2) 8.11.9.209 (beta) 8.11.5, 8.11.7 Version of .NET needed 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 SewerCAD V8 V8i compatibility chart Version 08.11.05.58 (SS5) 08.11.04.54 (SS4) 08.11.03.84 08.11.03.83 (SS3) 08.11.03.77 (SS3) 08.11.02.75 (SS2) 08.11.02.49 (SS2) 08.11.02.46 (SS2) Date Released 05/08/2015 07/15/2013 07/15/2013 01/17/2013 11/07/2011 12/16/2010 07/01/2010 O/S compatibility * = Certified Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP SP3 (32 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows Server 2003 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP SP3 (32 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows Server 2003 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows Vista SP2 (32/64 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 (32/64 bit) Windows Vista SP0/SP1 (32/64 bit) Windows 2008 Server SP1/SP2 (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows Vista SP2 (32/64 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 (32/64 bit) WindowsVista SP0/SP1 (32/64 bit) Windows 2008 Server SP1/SP2 (32/64 bit) Windows 2008 Server R2 (64 bit only) Supported AutoCAD Versions ( * = basic testing only) 2016 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit) 2011 (32/64 bit) 2011 2010 2011 2010 Certified MicroStation versions (older versions also supported) SS3 08.11.09.357(SS3) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 08.11.09.357(SS2) 08.11.07.443 (SS3) 08.11.07.443 (SS2) 08.11.09.357 (SS3) 8.11.7.x 8.11.7.x Version of .NET needed 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 FlowMaster compatibility chart Version 08.11.01.03 08.11.00.03 08.01.071.00 08.01.068 Date Released 11/14/2009 8/27/2008 3/6/2007 11/10/2006 O/S compatibility * = Certified Windows XP SP3 (32/64 bit)* Windows Vista SP2* Windows XP SP2 or later (32/64 bit) Windows 7 (32/64 bit) Windows Server 2003 SP2 or later (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP* Windows Vista* Windows Server 2003 Windows Server 2003(64bit) Windows XP (64 bit) Windows Vista (64 bit) Windows 7 Windows 2000* Windows 2003* Windows XP (32/64 bit)* Windows Vista (32/64 bit)* Windows 2000* Windows XP (32/64 bit)* Version of .NET needed 2.0 2.0 1.1 1.1 CulvertMaster compatibility chart Version 03.03.00.04 03.02.00.01 03.01.010.00 03.01.009.00 Date Released 11/5/2009 8/11/2008 2/14/2007 12/6/2005 O/S compatibility * = certified Windows Vista SP2* Windows XP SP3 (32/64 bit)* Windows XP SP2 or later (32/64 bit) Windows Server 2003 SP2 or later Windows 2008 Server Windows 7 Windows 2008 Server R2 Windows Server 2003 SP1 or later Windows Server 2003 (64 bit) Windows XP SP2 or later* Windows XP (64 bit) Windows Vista* Windows Vista (64 bit) Windows 2000* Windows Server 2003* Windows XP (32/64 bit)* Windows Vista (32 bit/64 bit)* Windows 2000* Windows XP (32/64 bit)* Version of .NET needed 2.0 2.0 2.0 1.1 Hammer XM & Hammer V8i compatibility chart Version 08.11.05.61 (SS5) 08.11.04.58 08.11.04.58 (SS4) 08.11.04.50 (SS4) 08.11.03.16 08.11.03.17 08.11.03.19 (SS3) 08.11.02.31 (SS2) 08.11.01.32 (SS1) Date Released 8/4/2014 7/1/2013 5/6/2013 7/8/2011 12/7/2010 10/26/2009 O/S compatibility * = certified Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Note: Windows XP is no longer supported Windows 8 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 2008 Server R2 (64 bit only)* Windows 2008 Server (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows 7* Windows XP SP2 or later Windows XP SP2 or later (64 bit) Windows Server 2003 SP2 or later Windows Vista Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows Vista SP2* Windows XP SP1/2 Windows XP (64 bit) Windows Vista SP0 Windows 2008 Windows 7 Supported AutoCAD Versions ( * = basic testing only) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit) 2011 (32/64 bit) 2011 2010* 2010 2009* ArcGIS versions in HAMMER 10.2, 10.2.1 10.2 (build .58 only) 10.1 SP1 10.0 SP5 10.0 SP5 10.1 9.3.1 SP2 10.0 (Certified in 10.0 only) 9.3.1 SP1 10.0 9.3 9.3.1 Certified MicroStation versions (older versions also supported) 08.11.09.459 (SS4) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 08.11.09.357 (SS3) 08.11.07.443(SS2) 08.11.07.443 08.11.07.443 8.11.7.x Version of .NET needed 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 SewerGEMS V8i compatibility chart Version 08.11.05.58 (SS5) 08.11.04.54 (SS4) 08.11.03.83/84 (SS3) 08.11.03.77 (SS3) 08.11.02.75 (SS2) 08.11.02.49(SS2) Date Released 05/08/2015 06/03/2014 07/15/2013 12/19/2012 11/07/2011 12/16/2010 O/S compatibility * = certified Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)* Windows 7, 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP SP3 (32 bit)* Windows Server 2003 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP SP3 (32 bit)* Windows Server 2003 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only) Windows 8 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Win XP SP3* Win 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP0/SP1 (32/64 bit) Windows 2008 Server SP1/SP2 (32/64 bit) Windows 2008 Server R2 (64 bit only) Supported AutoCAD Versions (* = basic testing only) 2016 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit)* 2013 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit) * 2012 (32/64 bit) 2011 (32 bit) 2011 (64 bit)* 2011 2010 Certified ArcMap versions (older versions also supported) 10.3 10.2.2 10.2.1 10.2 10.2 SP1 10.2 10.2 10.1 SP1 10.1 10.0 10.1 10.0 9.3.1 SP2 + 10.0 9.3.x Certified MicroStation versions (older versions also supported) SS3 08.11.09.357 (SS3) 08.11.09.357 (SS3) 08.11.09.357 (SS3) 8.11.7.443 (SS2) 08.11.7.x 08.11.09.209 (beta) 08.11.7.x Version of .NET needed 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 CivilStorm V8i compatibility chart Version 08.11.05.58 (SS5) 08.11.04.54 (SS4) 08.11.03.83/84 (SS3) 08.11.03.77 (SS3) 08.11.02.75 (SS2) 08.11.02.65 (SS2) Date Released 05/08/2015 6/03/2014 7/15/2013 1/17/2013 11/07/2011 12/16/2010 O/S compatibility * = certified Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)* Windows 7, 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit) Windows XP SP3 (32 bit)* Windows Server 2003 (32/64 bit)* Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit)* Windows 7 (32/64 bit)* Windows 8 (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows 8 (32/64 bit) Windows XP SP3 (32 bit)* Windows 7 (32 bit/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows 7 (32/64 bit)* WinXP (SP2 or later) WinXP 64-bit (SP2 or later) Windows Server 2003 SP2 (32/64 bit)* Windows Vista SP0/SP1 (32/64 bit)* Windows 2008 Server SP1/SP2 (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Supported AutoCAD Versions (* = basic testing only) 2016 (32/64 bit 2015 (32/64 bit) 2014 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit) 2012 (32/64 bit) 2011 (32/64 bit) 2011 2010 ArcGIS Integration N/A N/A N/A N/A N/A N/A Certified MicroStation versions (older versions also supported) SS3 08.11.09.357 (SS3) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 8.11.7.X 8.11.9.209 (beta) 8.11.7.X Version of .NET needed 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1
↧
Forum Post: RE: Adding profile of long pipeline into WaterCAD or HAMMER
Hello Ahmed, If this is an existing model, you may need to simplify the model. HAMMER has a tool called Skelebrator which help with this function. There is detailed information on how to use Skelebrator in HAMMER's help documentation. Something like the Series Pipe Merging might be useful for your modeling case. Note that functions in Skelebrator cannot be undone, so you may want to try this on a copy of the model first. If you are just building the model, you could adjust the source file so that there are few pipes that are imported when you do this. Depending on the type of source file, you could also add the source file to a new model as a background file. You could then manually place the 38 junctions you want to model and the pipes. Alternatively, you could import the model data as is, and use Skelebrator to simplify the model. Regards, Scott
↧
Wiki Page: Sorting and relabeling a flextable based on upstream-downstream order
Applies To Product(s): Bentley WaterGEMS, WaterCAD, HAMMER, StormCAD, SewerCAD, SewerGEMS, CivilStorm Version(s): 08.11.XX.XX Environment: N/A Area: Output and Reporting Subarea: Original Author: Jesse Dringoli, Bentley Technical Support Group Problem How do I sort a flextable (such as pipe or conduit) in order of upstream to downstream? Background By default, element flextables are ordered by their element ID, which is based on the order that they were drawn or inserted into the model. Sometimes it is necessary to view a flextable in a different order such as upstream-downstrean, not by ID or label. This also allows the user to use the relabel function to change the labels of elements based on the order in the flextable. Our storm and sewer products have an ability to do so because the flow is always in the same direction. However our water modeling products can have flow in either direction, so the situation is different. Steps to Accomplish StormCAD, SewerCAD, SewerGEMS or CivilStorm If you want to see all elements sorted upstream-downstream at once, first open the flextable. Otherwise if you want to see only a specific path/branch, select the elements in the path that you want to sort, either manually in the drawing or using one of the drawing queries. Right click any column header and choose either "Sort Upstream->Downstream" or "Sort Downstream->Upstream". WaterCAD, WaterGEMS, HAMMER Select the elements in the path that you want to sort, either manually in the drawing or using one of the drawing queries such as "trace downstream" or "find shortest path" (skip to step 3 if you want to sort all elements in the model) Right click in the drawing plan view, choose "Edit Group", then double click the pipe table Ensure that the Hydraulic grade (start) or Hydraulic Grade (stop) field is added to the table Right click the HGL start or stop field and choose either Ascending or Descending, depending if you want to sort upstream or downstream. This of course assumes that you have at least some flow in the pipes you're sorting, so as to have a decrease in HGL as you move downstream. Using user data extensions for greater control over sorted order If you want complete control over order, you could add a numeric User Data Extension field (Tools > User Data Extensions), add that column to your FlexTable, enter a value to specify the order for each row, then sort by that field. Relabeling elements based on a specific order If you need to label your elements based on a specific order, such as upstream-downstream or based on the connection order of each branch of a branched system, first use the above guidance to get your flextable sorted in the order that you want the elements labeled. Filter the table down if needed (based on selection set or query for example) if you only need to relabel certain elements. Next, Right click the Label field's column header, choose Relabel, then choose Renumber as the Relabel Operation. Configure the prefix, suffix, etc and click OK.
↧
Forum Post: RE: How to name(number) the junctions and pipes to follow the general direction of water flow in WaterGEMS V8i?
Hello Pankhuri, The following link should be of some use to you in relabeling the elements in your model: communities.bentley.com/.../9054.sorting-and-relabeling-a-flextable-based-on-upstream-downstream-order Regards, Scott
↧
↧
Forum Post: RE: Export Shapefile of Network using WaterObjects
Jesse, Your idea of creating a demo project was a good one. I added the following event handler to my existing project to see if I could isolate the problem. I ran it and am still coming up with an dbf file where the fields have been created but their contents are all null. I've uploaded the project using your Secure File Upload capability. To run the application, the developer will need to change line 923 of WQWorkstationParentForm.vb so that it contains a valid local folder. Then compile and click on the Create Shapefile button. That will run the following code. As I mentioned, the dbf file is created, the fields within the dbf file are there, but the contents of the records within the dbf file are all null. Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click Dim sShapeFileName As String = "shapefile.shp" Dim sFolder As String = "C:\Users\Bruce\Documents\HydroAnalysis\J392 - Wilmington 2015\watercad\Final\" Dim pathShpFle As String = sFolder + sShapeFileName Dim dbFields(4) As DBFFieldInfo dbFields(0) = New DBFFieldInfo("MonYr", DBFFieldType.String) dbFields(1) = New DBFFieldInfo("Id", DBFFieldType.String) dbFields(2) = New DBFFieldInfo("conc", DBFFieldType.Double) dbFields(3) = New DBFFieldInfo("StrtNd", DBFFieldType.String) dbFields(4) = New DBFFieldInfo("EndNd", DBFFieldType.String) Dim shpWriter As ShapefileDataSourceWriter = New ShapefileDataSourceWriter() If (shpWriter.CreateDataFile(pathShpFle, dbFields, True, ShapeType.Polyline)) Then Dim sMonthYr As String = "jan-74" Dim sId As String = "P-1" Dim c As Double = 0 Dim sNd0 As String = "J-1" Dim sNd1 As String = "J-2" Dim x0 As Double = 0 Dim y0 As Double = 0 Dim x1 As Double = 1 Dim y1 As Double = 1 Dim geoPt0 As GeometryPoint = New GeometryPoint(x0, y0) Dim geoPt1 As GeometryPoint = New GeometryPoint(x1, y1) Dim ln() As GeometryPoint = {geoPt0, geoPt1} shpWriter.AddRecordBegin() shpWriter.WriteFieldData(sMonthYr, "MonYr") shpWriter.WriteFieldData(sId, "Id") shpWriter.WriteFieldData(c, "conc") shpWriter.WriteFieldData(sNd0, "StrtNd") shpWriter.WriteFieldData(sNd1, "EndNd") shpWriter.WritePolylineGeometry(ln) shpWriter.AddRecordEnd() shpWriter.Close() End If End Sub
↧
Forum Post: RE: Export Shapefile of Network using WaterObjects
Hi Bruce, I took a few minutes and looked at your code. I have some comments. I have no tried these ideas so they may or may not work but it's worth a shot. VB.Net has the ability to use either 0 or 1-based arrays. The first thing I noticed is that you are using Dim dbFields(4) As DBFFieldInfo You might want to use using dbFields(5) instead. This way you use indices 0 thru 4. The DBF writer is C# and I'm not sure how would it handle this situation. The second thing I noticed is that you are using whole numbers without decimals for assigning your double variables. I recommend, if only for consistency, to use a true double value like 1.0 or 0.0 instead of 1 or 0. I don't know if this would make a difference or not. I checked our own code for when we export to Shapefile from a FlexTable and we create the DBFFieldInfo a little bit differently. In addition we add an instance of DBFFieldInfo to an ArrayList and then use ToArray() to create the array. In my example here I'll use a generic list instead. Note that this is C# code, not VB.Net code (you should get the gist of the idea though). List fields = new List (); DBFFieldInfo field = new DBFFieldInfo(); field.FieldName = "MonYr"; field.FieldType = DBFFieldType.String; if(field.FieldType == DBFFieldType.String) field.FieldLength = DBFFieldType.MaxTextFieldLength; //You were actually missing this setting. fields.Add(field); You could easily refactor the code above between the creation of the List<> and the Add call into a method. You could pass in the fieldname and type and return the resulting object. Then you could do something like this: fields.Add(Newfield("MonYr", DBFFieldType.String)); Then once your fields are added, you can initialize the writer like this: if (shpWriter.CreateDataFile(pathShpFile, fields.ToArray(), true, ShapeType.Polyline)) ... In this case you would know for sure the exact number of elements are in the array when it is passed to the function. I hope that helps. Kris Culin Bentley Software Development
↧
Forum Post: RE: Export Shapefile of Network using WaterObjects
I don't think you're right about the Visual Basic arrays. That's actually how they're defined. They have zero based indices, but you indicate the maximum index value when you create the array. I took your tip and added assignments for the FieldLength property. I couldn't find that DBFFieldType had a MaxTextFieldLength property, but I arbitrarily assigned it the length 12 and everything's good now. I also changed the concentration field type from DBFFieldType.Double to DBFFieldType.Numeric and that did the trick. I think that what .NET considers to be a double is not the same a double field in a DBF table. I'm not sure. I don't mean to complain, but you might want to consider adding a constructor for DBFFieldInfo that includes the field length. Thanks for your help. Bruce Jacobs
↧
Forum Post: The total catchment area exceeds the total combined area. Select Series 4
Hello, I have a stormCAD model that I can not get to validate or run because every time I do I get the following error: "The total catchment area 2,676.0 ft² exceeds the total combined area 2,676.0 ft². The total area specified in the subareas collection must equal the total catchment area." Once I fix the area called out in the error, by changing the percentage decimal points, and try running the model, another catchment area will claim to have the same error. I have over 60 catchment areas in one model alone. It would appear the only way to enter catchment area information is to give the over all number for the Area (User Defined) in the Geometry portion of the properties box, and then enter a percentage of separate coverage types in the Subareas portion of property box under Runoff. I remember in Select series 3 you could just enter the areas of each coverage type and it would calculate the overall area of the catchment area. It would appear this procedure is no longer valid for Select Series 4 Thanks!
↧
↧
Wiki Page: How to resolve the user notification: Gravity sub-network has more than one outfall or wet-well
Applies To Product(s): Bentley SewerCAD, Bentley SewerGEMS Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Problem Description How can you resolve the following user notification: Gravity sub-network has more than one outfall or wet-well Steps to Resolve A given gravity network in SewerCAD (or SewerGEMS when using the SewerCAD) can only have a single outfall or wet well. Basically only one outfall or wet well is allow per gravity network. When the program detects either multiple outfalls or wet wells, or both an outfall and a wet well, for a single gravity network, this notification is generated. To resolve this issue, you must consolidate the outfalls and/or wet wells in the model on a gravity network drains to a single outfall or a single wet well. You can visually search for where this might be occurring in the model. Another option is to use Network Navigator to find where the issue is occurring. If you are using SewerCAD, to use Network Navigator, go to View > Network Navigator. Select the ">" button and choose Network Review > Find Gravity Sub-network with more than one Outfall or Wet well. **If you are using SewerGEMS with the GVF Convex solver the "Find Gravity Sub-network with more than one Outfall or Wet well" is located under the Network Trace menu in Network Navigator.** Network Navigator will populate with the elements that have more than one outfall or wet well associated with it. To view these in the drawing, select either the "Highlight" or "Select in Drawing" button. This will help locate the areas where the issue is occurring and allow you to edit the drawing. Please note that if you're using SewerGEMS and do not see this query, you will need to upgrade to a later version in order to access. As of the writing of this article, SELECTseries 5 (08.11.05.58) is the latest. Previous versions of SewerGEMS do not have this query. This was largely because the Implicit (SewerGEMS) solver can have multiple outfalls or wet wells, as it uses a dynamic wave solver to solve a network. The GVF-Convex (SewerCAD) solver do not allow for multiple outfalls for a single gravity sub-network.
↧
Forum Post: A User notification message in HAMMER
Dear All, I have an message in my User notification window which I could not understand. It says "The root sought in BISECT is not sufficiently close to the estimated root at time step 400. Please check the initial conditions or try a large timestep." Transient Engine
↧
Forum Post: Difference between running EPS and Transit for the same time period
Dear All, I want to understand the difference of running a transit analysis simulation for any model and the EPS for the same time. In my thought it is the same but what I am getting is not. Please could any one describe in details the difference between those 2 items ?? And when I could use steady state with transit and when I could use EPS with transit ?? Regards,,, Ahmed
↧
Forum Post: SewerGems
Hi Dear, We are working to develop a model for foul network of length about 122 kilometers. We have this licensed software installed in our company Ch2m Middle east UAE. Major issue in the model is the Velocities – we are not able to achieve self-cleansing velocities in 75% of the model pipes with the given design constraints. Just for your information we need minimum 0.70 m/sec velocity. We are not sure how the software is using the design priorities based on the provided design constraints. We will appreciate some more guideline on this. Please could you guide me or point to the right direction to get assistance. Thank you With best Regards Saeed Sent from my iPad
↧
↧
Forum Post: What is the difference between the working phenomena of a vented vessel and air valve
Dear All, What is the difference between the working phenomena of a vented vessel and air valve . It seems that they are exactly the same. Then what is the purpose of this type of vessels.
↧
Forum Post: RE: A User notification message in HAMMER
Hello Ahmed, The following link has information on this issue: communities.bentley.com/.../14752.the-root-sought-in-bisectwin-is-not-sufficiently-closed-to-the-estimated-root-solution-500000076138 In addition to the information in that link, make sure that you have no errors in your initial conditions. If you have questionable results in the initial conditions, that could throw off the transient results as well. HAMMER works best with well-calibrated, stable models. Regards, Scott
↧
Forum Post: RE: A User notification message in HAMMER
This is a generic error that can occur in a number of different situations. It could be due to a data entry error causing the transient results to become unstable. The first step would be to check all of your data input for errors. You could also try setting the transient simulation duration just under the time when the error occurs (time step 400) and view the results for clues as to what is causing the instability. If this doesn't help, please provide your HAMMER version number (see Help > About) and upload your model (either .wtg and .wtg.mdb or .wtg and .wtg.SQLite depending on your version). There are two options for sharing your model files on Communities. If you would like the files to be visible to other members, compress the files into a zip file and upload them as an attachment using the ‘Advanced Reply editor’ before posting. If your data is confidential, you can follow the instructions in the link below to send it to us via Bentley Sharefile. Files uploaded to Sharefile can only be viewed by Bentley. communities.bentley.com/.../7079.be-communities-secure-file-upload
↧