AVwater New Features at Version 3.3b

 

1.         Modification to the |Find and Zoom| tool in the {CEDRA-DataFrame-Tools-2} toolbar for ArcGIS users.  This tool has been modified to process all active layers.  Previously, the tool would process only 1 active layer.  Now, the user is to able to select features from all of the active layers based upon an attribute query.  There is no limit to the number of active layers that can be processed.

 

2.         Modification to the |Find and Zoom| tool in the {CEDRA-DataFrame-Tools-2} toolbar for ArcGIS users.  A new parameter called Custom Query has been added to the multi-input dialog box that is presented by this tool.  Using this new parameter the user is able to build compound query statements using the syntax employed by the ArcMap [Select By Attributes] command.  When this parameter is filled in (that is, a non-blank) it supercedes the Query String parameter.  That is to say, the string entered for the Custom Query parameter is processed first, provided it is a non-blank string.

 

3.         Modification to the Line 8 tool |PT SLOP| to allow the user the option of selecting a baseline in which the newly created line will be trimmed to.  To do so, the user should first select the baseline feature (this must be a line feature), after which, the tool is selected.  At this point the tool operates as before.  Once the line has been established the tool trims the newly created line to the intersection with the baseline feature.  Since the line is trimmed to the intersection with the baseline, the distance which is prompted for in the multi-input dialog box is used only to set the initial direction of the line.  The actual length of the line is based upon the location of the intersection.

 

4.         Modification to the Line 8 tool |PT SLOP| to allow the user the option of deleting the last line that was created.  Once a line has been created a new parameter will appear at the bottom of the multi-input dialog box called Delete Feature Just Created (Y=yes, N=no).  Selecting the Yes option in response to this parameter will result in the last line that was created being deleted.  In so doing, should the user enter incorrect data, the user is able to delete the line and repeat the data entry process.

 

5.         Modification to the [Import Points] command to allow the user to specify whether the point numbers found in the file being processed are purely numeric or alphanumeric.  A new parameter called Alphanumeric Point Numbers (Y=yes, N=no): has been added to the multi-input dialog box, which is posed by the command.  Selecting the Yes option denotes that the point numbers are alphanumeric (BL-4, X-45 and so forth), while the No option indicates that the point numbers are purely numeric (1, 2, 3, etc.).  If the point numbers are alphanumeric, the point number will be stored in the PNTstr field, while if the point numbers are numeric they will be stored in the PNT field.  Additionally, if the point numbers are alphanumeric, the value zero will be stored in the PNT field, while if the point numbers are numeric a single blank character will be stored in the PNTstr field.

 

6.         Modification to the CEDRA-DataEditor extension, for ArcGIS users.  The user is now able to create multi-column dialog boxes with or without sub-columns within a column.  Previously, the user could only create a series of single column dialog boxes.  Now, the user is able to create a multi-column dialog box with a maximum of 50 attributes in the dialog box.  To create a multi-column dialog box, the user should employ the multi-column commands.  Note, the user is able to define single and multi-column dialog boxes in a single Theme Attribute Data File (themes.txt).

 

7.         Modification to the CEDRA-DataEditor extension, for ArcGIS users.  If the user makes a pick that results in only one feature being found, the Edit Features Attribute Tool will bypass the traditional feature confirmation message box and immediately display the dialog box containing the attributes which can be edited.  However, if two or more features can be found, the tool operates as before.

 

AVwater New Features at Version 3.3a

 

1.         Modification to the Point 7 command |POINT TICKS| to provide the user the ability to break the selected feature(s), rather than create point features.  Under this mode, the selected feature(s) are broken at the locations where the point features would have appeared.  A new data line has been added to the dialog box that is displayed by this command.  The new data line is as follows:

 

            Break-up the Feature (Y=yes, N=no):

 

            The default response is no.  A response of Y or y will result in the command breaking a feature at the location where a point feature would have been created.  Note that if a feature is to be broken, the command will not create point features.  That is to say, the user can either break a feature or create point features, not both at the same time.  If point features are to be created in addition to breaking the feature, the user will need to execute this command twice, creating point features during the first invocation of the command followed by breaking the feature(s) during the second invocation.

 

2.         Update and inclusion of the CEDRA-AVcad User's Manual in the distribution directory.  In the \cedra\help folder a file called AVcad.pdf will appear containing the latest version of the documentation for the software.  Previously, the User's Manual was not included in the distribution directory.

 

3.         Inclusion of the CEDRA-AVwater User's Manual in the distribution directory.  In the \cedra\help folder a file called AVwater.pdf will appear containing the latest version of the documentation for the software.  Previously, the User's Manual was not included in the distribution directory.

 

4.         Modification to the [Create DXF File] command within the CEDRA-DXF-Export extension, for ArcGIS users.  The command will now process grouped graphic elements.  Previously, grouped graphic elements were ignored.  Now the command will decompose the grouped graphic elements and export each of the graphic elements.  The original grouped graphic element is left in tact, that is to say, the grouped graphic element is still grouped.  The ungrouping of the grouped graphic element is done internally (no modification of the original grouped graphic element is performed).

 

5.         Addition of the Use Data Frame's Rotation Value when Exporting parameter to the [Create DXF File] command within the CEDRA-DXF-Export extension, for ArcGIS users.  This new parameter enables the user to control whether or not the data frame's rotation value is applied to the feature prior to the feature being exported.  Previously, when the data frame had a rotation value assigned to it, the program would rotate the feature in accord with the data frame's rotation value and then export the rotated version of the feature.  In so doing, the feature reflects the rotation of the data frame.  Now, with the addtion of this new parameter, the user is able to control whether or not this rotation is applied.  This is particularly useful when the user wishes to create a DXF file that does not reflect the rotation value of the data frame, but rather the unrotated version.

 

6.         Modification to the [Create DXF File] command within the CEDRA-DXF-Export extension, for ArcGIS users.  The command will now limit the number of characters that can appear in a layer name or block name to 31.  Previously, there was no limit, but to ensure maximum compatibility the 31 character limit is enforced.

 

7.         Modification to the [Create DXF File] command within the CEDRA-DXF-Export extension, for ArcGIS users.  The command will now process Group Elements that are nested up to 4 levels.  Previously, the command would only process a Group Element that consisted of one level.  Now if a Group Element contains a Group Element that contains another Group Element that in turn contains another Group Element all 4 Group Elements will be processed.

 

8.         Modification to the [Create DXF File] command within the CEDRA-DXF-Export extension, for ArcGIS users.  The command when performing an export from Layout View will create a World File (.wld) if only one data frame is being exported.  That is to say, if the Layout View contains a single data frame that is being exported, the command will create a World File (using the root name of the DXF file being created with the .wld extension).  The World File contains georeferencing information in the form of two lines.  These lines contain four items on each line.  The first line contains the NW corner of the data frame in terms of its sheet and world coordinates for the NW corner.  Likewise, the second line contains the sheet and world coordinates for the SE corner of the data frame.

 

9.         Addition of the [Lines Connected to Points] command within the CEDRA-Skeletonization extension, for ArcGIS users.  This new command can be found in the CEDRA-Skeletonization-Tools toolbar.  This command enables the user to find the line features that are connected to point features and assign a value to a specific attribute of the point provided the lines share a common attribute value.  For example, if a manhole is connected to two pipes that both have an attribute called AFIELD and whose values are ABND, the user is able to transfer ABND to a specific attribute within the manhole.  In using this command, the user must select or activate the point and line layers prior to activating the command.  Only visible and selected point and line layers are processed.  A multi-input dialog box is presented from which the user specifies the: (a) the features to be processed, (b) the mode of operation, (c) the Point ID field, (d) the Point Attribute field to be modified, (e) the Point Attribute field value, (f) the Line ID field, (g) the Line Attribute field to be checked and (h) the Line Attribute field common value (in the example above, the user would specify ABND for this parameter).  In addition to the parameters specified above, the user can enter a proximity tolerance value and a report filename.  The proximity tolerance value is used to determine the lines that are closest to a point, while the report filename will contain the results of the processing.  Within the report, the user will find a list of the points that were processed along with: (a) the number of lines that were found to be close to the point, (b) the line layer and ID of the lines that were determined to be close to the point and (c) the value, if any, that was stored with the point.

 

10.       Modification to the {AVcad Tools} [Import Points] command, for ArcGIS users.  A new file format called Polygon/String COGO File has been added to the list of available file formats.  This new format enables a user to define multiple parcels and/or traverses in a single ASCII based file.  The result of importing this file format will be the creation of point, line, curve and polygon features, depending upon which commands are placed in the file.  The December 2009 issue of Command of the Month discusses this file format in detail.

 

11.       Addition of the [Points from Annotation] and the [Point from Annotation] commands within the CEDRA-Skeletonization extension, for ArcGIS users.  These new commands can be found in the CEDRA-Skeletonization-Tools toolbar.  These new commands enable the user to create a point feature from selected annotation features.  The text that is associated with the annotation features is then stored as an attribute with the point feature.  For example, if there are two annotation features whose text was ROOM and A-202, these new commands would create a point feature whose PTDESC attribute value would be ROOM A-202.  Note that the user can control the delineating string between the text, for example, rather ROOM A-202, the attribute value could be ROOM - A-202, if desired.

 

12.       Addition of the [Delete Vertices] tool to the CEDRA-ArcView3-Tools toolbar, for ArcGIS users, to handle the deleting of a group of vertices from a selected polyline or polygon feature.  After selecting this tool, the user makes a pick in the map area identifying the polyline or polygon feature to be processed.  Confirmation of the selected feature is asked for.  After confirmation, the tool highlights the vertices which comprise the polyline or polygon feature.  The user is then able to define a rectangle that encloses the vertices to be deleted.  Once the rectangle is defined, the tool determines which vertices fall within the rectangle and removes them from the selected feature.  The tool remains active thereby enabling the user to delete another group of vertices from the same selected feature.  To deactive the tool, the user selects another tool.

 

13.       Modification to the CEDRA-DataEditor extension, for ArcGIS users.  The user is now able to use the Up and Down arrow keys to traverse through the various parameters displayed in the multi-input dialog box.  Previously, the user had to use the Tab key to advance to the next parameter within the dialog box.  Now the user is able to move up and down through the parameters using the Up and Down arrow keys.

 

14.       Modification to the dialog boxes, for ArcGIS users.  The user is now able to use the Up and Down arrow keys to traverse through the various parameters displayed in a multi-input dialog box.  Previously, the user had to use the Tab key to advance to the next parameter within a dialog box.  Now the user is able to move up and down through the parameters using the Up and Down arrow keys.

 

AVwater New Features at Version 3.2u

 

1.         Modification to the Sequential IDs command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Sequential IDs command can be found in the CEDRA-Skeletonization-Tools toolbar.  Rather than displaying two dialog boxes, the Sequential IDs command has been modified to display only one.  Previously, a second dialog box, was displayed prompting the user to select the attribute to be processed.  Now, a new parameter, Attribute to be Populated, has been added to the initial multi-input dialog which enables the user to specify the attribute for processing.

 

2.         Modification to the Sequential IDs command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Sequential IDs command can be found in the CEDRA-Skeletonization-Tools toolbar.  The Sequential IDs command has been modified to be able to compute the high value for a specified attribute (field).  This effects the first data line parameter, Enter Starting ID Number, which appears in the multi-input dialog box.  The user is now able to either: (a) enter the starting value explicitly, or (b) select from a choice list the option, Attribute High plus Increment, to denote that the starting value is to be computed by taking the highest value in the attribute to be processed and adding the ID increment value to it.  The ID increment value is specified in the second data line parameter.

 

3.         Modification to the Change Feature's Shape tool for ArcGIS users.  This tool can be found in the CEDRA-Polygon-Tools-2 toolbar.  The Change Feature's Shape tool will now allow the user to change the shape of a part within a multi-part feature.  Previously, the user could change the entire shape of a multi-part feature but not just a single part within the feature.  Now, the user can alter the shape of a specific part within a multi-part feature.  To do so, the user when selecting the multi-part feature for processing should make a pick close to any vertex on the part to be modified.  That is to say, when selecting the base feature to be modified, make your pick on the boundary of the part to be modified.  If a part within the multi-part feature is found, a new option will appear in the choice list message box, which is presented by the command, of the form "Change Shape of Part xx only", where xx denotes the part number.  Note that part numbers begin at zero and increase sequentially by one.  Selecting this option will result in the geometry of the selected part being altered to match that of the second feature that is selected.  All other parts within the multi-part feature will remain unaltered.

 

4.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when performing a fire flow analysis.  These commands will now create a new table called FireFlowSummary which contains a summary of the nodes that were assigned a fire flow load with their results (Demand, Grade Line, and Pressure).  The table contains the following fields (attributes): FIRFLO_RUN, NODENO, DEMAND, GRADLN and PRESSR.  So that, by examining this new table the user can see on a fire flow run basis, the demand, grade line and pressure for each node that was assigned a fire flow load.

 

5.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when performing a fire flow analysis.  These commands will now process more than 80 nodes.  Previously, the maximum number of records which could appear in the FireFlowData table was 80.  Now the limit is 99999 records.  The reason for the previous limit of 80 is that there is a limit to the number of fields which can appear in a dBase table.  To get around this limitation, if there are more than 80 records in the FireFlowData table, the commands will create multiple FireFlowNodes and FireFlowPipes tables.  For example, if the FireFlowData table contains 100 records, the commands will create the following tables: FireFlowNodes_1, FireFlowNodes_2, FireFlowPipes_1 and FireFlowPipes_2.  The _1 tables will contain the results for the first 80 records in the FireFlowData table, while the _2 tables will contain the results for the remaining records.  Thus, the multiple FireFlowNodes and FireFlowPipes tables are broken down into groups of 80.  Note that there will be only one FireFlowSummary table, which will contain the same number of records as the FireFlowData table.

 

6.         Addition of the [Divide Fire Flow Loads] command under the {AVwater Modify commands} combo-box for ArcGIS users.  This command enables the user to divide a fire flow load which has been assigned to a selected node and have the load applied to other nodes which are within a user-specified proximity of the selected node.  To use this command, the user first selects the node or nodes to be processed.  Following this, the command can be selected.  A multi-input dialog box appears enabling the user to specify the proximity tolerance and the maximum number of nodes that are to be processed at a selected node location.  Note that this value includes the selected node.  In addition to these two parameters the user can control: (a) the field containing the original fire flow load, (b) the field to contain the new computed fire flow load (this can be the same as the original fire flow load field), (c) the node types that can be processed (all nodes, fittings only, hydrants only, fittings and hydrants), (d) the fire flow load distribution method (equally divided amongst the maximum number of nodes within proximity of the selected node or use the original fire flow load as is), (e) update the FireFlowData table with the node numbers of the nodes which are in proximity to the selected node, (f) whether or not circle buffers are to be drawn centered about the selected node and (g) the name of a report file.  The circle buffers are stored in a graphics layer called DivideFFLoads.  The report file contains a list of the selected nodes that were processed and the nodes which were modified for each selected node.  The file also contains the distance from the selected node to the node that was modified and the value that was assigned to the node.

 

7.         Modification to the CheckEndPoint procedure for ArcGIS users.  This procedure performs the point snapping for every tool in the software.  The procedure has been modified to operate on an array of coordinates rather than a list of coordinates.  This results in the procedure performing its task much faster than previously.  This becomes very noticable when dealing with features which are comprised of many vertices.

 

8.         Addition of the Transfer Attribute command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Transfer Attribute command can be found in the CEDRA-Skeletonization-Tools toolbar.  This command enables the user to transfer or assign the attribute value of one feature to another feature based upon a spatial relationship (features close to a point feature or features within a polygon feature).  To use this command, the user activates two layers in the Table of Contents.  One of the layers will contain the features to be modified, while the other contains the features whose attribute is to be transferred to the other.  Upon activation of the command a multi-input dialog box will be presented, from which, the user specifies: (a) the layer containing the features to be modified, (b) whether all features in this layer are to be modified or only the selected features, (c) the layer containing the attribute to be transferred, (d) the attribute in this layer to be transferred, (e) the attribute that this attribute is to be stored in, (f) the proximity tolerance, (g) whether the command is to transfer the attribute value only, highlight the corresponding feature only or transfer and highlight and (h) whether the layer name and OID of the corresponding feature are to be transferred as well.  An example of the application of this new command is when there are two layers, a point layer and a polygon layer.  The polygon layer contains an attribute called ZIP4 and it desired to transfer the ZIP4 value of a polygon feature to a point feature which falls within a specific polygon.  This command can be used to accomplish this task.

 

9.         Modification to the CEDRA-DXF-Export extension, Version 1.8 for ArcGIS users.  The program will now take into account the rotation angle that has been applied to a data frame.  Previously, the data frame's rotation angle property was ignored.  Now, the features which are to be exported in the data frame will be rotated to properly reflect the data frame's rotation angle.

 

10.       Modification to the CEDRA-DXF-Export extension, Version 1.8 for ArcGIS users.  The program will now take into account the various horizontal and vertical alignment properties for multi-line graphic text elements.  Previously, only the horizontal property was taken into consideration when exporting graphic text elements.  Now, the vertical alignment, as well as, the X and Y offset values are accounted for.

 

11.       The EPANET 2 interface has been upgraded to support Version 2.00.11 of the EPANET 2 modeler.  Previously, Version 2.00.10 was supported.  Now, the analytical results are computed using EPANET 2 Version 2.00.11 and not 2.00.10.

 

12.       Modification to the {AVcad Tools} [Export Generate] command, for ArcGIS users in exporting polyline and polygon features.  Two new choice items called Traverse File Format and Traverse File Format - Multiple Files have been added to the list of available file types.  These new options enables the user to export polyline and polygon features using the Traverse File Format structure.  The October 2007 issue of Command of the Month should be consulted for detail information regarding the use of the [Export Generate] command as well as the structure of the Traverse File Format.

 

13.       Modification to the CEDRA-DataEditor extension, for ArcGIS users.  A new tool has been added to the toolbar called Map Tips.  This tool displays the attribute values for those attributes which have been defined in the Theme Attribute Data File (themes.txt) as a Map Tip for a specific feature.  Once the tool has been activated, the user simply positions the cursor on top of the feature to be processed.  If the command finds a feature, which belongs to a theme which appears in the Theme Attribute Data File, the command will display as a Map Tip the attribute values currently assigned to the feature.  The values which are displayed are those which belong to the attributes identified in the Theme Attribute Data File.  In addition to the attribute values, the attribute labels (as defined in the Theme Attribute Data File) will precede the attribute value.  For example, the Map Tip window could contain a line such as Parcel: 101 or Diameter: 12.  This new tool provides a quick and easy method of displaying attributes values without having to select a feature with the Edit Feature Attributes tool.  The order of the attribute value listing is identical to the order of the attribute specification in the Theme Attribute Data File.

 

14.       Addition of the Dimension 5 command |SAV MAB| for ArcGIS users.  This new tool enables the user to generate a metes and bounds type of dimension based upon two picks made by the user.  If a curve is to be annotated, the user can either: (a) explicitly enter the radius of the curve, or (b) make a pick denoting a point on the curve.  The user can generate a distance, azimuth, bearing, distance and azimuth or distance and bearing type of annotation.  This tool augments the {Annotate} [Distance], [Azimuth], [Bearing], [Distance and Azimuth] and [Distance and Bearing] commands by offering the ability to operate on two picks, rather than selected features.

 

15.       Addition of the Center Text tool to the CEDRA-Text-Tools toolbar for ArcGIS users.  In using this tool, the user: (a) selects the annotation feature(s) to be processed, (b) activates the tool, (c) makes two picks denoting the baseline and (d) specifies the type of centering to be performed.  The user can center annotation features using any of the following options:  Center within Horizontal Box, Center within Vertical Box, Center about Horizontal Line, Center about Vertical Line or Center about Inclined Line.  When centering about a line, the user is able to specify a spacing value, if desired.  The spacing value denotes the distance between the selected annotation features.  A value of zero denotes leave the annotation feature spaced as is and only center the annotation features about the baseline.  When centering annotation features within a box, the spacing value is computed by the command.  This tool augments the text alignment options offered by native ArcMap functionality.

 

16.       Modification to the CEDRA-DataEditor extension, for ArcGIS users.  The user is now able to specify either the name of the attribute (field) or the alias name for an attribute in the Theme Attribute Data File.  Previously, the software would only accept the true name of the attribute.  Now the user is able to specify either the attribute's true name or its alias name, provided one has been specified.

 

17.       Modification to the CEDRA-DataEditor extension, for ArcGIS users.  The user is now able to use the functions: LEN, TRIMR1, TRIMR2, TRIMR3, TRIMR4, TRIMR5, TRIMR6, TRIML1, TRIML2, TRIML3, TRIML4, TRIML5 and TRIML6 when defining an attribute equation.  The function LEN will return the number of characters in a string.  The TRIMR1 function will remove the last character in a string, TRIMR2 will remove the last two characters, TRIMR3 will remove the last three characters in a string, TRIMR4 removes the last four characters, TRIMR5 the last five characters and TRIMR6 the last six characters.  Likewise, TRIML1 will remove the first character in a string, TRIML2 will remove the first two characters, TRIML3 will remove the first three characters in a string, TRIML4, TRIML5 and TRIML6 the first four, five and six characters, respectively.

 

18.       Modification to the CEDRA-DataEditor extension, for ArcGIS users.  Those users who wish to display a value that is different from what is stored in the database can use the \\ characters when entering a value under the CHOICES command.  For example, review the following:

                                                CHOICES

                                                CAP-BNK\\CAPACITY-BANK

                                                FUS-CUT\\FUSED-CUTOUT

                                                LIN-FUS\\LINE-FUSE

                                                END

            The above is an example where the \\ characters are used to separate the actual value, which is stored in the database, from the value that should appear in the choice list.  In this example, CAPACITY-BANK, FUSED-CUTOUT and LINE-FUSE would appear in the choice list, while the values, CAP-BNK, FUS-CUT and LIN-FUS, would be stored in the database.  As such, the user first specifies the value to be stored in the database, followed by the \\ characters, followed in turn by the value to appear in the choice list.  In so doing, a more friendly name can be presented to the user, while a desired coded value is stored in the database.  Note, if a blank value is to be stored in the database and the user wishes to display something other than a blank character in the choice list, the user should enter a blank character, followed by the \\ characters and then the string to appear in the choice list.

 

19.       Addition of the Points at Line EPts command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Points at Line EPts command can be found in the CEDRA-Skeletonization-Tools toolbar.  This command enables the user to find the point feature closest to each end point of a line feature and transfer to the line feature two point attributes (such as node number and node type).  In using this command, the user must select or activate the point and line layers prior to activating the command.  Only visible and selected point and line layers are processed.  The command processes selected line features, if  no features are selected in the active line layer then all line features in the layer will be processed.  A multi-input dialog box is presented from which the user specifies the two attributes in the point layer that are to be transferred to the line layer.  The labels for these two attributes are Point ID and Point Type.  A drop-down list appears containing all of the point attributes in the active point layer.  The user simply selects the one attribute that should be used for the Point ID and Point Type.  If no attribute is to be used for the Point Type parameter, the user should select the <none> option.  Note that the Point ID attribute must be specified, the Point Type attribute is optional.  In addition to the two point attributes, the user will specify four line attributes, two for the start point of the line and two for the end point of the line.  These attributes will contain the Point ID and Point Type values of the point that is closest to the start and end points of the line.  In addition to the six attributes specified above, the user can enter a proximity tolerance value and a report filename.  The proximity tolerance value is used to determine which point is closest to the start or end point of the line, while the report filename will contain the results of the processing.  Within the report, any line features which did not have a node feature close to an end point will be identified by their object ID (FID, OID, OBJECTID) value.

 

20.       Modification to the CEDRA-DataEditor extension, for ArcGIS users.  The Map Tips tool has been changed to deactivate itself when the user depresses the left mouse button.  Previously, the tool could only be deactivated by activating another tool.  Now, when the user clicks the left mouse button the tool deactivates and the default ArcMap tool becomes active.  In so doing, the user can now display map tips as desired and when finished, simply click the left mouse button to terminate the displaying of map tips.

 

21.       Addition of the [Shapefiles from Layer] command to the CEDRA-DXF-Export extension, for ArcGIS users.  This new command enables the user to create individual shapefiles from an active layer using the value of an attribute within the layer.  To use this command, the user first activates the layer to be processed.  A multi-input dialog box is then displayed, from which, the user is able to specify: (a) the field containing the name for the shapefiles to be created, (b) the entity types to be processed, (c) the destination folder where the new shapefiles are to be stored and (d) whether the new shapefiles are to be added to the document or not.  Essentially this command finds all of the unique values for the specified field and uses these values as the names of the shapefiles to be created.  Values that are NULL or blank are disregarded.  If the user selects the Basic Types option for the Entity Type to Process parameter, the command will only export features whose ENTITY value is ARC, CIRCLE, LINE and POLYLINE.  Note that this occurs only if the ENTITY field is present in the layer.

 

22.       Modification to the [Transfer Attribute] command within the CEDRA-Skeletonization extension, for ArcGIS users.  The [Transfer Attribute] command can be found in the CEDRA-Skeletonization-Tools toolbar.  This command enables the user to transfer or assign the attribute value of one feature to another feature based upon a spatial relationship (features close to a point feature or features within a polygon feature).  The command has been modified to transfer up to five attributes, rather than just one.  Previously, the user could specify just a single attribute to be transferred, now the user can identify up to five attributes.  The multi-input dialog box has been expanded to include Attributes 1 through 5.  If one of these attributes is not to be used, then the <none> option for the attribute should be selected.  The default option for Attributes 2 through 5 is <none>.  So that, if more than one attribute is to be transferred the user can simply change the default for Attribute 2, 3, 4 or 5.

 

23.       Addition of the [Set Active Layer] tool to the CEDRA-ArcView3-Tools toolbar, for ArcGIS users, to handle the setting of the current active layer.  This new tool appears on the far right of the toolbar and upon activation displays a list of the layers in the Table of Contents, from which, the user can select one to indicate the current active layer.  Similar to the [Set Active Layer] command, within the {CEDRA-AVcad-Menus} toolbar, when using the Picking Existing Layer option, this new tool provides a fast means of defining the current active layer.  In addition, when the user moves the cursor over the tool in the toolbar, the tool will display the name of the current active layer in the status bar area.  Note that when a layer is selected, which does not conform to the CEDRA Layer Naming convention, the tool will place the Editor in edit mode and make the current active layer the Target Layer.  Additionally, the current Task will be set to Create New Feature.

 

24.       Modification to the ReadPublic and SavePublic subroutines when reading and writing the global parameter setting file (c:\public.txt).  Previously, this file was always stored in the root level of the C: drive.  Now, these subroutines will process the file from the: (1) c:, (2) c:\cedra\avprjs, (3) $CEDRA, (4) $HOME, (5) $TEMP or (6) $TMP folders depending upon which one exists and the user has permission to read and write to.  Note that the $ character in front of the name denotes an environment variable and as such will point to a user-specified location.

 

25.       Addition of the CL tool to the CEDRA-Deed-Tools toolbar for ArcGIS users.  This tool will clean the parcels in the current active view.

 

AVwater New Features at Version 3.2t

 

1.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when using the EPANET 2 modeler.  These commands will now run faster due to the fact that the EPANET 2 modeler has been modified to eliminate the need for certain "Calculate" functions to be performed.  The performance increase will be very noticable when the model contains a large number of pipes.

 

2.         Addition of the EPANET 2 attribute, FLOWCOEF, to the WaterHydrants specialty table.  The FLOWCOEF attribute pertains to the flow coefficient, flow units at 1 psi (1 meter) pressure drop, which is associated with Emitter types of hydrants.  To define Emitter hydrant types, a HYDTYP value of 15 should be entered for the hydrant type attribute, which is displayed by the Define Node tool (N) and the Modify tool (M) when processing nodes.  When using the Modify tool (M) on an Emitter type of hydrant, the user is able to enter a value for the FLOWCOEF attribute.

 

3.         Addition of the RPRESS attribute to the water nodes layer.  This attribute is used to store the required pressure head for a node.  The required pressure head is defined as 2.3 times the pressure (psi), that is desired for the node.

 

4.         Modification to the L tool to allow the user the option of entering a required pressure head as a fire flow load.  As such, the user can now specify the fire flow load as a pure demand or as a required pressure head.

 

5.         Modification to the {Modeling} [Execute] command when performing a fire flow analysis.  The fire flow analysis message box has been changed to a choice list from which the user can specify: (a) that no fire flow analysis is to be performed, (b) an analysis to determine the Maximum Pressure Available is to be performed, or (c) an analysis to determine the Maximum Flow Available is to be performed.  Under item b, the FIRFLO attribute is used in the fire flow analysis.  This is how the command previously operated.  Under item c, the RPRESS attribute is used in the fire flow analysis.  This is a new feature that has been added.  This mode of fire flow analysis is only available with the EPANET 2 modeler.  The EPANET and KYPIPE modelers do not support this mode of analysis.  When using this mode of fire flow analysis the required pressure head value is added to the node's elevation and the nodes's Emitter flow coefficient value (FLOWCOEF) is used in the analysis.  In this mode of fire flow analysis, the user is able to determine the maximum flow at the node, rather than the maximum pressure.  The Emitter flow coefficient value should be entered as 100 times the expected flow.

 

6.         Modification to the CEDRA-AVwater-EPANET-Import extension, Version 1.8, to process the EPANET VERTICES command.  This command enables the user to include polyline pipes in the model, rather than just two-point lines.  Previously, this command was not processed and as such all pipes in the model were represented as two-point lines.  Now the user is able to include polyline shaped pipes in the model.

 

7.         Modification to the {Query} [Range], [Highs], [Lows] and [Rev. Flow] commands to include the attribute value in the reports that these commands generate.  Previously, this was not done.  Now the user is able to view the value of the attribute for the feature which satisfies the specified query.

 

8.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when performing an analysis.  The analysis programs are now launched using Windows API calls rather than the Shell command.  From the user point of view there is no real difference that will be noticed.  However, this modification does make the software more compatible with various types of PCs.

 

9.         Addition of the ALIGNUM, STATION and ALIGOFF attributes to the water node theme.  These attributes pertain to the corresponding horizontal alignment, station along the alignment and offset from the alignment, respectively, for the water nodes in the model.  These attributes are used when creating profiles using station values.

 

10.       Addition of the [Compute Stationing] command under the {AVwater Modify commands} combo-box for ArcGIS users.  This command enables the user to compute a station value for a selected set of sewer nodes.  The station values are computed in relationship to a design horizontal alignment as established with the CEDRA-AVland software.

 

11.       Modification to the {Text Properties} [Modify Annotation Features] command, for ArcGIS users.  This command now allows the user to reposition an annotation feature by centering a text string along a line while either (a) maintaining an offset or (b) fixing the offset of the annotation from a line.  Two new options have been added to the Reposition by choice drop-down list providing for this new functionality.  These options are called Maintaining Offset from a Line & Center and Fixed Offset from a Line & Center, respectively.

 

12.       Modification to the CEDRA-DXF-Export extension, Version 1.7, for ArcView GIS users, when exporting point features.  If the point feature is not ZAware, that is to say not a 3D point, the program will try to use one of the following attributes; Z, ELV, ELEV or ELEVATION in exporting an elevation value.  If none of these attributes exist and the point is not ZAware, the elevation value 0.0 will be written to the DXF file.  If one of these attributes do exist, the program will export the value for the first attribute it finds.  Previously, a non-zero elevation value would be written only when the point feature was ZAware (a 3D point).

 

13.       Modification to the [Compute Stationing] command under the {AVwater Modify commands} combo-box for ArcGIS users.  This command now allows the user to compute station values which are in relationship to a strip's linear direction, as well as, in relationship to a design horizontal alignment as established with the CEDRA-AVland software.  When computing station values in relationship to the strip's linear direction, the user is able to specify the starting station value for the first node in the strip.  The multi-input dialog box has been redesigned to present the appropriate data fields for both types of station value computations.  Note that if the view does not contain any design horizontal alignments, the user will only be able to generate station values in relationship to the strip's linear direction.  Furthermore, if the direction of the desired stationing opposes the physical direction of the strip, the option Linear - Reverse Direction can be selected.  This saves the user the trouble of having to reverse the physical direction of the strip.

 

14.       Modification to the {Modify} [Classification] command to display a new option called Strip Number.  This new option enables the user to classify the pipe theme according to the unique strip number values for all of the pipes in the model.  The attribute STRIP is used in this type of classification.

 

15.       Addition of the [Profile on Profile] command under the {AVwater Annotation commands} combo-box for ArcGIS users.  This command enbles the user to superimpose upon an existing water profile another water profile.  The user is asked to specify the service area and strip number for the pipes to be plotted.  In addition, the user is asked to enter a starting station value along with the data frame containing the existing water profile.  The pipes to be plotted are then added to the existing water profile.

 

16.       Addition of the [Profile using Stationing] command under the {AVwater Annotation commands} combo-box for ArcGIS users.  This command enbles the user to superimpose upon an existing profile a water profile using the station values which are assigned to the water nodes.  The attribute, STATION, contains the station value of the node, while the ALIGOFF attribute contains the offset of the node from the horizontal alignment it is associated with.  The ALIGNUM attribute contains the horizontal alignment ID which the node is associated with.  Only the STATION attribute is used by this command.  The [Compute Stationing] command under the {AVwater Modify commands} combo-box can be used to populate the STATION attribute.

 

17.       Modification to the [Update Geometry] command for ArcGIS users, which appears under the {CEDRA commands} combo-box within the CEDRA-AVcad-Menus toolbar  A new option called Update Shapes using Coordinates has been added to the Mode of Operation choice list that is presented by this command.  This new option provides the user the ability to alter the geometry or shape of a feature by using coordinate values that are stored in the attribute table.  This option processes the current active point or polyline layer.  Once activated, the user is able to specify the fields which contain the X and Y coordinate values and how the coordinates are to be processed.  The coordinate processing options include Use Coordinates As Is, Project Decimal Degrees to Map Units and Project Distance to Map Units.  The last option Project Distance to Map Units is sensitive to the Display Units setting for the Data Frame.  When dealing with point features, this command will position the point using the X and Y coordinates found in the attribute table, while for polyline features the command will alter only the start and end points of the polyline, any intermediate vertices will remain unaltered.

 

18.       Modification to the CEDRA-DXF-Export extension, Version 1.8 when exporting attributes for a single layer.  Previously, the software would not output the BLOCKS command line in the DXF file, which resulted in the DXF file being incomplete.  This has been corrected so that attributes can be exported for one or many layers.

 

19.       Modification to the extension, CEDRA-PolyTools (Version 1.4), for ArcGIS users when using the Snap To Points command.  The user is now able to specify whether all visible layers are to be processed or only the visible active layers are to be processed.  Previously, the command would process all visible layers.  Now the user has a choice as to which layers are to be processed.  In addition, if the Editor is in session an additional parameter will be presented in the multi-input dialog box presented by the command, enabling the user to either: (a) stop the Editor saving any edits which may have been made, or (b) stop the Editor ignoring any edits which may have been made.  In order to use this command, the Editor should be stopped prior to invoking the command, if the Editor is not stopped, this additional parameter will appear in the multi-input dialog box.

 

20.       Modification to the extension, CEDRA-ChangeFeatures (Version 2.4) when using the Change Feature's Shape tool.  The tool will now check if one or two layers are active.  If so, the tool tries to select two features from the active layer(s).  If two features can not be selected, the command functions as before.  If two features of the same type can be selected, the command highlights the first feature found and prompts the user as to if this is the base feature to be modified in the form of a Yes/No/Cancel message box.  By activating the layer or layers containing: (a) the feature to be modified and (b) the feature containing the new shape, the user is able to reduce the number of clicks in altering the shape of a feature.

 

21.       Modification to the CEDRA-DXF-Export extension, Version 1.8 for ArcGIS users.  The program will now export Callout elements.  Previously, Callout elements were ignored and as such would not appear in the DXF file that was created.  Now Callout elements are processed from both Data View and Layout View.

 

22.       Modification to the CEDRA-DXF-Export extension, Version 1.8 for ArcGIS users.  The program will now export the Data Frame's border, if one has been associated with the Data Frame, when the export is performed from Layout View.  Previously, the Data Frame's border would not be processed.  Now the program will export the Data Frame's border when creating a DXF file from Layout View.

 

23.       Modification to the CEDRA-DXF-Export extension, Version 1.8 for ArcGIS users.  The program will now export multi-line annotation features stored in a geodatabase.  Previously, only single-line annotation features were handled.  Now, both single and multi-line annotation features are properly exported from both Data View and Layout View.

 

24.       Modification to the {AVcad Tools} [Import Points] command, for ArcGIS users when importing a CEDRA drawing, files of type CEDRA Dwg (*.ctl).  The command will now import the point code and description of a point feature, provided the point has been assigned a code and a description.  Previously, the point code and description, which appeared in the CEDRA drawing, were ignored by the command.  Now, these attributes will appear under the PTCODE and PTDESC fields.

 

25.       Modification to the CEDRA-DXF-Export extension, Version 1.8 for ArcGIS users.  The program will now export scale bar elements when the export is performed from Layout View.  Previously, scale bar elements were ignored.  In addition, the program has been modified to export a polyline which represents the outline of north arrow and picture frame elements.  Although the program does not export the features which comprise the north arrow (since it is actually an ESRI font character) or a picture frame, the program will export a polyline which denotes the location of these two types of elements.

 

26.       Modification to the {AVcad Tools} [Export Generate] command, for ArcGIS users in exporting point features.  A new choice called Single Point Coordinate File has been added to the list of available file types.  This new option enables the user to export point features in a variety of formats similar to the file formats presented by the [Import Points] command.

 

27.       Modification to the CEDRA Tool Palette for ArcGIS users.  The visibility of the palette is now stored in the global parameter setting file (c:\public.txt) so that when the user reinvokes the program and the palette was visibile the last time the program was used, the palette will now be displayed at its last position without the user having to select the [CEDRA Tool Palette] command.

 

28.       Modification to the Sequential IDs command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Sequential IDs command can be found in the CEDRA-Skeletonization-Tools toolbar.  The Sequential IDs command has been modified to allow the user the ability to add a prefix or suffix to the sequential index value that is computed, if so desired.  The text, <none>, denotes that the prefix or suffix is not to be added, any other text which is entered in the appropriate data fields will be used as either a prefix or suffix.  In addition, the user is able to specify the increment value that is to be used.  Previously, the increment value was always 1.  Now the user can enter the desired increment value.  The multi-input dialog box posed by this command has been modified to accommodate the three new parameters: ID increment value, prefix and suffix.

 

29.       Modification to the Sequential IDs command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Sequential IDs command can be found in the CEDRA-Skeletonization-Tools toolbar.  The Sequential IDs command, prior to displaying the multi-input dialog box, will check if there are any selected graphic line elements.  If so, an additional parameter will appear in the multi-input dialog box with the label, Use selected graphic for order (Y=yes, N=no):.  This new parameter enables the user to control the order of the features which are processed.  Previously, the order was based upon the feature's sequential OID value.  Now, when a selected graphic line element is present, the command will use the order of the vertices comprising the graphic line element to determine the order of how the features will be processed.  That is, the feature which is closest to the first vertex in the graphic line element will be processed first, while the feature which is closest to the last vertex will be processed last.

 

30.       Modification to the Sequential IDs command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Sequential IDs command can be found in the CEDRA-Skeletonization-Tools toolbar.  The Sequential IDs command will now remember the values which were previously specified.  Prior to this modification, the same default values would always appear whenever the command was invoked.  Now the command will display the values which were last entered as the default values.

 

31.       Modification to the Relocation 4 command |EXT/ELE/XING| for ArcGIS users.  The command now displays a check box control at the bottom of the Yes/No/Cancel query box, which is displayed after the user selects the features to be extended, that enables the user to control whether or not point features are to be created at the computed intersections.  If the check box control is not checked, the command functions as it always did.  However, if the user checks the control, the command will not extend the selected features, but rather, will create point features at the computed intersections.

 

32.       Addition of the Assign Attribute command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Assign Attribute command can be found in the CEDRA-Skeletonization-Tools toolbar.  The Assign Attribute command enables the user to assign a value (explicitly or picked from a list) to a specific attribute or field.  This command operates on the current active layer processing either all features in the layer or only the selected features, if any are present.  A multi-input dialog box is posed, from which, the user can specify the field to be processed and the explicit attribute value.  If the user desires to display a list of the unique values for the attribute, a parameter labeled List Attribute Unique Values (Y=yes, N=no) appears in the dialog box where the user can select either Yes or No.  If a unique attribute value list is displayed, it is possible for the user to select a value from the list and have it assigned to the features.  A parameter labeled Use a Unique Attribute Value (Y=yes, N=no) provides the user the ability to indicate if one of the unique attribute values is to be used or not.  If the user responds Yes, the multi-input dialog box is redisplayed with a list of the unique values for the selected attribute.  Note that no features are modified during the generation of the unique attribute value list.

 

33.       Modification to the Assign Attribute command within the CEDRA-Skeletonization extension, for ArcGIS users.  The Assign Attribute command can be found in the CEDRA-Skeletonization-Tools toolbar.  The Assign Attribute command can now transfer the values from one field to another.  To do so, the user specifies in the first data line item, within the multi-input dialog box that is displayed, the field or attribute to be modified (the one which will receive the new values).  In the second data line item, the user specifies the name of the field (attribute) to be copied into the field specified in the first data line item, enclosing the name of the field within the square brackets [ ].  For example, if the user entered [AREA] in the second data line item, the command would copy the value from the attribute AREA into whatever field was specified in the first data line item.  Note, when specifying date values, the user does not need to enclose the date in double-quote characters (").  For example, the date 12/08/2006 would be a valid date entry.

 

34.       Modification to the Edit Feature command within the CEDRA-EditFeature-Tools toolbar, for ArcGIS users.  The Edit Feature command will now display as the name of the label either the: (a) true attribute (field) name or (b) the alias of the attribute, if one has been assigned to the attribute.  Previously, the command would only display the true attribute name and would not display the alias of the field.

 

AVwater New Features at Version 3.2s

 

1.         Addition of the Echo 5 tool to the CEDRA-Echo-Tools toolbar for ArcGIS users.  This tool enables the user to echo or display the plus and offset of a point along a string, as well as, the overall length of the string.  A string may be comprised of one or more features (lines and/or curves).  When activated, the user will be asked to select the first element in the string.  A choice message box will appear enabling the user to define the string in one of three modes.  Once the string has been defined, the user makes a pick.  The command will project this pick onto the string and display the plus and offset values associated with the point of projection.  The user is then able to make another pick to display new plus and offset values.  The command remains in this mode of operation until another command is selected.

 

2.         Modification to the [Contours] command under the {AVwater Annotation commands} combo-box for ArcGIS users.  This command has been modified to prompt the user as to if the existing contour information (polylines and annotation), which reside in the current active layer, is to be deleted or added to when processing the new contour data.  This command will now check if the current active layer contains any contour information, if it does not, the command functions as before.  If the current active layer does contain contour information, a Yes/No/Cancel message box will be displayed asking the user if the existing contour information is to be deleted, added to, or the command aborted.  Previously, the user had to delete the existing contour information prior to selecting this command, otherwise, the new contours would overlay on top of the previous contours.

 

3.         Modification to the CEDRA-DXF-Export extension, Version 1.7 to be able to export the visible data in either: (a) the current coordinate system of the view (data frame) or (b) in the coordinate system of the theme's data source.  A new option has been added to the dialog box posed by the Create DXF File command called Export using same Coordinate System as the Data Frame.  When this option has been activated (checked), all of the data that is exported will be in the same coordinate system as the view (data frame).  When this option is not activated (not checked), each theme (layer) will appear in the coordinate system of its data source.  As such, when this option is not checked it is possible for the themes (layers) to not overlay as expected since each theme (layer) could be in a different coordinate system.

 

4.         Addition of the Mirror Features and Repeat Features options to the Transformation tool for ArcGIS users.  These options appear below the Translate, Rotate, Scale Features option at the bottom of the choice list and enable the user to either mirror or repeat the selected features.  Both options create new features placing them in the current active layer.  Attributes of the selected features will be transferred to the new features provided that the layer into which the new features are stored contain the same attributes as the selected features.  When mirroring features the user can mirror about: (a) the X axis, (b) the Y axis or (c) an arbitrary baseline.  The options Pick Baseline Point 1 and Pick Baseline Point 2 should be used to specify the baseline control points.  When repeating features the user can: (a) create multiple copies, (b) apply a scale factor and/or (c) apply an angle of rotation.  The option Pick Baseline Point 1 should be used to specify the "control point" for the selected features, while the option Pick New Baseline Point 1 should be used to denote the new location of the "control point".

 

5.         Modification to the Transform Features and Stretch Features options in the Transformation tool for ArcGIS users when processing polyline and polygon features which have a large number of vertices comprising the feature.  These options will now process these types of features faster than before.

 

6.         Modification to the CEDRA-DataEditor extension, Version 2.1, for ArcGIS users when processing a feature in a layer that has labels displayed.  The software will now refresh the layer, upon completion of the editing, to ensure that the labels which are displayed reflect the proper values.  Previously, there was no refreshing so that in order for the labels to be updated the user had to manually refresh the display of the layer.  Now, the software will perform this updating for the user.

 

7.         Modification to the CEDRA Tool Palette for ArcGIS users.  The position of the palette is now stored in the global parameter setting file (c:\public.txt) so that when the user reinvokes the program and redisplays the palette, it will appear in the location in which it was last displayed.  In so doing, the user no longer has to reposition the palette, but rather, the palette will always be displayed in the location in which it last appeared.

 

8.         Addition of the CEDRA-Callout-Tools toolbar for ArcGIS users.  This new toolbar provides similar functionality to the Callout tools found in the Text tools drop-down list, found in the ArcView GIS environment, for creating various types of Callouts.  Since there is no out of the box toolbar in ArcMap for creating Callouts, this new toolbar is extremely useful for those users who need to create Callouts from within ArcMap.

 

9.         Modification to the [Print Data Frame] command under the {Data Frame Tools} combo-box for ArcGIS users.  ArcGIS users will find this combo-box within the CEDRA-DataFrame-Tools toolbar.  The radial button Custom, under the Paper Size frame, has been changed to a listbox control containing the names of the maps in the document.  Selecting the radial button to the left of this listbox enables the user to specify custom sheet height and width values.  If the user selects the Include Data Frame matching the Paper Size option the user can select a map from this listbox for inclusion in the plot that is created.  Previously, the Data Frame that was included had to be called Custom.  Now the Data Frame that is included can be named anything the user desires.

 

AVwater New Features at Version 3.2r

 

1.         Modification to the CEDRA-Text-Tools toolbar for ArcGIS users.  Four tools have been added to the toolbar.  The first three correspond to the Set Graphic Text Angle (2 Pts), Set Graphic Text Angle (Pick Line) and Set Graphic Text Angle (Explicit) options within the Transformation tool.  These tools enable the user to define the angle of inclination for an annotation feature by: (a) picking two points, (b) picking an existing line feature or (c) explicitly entering an angle.  In using these tools, the user is able to (a) "pick" the annotation feature to be processed and then specify the appropriate data, or (b) "select" the annotation feature prior to activating the tool and then specify the appropriate data required by the tool.  The fourth tool is the Edit A Text tool which enables the user to edit the text string that is associated with the annotation feature (see the description below for more information).

 

2.         Addition of the Edit A Text tool to the CEDRA-Text-Tools toolbar for ArcGIS users.  In using this tool, the user "picks" the annotation feature to be modified, after which, the command displays a multi-input message box containing the annotation feature's current text string and the attributes which are associated with the annotation feature.  The user is then able to enter a new text by overwriting the current text string that is displayed or by selecting the attribute whose value is to be used as the text string.  Should the user wish to break the text into separate text strings, the characters || can be used.  When the || characters are found, the command will create a new annotation feature in the same layer as the original selected annotation feature.  There is no limit to the number of times the || characters can appear in a text string.  When the || characters are used, the command will center the annotation features about the original selected annotation feature's position.  In addition, this tool can be used to transfer the attribute value of a line feature to the text string.  When selecting the annotation feature to be processed, if the "pick" that is made to select the feature can also be used to select a line feature, the command will highlight both the annotation feature and the line feature and display the attributes of the line feature in the multi-input dialog box.  The user can then select one of the line feature's attributes, if desired.

 

3.         Modification to the CEDRA-Transform-Tools toolbar for ArcGIS users.  An additional tool has been added to the toolbar.  This tool corresponds to the Translate, Rotate, Scale Features option within the Transformation tool.  This tool enables the user to translate, rotate and scale selected features without taking into consideration a baseline.  This means that the transformation, which is applied to the selected features, is in respect to the X and Y axes.  In using this tool, the user selects the feature(s) to be transformed and then selects this tool.  The command will then display the transformation parameter multi-input dialog box, from which, the user can enter the appropriate data.  Once entered, the transformation is applied to the selected features and the dialog box redisplayed so that another transformation can be applied to the same features.  To terminate the command, the user selects the Cancel button.

 

4.         Modification to the CEDRA-Text-Tools toolbar for ArcGIS users.  A new tool, Curved Text, has been added to the toolbar.  This brings the total number of tools in this toolbar to six.  The Curved Text tool enables the user to convert an existing annotation feature into a text string which follows the path of an existing polyline feature.  In using this tool, the user first selects and confirms the annotation feature to be processed followed by selecting and confirming the polyline feature which the annotation feature is to follow.  Once both features have been identified, the command presents a multi-input dialog box which enables the user to control: (a) the X and Y offsets along the polyline, (b) the text string and (c) whether the text string is to be flipped or reversed.  The dialog box will remain visible until the user selects the Cancel button.  This allows the user the ability to enter various values until the desired position has been achieved.

 

5.         Addition of the Duplicate Features command to the extension, CEDRA-PolyTools (Version 1.6) for ArcGIS users.  ArcGIS users will find this new command in the combo-box on the CEDRA-Polygon-Tools toolbar.  This command checks to see if there are any duplicates features in a layer or if there are any duplicate features between two layers.  In determining duplicate features this command checks if there are features which have the exact same geometry.  As such, the direction of a feature's geometry is important in determining if a duplicate feature exists.  Once the duplicate features have been identified, the user has the option to: (a) highlight the duplicate features, (b) delete the duplicate features, (c) add the attributes of the duplicate features which are missing (available only when two layers are being processed) or (d) update the common attributes using the values of the duplicate features.

 

6.         Modification to the Change Feature's Course tool within the extension, CEDRA-ChangeFeatures (Version 2.2).  This command has been modified to better find vertex matches when the end points of the second feature selected do not have an exact match with the first feature selected.  When the end points of the second feature do not have an exact match with any vertex of the first feature, the command will use the vertices on the first feature which are the closest to the end points of the second feature.  This command appears in the CEDRA-Polygon-Tools2 toolbar for ArcGIS users.

 

7.         Addition of the Point Elev. from TIN and Point Elev. from Contours commands to the extension, CEDRA-PolyTools (Version 1.6) for ArcGIS users.  ArcGIS users will find these new commands in the combo-box on the CEDRA-Polygon-Tools toolbar.  These new commands enable the user to interpolate an elevation for point features based upon a TIN dataset or a layer containing contour strings, respectively.  In using these commands, the user must first activate in the table of contents the two layers which represent the point layer and the TIN or contour string layer to be processed.  Once done, the user can select the appropriate command.  Upon selection of the command, the program will display a dialog box where the user can specify the desired interpolation parameter values.

 

8.         Addition of the Profile from TIN command to the extension, CEDRA-PolyTools (Version 1.6) for ArcGIS users.  ArcGIS users will find this new command in the combo-box on the CEDRA-Polygon-Tools toolbar.  This new command enables the user to extract a profile based upon a TIN dataset and a selected feature in a polyline layer.  In using this command, the user must first activate in the table of contents the two layers which represent the polyline layer and the TIN layer to be processed.  Once done, the user can select this command.  Upon selection of the command, the program will display a dialog box where the user can specify the desired profile extraction parameter values.

 

9.         Modification to the [Set Text Size] command under the {Text Properties} menu item for ArcGIS users.  The command will now display the text size that should be used (for each of the annotation layers in the current active map) to generate a text identical in size as that of the selected text.  A choice list message box is displayed containing the text size and the annotation layer it corresponds to, from which, the user selects the desired text size.  Note that this occurs only when an annotation feature is selected.  This will not occur when a graphic text element is selected.

 

10.       Modification to the [Select Features from Active Layers] command in the CEDRA-ArcView3-Tools toolbar to handle cases where one of the active layers is a raster image or a CAD drawing.  Previously, the command would not select any features if one of the active layers was a raster image or a CAD drawing.

 

11.       Addition of the [Plot Profile Table] command under the {Cross-Section/Profile commands} combo-box for ArcGIS users.  This command enbles the user to superimpose upon an existing profile another profile surface.  The profile, which is to be superimposed, must reside in a Profile Data Table, that is, a table which contains two fields called STATION and ELEVATION.

 

12.       Modification to the {Text Properties} [Modify Annotation Features] command, for ArcGIS users.  This command now allows the user to modify the text angle, which is associated with the selected annotation feature(s), by: (a) explicitly entering a desired text angle or (b) by adding an incremental angle.  Two new options have been added to the Mode of Operation choice drop-down list providing for this new functionality.  These options are called Set the Text Angle (degrees) and Add to the Text Angle (degrees), respectively.

 

13.       Modification to the [Select Features from Active Layers] command in the CEDRA-ArcView3-Tools toolbar to place the features which are selected in the map's feature selection list when the Editor is in an edit state.  This enables the user to use ArcMap's Edit Tool to relocate the selected feature(s).  Previously, this was not done and as such, the user had to first select the feature(s) and then place the Editor in an edit state in order to be able to use the Edit Tool.  Now, the user is able to select the feature(s) when the Editor is in an edit state and use the Edit Tool.  Note, that the Edit Tool is the tool which appears immediately to the right of the Editor button on ArcMap's Editor toolbar.

 

14.       Modification to the [Update Geometry] command for ArcGIS users, which appears under the {CEDRA commands} combo-box within the CEDRA-AVcad-Menus toolbar  A new option called Dirty Features Check has been added to the Mode of Operation choice list that is presented by this command.  This new option will check the active layer for features which have Null or Empty geometries, including annotation features which may also have a Null text string assigned to them.  If no dirty features are found, an information message box to this effect will be displayed.  If there are dirty features the user has the ability to delete them from the active layer.  Note that this option will process only one active layer at a time and if features are deleted, the user has the ability to Undo the deletion, if so desired.

 

AVwater New Features at Version 3.2q

 

1.         Addition of the [Change Conversion Properties] command under the {CEDRA Utilities} menu item.  The six items which appear in the multi-input message box posed by this new command were formerly under the [Change Text Properties] command.  These items were removed to make room for six new items.  The items handled by this new command deal with the conversion and annotation of polygon features.

 

2.         Modification to the {CEDRA Utilities} [Change Text Properties] command.  The bottom six items in the multi-input message box have been replaced by six new items.  The six items which were replaced now appear in the {CEDRA Utilities} [Change Conversion Properties] command.  The six new items deal with the annotation of area values.  The last item in the multi-input message box is a new parameter which enables the user to control the location of the area annotation.  The default value for this parameter Offset from Centroid will locate the area annotation in the same position as previously done.  The other settings, Centroid, Centroid - Above and Centroid - Below are new and enable the user to position the area annotation at the centroid, slight above the centroid and slightly below the centroid of the polygon.

 

3.         Modification to the {CEDRA Utilities} [Update Geometry] command.  The command will now prompt the user as to whether all of the active themes are to be processed or if all of the visible themes are to be processed.  A choice list message box is displayed upon activation of the command.  Previously, a YesNo message box was displayed when the command was activated.  Now the user selects from the drop-down the desired mode of operation.  As before, if a theme contains no selected features then all of the features in the theme are processed, otherwise, only the selected features are processed.

 

4.         Modification to the CEDRA-DataEditor extension, Version 2.1, for ArcGIS users.  The maximum number of items which can be displayed per dialog box has been increased from 20 to 30.  Note that when more than 20 items are to be displayed it is suggested that the screen resolution be set to 1280x1024 or higher.  If not, the dialog box will occupy a large part of the screen covering up more of the map display than is desired.

 

5.         Modification to the CEDRA-DXF-Export extension, Version 1.6, for ArcView GIS users, to be able to perform an export operation from within a Layout document.  Previously, an export operation could only be performed from within a View document.  Now, the user is able to export a Layout document, in addition to a View document, into a DXF file.  When this extension is loaded and a layout document is activated, the user will see the DXF Export menu item in the Layout menu bar.

 

6.         Modification to the CEDRA-DXF-Export extension, Version 1.6, for ArcGIS users, to be able to perform an export operation from within the Layout View.  Previously, an export operation could only be performed from within the Data View.  Now, the user is able to export a Layout View, in addition to a Data View, into a DXF file.  This is particularly useful when the user wishes to create a DXF file which reflects a fully assembled drawing, rather than a world view.

 

7.         Modification to the CEDRA-DXF-Export extension, Version 1.6, to honor a layer's scale threshold values.  Previously, this was not done, so that, even though the layer did not appear in the map the layer would be exported because it was visible.  Now, if the layer is visible in the Table of Contents, but due to the layer's scale threshold values it does not appear in the map, the layer will not be exported.

 

8.         Modification to the CEDRA-DXF-Export extension, Version 1.6, when exporting Arc/Info coverage annotation.  The degree symbol, ^, will now be converted into the typical degree symbol when the DXF file is created.  As such, the user will no longer see the ^ character when importing the DXF file.

 

9.         Addition of the {Text Properties} [Modify Graphic Text] command, for ArcGIS users.  This new command enables the user to change the properties of graphic text elements.  Specifically, the size, color, font and font style.  Users are able to modify the properties of selected graphic text elements or all graphic text elements in the map.

 

10.       Addition of the {Text Properties} [Modify Annotation Features] command, for ArcGIS users.  This new command enables the user to change the properties of annotation features.  Specifically, the size, color, font and font style.  Users are able to modify the properties of selected annotation features.  If there are no selected annotation features, an appropriate error message will be displayed.

 

AVwater New Features at Version 3.2p

 

1.         Modification to the CEDRA-DataEditor extension, Version 1.9, for ArcGIS users when using the ADDONE option in conjunction with the DEFAULT command.  The software will now keep track of the largest value assigned to an attribute using global memory.  The first time the ADDONE option is encountered for a specific attribute, the largest value for the attribute will be ascertained by parsing through the entire database at which point the largest value will be placed in global memory.  Thereafter, subsequent references to ADDONE for the same attribute, the software will use global memory to determine the largest value, rather than, parsing the entire database.  This modification increases performance greatly, especially when the database is large.

 

2.         Modification to the Avenue Wraps dynamic linked library (DLL) for handling PC ArcInfo coverages.  This modification enables ArcGIS users to have PC ArcInfo coverages loaded in their ArcMap document files.  Previously, ArcGIS users could not have a PC ArcInfo coverage loaded in their ArcMap document file.  This no longer is the case.

 

3.         Modification to the CEDRA-DataEditor extension, Version 2.0, when reading the Theme Attribute Data file.  The program will now check to see if the THEME and CHOICES commands are properly terminated with the END command.  If these commands are not terminated with the END command, an appropriate error message is generated.  Once the program has finished reading the entire Theme Attribute Data file, if any errors were detected, a list message box will be displayed informing the user as to what errors were detected.  The user can then modify the Theme Attribute Data file, afterwhich, the Reload Theme Attribute Data File tool can be used to import the modified file.  Previously, no error checking was performed.

 

4.         Modification to the A, N and P tools, for ArcGIS users when creating new shapefiles.  These tools will now assign the spatial reference to the respective shapefiles, provided the map has a spatial reference assign to it.  If the map does not have a spatial reference assigned to it, the Unknown Coordinate system will be assigned to the shapefiles.

 

5.         Modification to the Sequential IDs command within the CEDRA-Skeletonization extension, Version 2.1, to be able to process Tables, as well as, Themes.  Previously, the command would only process themes.  Now, if there are no active themes, the command will display the tables that exist in the project file, from which, the user selects the table that is to be processed.  For ArcGIS uers, the Sequential IDs command can be found in the CEDRA-Skeletonization-Tools toolbar and the user must select the Table that is to be processed.  Note that the Source tab at the bottom of the Table of Contents can be used to display the tables which exist in the ArcMap document.

 

6.         Addition of the Open Theme Table and Switch the Selection Set tools to the CEDRA-ArcView3-Tools toolbar.  This modification is for ArcGIS users only.  The Open Theme Table tool is used to open the attribute table for the active or selected layers in the map. This tool will also handle tables in addition to layers.  The Switch the Selection Set tool is used to switch or reverse the selection set for the active or selected layers in the map. That is to say, whatever is selected will become deselected and what was unselected will become selected. If the layer contains no selected features, then all features in the layer will be made selected, providing a quick way of selecting all features in a layer. This tool will also handle tables in addition to layers.

 

7.         Modification to the ReClassifyTheme subroutine, for ArcGIS users, to better maintain the existing symbology that is applied to a layer.  Previously, under certain conditions the classification of a layer would be altered by this subroutine.  Now, a layer's classification should be maintained when processed by this subroutine.

 

AVwater New Features at Version 3.2o

 

1.         Modification to the icatan and icasinan scripts for improved precision in computing arc tangent and arc sine values.

 

2.         Modification to the Dformat script for ArcView 3.3 compatibility.  This script is used to convert numbers into formatted strings.

 

3.         Modification to the Relocation tool for increase speed performance when updating the geometry and attributes of the pipes connected to the node that was moved.

 

4.         Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users to enable the user to assign a default value to an attribute that is equal to the maximum value in the field plus one (1.0).  A new option to the DEFAULT command called ADDONE has been added that provides this functionality.  The syntax of this option in conjunction with the DEFAULT command would be DEFAULT ADDONE.  Note that this option will work for both numeric and string type fields.

 

5.         Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users to enable the user to assign a default value to an attribute that is the current date.  A new option to the DEFAULT command called CURRENT_DATE has been added that provides this functionality.  An example of this option in conjunction with the DEFAULT command would be DEFAULT CURRENT_DATE.  The date string that is generated is of the form month/day/year, where the month and day values are numeric with no leading zero and each component is separated with the / character.  For example 6/9/2004 would be generated to represent June 9, 2004.  Note that this option will work for both date and string type fields.  If the user wishes to generate a custom date string the characters m, mm, mmm, mmmm, d, dd, ddd, dddd, yy and yyyy can be used.  For example the user could enter DEFAULT CURRENT_DATE_mm/dd/yyyy to generate a date string 06/09/2004.  As can be seen the m characters represent the month component, the d characters denote the day component and the yy and yyyy strings represent the year in short (04) and long form (2004).  The m and d characters denote the following:

            m                     month in numerical form with no leading zero

            mm                   month in numerical form with a leading zero, if need be

            mmm                month in abbreviated text form (i.e. Sep for September)

            mmmm             month in full text form (i.e. September, October, etc.)

            d                      day in numerical form with no leading zero

            dd                    day in numerical form with a leading zero, if need be

            ddd                  day in abbreviated text form (i.e. Wed for Wednesday)

            dddd                day in full text form (i.e. Monday, Tuesday, etc.)

            Should the user wish to introduce a space in the date string, the underscore character (_) should be used to represent the space.  Spaces can not be entered directly.  For example DEFAULT CURRENT_DATE_d_mmmm_yyyy would create the date string 9 June 2004.

 

6.         Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users to enable the user to control the number of attributes that are displayed in the dialog box, generated by this extension.  A new command called NLINES has been added which enables the user to specify a value between 1 and 20.  An example of the use of this command would be NLINES 12 which indicates that the maximum number of attributes that will be displayed in a dialog box would be twelve.  At least one blank character (space) must separate the number of attributes value from the NLINES command.

 

7.         Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users to enable the user to assign a default value to an attribute that is the X or Y coordinate of the feature's start, mid or end point.  Thirty-two new options have been added to the DEFAULT command.  A description of these options appears in the THEMES.TXT file located in the AVPRJS folder within the CEDRA distribution directory.

 

8.         Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users to enable the user to control the number of digits to the right of the decimal point that appears in the seconds component of a latitude or longitude value.  A new command called SECONDS has been added which enables the user to specify a value between 0 and 9.  An example of the use of this command would be SECONDS 3 which indicates that the number of digits in the seconds component would be three.  At least one blank character (space) must separate the value from the SECONDS command.

 

9.         Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users when using the TAB key.  Now, when the TAB key is used the software will highlight the text in the data field which has focus.  Previously, the software would simply place the cursor at the beginning or end of the text in the data field.

 

10.       Modification to the CEDRA-DataEditor extension, Version 1.8, for ArcGIS users when processing a feature in a layer which is classified to refresh the display of the layer.  Previously, this was not done which had the effect that if the feature which was processed was modified in such a way that the classification was effected, the display was not updated to reflect the new classification.  Now the software will refresh the display so that the classification is properly reflected.

 

11.       Modification to the {CEDRA Utilities} [Import Points] command when processing a file with one of the Polygon File Formats.  Previously, there was a restriction that each data line, below the initial data line describing a polygon, had to have at least five characters.  This restriction has now been removed.

 

12.       Modification to the Line 3 command |LINE DIR/DIST| in the display of the initial or default baseline direction.  The seconds component value is now displayed to five digits to the right of the decimal point.  Previously, it was displayed to only one digit.  This modification improves the calculations in maintaining the true direction of the baseline when the baseline is a "picked" line or when the baseline is defined by two picks.  If the baseline is explicitly entered, this modification will have no effect.

 

13.       Modification to the Point 3 command |POINT DIR/DIST| in the display of the initial or default baseline direction.  The seconds component value is now displayed to five digits to the right of the decimal point.  Previously, it was displayed to only one digit.  This modification improves the calculations in maintaining the true direction of the baseline when the baseline is a "picked" line or when the baseline is defined by two picks.  If the baseline is explicitly entered, this modification will have no effect.

 

AVwater New Features at Version 3.2n

 

1.         Modification to the Point 2 command |POINT DIR/DIST| in the display of the direction of the blue arrow when a polyline element is selected.  Previously, the direction would reflect the polyline's start to end point direction.  Now, the direction of the blue arrow will reflect the direction of the first or last course of the polyline, depending upon, which end point of the polyline is closest to the pick that was made to select the polyline.

 

AVwater New Features at Version 3.2m

 

1.         Modification to the {Modeling} [Execute] and [Re-Execute] commands to allow the user to select the EPANET 2 modeler, in addition, to the EPANET and KYPIPE modelers.  Version 2.00.10 of the EPANET 2 modeler is supported by AVwater and will be the default modeler displayed, when the {Modeling} [Execute] command is selected.

 

2.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when performing an analysis on a Windows XP system.  Previously, the analysis would take much longer than it should have.  Now, the analysis operates as quickly as it should, regardless of the type of Windows system in use.

 

3.         Modification to the CEDRA-AVwater-EPANET-Import extension, Version 1.6, to establish the EPANET 2 specific specialty tables, EPANETCurves, EPANETDemands, EPANETEnergy and EPANETRules when processing a .map and .inp file that was created with EPANET 2.  Previously these EPANET 2 commands were ignored by the extension.  Now the data that is associated with these commands will be stored in the respective specialty table.

 

4.         Modification to the {Modeling} [Times] command to display the current time values if the EPANETTimes specialty table exists.  In so doing, the user can modify existing values if desired.

 

5.         Addition of the EPANET 2 attributes, MODEL, COMPVOL and VOLCURVE, to the WaterTanks specialty table.  The MODEL attribute pertains to the mixing model that is associated with a storage tank.  Possible values for the MODEL attribute include MIXED, 2COMP, FIFO and LIFO.  The COMPVOL attribute pertains to the compartment volume, which represents the fraction of the total tank volume devoted to the inlet/outlet compartment.  The VOLCURVE attribute pertains to the volume curve ID, which enables the user to model non-cyclindrical tanks by specifying a curve of volume versus water depth.  The VOLCURVE attribute is a value that references a curve defined in the EPANETCurves specialty table.

 

6.         Addition of the EPANET 2 attribute, FLOWCOEF, to the WaterFittings specialty table.  The FLOWCOEF attribute pertains to the flow coefficient, flow units at 1 psi (1 meter) pressure drop, which is associated with Emitter types of fittings.  To accommodate Emitter fitting types, a NODTYP value of 15 has been added to the list of available fitting types display by the Define Node tool (N) and the Modify tool (M) when processing nodes.  When using the Modify tool (M) on an Emitter type of fitting, the user is able to enter a value for the FLOWCOEF attribute.

 

7.         Addition of the EPANET 2 attributes, CURVE, SPEED and PATTERN, to the WaterPumps specialty table.  The CURVE attribute pertains to the ID of the curve that describes head versus flow for the pump.  The CURVE attribute is a value that references a curve defined in the EPANETCurves specialty table.  The SPEED attribute pertains to the relative speed setting of the pump (normal speed is 1.0, 0.0 means the pump is off).  The PATTERN attribute pertains to the time pattern that describes how the speed setting varies with time.  The PATTERN attribute is a value that references a pattern defined in the EPANETPatterns specialty table.

 

8.         Addition of the EPANET 2 attributes, UNBALANCE, PATTERN, MULTIPLIER, EXPONENT and TOLERANCE, to the ControlData specialty table.  The UNBALANCE attribute determines what happens if a hydraulic solution cannot be reached within the prescribed number of trials.  Possible values for the UNBALANCE attribute include, STOP, CONTINUE and CONTINUE n, where n represents another "n" trials.  The PATTERN attribute represents the ID of a default pattern to be applied to all junctions where no demand pattern was specified.  The PATTERN attribute is a value that references a pattern defined in the EPANETPatterns specialty table.  The MULTIPLIER attribute pertains to the demand multiplier used to adjust the values of baseline demands for all junctions and all demand categories.  The EXPONENT attribute specifies the power to which the pressure at a junction is raised when computing the flow issuing from an Emitter type of fitting.  The TOLERANCE attribute represents the difference in water quality level below which one can say that one parcel of water is essentially the same as another.

 

9.         Addition of the EPANET 2 attribute, SOURCE, to the EPANETSources specialty table.  The SOURCE attribute pertains to the type of a water quality source.  Possible values for the SOURCE attribute include, CONCEN, MASS, FLOWPACED and SETPOINT.

 

10.       Addition of the EPANET 2 attributes, PATTERN_START, PS_UNITS, RULE_TIMESTEP, RU_UNITS, STARTCLOCK, CLOCKTIME and STATISTIC, to the EPANETTimes specialty table.  The PATTERN_START is the time offset at which all patterns will start.  The PS_UNITS attribute reflects the units of the PATTERN_START attribute value.  The RULE_TIMESTEP is the time step used to check for changes in system status due to activation of rule-based controls between hydraulic time steps.  The RU_UNITS attribute reflects the units of the RULE_TIMESTEP attribute value.  The STARTCLOCK attribute is the time of day at which the simulation begins.  The CLOCKTIME attribute reflects the units of the STARTCLOCK attribute value.  The STATISTIC attribute determines what kind of statistical post-processing should be done on the time series of simulation results generated.  Possible values for the STATISTIC attribute include, NONE, AVERAGED, MINIMUM, MAXIMUM and RANGE.

 

11.       Addition of the EPANET 2 attributes, ORDER_BULK, ORDER_WALL, ORDER_TANK, POTENTIAL and ROUGHNESS, to the EPANETReactions specialty table.  The ORDER attributes pertain to the order of reactions occurring in the bulk fluid, at the pipe wall or in tanks, respectively.  The POTENTIAL attribute specifies that reaction rates are proprtional to the difference between the current concentration and some limiting potential value.  The ROUGHNESS attribute will make all default pipe wall reaction coefficients be related to pipe roughness.

 

12.       Modification to the TIME_PATTERN attribute in the EPANETSources specialty table from a short integer to a character or string type of field.  This modification effects only those EPANETSources tables which are created using this version or later of the software.  Tables which were created with earlier versions of the software will still have the TIME_PATTERN attribute handled as a short integer field.

 

13.       Modification to the PATTERN_ID attribute in the EPANETPatterns specialty table from a short integer to a character or string type of field.  This modification effects only those EPANETPatterns tables which are created using this version or later of the software.  Tables which were created with earlier versions of the software will still have the PATTERN_ID attribute handled as a short integer field.

 

14.       Modification to the TIMEID attribute in the water model node theme from a short integer to a character or string type of field.  This modification effects only those node themes which are created using this version or later of the software.  Node themes which were created with earlier versions of the software will still have the TIMEID attribute handled as a short integer field.

 

15.       Modification to the {Modeling} [Times] command to enable the user to specify a value for the PATTERN_START and PS_UNITS attributes.

 

16.       Modification to the {Modify} [Control Data] command to enable the user to specify values for the EPANET 2 attributes UNBALANCE, PATTERN, MULTIPLIER, EXPONENT and TOLERANCE.  A new option called EPANET 2 Options has been added to the default pull-down list that is displayed by the command upon activation.  If one of these attributes is not present the ControlData specialty table, an error message will be displayed and the command aborted.

 

17.       Modification to the {Modeling} [Controls] command to enable the user to specify AT CLOCKTIME for the CONTROL_TYPE attribute.  Previously, only the options IF NODE and AT TIME were available.  Note that this value can only be used in conjuction with the EPANET 2 modeler.

 

18.       Modification to the {Modeling} [Controls] and the {Modify} [Control Data] commands expanding the list of available flow units to include the following: "GPM", "CFS", "MGD", "IMGD", "AFD", "LPS", "LPM", "MLD", "CMH", "CMD".  Note that only the EPANET 2 modeler will support all of the available flow units.  The EPANET and KYPIPE modelers will accommodate only those flow units which were previously available ("GPM", "CFS", "MGD", "SI").  The previously supported value, "SI", corresponds to the new value, "LPS".

 

19.       Addition of a new PRV type of valve.  The new type is referred to as a GPV or general purpose valve and corresponds to PRVTYP = 6 in the WaterPRVs specialty table.  Only the EPANET 2 modeler supports this type of PRV.

 

20.       Modification to the {Modeling} [Update Model Geometry] command to add any of the new fields discussed above into the appropriate tables, provided that the tables exist.  So that, if the user executes this command and if the tables mentioned above exist in the project file, the new fields that have been introduced as of this version will be added to the tables if they do not exist.

 

21.       Modification to the CEDRA-DataEditor extension, Version 1.7, to check if a field can be editted prior to writing to the field.  Previously, the extension would write to a field without performing this check, which would result in an attempt to edit read-only field error message.  Now the extension, first checks, if the field can be modified prior to writing any information to a field.

 

22.       Modification to the {CEDRA Utilities} [Import Points] command when processing a line shapefile in order to create point features at the endpoints of the lines in the shapefile.  The command will now ignore line features that have a zero length value.  Previously, invalid line features (lines that had no length or distance) would cause the command to "hang".

 

23.       Modification to the {Annotate} [Profile] command when generating a profile grid to display the index grid lines using a dashed linestyle and the heavy grid lines using a solid linestyle.  Previously, all grid lines were displayed using a solid linestyle.  The PEN attribute, within the grid line theme, is used to uniquely classify the grid line theme.

 

24.       Modification to the {Annotate} [Contours] command to allow the user to generate contours for any numeric attribute in the water nodes theme.  Previously, only the INFLOW, DEMAND, GRELVZ, GRADLN, PRESSR and WQANAL attributes were processed.  Now the user is able to select in addition to the above attributes any other numeric attribute (field) in the water nodes theme.

 

25.       Modification to the {Annotate} [Contours] command in creating the theme which contains the contour lines.  This code has been improved so as to decrease the amount of time that is used in generating the theme.

 

26.       Modification to the {Modeling} [Execute] and [Re-Execute] commands to perform the analysis in a temporary directory and then copy the resultant model files into the directory, as specified when the output file name is entered.  The temporary directory will be either c:\windows\temp, c:\winnt\temp, c:\temp, $temp, or the current working directory whichever is found first.  $temp denotes the Windows TEMP environment variable.  This modification enables the user to store the model in a directory structure with directory names longer than 8 characters.  Previously, the analysis was performed in the current working directory and as such each component of the directory structure had to be 8 characters or less in length.  Note that the output filename, which is specified, must still be 8 characters or less in length.

 

27.       Modification to the Point 2 command |POINT DIR/DIST| in the display of the direction of the blue arrow when a curve element is selected.  Previously, the direction would reflect the radial direction.  Now, the direction of the blue arrow will reflect the tangential direction of the curve.

 

28.       Modification to the Transformation tool when processing graphic text elements.  The tool has been modified for increased speed in determining which point feature a graphic text element is attached to, if any.  In conjunction with this modification, the user needs to create an index on the PNTN field (attribute) for all point themes which contain CEDRA text elements.  Typically these types of themes will carry the tx.shp extension.  Normal ArcView functionality can be used to create the index.  Note the index must be created in order to realize the improvement in performance.  If not, only a slight performance improvement will be recognized.

 

AVwater New Features at Version 3.2l

 

1.         Modification to the CEDRA-DataEditor extension, Version 1.6, to handle strings when using the ATTRIBUTE_EQUATION command.  Previously, the ATTRIBUTE_EQUATION command would only handle numeric expressions.  That is, the result of the equation had to yield a numeric value.  The ATTRIBUTE_EQUATION command can now be used to develop a string.  In this mode the plus sign (+) operator can be used to concatenate individual strings to form an overall string.  In addition, a new function called STRING has been added.  The STRING function can be used in conjunction with the ATTRIBUTE_EQUATION command to inform the extension that a field should be treated as a string and not a numeric.  Since it is possible to store numbers in string (character) fields, the STRING function allows the user to specify that a field contains string values and not numeric values.  If the STRING function is not used, the values for a field will be treated as numbers.  Furthermore, if the user wishes to explictly enter a hard-coded string, the user should enclose the string in double-quotes (").  In example number 2 below, the fields (attributes) PIN1, PIN2 and PIN3 are separated by a single dash.  There is no limit to the number of characters that can appear between the double quotes.

 

            The following illustrates the correct syntax for sample equations that develop strings.  Note that PIN1, PIN2 and PIN3 represent sample attributes (fields).

 

            1.         STRING(PIN1)+STRING(PIN2)

            2.         STRING(PIN1)+"-"+STRING(PIN2)+"-"+STRING(PIN3)

            3.         "My String = "+STRING(PIN1)+"000"+STRING(PIN2)+"-"+STRING(PIN3)+"00"

 

2.         Modification to the CEDRA-DataEditor extension, Version 1.6, to allow the user to use the wildcard character (*) when specifying the theme name in the Theme Attribute Data File.  Previously, the theme name had to be defined explicitly.  That is, the theme name had to be identical to how it appeared in the Table of Contents.  Now the user is able to use the wildcard character (*) so that multiple themes, which share common attributes and a common naming convention, can be specified with a single configuration.  For example, a view could contain three themes called ThemeA.shp, ThemeB.shp and ThemeC.shp.  The user, in this situation, could identify all three themes by entering Theme*.shp below the THEME command in the Theme Attribute Data File.  Likewise, if the themes shared a common prefix the user could enter Theme*, which would indicate that all themes beginning with the string Theme would be applied the configuration that appeared in the Theme Attribute Data File.

 

3.         Modification to the {CEDRA Utilities} [Convert Graphic Text] command to properly compute the text angle and store the angle in terms of degrees.  Previously, the command would convert the text angle from radians into degrees when the text angle was already in degrees.

 

4.         Modification to the {CEDRA Utilities} [Convert Graphic Text] command in terms of performance when processing large number of graphic text elements.  The command should now execute much faster when dealing with a large number of graphic text elements.  The script icfilstx has been modified to not issue the .GetNumRecords request when the attribute table is in edit mode.  This allows the command to run faster.

 

AVwater New Features at Version 3.2k

 

1.         Modification to the {Import} [Points] command to enable the user to create two-point line features based upon vertex coordinates.  A new option called Line Coordinate File - 3 has been added to the File Type pull-down list that is presented by the command.  The Line Coordinate File - 3 option, enables the user to process a file that contains a sequential list of point coordinates, which are to be connected in series.  This option creates lines using coordinate pairs.  That is, once the option has two points it creates a line.  For example, the points contained on data lines 1 and 2 form the first line.  The points contained on data lines 2 and 3 form the second line, while the points contained on data lines 3 and 4 form the third line and so forth.  As can be seen, the end point of the previous line acts as the start point of the subsequent line.  In addition, if the user wishes to copy the attributes of the points into the line theme that is created, the command will store the attributes of both points that define the line.  The two character extension _S is added to the field name to indicate that the information in this field pertains to the first or start point that defines the line.

 

2.         Modification to the Transformation tool when using the option Set Graphic Text Angle (Explicit), this option will now display the text angle of the selected graphic text element, according to the setting of the direction property, as the default value in the appropriate data field.  For example, if the direction property is set to bearings, the default value that will appear in the bearing data field will be the current text angle of the selected graphic text element.  Should the user wish to enter a text angle in a form other than that as specified by the direction property, the user can simply enter the desired value in the appropriate data field and enter a blank in the other data field.

 

3.         Modification to the Transformation tool when using the option Set Graphic Text Angle (Explicit), this option will now process more than one selected graphic text element.  Previously, this option only processed a single selected graphic text element.  This option will now process all of the selected graphic text elements.  This default text angle that is displayed is the text angle for the first selected graphic text element that is found.

 

4.         Modification to the Transformation tool when using the option Set Graphic Text Angle (2 Pts), this option will now treat baseline angles that are between 270 and 274 degrees as if they were between 90 and 94 degrees.  In so doing, the graphic text elements will be pointing upward and not downward.

 

AVwater New Features at Version 3.2j

 

1.         Modification to the CEDRA-DataEditor extension, Version 1.5, to display the BACK button immediately below the CANCEL button, when multiple pages are displayed.  The BACK button enables the user to return to the previous page that was displayed.  Previously, there was no way for the user to back up or return to a page that was previously displayed.  Now the user can use the OK button to advance one page and the BACK button to return to the previous page.  Note that the BACK button will not appear on the first page of a multi-page set.

 

2.         Modification to the CEDRA-DataEditor extension, Version 1.5, to support the ATTRIBUTE_EQUATION command.  This new command enables the user to have the value for an attribute calculated by evaluating a user-defined equation, as opposed to direct user entry.  Immediately below the ATTRIBUTE_EQUATION the user enters on a single line the desired equation.  Equations are solved proceeding left to right resolving expressions within parentheses first.  When parentheses are nested they are resolved inside to outside.  That is, the inner most set of parentheses are solved first, then the next inner most and so forth.  When there are more then one nests of parentheses, each nest is resolved inside to outside and from left to right.  The user is able to use parentheses to ensure that the desired sequence of calculations is performed

 

            The supported Mathematical operators include:

 

            1.         ^                      = Exponentiation,

            2.         /                       = Division,

            3.         *                      = Multiplication,

            4.         +                      = Addition,

            5.         -                       = Subtraction.

 

            The supported Boolean operators include:

 

            1.         =                      = Equality,

            2.         <                      = Less than,

            3.         >                      = Greater than,

            4.         <=                    = Less than or equal to,

            5.         >=                    = Greater than or equal to,

            6.         <>                    = Not equal to.

 

            The supported Functions include:

 

            1.         ABS                = absolute value of a number,

            2.         ACOS             = arc cosine of a number expressed in radians,

            3.         ASIN               = arc sine of a number expressed in radian,

            4.         ATAN             = arc tangent of a number expressed in radians,

            5.         COS                = cosine of a number expressed in decimal degrees,

            6.         DEG2RAD     = conversion of degrees to radians,

            7.         RAD2DEG     = conversion of radians to degrees,

            8.         ROUND         = rounding up of a number to the nearest whole number,

            9.         SIN                 = sine of a number expressed in decimal degrees,

            10.       SQRT             = square root of a number greater than zero,

            11.       TAN                = tangent of a number expressed in decimal degrees,

            12.       TRUNCATE  = truncation of a number.

 

            The user is also able to employ the IF( conditional to add decision making functionality into the equation evaluation process.  When using the IF( conditional, the user specifies an expression, a true condition and a false condition.  As such, the command evaluates the expression so that either a true or a false condition exists.  The true or false condition that the user specifies is then applied.

 

            The following illustrates the correct syntax for sample equations.  Note that J2, K2, P2, R2, Q2, M2, L2, S2 and N2 represent sample attributes (fields).

 

            1.         J2-K2

            2.         29.8*P2*R2*Q2^2*SQRT(M2)

            3.         ((J2-20)/L2)^0.54*N2

            4.         S2*N2

            5.         IF(Q2=2.5,0.9,IF(Q2=4.5,0.78,IF(Q2=1.9,0.97,IF(Q2=2.5,(Q2^-0.092*1.0808),4.0))))

            6.         DEG2RAD(ACOS(0.5))

            7.         ASIN(0.75)

            8.         ATAN(0.35)

            9.         SIN(30)

            10.       COS(60)

            11.       TAN(45)

            12.       ROUND(4.75)

            13.       TRUNCATE(4.75)

 

            It is noted that in the sample equations above there are no leading, trailing or embedded blank spaces.  However, such blank spaces may be introduced if deemed necessary for the sake of clarity.  If so, they will be disregarded by the program.

 

3.         Modification to the {CEDRA Utilities} [Convert Graphic Text] command to store the font name and style (italic/bold) in the database.  Previously, this was not stored.  Now when a graphic text element or a group of graphic text elements are converted the font name and style properties will be stored in the database (shapefile).  So that if the {CEDRA Utilities} [Generate Text from Table] command is used to recreate the graphic text element, the graphic text element that is created will properly reflect the original graphic text element.

 

4.         Modification to the Transformation tool.  Three new options have been added to the pull-down list that is presented by the command.  The new options include Set Graphic Text Angle (2 Pts), Set Graphic Text Angle (Pick Line) and Set Graphic Text Angle (Explicit).  These new options provide the user the ability to set the angle of inclination for a graphic text element.  In addition, these options will update the database if the graphic text element is associated with a feature in a shapefile.  Note that the options Set Graphic Text Angle (2 Pts) and Set Graphic Text Angle (Pick Line) will offset the graphic text element from the implied two point or picked line using the value for the annotation offset parameter under the [Text Parameters] command.

 

AVwater New Features at Version 3.2i

 

1.         Modification to the CEDRA-DataEditor extension, Version 1.4, in which the DEFAULT command has been modified to support the keycodes RETURN_LENGTH, RETURN_AREA and RETURN_AREA_UNITS.  These commands will use as the default value for an attribute: (a) the length or perimeter of a feature (RETURN_LENGTH), (b) the area of a feature in square feet or square meters (RETURN_AREA) or (c) the area of a feature in acres or hectares (RETURN_AREA_UNITS).  To use these keycodes, the user simply enters the appropriate keycode after the DEFAULT command with at least one space separating the two items.  As an example, the user could enter DEFAULT  RETURN_AREA to have the DataEditor extension compute and display the area of a feature, in square feet or square meters, as the default value for an attribute.

 

2.         Addition of the CEDRA-UndoEdits extension, Version 1.1, which when used with the CEDRA-DataEditor extension enables the user to utilize the CEDRA-DataEditor extension without loading the AVwater extension.  In so doing, the CEDRA-DataEditor can operate in a stand-alone environment.

 

3.         Modification to the {Modeling} [Load Generation] command to recognize either the AVW_NODENO or NODENO fields as the field containing the node number to which the polygon is attached to.  Previously, only the AVW_NODENO field was examined.

 

4.         Modification to the Modify tool (M) when modifying a node or a pipe number to update all specialty tables that reference the original node or pipe number.  Previously, when a node or pipe number was changed, the command would not check all of the specialty tables.  As such, even though the node or pipe number was changed, some of the specialty tables would still reference the original node/pipe number.  This no longer will occur.

 

5.         Modification to the Modify tool (M) to operate fully with the {CEDRA Utilities} [Oops] command.  So that, if the user wishes to undo an operation performed with the Modify tool, the user can now do so.

 

6.         Modification to the {Modify} [Classification] command to display two new options called User Defined Node and User Defined Pipe.  These options inform the program that the user has assigned a customized classification to the node or pipe themes and that the program should leave the classification of these themes as is.  Previously, if the user had customized the legend for the node or pipe theme and then defined or modified an existing node or pipe, the program would replace the customized legend with one of the AVwater default legends.  This no longer will occur.  So that, if the user customizes the legend for the node or pipe theme and wishes to maintain this legend, the user should activate this command and select either the User Defined Node or User Defined Pipe option depending upon which legend has been customized.  Note that when AVwater is loaded, it checks to see if the project file contains an AVwater model, if so, the legend assigned to the node and pipe themes is maintained.  If the project file does not contain an AVwater model and one is created, the program will use the AVwater default model legend for the node and pipe themes.  Furthermore, note that the {CEDRA Utilities} [Update Classifications] command can be used to refresh or update the legend that is assigned to a theme.  This is useful when the user adds or deletes features in a theme that has a customzied legend.  In this case, the legend in the Table of Contents is not updated by ArcView to reflect the addition or deletion of the feature.  The [Update Classifications] command, however, can be used to refresh or update the legend to properly reflect the addition or deletion of the feature.

 

7.         Modification to the {CEDRA Utilities} [Update Classifications] command to not only check the label that is assigned to a class but also the range of a class in order to maintain the symbology and labels used in a classification.  Previously, only the label was checked which would not handle the case of  a theme being classified on a field of numeric type and with labels that are strings.  This modification provides a stronger methodology of ensuring that the same symbols and labels that appear in a legend are maintained when the theme is reclassified.  This command is very useful when the user adds or deletes features in a theme that has a customzied legend.  In this case, the legend in the Table of Contents is not updated by ArcView to reflect the addition or deletion of the feature.  The [Update Classifications] command, however, can be used to refresh or update the legend to properly reflect the addition or deletion of the feature.

 

8.         Modification to the {Modeling} [Update Model Geometry] command for improved importing of existing Cybernet models.  The command will now process the individual shapefiles that are created by Cybernet for the various node types that comprise the model.

 

9.         Modification to the {Modeling} [Update Model Geometry] command to add the PIPNAM attribute into the water pipe theme.  This new attribute is of character or string type with a field width of 40 characters.  The intent of this new attribute is to store an alphanumeric ID.

 

10.       Modification to the {Query} [Range], [Highs], [Lows] and [Rev. Flow] commands to include the NODNAM and PIPNAM attribute values in the reports that these commands generate.  Note that the NODNAM and PIPNAM attributes can be used to store node or pipe IDs, respectively, which are alphanumeric in nature.  The maximum number of characters that can be used in an alphanumeric ID is 40.

 

11.       Modification to the Load tool (L) when processing PRV type of valves.  The command will now recognize the various types of PRV values (PSV, PBV, FCV, ...).  Previously, the command only handled PRV type of valves.  Now the command will prompt the user accordingly based upon the type of PRV being processed.

 

12.       Modification to the {CEDRA Utilities} [Generate Text] command for increased performance in terms of speed.  That is to say, the command will now create text primitives significantly faster.  The command will also display the time at which processing began and terminated in the status bar area.  In so doing, the user is able to determine how long it took to generate the text primitives.

 

13.       Modification to the icfilstx script to store the name of the font in addition to the other pertinent text primitive attributes (such as height, width, etc.).  A new field called NAME will appear in the text primitive shapefile.  This is a string or character type field with a maximum width of 80 characters.  The Text Panel within the Symbol Window can be used to define the current active font.

 

14.       Modification to the icfilstx script to store the font type style of the text primitive being created.  The font type style pertains to whether the font is normal or italic and whether it is bold or normal.  The ITAL field contains a numeric value denoting if the font is normal (ITAL = 1) or italic (ITAL = 2).  The MODE field, likewise, contains a numeric value denoting if the font is normal (MODE = 1) or bold (MODE = 3).

 

15.       Modification to the icfilstx script to store the color of the text primitive being created.  A numeric value corresponding to the color index value is stored under the COLR field.  Color index values begin at zero and are incremented sequentially by one.  The color index value can be determined by reviewing the Color Panel within the Symbol Window.  In the Color Panel there will be several rows and columns of different colors.  Color Index 0 represents column one of row one.  Proceeding left to right on a row by row basis, the color index values increment by one.  So that, the color index value of the sixth column of row one is 5 (typically the color black).  Likewise, the color index value of the first column of row two is 6.

 

16.       Modification to the {CEDRA Utilities} [Generate Text] command to use the current active font, as defined in Text Panel within the Symbol Window, when creating text primitives.  The exception to this is when the table that is being processed contains a font name.  The font name is stored under the NAME field.  If this field exists, the font appearing in this field will be used and not the current active font.

 

17.       Modification to the Transformation tool.  Two new options have been added to the pull-down list that is presented by the command.  The new options include Move Selected Features (dx,dy) and Move Selected Features (dir,dist).  These new options provide the user the ability to move a feature or a group of selected features either (a) along the x and y axes a user-specified amount, or (b) along a direction a user-specified distance.

 

18.       Modification to the {CEDRA Utilities} [Zoom Scale Factor] command to remain active until the user selects the Cancel button.  In so doing, the user is able to alter the display of the view without having to reselect the command.

 

19.       Modification to the Point 3 command |PLUS/OF| to provide the user the ability to specify a starting station value.  When a starting station value has been specified, the plus value that is used in computing the point is the difference between the plus value entered by the user and the starting station value.  For example, if the starting station value is 1000 and the plus value entered by the user is 1400, the command would use 400 in computing the coordinates of the point.

 

AVwater New Features at Version 3.2h

 

1.         Modification to the {Annotate} [User Text] command to enable the user to create annotation or text for multiple fields in a single operation.  A new option called Attribute(s) from the Table has been added to the choice message box that is displayed by the command. When creating text for certain fields in a database, the user should first select the feature or features that are to be processed.  Once selected, the [Text or Attribute] command can be activated followed by selecting the Attribute(s) from the Table option. The user will then be asked to identify the field or fields that are to be used in the generation of text.  Upon completion of the field identification, a dialog box will be displayed. On a row by row basis, the field or fields selected by the user will be listed. The default order of the fields will correspond to their order in the database. The user, at this point, can control the order of the text by selecting the appropriate field from the Attribute pull-down list. The order in which the fields are listed in the dialog box will reflect the order in which the text is listed on the map.  For each field in which text is to be created, the user is able to control the font, font style and font size that is used in creating the text. Any true-type font installed on the computer is available to the user for selection. In addition, the user is able to specify a prefix and/or suffix to the text.  Once created, the user has the ability to reposition the text to eliminate any overlap or interferences, if any, using any of the available relocation tools.  The [Text or Attribute] command will process Point, Line and Polygon features and always lists the text in a vertical fashion. Users involved with surveying or engineering applications will find this command an ideal tool for labeling curve data, while those involved with marketing or business applications will find this command extremely helpful in transferring database information onto a map.

 

2.         Modification to the CEDRA-DataEditor extension, Version 1.3, in which (a) the width of the dialog box has been increased, (b) the DataEditor tool has been converted into a tool menu and (c) the addition of the REMEMBER_LAST command.  The CEDRA-DataEditor extension now consists of a tool menu that is comprised of 3 individual tools.  The first is the DataEditor tool, previously available, which allows the user to edit specific attributes that are associated with a feature.  The two new tools that have been added enable the user to (a) reload the Theme Attribute Data File from within ArcView and (b) delete selected features that exist within the user-defined themes.  Should the features that are to be deleted have associated tables related to them, the corresponding records in the associated tables will also be deleted.  The new command REMEMBER_LAST allows the user to use the last value that was assigned to an attribute as the default value for an attribute, provided that the current value for the attribute is blank, for a character type field, or 0, for a numeric type field.

 

3.         Addition of two new size options to the {Resize} [Application] menu item.  These new options enable the user to see the task bar concurrently with the ArcView application.

 

4.         Addition of new size options to the {Resize} [Windows] menu item.  These new options provide additional pre-defined window sizes for the user to chose from.

 

AVwater New Features at Version 3.2g

 

1.         Addition of the CEDRA-DataEditor extension which enables the user to interactively edit the attributes associated with a feature.  When loaded, the CEDRA-DataEditor extension adds one tool to the View document toolbar, which is referred to as the Edit Feature Attributes tool.  This tool enables the user to select a feature (point, line, curve or polygon) and edit the attributes that are associated with the feature.  A multi-input dialog box is displayed containing the feature's attributes.  The user can control which attributes are displayed and their order by modifying the file themes.txt which is located in the CEDRA distribution directory, for PC based users typically \cedra\avprjs.  The file themes.txt contains a list of themes and the attributes within the theme which are available to the user for editting with the Edit Feature Attributes tool.  If a feature is selected that belongs to a theme, which does not appear in the themes.txt file, the user has the option of copying the feature into a theme, of the same feature type, that does appear in the themes.txt file.  When loaded, the CEDRA-DataEditor extension searches the current working directory for the themes.txt file.  If this file does not exist in the current working directory, the CEDRA distribution directory is searched.  In so doing, the user is able to create different themes.txt files for different projects, which the user is involved with, by storing in different directories the various themes.txt files.  If the themes.txt file does not exist in the CEDRA distribution directory, an error message will be displayed and the user will not be able to use the Edit Feature Attributes tool.  If the themes.txt file is modified while the extension is loaded, the user will need to exit ArcView and reload the project file in order for the modifications to the themes.txt file to be available to the user.  That is to say, the themes.txt file is read only once, and it is when the extension is initially loaded.  It is recommended that the user copy the themes.txt file from the CEDRA distribution directory into a working directory and modify the file as desired.  Any word processor or text editor can be used to modify the themes.txt file.  Instructions on how the file should be structured are included in the file.

 

2.         Modification to the Point 2 command |POINT DIR/DIST| when using the R option to compute the coordinates of the point so as to coincide with the direction of the blue arrow.  Previously, the point that was created was based upon a direction that was opposite (180 degrees out of phase) of that shown by the blue direction arrow.  This situation only occurred when the user selected a line or curve feature, with the pick that was made to select the feature being closer to the feature's start point.  If the pick that was made to select the feature was closer to the endpoint of the feature, the point that would be generated would coincide with the direction of the blue arrow.

 

3.         Modification to the extension to allow the user to enter a Bearing direction even though the user is prompted for an Azimuth or Cartesian direction.  Whenever, the user is prompted for an Azimuth or Cartesian direction, and the user wishes to enter the direction as a Bearing, the user can do so provided the quadrant identifier is in character form, not numeric.  For example, the user could enter a Bearing of NW 20 45 50.1, or N 20 45 50.1 W.  The normal rules for entering Bearings using the characters, NE, SE, SW, NW, N, S, E or W to identify the quadrant apply.  This modification enables the user to enter a direction in a form different than the setting of the direction property, without having to change the direction property.

 

4.         Modification to the extension to allow the user to enter an Azimuth or Cartesian direction even though the user is prompted for a Bearing direction.  Whenever, the user is prompted for a Bearing direction, and the user wishes to enter the direction as an Azimuth or Cartesian, the user can do so by entering the desired direction preceded by the keycode A or C, denoting an Azimuth or Cartesian direction.  For example, the user could enter a Cartesian direction of C 45, or C 20 45 50.1.  As long as the keycode precedes the value, with at least one space separating the keycode and value, the user is able to enter directions in a form different than the setting of the direction property, without having to change the direction property.

 

5.         Modification to the CEDRA-GridAQuadrilateral extension to enable the user to generate line segments that represent the sides of the polygons that are created and/or polylines that represent the outline of the polygons that are created.  Two new data items have been added to the multi-input dialog box that the command displays.  By entering Y or N to the appropriate data item, the user indicates whether these features are to be created or not.  The default response to the create polyline data item is Y.  In so doing, the user can continue to perform subdivisions on the polylines that are created.

 

6.         Modification to the {Modify} [Node/Pipe Numbers] command to process the speciality tables.  Previously the speciality tables were ignored since the command was initially designed to be executed prior to the model being defined.  Now this command can be executed after a model has been defined knowing that all references to node and pipe numbers will be adjusted throughout the model.

 

7.         Modification to the {Import} [Points] command when processing EPANET .map files.  The command will now process EPANET Version 2.0 .map files.  Previously, only EPANET Version 1.0 .map files were processed, now the command will import both versions.

 

AVwater New Features at Version 3.2f

 

1.         Modification to the extension to not resize the ArcView application window when the extension is loaded.  Previously, the extension would resize the application window to fill up as much of the desktop area as possible.  Now the extension will honor the size of the ArcView application window leaving it in the same position and at the same size.

 

2.         Modification to the extension, CEDRA-ChangeFeatures (Version 1.4), which is included with the distribution software.  The two commands within this extension will now query the user if the common attributes of the selected features are to be updated in addition to changing their shapes.  This query is presented just prior to changing the shape of the selected feature(s).  A YesNoCancel message box is displayed.  If the Cancel button is selected the commands will abort without changing the shape or the attributes of the selected features.  If the No button is selected the commands will only change the shape of the selected features.  If the Yes button is selected, the commands will change not only the shape of the selected features but also all of the common attributes.  A common attribute is defined as a field which not only has the same name but is also of the same type.

 

3.         Modification to the S tool when encountering small segments during the Point and Auto-Search operation.  Previously when a small segment was encountered nothing special was done.  As such, depending upon the view it was sometimes very difficult, if not impossible, to determine the exact path that was being highlighted.  The search engine used by this command has now been changed to alter the display of the view when (a) encountering small segments and (b) when a feature falls outside of the current view.  In so doing the user is now able to easily determine which path is being displayed during the Point and Auto-Search operation.  Upon confirmation of the path, one way or the other, the display of the view is changed back to its original state.  A small segment is defined as one which has a length that is less than 1.5 times the snap tolerance value.  If the snap tolerance is defined as a percentage of the view, then this value changes in accord with the view.

 

4.         Modification to the {Modeling} [Load Generation] command to check if the A, B or C fields contains null data.  Previously this was not done and as such, if one of these fields contained null data, the field in which the computed load was to be stored would also contain null data.  Now, if one of these fields contains null data, the command will use a value of one (1.0) in its computations.  Note that this command expects the values in the A, B and C fields to be of numeric type (numbers), not of character or string type.

 

5.         Modification to the {CEDRA Utilities} [Flip/Reverse Lines] command to redraw the view upon completion of the command's processing.  Previously the view was not redrawn, so that if the features which were flipped were drawn in a direction oriented linestyle (such as with arrow heads), the effect of the command would not be immediately realized graphically.

 

6.         Modification to the {Modeling} [Load Generation] command for methods 1 through 4 to allow the user to define the nodal contributing polygon such that each building polygon's center that falls within the nodal contributing polygon will be constituted as contributing to the associated node.  Previously, the entire building polygon had to be contained within the nodal contributing polygon.  This modification makes the definition of the nodal contributing polygon a little bit easier for the user.

 

7.         Addition of the CEDRA-GridAQuadrilateral extension which enables the user to create polygons within a quadrilateral by specifying the number of rows and columns.  The quadrilateral is represented by a polyline feature that contains four sides and whose last point matches the first, thereby, forming a closed figure.  After the user selects the polyline feature, the command prompts the user for the number of rows and columns.  Using this information the command will create the appropriate polygons placing them in the current active layer.  The spacing between the rows is computed by taking the distance between the second and third points in the polyline and dividing by the number of desired rows.  Likewise, the column spacing is computed by taking the distance between the first and second points in the polyline and dividing by the number of desired columns.  The polygons are created left to right and from bottom to top.  The left to right direction is controlled by the direction of the first two points in the polyline.  In addition, the user has the option of creating points at the vertices of the polygons that are created.  The default is not to create points.  If the user desires to create points then the user should enter y in the appropriate location in the multi-input dialog box that is displayed by the command.  Note that no duplicate points will be created.  Like the polygons that are created, the points are placed in the current active layer.  If the user does not select a feature or selects a non-polyline feature (point or polygon), an appropriate error message will be displayed and the command aborted.

 

8.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when using the KYPIPE modeler during Extended Period Simulations.  Previously the data files that were created during the analysis and used by the {Annotate} [EPS Graphs] command were incomplete under certain conditions.  This is no longer the case and the user should be able to create EPS graphs when using the KYPIPE modeler as well as the EPANET modeler.

 

9.         Modification to the {Import} [Points] command to allow the user to have comment lines in the file that is to be processed.  By placing the /* characters in columns 1 and 2 of a data line, the user is able to enter a comment.  Comment lines are ignored by the command and enable the user to make the file more readable.

 

10.       Modification to the {Import} [Points] command when using one of the Polygon 1 through 12 formats.  These formats have been expanded to allow the user to define strings and to support the keycodes: NO POLY, POLY, START, END, CHORD, ANGLE and ARC.  Strings may be open or closed figures.  That is, the end point of a string may or may not be the same as the start point of the string.  The NO POLY keycode informs the command that polygon features are not to be created but rather line and curve features are to be created.  Once the NO POLY keycode has been specified it stays in effect until the POLY command appears.  The POLY command indicates that polygon features are to be created.  As such, it is possible for the user to create a file that creates both polygon as well as line and curve features.  If a string is to be created, the NO POLY keycode must appear in the file prior to the definition of the string(s).  Note that if only strings are to be created, the NO POLY keycode needs to appear only once.  The START keycode enables the user to specify the starting point of a polygon or a string to be the start point of a previously defined polygon or string.  Likewise, the END keycode enables the user to specify the starting point of a polygon or string to be the end point of a previously defined polygon or string.  The CHORD, ANGLE, and ARC keycodes enable the user to define tangent curves.  The default curve definition consists of specifying a chord direction, chord length and radius.  The CHORD, ANGLE and ARC keycodes provide the user three new means of defining a curve.  The curves that are created using these keycodes are tangent to the previous course.  A sample file containing comment lines as well as the keycodes mentioned above is shown below:

 

      /*

      /* This is a sample of the Polygon 6 file format

      /*

      /* Comments can be inserted in the file by placing the /*

      /* characters in columns 1 and 2 of a data line

      /*

      /* The special keycodes include the following:

      /*

      /* NO POLY  do not create polygons but rather lines and curves

      /* POLY     create polygons not lines and curves

      /* START    set start point of a polygon or string to be the start point of

      /*          a previously defined polygon or string

      /* END      set start point of a polygon or string to be the end point of

      /*          a previously defined polygon or string

      /* CHORD    tangent curve given chord length and radius

      /* ANGLE    tangent curve given central angle (Degrees, Minutes, Seconds) and radius

      /* ARC      tangent curve given arc length and radius

      /*

      /* Command denoting do not create polygons

      /*

      NO POLY

      /*

      /* First String (which happens to be a closed figure) with 10 vertices

      /*

      87831528 4000.0 4000.0 10

      586.77753 SW 88  8 41.7

      402.97627 NW 34  3 58.3

      348.47370 NW  5 12 41.3 361.045

      363.51546 NE 23 38 35.7

      407.47558 NE 74 27  0.8

      /*

      /* Note that you can have comments anywhere in the file

      /*

      282.80400 SE 78  4 28.4 306.486

      270.80277 SE 50 35 57.6

      171.79402 SE 20 29 13.3

      505.86450 SW  8 37 47.6 519.802

      268.99867 SW 37 44 48.5

      /*

      /* Second String comprised of 4 lines and 1 curve defined in a Clockwise direction

      /*

      87831529 5000.0 5000.0 5

      200 NE 00 0 0.0

      200 NE 90 0 0.0

      /*

      /* Curve defined by chord length, chord direction and a radius

      /*

      141.4214 SE 45 0 0 100.0

      -100 NE 0

      -300 NE 90

      /*

      /* Same as string above but defined in a CounterClockwise direction

      /*

      87831530 5000.0 5500.0 5

      300 NE 90

      100 NE 0

      /*

      /* Negative radius denotes CounterClockwise direction

      /* Positive radius denotes Clockwise direction

      /*

      141.4214 NW 45 0 0 -100.0

      -200 NE 90 0 0.0

      -200 NE 00 0 0.0

      /*

      /* Single line starting at known coordinates

      /*

      87831531 5500.0 5500.0 1

      300 NE 90

      /*

      /* Single line starting at the end point of the string defined above

      /*

      87831532 END 87831531 1

      -300 NE 00

      /*

      /* Command denoting create polygons not line and curve features

      /*

      POLY

      /*

      /* Polygon starting at the start point of a string

      /*

      87831533 START 87831532 5

      100 NE 00

      300 NE 90

      100 NE 00

      -300 NE 90

      -100 NE 00

      /*

      /* Command denoting do not create polygons

      /*

      NO POLY

      /*

      /* String with tangent curve defined by arc length and radius

      /*

      87831534 5300 5900 5

      -300 NE 90

      50 NE 0

      ARC 78.540 50

      250 NE 90

      -100 NE 0

      /*

      /* String with tangent curve defined by chord length and radius

      /*

      87831535 5700 5900  5

      -300 NE 90

      50 NE 0

      CHORD 70.7108 50

      250 NE 90

      -100 NE 0

      /*

      /* String with tangent curve defined by central angle and radius

      /*

      87831536 6100 5900  5

      -300 NE 90

      50 NE 0

      /*

      /* Central angle specified in degrees, minutes and seconds

      /*

      ANGLE 90 0 0 50

      250 NE 90

      -100 NE 0

      /*

      /* Same three strings above but defined in a CounterClockwise direction

      /*

      87831537 5000 4700 5

      300 NE 90

      50 NE 0

      ARC 78.540 -50

      -250 NE 90

      -100 NE 0

      /*

      87831538 5400 4700  5

      300 NE 90

      50 NE 0

      CHORD 70.7108 -50

      -250 NE 90

      -100 NE 0

      /*

      87831539 5800 4700  5

      300 NE 90

      50 NE 0

      ANGLE 90 0 0 -50

      -250 NE 90

      -100 NE 0

      /*

      /* String with Reverse Curves

      /*

      87831533 END 87831532 12

      250 NE 90

      ANGLE 90 0 0 50

      ANGLE 90 0 0 -50

      100 NE 90

      -100 NE 0

      -200 NE 90

      50 NE 0

      ANGLE 90 0 0 -50

      ANGLE 90 0 0 50

      -100 NE 90

      ANGLE 90 0 0 50

      /*

      /* End of the sample File

      /*

 

11.       Modification to the {Import} [Points] command when processing a line shapefile in order to create point features at the endpoints of the lines in the shapefile.  The command will now create two fields called FNODE_ and TNODE_ in the selected line shapefile.  The values stored in these fields reflect the from and to node numbers and correspond to the NODENO attribute associated with the points that are created.  The field definition for these two new attributes are #FIELD_LONG,12,0.

 

12.       Modification to the {Modeling} [Update Model Geometry] command to update the AREANO, NETWNO, MAPNUM and NODNAM attributes in the speciality tables to be identical with those stored in the node theme for the corresponding node.  Previously, if the user changed any of these attributes in the node theme, the user would have to perform the same modification on the appropriate speciality table.

 

13.       Addition of the {CEDRA Utilities} [Sort Table of Contents] command which allows the user to sort or rearrange the themes that appear in the View's Table of Contents.  Upon activation, the user is presented with a choice message box containing five options, (a) ASCENDING, (b) DESCENDING, (c) MOVE ACTIVE THEMES TO TOP, (d) MOVE ACTIVE THEMES TO BOTTOM and (e) MOVE ACTIVE THEMES BELOW THEME.  As the names of the options indicate, the user can (1) sort the Table of Contents such that (a) the themes appear alphabetically in an ascending order, or (b) the themes appear alphabetically in a descending order, or (2) rearrange the Table of Contents by moving the active themes (c) to the top of the Table of Contents, (d) to the bottom of the Table of Contents, or (e) below the location of another theme which the user specifies.  This command is very useful when the Table of Contents contains many themes which when using normal ArcView functionality, rearranging the Table of Contents can be tedious.

 

AVwater New Features at Version 3.2e

 

1.         Ability to customize the default values for certain AVwater properties such as the Units of Measure, Angular Form, Direction Form, Text Size, Annotation Offset and more.  An ASCII file called CONFIG.TXT, located in the CEDRA distribution directory, contains a list of the AVwater properties that can be customized by the user.  A single data line appears for every property available to the user.  On each data line the property value appears first followed by a comment describing the propery.  The comment begins with the /* characters and describes the property along with the possible values for the property.  The user may employ any word processor or text editor to customize the CONFIG.TXT file.  All that needs to be done by the user is to enter the desired property value on the appropriate data line.  The user does not need to modify the comment that appears on a data line but rather should review the comment for information describing the property being defined and its allowable values.  This file is read when the extension is loaded.

 

AVwater New Features at Version 3.2d

 

1.         Modification to the {Modeling} [Update Model Geometry] command to reduce the processing time when there are a large number of records in the WaterValves table.  Previously, if the WaterValves table contained a large number of records the [Update Model Geometry] command could take a long time to finish its computations.  Additionally, if the user wishes to introduce valves, PRVs and/or Pumps into their respective speciality tables, WaterValves, WaterPRVs and WaterPumps, without having these features considered during the [Update Model Geometry] processing, the user should define the VLVPIP, PRVPIP and PMPPIP attributes, in the respective speciality table, to be zero.  The command will skip or disregard those features whose VLVPIP, PRVPIP or PMPPIP attribute value is zero.

 

2.         Modification to the {Modify} [Classification] command when using the Default Model or Default Node options to preserve the classifications for those NODTYP values other than the default AVwater values (1-6).  So that if the user assigns NODTYP values other than 1 through 6, this command will now preserve the classification that was assigned to these values prior to invoking this command.

 

3.         Modification to the Point 2 command |POINT DIR/DIST| to redisplay the input dialog box when an error has been detected.  Previously if an error was detected in the data that was supplied by the user, the command would display an error message and abort.  Now the command displays the same error message but once the user acknowledges the error message, the command redisplays the input dialog box displaying the values that were entered when the error was detected.

 

AVwater New Features at Version 3.2c

 

1.         Modification to the {Import} [Points] command to enable the user to create line features based upon vertex coordinates, as well as, a combination of node number connectivies and coordinates.  Two new options called Line Coordinate File - 1 and Line Coordinate File - 2 have been added to the File Type pull-down list that is presented by the command.  The Line Coordinate File - 1 option, enables the user to process a file that contains a unique line identifier with coordinates of the points that comprise the line appearing sequentially, one after the other, to create polylines.  For every line that is defined at least two data lines must appear with all vertices comprising the line carrying the same line identifier.  Once a new line identifier is encountered the previous line definition is interpreted as being completed.  The Line Coordinate File - 2 option enables the user to generate two point lines based upon the coordinates of the two nodes that comprise the line.  Under this mode of operation, the file contains a data line for every line to be defined.  On a data line, the start node number of the line appears along with its coordinates as well as the end node number of the line.  Two passes are made in processing the file, the first is to read and store all of the start node numbers and their coordinates, while the second is to create the lines using the coordinates contained on a data line, as well as, the coordinates saved during the first pass.  In addition to the lines that are created, the command will generate points for each start node number that is referenced in the file.

 

2.         Modification to the Modify tool (M) when modifying a pipe with a pump assigned to it to eliminate an Avenue uninitialized variable error message that would appear.  Previously, if an invalid pump code was assigned to the pipe, the Avenue error message would appear.  Now if the pipe has an invalid pump code assigned to it, the command will treat the pipe as having no pump attached to it.

 

3.         Modification to the Point 2 command |POINT DIR/DIST| when displaying the direction arrow.  Previously, the direction arrow would be pointing in the opposite direction of what it should be when a deflection angle was being specified.

 

AVwater New Features at Version 3.2b

 

1.         The field definition for the PIPINDX, SNINDX and ENINDX attributes have been changed from #FIELD_SHORT,5,0 to be #FIELD_LONG,12,0.  In so doing, larger numbers for these attributes can be handled.

 

2.         Addition of the {Modify} [Node/Pipe Numbers] command which enables the user to generate sequential node and pipe numbers.  When the command is activated, the program checks if there are any selected node and pipe features.  If not, then all node and pipe features are processed by the command.  If there are selected node and pipe features then only the selected features are processed.  Once this is determined, the command prompts the user for the starting node and pipe numbers as well as a distance tolerance.  The command uses the starting node and pipe numbers and assigns them to the first node and pipe it processes.  All subsequent node and pipe numbers generated will be incremented by one.  The distance tolerance is expressed in world units and is used to determine which node is close to an endpoint of a pipe.  For most applications, the default value should be sufficient.  This command will alter the values in the NODENO, PIPNUM, STRNOD, SNINDX, ENDNOD and ENINDX fields and should be executed prior to invoking the {Modeling} [Update Model Geometry] command.

 

AVwater New Features at Version 3.2a

 

1.         Modification to the {Modify} [Output Table] command.  This command will now process either all nodes or pipes that were modeled or only those nodes or pipes that are selected.  Depending upon the table that is selected either nodes or pipes will be processed.  Previously, the command would process all nodes or pipes because it did not consider if the user had used normal ArcView functionality to select specific nodes or pipes prior to activating the command.  Now the command will check if there are any selected nodes or pipes and if so sort the specified table for those selected nodes or pipes based upon node or pipe number and time.  If there are no selected nodes or pipes then the entire table will be sorted based upon node or pipe number and time.  In addition, once the command has finished sorting the table, it will leave the records in the table, that are associated with the nodes or pipes that were processed, selected.  Previously, these records were deselected by the command prior to termination.

 

2.         Modification to the {Modeling} [Execute] command when using the KYPIPE analysis program in conjunction with an EPS simulation.  The command will now create the .con, .jun, .pip and .nod tables just as is done when the EPANET modeler is employed.  These tables contain the results of an EPS run and can be used in conjunction with the {Modify} [Output Table] command to view the computational results for selected nodes or pipes at the various reported time steps.  The .pip and .nod tables will contain the results for all of the reported time steps, while the .con and .jun tables will contain the results only for the final reported time step.

 

3.         Modification to the Point 2 command |POINT DIR/DIST| to remove the requirement of picking two points to define the baseline direction when a point feature has been selected.  Previously, when a point feature was selected and confirmed, the user had to pick two points to define the direction of the baseline.  When an explicit direction was being specified these points were not necessary.  Now, when a point feature is selected a new parameter, in the multi-input message box that is displayed by the command, will appear.  This parameter carrys the label Pick two point baseline (Y = yes, N = no).  If the user wishes to define the baseline direction when a point feature is selected, following the confirmation of the feature and the display of the multi-input message box, the user should enter y in the field to the right of the Pick two point baseline label.  Once entered, the user can pick the two points that define the direction of the baseline.  If the user does not wish to define the baseline direction when a point feature is selected, the user can simply enter the appropriate information in the multi-input message box that is displayed.  The default baseline direction when a point feature is selected is along the x axis or a Cartesian angle of zero degrees.  When a line feature is selected, the default baseline direction is identical to that of the line's direction.

 

4.         Modification to the Point 2 command |POINT DIR/DIST| to display a blue arrow denoting the direction of the baseline.  In so doing it is easier for the user to identify which side is to the right or left of the baseline.  Note that when central angles are being specified, the user should reverse the direction of the blue arrow.  That is, when central angles are being entered, the command adds 180 degrees to the direction of the baseline and then adds the specified central angle to the reversed baseline direction.

 

5.         Modification to the Point 3 command |PLUS/OF| to display a blue arrow denoting the direction of the baseline.  In so doing it is easier for the user to identify which side is to the right or left of the baseline.

 

6.         Modification to the Point 3 command |PLUS/OF| to handle curves whose central angle is greater than 180 degrees.  Previously, when a curve with a central angle greater than 180 degrees was being processed, the command would not properly compute the coordinates of the new point(s).

 

7.         Modification to the {Import} [Points] command to enable the user to create line features based upon node connectivities.  A new option called Line Connectivity File has been added to the File Type pull-down list that is presented by the command.  This option, when selected, assumes that the root name of the file that is selected matches the name of a visible point theme in the view.  Within the Line Connectivity File will be a single record, for every line to be created, containing as a minimum a start node and an end node number.  These node numbers correspond to a node number that appears in the corresponding point theme.  As the records are processed, the command extracts the coordinates of the start and end nodes from the correspond point theme and creates line features.  The user has the option of including or excluding the other attributes in the Line Connectivity File with the line features that are created.  Furthermore, the user is able to specify the field in the corresponding point theme that contains the node numbers, as well as, the fields in the file being processed that contain the start and end node values.  Since the user is able to specify the fields that contain the respective node numbers, the node numbers do not need to be purely numeric.  That is, the node number fields may be either numeric or alphanumeric.  However, processing numeric node number fields will be faster than alphanumerics fields.

 

8.         Modification to the {Modify} [Output Table] command to prompt the user for the name of a new table that will contain the results of the sorting operation.  Previously, this command would simply leave the records which were sorted in a selected state.  Now the command prompts the user for the name of a new file that will contain the records which were sorted.  If the user selects the Cancel button, the command terminates leaving the sorted records selected and without creating a new table.  If the user enters a valid filename, the command creates a new table and adds it to the project file using the root name of the filename as the name of the table.  Note that the user is prompted for a new table name only if the number of records which were sorted is less than the total number of records in the table.

 

AVwater New Features at Version 3.1x

 

1.         Modification to the {Modeling} [Controls] command.  A new field has been added into the EPANETcontrols table called LEVEL2.  This field is used only when the KYPIPE analysis program has been selected as the desired modeler and only when an EPS simulation is being performed.  Specifically, the value that appears in this field will appear in the KYPIPE input file under the Pressure Switch Data section.  Normal ArcView functionality must be used to populate the values under this field.

 

2.         Modification to the {Modeling} [Execute] command when using the KYPIPE analysis program.  It is now possible to control the open-closed status of a pipe during an EPS simulation based upon the grade at a specified node.  To do so, the {Modeling} [Controls] command should be used to specify the pipe to be controlled and the associated node whose grade value will dictate if the pipe is to be opened or closed.  All controls which are based upon the IF NODE link setting and ABOVE node setting will be processed as Pressure Switch Data and will be taken into account during the simulation.  All other controls will be ignored.  Within the EPANETcontrols table, which is created by the [Controls] command, two fields called LEVEL and LEVEL2 will appear.  The LEVEL field contains the first switching value, while the LEVEL2 field contains the second switching value.  The default is to set the second switching value to be the same as the first, if this is not the case, normal ArcView functionality should be used to set the second switching value by editing the EPANETcontrols table directly.

 

3.         Modification to the {Modeling} [Update Model Geometry] command to perform additional error checking on the tank special node table.  Previously, when the special node tables were being checked, the command did not verify that the pipe, stored in the tank special node table, was a valid value.  As such it was possible to have a reference to an invalid pipe in the tank special node table.

 

4.         Modification to the Modify tool (M) to allow the user to close a pipe when a pipe is associated with a pump node.  Previously, only pipes which were associated with valves could have their valve status changed to be closed pipe.  Now pipes which have either a pump or a valve associated with them can have their valve status changed to closed pipe.  When a pipe is closed, the OPNCLO attribute for the pipe is set to be equal to 2.  When a pipe is open and contains no valve, the OPNCLO attribute is equal to 0.  Note that normal ArcView editing functionality can be used to set the desired value for the OPNCLO attribute.

 

AVwater New Features at Version 3.1w

 

1.         Modification to the Transformation tool.  Seven new options have been added to the pull-down list that is presented by the command.  Six of the seven pertain to defining the individual points that establish the old and new baselines.  The seventh enables the user to employ a Stretch transformation.  The seven new options include Pick Baseline Point 1, Pick Basline Point 2, Pick Baseline Point 3, Pick New Baseline Point 1, Pick New Baseline Point 2, Pick New Baseline Point 3 and Stretch Features.  In order to use the Stretch Features option all six baseline points must be specified.  The six baseline points are comprised of three points defining the original or old baseline and three points which correspond to the three original or old baseline points but in a new coordinate system.  The command scales, rotates and translates the original or old baseline points to match the new baseline points.  A baseline, when using the Stretch Feature option, is defined by Points 1 and 2, which establish a direction, and Point 3 which is a point offset from an imaginary line connecting Points 1 and 2.  The Stretch Features option is different than the Transform Features option in that it will distort the features it processes.  The distortion occurs because the command forces the third point in the original or old baseline to match the third point in the new baseline.  The Transform Features option, on the other hand, simply uses the third point, if specified, to compute a Y scale factor.  If not specified, the Y scale factor is assumed to be the same as the X scale factor.

 

2.         Modification to the Point 2 command |POINT DIR/DIST| to provide the user the ability to specify a zero distance value without the command aborting.  When the direction mode r is employed, the user is able to enter a zero distance value without aborting the command.  Previously, the command would aborted when a zero distance was specified.  Now when a zero distance is entered, under the direction mode r, the command accounts for the relative angle without creating a point and redisplays the multi-input dialog box for further input.  Note that under the e and a direction modes a zero distance value will result in the command aborting.

 

3.         Modification to the {Modeling} [Update Model Geometry] command to perform additional error checking on the pump, valve and PRV valve special node tables.  Previously, when the special node tables were being checked, the command did not verify that the pipe, stored in the special node table, was actually associated with a pump or valve node (PRV or not).  It simply checked to see if a valid pipe number was specified.  As such it was possible to have a reference to a pipe that did not have a pump or valve (PRV or not) associated with it.

 

4.         Modification to the {Modeling} [Update Model Geometry] command to perform additional error checking on the special node tables.  The command will now delete those records in the special node tables which refer to node numbers that have not been defined.

 

5.         Modification to the {Modeling} [EPANET Controls] command to allow the user to specify a time value of zero (0.0).  Previously, when the AT TIME control was selected and a zero value was entered, the command would issue an invalid time value message.

 

6.         Modification to the {Modeling} [Execute] command to make the EPANET modeler the default value.

 

7.         Modification to eliminate a variable/class name conflict.  Previously certain extensions, when loaded with the CEDRA-AVwater extension, caused a variable/class name conflict for the variable/class, path.

 

AVwater New Features at Version 3.1v

 

1.         Modification to the {CEDRA Utilities} [Update Classifications] command to provide the user the ability to assign a specific color and symbol to a specific theme.  A new option, Match color and symbology from File, has been added to the pull-down list that is presented by the command.  This option reads the ASCII file, symblayr.txt, which is located in the CEDRA distribution directory, for PC based users, \cedra\avprjs.  This is a normal text file and can be modified by the user as desired.  Within the file are instructions as to how the file should be structured.  Essentially, the user specifies on a data line the name of a theme, a keycode and a keycode value.  These three parameters are separated by at least one space or blank character.  The name of the theme must appear as it does in the View's Table of Contents with the exception for CEDRA layers.  For CEDRA layers only the root name of the theme needs to be specified.  That is, those themes which end with the cn.shp, cv.shp, ln.shp, pg.shp, pl.shp, pn.shp and tx.shp characters do not need to have the exact theme name spelling in the symblayr.txt file.  For example, the theme L_0pn.shp would be defined in the symblayr.txt file as L_0, not L_0pn.shp.  The pn.shp characters are omitted.  The valid keycodes are COLOR, FILL, PEN and MARKER.  The keycode COLOR enables the user to assign a color to a theme.  The keycodes FILL, PEN and MARKER allow the user to assign a specific fill pattern, linestyle or point marker, respectively, to a theme.  The valid keycode values for the COLOR keycode are BLACK, BLUE, CYAN, GRAY, GREEN, MAGENTA, RED, WHITE and YELLOW.  The valid keycode values for the FILL, PEN and MARKER are those numbers greater than or equal to zero.  These numbers correspond to the index value for the symbols displayed in the Symbol Palette window.  These numbers begin at 0 and increment sequentially by one on a row by row basis.  That is, when the Symbol Palette is displayed usually three patterns, line styles or markers appear on a row, depending upon the type of palette that is displayed.  For the first row the index values would be 0, 1 and 2 proceeding left to right in the row.  Likewise, for the second row, the index values would be 3, 4 and 5 also proceeding left to right.  This process is applied to all of the remaining rows in the palette.  Once the symblayr.txt file is read, the command searches the Table of Contents for the specified theme.  If a match is made, a single symbol legend type is applied to the theme and the appropriate color and/or symbol assignments made.

 

2.         Modification to the CEDRA-AVwater-EPANET-Import extension to query the user as to if the node and pipe numbers should be biased.  This query is posed when the command determines that the lowest node number that is used is greater than or equal to 1000.  When the node and pipe numbers are biased, the command subtracts from the node and pipe numbers, a value equal to one less than the lowest node and pipe number assigned.  For example, if the lowest node number assigned is 1001 and the lowest pipe number is 3001, the command will subtract 1000 from the node numbers and 3000 from the pipe numbers to determine the new node and pipe numbers.  The original node and pipe numbers are maintained and stored in the fields, NODENO_OLD and PIPNUM_OLD, respectively.  The reason for wanting to bias the node and pipe numbers is solely for performance.  The lower and more sequential the node and pipe numbers the better the performance in terms of speed when performing an analysis.

 

3.         The field definition for storing node coordinates has been changed from #FIELD_DECIMAL,14,4 to be #FIELD_DECIMAL,18,6.

 

4.         The field definition for storing node and pipe numbers has been changed from #FIELD_SHORT_5 to be #FIELD_LONG_12.

 

5.         Addition of a new extension, CEDRA-ChangeFeatures, which is included with the distribution software.  This extension is comprised of one button and one tool that enables the user to change the shape of a single feature or a group of features using the shape of another feature.  The button is represented by the Link icon and its balloon help appears as Change Selected Features, while the tool is represented by the StyleRamp icon and its balloon help is Change Feature's Shape.  The function of these commands is to change the shape of selected features by substituting the shape of other features.  The Change Feature's Shape tool operates on a single feature, while the Change Selected Features button will process the current selected features, which may be comprised of one or more features.  The Change Feature's Shape tool will prompt the user to select the feature to be changed, followed by prompting the user to select the feature whose shape is to replace the feature initially selected.  The initial feature's shape is then changed to be identical to that of the second feature selected.  The second feature is left unaltered.  The Change Selected Features button will change the shape of the current selected features by using the shapes of features in a specific theme which have an identical attribute with the current selected features.  The user is asked to identify the theme containing the new shapes as well as the field or attribute that is to be used to make a match between the features.

 

6.         Modification to the {Import} [Points] command to provide the user the ability to create point features at the endpoints of lines.  If the user has selected a file containing the .shp extension, when prompted for the name of the file to be processed, the command assumes that the user wishes to create point features at the endpoints of the line features stored in the Shapefile.  Under this mode of operation, the Shapefile must have been loaded, in the current view, prior to invoking the [Import Points] command.  Using the name of the shapefile, selected by the user, the command will scan the view's Table of Contents for a visible theme of the same name.  If no theme is found, a warning message is displayed and the command terminates.  The name that appears in the top line of the warning message is the root name of the shapefile that was selected by the user.  A theme with this same name must be present in the current view for the command to operate under this mode.  It is the theme in the view that is processed and not the file that resides on disk.  If a theme is found, the command will begin to generate point elements at the endpoints of the selected line features in the theme.  If no lines have been selected then all line features in the theme will be processed.  The point features that are created will be stored in the current active layer and will be assigned typical AVseries point attributes.  In creating the point features, the command will not generate duplicate points at common endpoint locations.  In eliminating duplicate points, the command employs one of two methods.  The first method is to examine the selected line theme for the FNODE_ and TNODE_ attributes.  These are typical Arc/Info attributes that represent a from node number and a to node number.  If these attributes exist, the command will create a point feature for every unique node number.  In addition, the command will create an attribute called NODENO that will contain the FNODE_ or TNODE_ node number.  The second method is employed when the FNODE_ and TNODE_ attributes do not exist in the selected line theme.  Under this method, the command checks for common coordinates.  Note that this method is considerably slower than the first because every endpoint is compared with every other endpoint.  In examining the theme in which the created point features are stored, the user will notice the PNT and NODENO attributes.  The PNT attribute represents the sequential point number assigned to the point and will begin at one (1) if the theme contains no other point features or will begin at one higher than the highest PNT value present in the point theme.  The NODENO attribute will either be identical to the PNT attribute if the selected line theme does not contain the FNODE_ and TNODE_ attributes or will represent the FNODE_ or TNODE_ node number, if the selected line theme does contain these attributes.

 

7.         Modification to the {Text Properties} [Change Text Properties] command.  The default value for the Maximum Chord Deflection in Degrees option has been changed from 18 to 24.

 

AVwater New Features at Version 3.1u

 

1.         Modification to the {Modeling} [Load Generation] command.  A new option has been added called (Poly Area) x (Poly B) x (Poly C) / Nodes in Poly.  This option uses the area of a land polygon as Attribute A and expects each polygon to carry its own B and C attributes.  Thus, if the area of a land polygon is A, the polygon's demand is (A) x (polygon B) x (polygon C).  Once the polygon's demand has been computed, the command divides the value by the total number of fittings (NODTYP = 3) that are attached to pipes (INPIPE = 1), within the land polygon.  The result of this division is then applied to each of these fittings thereby providing for an equal distribution of the total polygon demand.  In this method, it is not necessary for the land polygons to be assigned to a node.

 

2.         Modification to the {Preferences} [View Parameters] command to enable the user to specify the snap tolerance either as a percentage or as an absolute value.  Previously, the user was able to only specify the tolerance as a percentage of the view display window width.  If the user wishes to specify the tolerance as an absolute value, the keycode a should be appended to the desired value.  For example, if the snap tolerance is to be defined as 10 feet, the user should enter 10 a, that is, the number ten followed by at least one space and then the a character.  If the keycode a is omitted, the command assumes that a percentage snap tolerance is desired.  If a percentage snap tolerance is to be entered, the user does not have to divide the value by 100 prior to entering the value.  Previously if a 2 percent snap tolerance was desired, the user would have entered 0.02.  Now the user should enter 2, if a 2 percent snap tolerance is desired.  Note that the snap tolerance does not have to be a whole number, a value of 2.45 would be acceptable.  In addition, when the command is activated, the command will append the text percent or absolute to the current snap tolerance value.  This is done to allow the user to determine the type of snap tolerance in effect.

 

AVwater New Features at Version 3.1t

 

1.         Modification to the {Modeling} [Execute] command when using the EPANET modeler.  During the reading of the results of an analysis, the command will now perform a validity check on the number of pipes that were actually modeled.  Previously, if there was an error in the model that resulted in the EPANET modeler modeling a fewer number of pipes that were supposed to be modeled, an assertion error would be generated.  This no longer occurs.

 

2.         Modification to the Modify tool (M) when a valve type of node is selected.  The PRV type choice message box has been eliminated.  The list of available PRV types has been added to the valve type choice message box which is displayed when the user indicates that the valve type is to be changed.  In addition, if the valve that is selected is a PRV type of node, the label CHANGE VALVE TYPE, which appears in the node modification multi-input message box, has been changed to CHANGE VALVE TYPE OR A PRV VALUE.  In so doing the modification of PRV types of nodes has been made faster and easier.  Note that in order to change a PRV grade or a PRV pressure setting, the user must respond Y or y to the CHANGE VALVE TYPE OR A PRV VALUE parameter.

 

AVwater New Features at Version 3.1s

 

1.         Modification to the {CEDRA Utilities} [Generate Text from Table] command to handle CAD drawing attribute tables for text elements.  Previously, only AVseries text attribute tables could be processed.  Now it is possible to generate AVseries text features from the text elements in a CAD drawing.  A CAD drawing attribute table for a text element is denoted by having the SHAPE, ENTITY and TEXT fields.  Using this new functionality provides the user the ability to edit text that is imported from a CAD drawing.

 

2.         Modification to the {Import} [Points] command.  The scripts which comprise this command have been extracted to form the CEDRA-ImportPoints extension.  In order for the user to use the {Import} [Points] command the CEDRA-ImportPoints extension needs to be loaded, if not, an appropriate error message will be displayed.

 

3.         Modification to the {Import} [Points] command to provide the user the ability to create point features using the text elements in a CAD drawing.  The text elements that are processed are those which represent numbers.  Text elements that do not represent a single numeric value are ignored.  The user has the option of creating point features at the start of the text element, the end of the text element, at the mid-point of the text element or at the location of the decimal point within the text element.  The number which the text element represents will be assigned to the Z attribute for the point feature.  Note that the Annotation or Text theme of a CAD drawing, when using this command, should appear above any of the other themes that are associated with the CAD drawing in the view's Table of Contents.

 

4.         Modification to the {Modeling} [Update Model Geometry] when importing Cybernet shapefiles.  Tank type nodes will now be recognized and classified as such in the wtrnodes.shp theme.  Previously, tank type nodes were classified as fittings.  Now they will appear as Tank nodes in the wtrnodes.shp theme.

 

5.         Modification to the {Import} [Points] command to enable the user to create point features at the endpoints of line endpoints.  No duplicate points will be created at common line endpoints.  Consult the [AVwater User's Manual] for more information.

 

AVwater New Features at Version 3.1r

 

1.         Addition of the Change Node tool (C) which provides the user the ability to change the node type of a node.  Previously, there was no AVwater command which provided the means to change, for example, a Fixed Grade Node to a Fitting, or a Fitting to a Hydrant, and so forth.  The user had to create a new node of the desired type and then delete the existing node.  Now, the user is able to use the C tool to directly change a node type.  The C tool will appear under the Modify Tool, M, as the last tool in the tool list.  The user can select this tool, followed by selecting and confirming the desired node to be modified.  Once confirmed, the command displays the current node type of the node, as well as its node number in the status bar, and prompts the user to select the new node type.  If the user selects the same node type as the node is currently assigned, the command will issue a beep and terminate.  If the user selects a new node type, the command will change the node to the new node type and update the display of the view.  Note that the {CEDRA Utilities} [Oops] command can be used, if need be.

 

2.         Modification to the {Annotate} [Contours] command to allow the user to generate contours for the water quality attribute, WQANAL.  This command has been changed by adding three items, Water Quality, Water Age and Source Flow Tracing, to the initial pull-down list that is presented.  All three items will result in contours being generated using the WQANAL attribute.  The WQANAL attribute contains the results for a water quality analysis at the last time step of the simulation.  If the user wishes to plot the results of a water quality analysis over time, the {Annotate} [EPS Graphs] command should be used.

 

3.         Modification to the Define Strip tool (S) to prompt and store a strip number for the pipes that the user has selected.  Previously, this was not done so that there was no way to recall a previously defined strip.  Now the user is asked to enter a strip number (between 1 and 99999, inclusive) when the Point & Auto-Search method is used or, if the Picking Pipes option is selected, when the user selects the last pipe in the strip twice.  A field or attribute called STRIP will be added to the pipe theme, if one does not exist, that will contain the user-specified strip number.  Furthermore, a new option, Enter Strip Number, has been added to the initial pull-down list that is displayed which enables the user to recall a previously defined strip simply by specifying the desired strip number.

 

AVwater New Features at Version 3.1q

 

1.         Modification to the Define Pipes tool (P) to repeat the multi-input dialog box if an error is detected.  Previously, when an error was encountered, the command would inform the user and terminate the command.  Now the command will inform the user and redisplay the multi-input dialog box.

 

2.         Modification to the {Modeling} [Execute] command when using the EPANET modeler.  The command will now create an EPANET map file (*.map) in addition to the EPANET input file (*.inp).  Previously, only the input file was created.  Within the map file will appear the node number and coordinates (x and y) for all of the nodes in the service area being modeled.

 

3.         Modification to the Define Pipes tool (P) to store in the WaterPRVs table the STRNOD attribute.  This attribute contains the record number of the start node of the pipe and is a required attribute for performing an analysis.  In addition, this command will also populate the DWNNOD attribute of the WaterPumps table.  This attribute contains the end node number of the pipe that the pump is associated with.  Previously, these values were not populated and the user had to use the {Modeling} [Update Model Geometry] command to populate these fields.

 

AVwater New Features at Version 3.1p

 

1.         Modification to the {CEDRA Utilities} [Copy Selected Features] command to provide the user the ability to specify whether attributes, that are associated with the selected feature(s) to be copied and which are missing from the resultant theme, are to be copied in addition to the shape of the selected feature(s).  Previously, the command would always copy any missing attributes which would result in the list of attributes, associated with the resultant theme, being expanded.  The user now has a choice which is presented in the form of a query (Yes-No-Cancel message box).  Responding Yes results in the command copying any missing attributes along with the shape of the feature into the resultant theme.  A response of No results in the command copying only the shape of the feature ignoring any attributes that may not be present in the resultant theme, while a response of Cancel will abort the command.

 

2.         Modification to the Load tool (L) to reverse the order for entering inflow and outflow loads.  Previously, the Inflow load would appear at the top of the multi-input dialog box.  Now the Outflow load appears at the top, the Inflow in the middle and the Fire flow load at the bottom.

 

3.         Modification to the {CEDRA Utilities} [Update Geometry] command to store the line length value in the fields LENGTH and PLONG, if present, for line type themes.  Previously, only the LEN field would be updated with the line length value.  Now, the LEN, LENGTH and PLONG fields will be updated if they are present.  Note that any previous value in these fields will be overwritten.

 

AVwater New Features at Version 3.1o

 

1.         Modification to the {Import} [Points] command to accept the space, comma or tab characters as separating characters between the items on a data line.  Previously, only the space and comma characters were valid delineating characters, at this version, the tab character has been added.

 

2.         Modification to the Load tool (L) to remove from the FireFlowData table (if one exists) the record or records where the Node_1 value matches the node number of the node being loaded.  This will occur only when the fire flow load, as specified by the user, is equal to zero (0.0).  If a non-zero fire flow load is specified, this tool will not add a record to the table.  Records are only added to the FireFlowData table when the user invokes the {Modeling} [Execute] command and if:

 

            a.         There are nodes with fire flow loads and the FireFlowData table does not exist, or if

            b.         The FireFlowData table exists and the user specifies that the table is to be modified.

 

            Consult the [AVwater User's Manual] for more information.

 

AVwater New Features at Version 3.1n

 

1.         Modification to the {Modeling} [Execute] and [Re-Execute] commands when performing an analysis with fire flow loads.  Previously, the program would simply compute the load for a node as DEMAND = OUTFLO + FIRFLO - INFLOW and include all nodes with fire flow loads in the analysis.  This process has been totally redesigned enabling the user to conduct multiple fire flow analyses (load cases) and create summary tables that contain the node and pipe computational results for each of the load cases modeled.  Consult the [AVwater User's Manual] for more information.

 

AVwater New Features at Version 3.1m

 

1.         The AVwater extension will now take into account the View Properties settings for Map Units and Distance Units when the view is not assigned a projection.  Previously, when the View was not assigned a projection, the extension would assume that the Distance Units setting was the same as the Map Units setting. This modification allows the user the ability to work in an environment where the Map Units is set to meters and the Distance Units as feet.  In so doing, the user is able to enter distances in terms of feet rather than meters since the Distance Units property controls the units in which distances are specified.

 

2.         Modification to the {Query} [Node] and {Query} [Pipe] commands, when searching for a single feature, to allow the user the ability to enter a single node or pipe number under the low number parameter.  Previously, if a single node or pipe feature was to be found, the user had to enter the same number under both the low and high number parameters.  Now, if a single feature is to be found, the user is able to simply enter the desired number under only the low number parameter, without having to specify any value for the high number parameter.  Consult the [AVwater User's Manual] for more information.

 

AVwater New Features at Version 3.1l

 

1.         Modification to the Point 2 command |POINT DIR/DIST| to provide the user the ability to turn an angle off a baseline in addition to being able to explicitly enter a direction.  Previously, the user was only able to explicitly enter a direction.  Now the user has the option of specifying an angle that is turned off a baseline direction.  A new parameter, direction mode, appears in the multi-input message box.  Consult the [AVwater User's Manual] for more information.

 

2.         Modification to the [Import Points] command to enable the user to build polygons from an ASCII based file.  The polygons that are created can contain sides that are linear (straight) or curved.  Additional file types have been added to the file type pull-down list  Consult the [AVwater User's Manual] for more information.

 

3.         Ability to work with views that contain raster images.

 

4.         Ability to work as an extension with Version 3.1 of ArcView.

 

5.         Ability to work with views that have been assigned a projection.

 

6.         Modification to the {Annotate} [Contours] command to enable the user to generate contours for the node attributes pertaining to Supply, Demand, Gound Elevation, Grade Line and Pressure.  Consult the [AVwater User's Manual] for more information.

 

7.         Modification to the {Modeling} [Update Model Geometry] command to recognize Cybernet generated shapefiles when developing an AVwater model.  In so doing, the conversion of a Cybernet model into an AVwater model has been automated and eliminates the normal user-interaction required by the [Update Model Geometry] command.  Consult the [AVwater User's Manual] for more information.

 

8.         Modification to the {Modeling} [Execute] command to process the current active service area.  Previously, all nodes and pipes in the model would be analyzed regardless of the service area they were assigned.  Now, only the nodes and pipes within the current active service area will be analyzed.  Consult the [AVwater User's Manual] for more information.

 

9.         Modification to the {Modify} [Classification] command to allow the user to classify pipes based upon their valve and pump status.  Two new items called Valve Status and Pump Status have been added to the classification pull-down list.  Consult the [AVwater User's Manual] for more information.

 

10.       Modification to the {Modeling} [Load Generation] command to allow the user to uniformly distribute the load, computed in a contributing nodal load polygon, amongst the nodes within the polygon.  A new option has been added to the Load Generation pull-down list called (Bldg A) x (Bldg B) x (Bldg C) / Nodes in Poly.  Consult the [AVwater User's Manual] for more information.

 

11.       Modification to the {Modeling} [Execute] command to speed up the post-processing of the results that are computed when using the EPANET modeler.

 

12.       Modification to the {Modeling} [Re-Execute] command to speed up the post-processing of the results that are computed when using the EPANET modeler.

 

13.       Addition of the CEDRA-AVwater-EPANET-Import extension to facilitate the conversion of an EPANET model into an AVwater model.  This extension requires an EPANET map file (.map) as well as an EPANET input file (.inp).  This extension does not modify the View GUI but rather is utilized by the [Import Points] command.  The [Import Points] command should be used to import the EPANET map file (.map).  If the CEDRA-AVwater-EPANET-Import extension is loaded, [Import Points] will use the extension to develop an AVwater model.  Consult the [AVwater User's Manual] for more information.