Frequently Asked Questions

How do I create utility network layers?

To create intelligent utility network layers, Cadcorp topological overlays can be used, as described in the Map Compiler topic's Topological Overlays section, and here are the steps to create its example using the Cadcorp SIS Desktop application:

1. CREATE CADCORP SYMBOLS AND SISfm ICONS

Two map icons are required, to represent pits and lamps. These are Cadcorp symbols named mapicons.name-ext and corresponding SISfm icon files named name.ext under the DataFolderMapIcon folder. This folder may already contain Node.gif and Lamp.png, and here we create corresponding symbols in SIS Desktop. To save time we will use copies of suitable existing symbols rather than creating new ones.

  1. In the SIS Desktop Libraries control bar, use Open Library from the Libraries's local menu to open your NOL (Named Object Library) file.
  2. Expand the (standard) library node, then Symbol, then use Copy from the Circle symbol's local menu.
  3. Use Paste from your NOL file node's local menu to add the Circle symbol to it, then rename it as Node-gif.
  4. Use New Folder from your NOL file Symbol node's local menu to create a folder named mapicons if necessary, then copy and paste Node-gif to this folder, then delete the original.
  5. Repeat the previous three steps for the symbol named "Off Set Circles.A - 3 categories.Circle 1", renaming it as Lamp-png. (Expand the Off Set Circles folder, then the A - 3 categories folder, then copy Circle 1.)

2. CREATE NETWORK INFRASTRUCTURE

Here we create the infrastructure, as pits and trenches, that will house the light network.

  1. In the SIS Desktop Maps control bar, use Open File from the SIS Workspace Definitions' local menu to open your site SWD file.
  2. Use Home / Map / Add Overlay / Files / New File and specify a BDS (Cadcorp Base Dataset) file named Site-Service.bds in the same folder as Site.swd.
  3. In the Maps control bar, use the new overlay's local menu to rename it from Site-Service.bds to Service.Pit, and to make it current (it's name in bold face).
  4. Use Topology / Build / Link to create several connected Link items forming a network. Note that SISfm only permits Link items with two vertices.
  5. Use Select Items from the overlay's local menu, then use the map's local menu to see that both Link and Node items have been created.
  6. Use Properties from the overlay's local menu, in the Overlays dialog select Styles, select symbol mapicons.Node-gif, enter a Point scale override of 100 and select Apply to see the effect; change the Point scale override if necessary; then select OK to close the dialog.
  7. Use Copy from the overlay's local menu, then Paste Overlay from the SWD's local menu, to create a copy of the overlay, and rename this as Service.Trench.
  8. Use Properties from the Service.Pit overlay's local menu, then in the Overlays dialog select Dataset; in this dialog select the Service.Trench overlay to see the same dataset details, including the Locked checkbox which signifies that the BDS file can only be updated by this SIS Desktop application.
  9. In the Maps control bar:
  10. Use Properties from the Service.Pit overlay's local menu, then in the Overlays dialog select Schema, then use delete and add to obtain the following columns:

    Item ID (_id&)
    Item class (_classLocal$)
    Origin X (_ox#)
    Origin Y (_oy#)
    Links (_links$)
    Symbol (_shape$)
    Pit_ID (Pit_ID$) - an attribute

    (Note that a schema can be copied and pasted between overlays using Copy Overlay settings and Paste schema buttons in this dialog, which may assist here).

  11. Use Open in Table Window from the Schema node of the Service.Pit overlay, then use New Horizontal Tab Group from the local menu of the table window tab, to see both the map and table windows.
  12. Enter Pit ID values in the table window, e.g. P1, P2, P3,...
  13. Use Add Theme from the Theme node of the Service.Pit overlay, select Annotation, then Labels; select Pit_ID then Next, then Finish to label the pit items.
  14. Repeat the last four steps for the Service.Trench overlay and the following schema columns:

    Item ID (_id&)
    Item class (_classLocal$)
    Number of vertices (_np&)
    Start Node (_id1&)
    End Node (_id2&)
    Trench_ID (Trench_ID$)

    entering values for the latter, e.g. T1, T2, T3,... and specifying Trench_ID for its label theme with Label placement Middle and Rotate labels True.

  15. Use Save from the SWD's local menu, and select Save all, without prompting, which will save both Site.swd and Site-Service.bds.
  16. Use the Administrator module's Configuration page (config.aspx) to set a MapLayerTopo setting to Service, then Save.
  17. Use Map Compiler to compile the site plan. This will log: 
    ERROR: Topology "Service" table "service_pit" does not exist
ERROR: Topology "Service" table "service_trench" does not exist
ERROR: Topology "Service" tables invalid - valid SQL for schema and DDL is:
    followed by a list of SQL statements; copy these to the clipboard.
  18. Use the Database Manager's SQL.aspx page with your database connection string, and paste the clipboard as the SQL to execute. Select Execute and observe that all statements have executed without errors.
  19. Use Map Compiler to compile the site plan again. If this logs other Topology "Service" errors, return to SIS Desktop and correct them.
  20. Use Map Enquiry to view the two new layers.
  21. Use the Administrator / Configuration page to add the following MapTheme settings: 
    label,  service_pit.pit_id,               Service Pit ID
tip,    service_pit.pit_id,                       Pit ID
label,  service_trench.trench_id,         Service Trench ID
tip,    service_trench.trench_id,                 Trench ID
  22. Refresh the site plan in Map Enquiry, and confirm that these settings have defined pit and trench item dialogs and labels.

3. CREATE LIGHT NETWORK

Next we add the light network, as lamps and circuits, to this network infrastructure.

  1. Copy and paste overlay Service.Pit as two more overlays named Service.Light.Lamp and Service.Light.Circuit, and change their filters to restrict the item class to TopoPoint and TopoLinestring respectively.
  2. Use the Overlays dialog to set the Pen to Red for overlay Service.Light.Circuit and the Symbol to mapicons.Lamp-png for overlay Service.Light.Lamp.
  3. Make overlay Service.Light.Circuit current, then use Topology / Build / TopoLineString to create several TopoLineString items (each by selecting their start and end Link items and then pressing Enter to trace between them).
  4. Make overlay Service.Light.Lamp current, then use Topology / Build / TopoPoint to create several TopoPoint items (each by selecting a Node item). Change the Point scale override to get a suitable symbol size.
  5. For overlay Service.Light.Lamp define the following schema, open it as a table window, enter Lamp ID values, e.g. L1, L2, L3,... (and lamp Angle, their Status as Working or Failed, and other attribute values as desired), and add a label theme for Lamp ID:

    Item ID (_id&)
    Item class (_classLocal$)
    Node (_node&)
    Angle (_angleDeg#)
    Lamp_ID (Lamp_ID$)
    Network_ID (Network_ID$)
    Bulb_Type (Bulb_Type$)
    Condition (Condition$)
    Direction (Direction$)
    Operation (Operation$)
    Category (Category$)
    Status (Status$)

  6. Repeat the previous step for overlay Service.Light.Circuit, Circuit ID values e.g. C1, C2, C3,..., and this schema (with Condition entered as as Good or Poor):

    Item ID (_id&)
    Item class (_classLocal$)
    Links (_links$)
    Circuit_ID (Circuit_ID$)
    Network_ID (Network_ID$)
    Cable_Type (Cable_Type$)
    Condition (Condition$)
    Underground (Underground$)

  7. For each item in both overlays, enter a Network ID to specify which network it is a member of (e.g. N1). The simple case is that all items form a single network. Try to form two networks (e.g. N1, N2) as in the example. Note that the circuit members of each network must form a tree, and that a lamp's Network ID must be the same as a circuit's at that point.
  8. To distinguish N1 and N2 circuit items, select one set and assign them a pen with colour Green, width 2mm, offset 2mm (as in the example). Try also including a dash pattern, either using a Style of Dash or a custom dash pattern.
  9. From the SWD's local menu, use Save / Save all.
  10. Use Map Compiler to compile the site plan again, then use SQL.aspx to execute the logged SQL for creating the new tables and schema, then use Map Compiler to compile the site plan again. If this logs other Topology "Service" errors, return to SIS Desktop and correct them.
  11. Use the Administrator / Configuration page to add the following MapTheme settings: 
    label,  service_light_lamp.lamp_id,       Light Lamp ID
tip,    service_light_lamp.lamp_id,             Lamp ID
tip,    service_light_lamp.network_id,          Network ID
tip,    service_light_lamp.status,              Status
colour, service_light_lamp.status,        Light Status
label,  service_light_circuit.circuit_id, Light Circuit ID
tip,    service_light_circuit.circuit_id,       Circuit ID
tip,    service_light_circuit.network_id,       Network ID
tip,    service_light_circuit.condition,        Condition
colour, service_light_circuit.condition,  Light Circuit Condition

    and the following MapLegend settings: 

    service_light_lamp.status, Working, 00FF00
service_light_lamp.status, Failed, 0000FF
service_light_circuit.condition, Good, 00FF00
service_light_circuit.condition, Poor, 0000FF

    and optionally the following AssetTable settings: 

    0,service_light_lamp,Lighting - Lamps,service_light_lamp_id lamp_id circuit_id condition status bulb_type direction operation category site_id x y
0,service_light_circuit,Lighting - Circuits,service_light_circuit_id circuit_id condition cable_type underground site_id x y
  12. Refresh the site plan in Map Enquiry to view the two new layers, their item dialogs, and their label and colour themes. In their item dialogs, select Network Details to see further details, and to trace their networks. and select Details to display their details in the Asset details panel, from where (if AssetTable settings include field names) they can be displayed in the Asset Manager module.
  13. Use Database Manager to view the four tables:

    Service Pit (service_pit)
    Service Trench (service_trench)
    Service Light Lamp (service_light_lamp)
    Service Light Circuit (service_light_circuit)

4. ADDING DIFFERENT NETWORK TYPES TO THE SAME INFRASTRUCTURE

The Map Compiler topic's Topological Overlays section's example includes a second network type that shares the same pit and trench infrastructure (Power networks with Line and Outlet items). With multiple network types:

If you need further assistance, please contact IFM Support <support@integratedfm.com.au>.