If you want to specify the locations of Layer Points at the distribution, drop or backbone layer for optimization, and if this data is not available digitally for an import via the import dialog, you can generate it manually via the “Draw Layer Point” workflow.
You can also use layer points to bring fibers to specific locations for future requirements. To do this, an additional Structure must be created at the layer point. This structure is used to define the fiber requirement at the layer point.
Please note that, when using the Comsof optimizer and when using the layer points as required points with the atesio optimizer, a (default) layer point always requires a (default) cluster on the same network layer.
Both the import and the workflow generate data in the “Layer Point” feature class. These are not changed by the optimization in the calculation.
Start the workflow by double-clicking the corresponding entry in the workflow explorer under “Create Objects”, right-click and execute or by clicking the “Execute” button at the bottom right of the workflow explorer.
The dialog box for filling in the attributes opens on the right.
Select the layer.
If the “AggID from Cluster” option is activated, the new layer point receives the aggregation ID from the cluster in which it is geometrically located. The manual entry of the aggregation ID is locked.
If the “AggID from Cluster” option is not active, assign an aggregation ID manually. The default cluster and default layer point are linked via the aggregation ID.
If a manually allocated aggregation ID is already assigned on the corresponding network layer or if the field is not populated, “OK” will not be released at the end of the workflow. The aggregation ID is a required attribute and must be populated. Please note that a default layer point always requires a cluster with the same aggregation ID on the corresponding network layer.
If the module for output according to GIS Nebenbestimmungen is activated in your project, please select the corresponding attributes here. You can find more information here.
Use the “Is Existing” attribute to define the status of the layer point. You can use this attribute to differentiate the costs in the rules.
Fill in the attributes with the corresponding values. These are not mandatory attributes.
If the “Is Included” attribute is activated, the layer point is taken into account in the calculation.
In “Max. usable Ducts”, you can define the number of spare microducts that should be kept available for connecting this layer point. If nothing is entered there, the optimizer takes the value from the rules.
Start the digitization of the layer point by clicking the “OK” button.
The “Cancel” button closes the workflow.
After manually entering layer points, run the preprocessing again.
The layer point has been recorded. If defined in the display model, the aggregation ID is displayed.
Special feature for network nodes on main level
If the network node at the main level is to be taken into account during optimization, this must be set in the planning rules.
If you select this option, the central office must be specified for all clusters at the main level. Otherwise, for example, a (default) central office point that should actually only apply to 1 cluster will be used as the default (network node point) for all other clusters at the main level.