Duplicate Labels in Haestad

There is a query under Network Navigator to find Duplicate labels.

View > Network Navigator > Input > Duplicate Labels

If you are worried about duplication, you can also rely on ID's instead of labels as a way to find things. There are no duplicate ID's.

Thanks, Tom. I am aware of the query and other tools to find the duplicates. I'd like a way to make sure that there are no duplicates in the first place. For example, after I place a new pipe, I need to make sure that the new pipe does not have a duplicate label. I wish the software would ensure that the duplicate label was not assigned in the first place.

I use ID's for some elements, but for others I need a way to customize the ID. As far as I know, there is no way to do that.?

Please consider adding the option of refusing duplicate labels. This is a common issue that I have had in WaterCAD, StormCAD, SewerCAD and today in CivilStorm.

I'm not sure what your suggestion has to do with duplicate labels.? Even if I go to Tools > Options > Labeling every time I place a new element, the new label could still be a duplicate. Also, labels are always automatically generated, correct?

Here's some screenshots showing why your suggestion does not help this issue:

-------

What you need to do is be creative in your prefix and suffix selection. In your example, set the prefix to Junc and suffix to added and next to 1003 and the next elements will be Junc-1003Added and Junc-10004Added.

You don't need to do all three things but you see how can ensure that you don't have duplicates.

I still don't see how your suggestion addresses the problem of duplicate labels. Your suggestion does not ensure that I don't have duplicates.

Also, when I create a report, I want to see J-1, J-2, J-3, etc.

I do not want to see J-1, Jun-1002Added, Junc-10003JustAdded, Juncti-4000AddedAnother, etc.

There are two ways that labels exist: they are already in the model or you add them.

If they are in the model, then that Network navigator query shows you where they are and you can fix them

If you are adding them, then set the label options so that you get unique labels. I was being a bit silly when I made up that example, but you can give your new elements some distinguishing feature so that they don't duplicate existing ones. You can run that query occasionally to check if you messed up and duplicated anything.

Please see previous response

Unknown said:

I am aware of the query and other tools to find the duplicates. I'd like a way to make sure that there are no duplicates in the first place.

Please see previous response

Unknown said:

I am aware of the query and other tools to find the duplicates. I'd like a way to make sure that there are no duplicates in the first place.

What version of the software are you using currently ?

SewerCAD 8.11.3.77
WaterCAD 8.11.4.57
StormCAD 8.11.3.77
CivilStorm 8.11.5.58

I run into this issue in almost every model that I create. Many of our models are constantly evolving. So, even though a model may be created from Modelbuilder, it is typically modified may times in the software though scenario analysis, pipe splitting, proposed alternatives, etc.

Some thoughts:

1) If a model already has duplicates, send a pop-up or warning message.
2) For those users who would not want to be restricted to unique labels, allow the option of duplicate labels. Maybe there could be a setting in Tools-Options
3) When data is imported from another source (such as through modelbuilder) and duplicate labels are possible, ask user if new labels should be renamed.

Some options for implementation:
1) Perhaps a pop-up when laying out, with an option to use the duplicate label anyways, and a “do not show again” check box?
2) If setting is enabled, never allow duplicates. Show message when potential duplicate label is about to be added, then increment label until duplicate is not created.

We appreciate your coming up with positive suggestions for improving our software. We value this type of input.

We now have a request for a new enhancement based on your suggestions.

Thanks
Tom