|
|
Our team finds map labels quite useful, especially as they are migrating from InfoWater where the use of map labels is quite common. Although the label functionality in InfoWorks WS Pro is quite good, working with them can be slightly unintuitive and I think this is why we don't see them used that often.
My suggestions to improve the general workflow:
Support for Importing / Exporting to JSON, ideally somewhat documented, and with Ruby API support
Allow updating an existing label list object from the current network - there is a precedent for this with selection lists. Currently we have to delete and recreate the list each time we want to update it
If unsaved changes have been made to the labels, warn the user when they try to close the map. Because labels are only temporary, many users set up labels and forget to save them, and lose their work when closing the map
Allow label lists to be associated with a network, so that they automatically open with it
More significantly - perhaps labels could be part of the network structure so that their management is more closely linked to the network itself, and could be tied to scenarios, etc?
