Aller au contenu principal

Filter trace configurations to those shared with the Map

Terminée
Sam De Lore

We have a large number of trace configurations in our EGDB that are used for all sorts of things, but there's only a handful of those that we want to make available to Network users. It would be great if we could filter the trace configs in the Networks app to only those shared with the map
 

0

Commentaires

5 commentaires

Date Votes
  • Commentaire officiel
    Daniel Carrion

    Hi Sam, Thanks for submitting this request! I've created a corresponding User Story and agree—it makes sense to filter traces based on the Trace Configuration Property of the WebMap. I'll bring this up with the development team, and we hope to include this enhancement in one of the upcoming releases.

    In the meantime, if this is urgent, there is an undocumented workaround you can use. It allows you to override the trace configurations listed in the app by manually modifying the app.json of the Studio Web Application. Specifically, you can adjust the utility-network-service property and manually add the trace configurations you'd like to expose. This is an example:

    {
        "id": "utility-network-service",
        "traceConfigurations": [
            {
                "creator": "max.power@vertigis.com",
                "name": "Find LV Service Points",
                "description": "Find all connected LV Service Points",
                "traceType": 5,
                "resultTypes": [],
                "creationDate": 1730300357000,
                "tags": [],
                "configuration": {
                    "includeContainers": true,
                    "includeContent": true,
                    "includeStructures": true,
                    "includeBarriers": false,
                    "validateConsistency": true,
                    "validateLocatability": false,
                    "synthesizeGeometries": false,
                    "includeIsolated": false,
                    "ignoreBarriersAtStartingPoints": false,
                    "includeUpToFirstSpatialContainer": false,
                    "allowIndeterminateFlow": true,
                    "useDigitizedDirection": false,
                    "domainNetworkName": "ELE",
                    "tierName": "ELE_LV_Level",
                    "targetTierName": "ELE_LV_Level",
                    "subnetworkName": "",
                    "diagramTemplateName": "",
                    "shortestPathNetworkAttributeName": "",
                    "filterBitsetNetworkAttributeName": "",
                    "traversabilityScope": "junctionsAndEdges",
                    "functionBarriers": [],
                    "arcadeExpressionBarrier": "",
                    "filterBarriers": [],
                    "filterFunctionBarriers": [],
                    "filterScope": "junctionsAndEdges",
                    "functions": [],
                    "outputConditions": [],
                    "propagators": [],
                    "nearestNeighbor": {
                        "count": -1,
                        "costNetworkAttributeName": "",
                        "nearestCategories": [],
                        "nearestAssets": []
                    },
                    "conditionBarriers": [
                        {
                            "name": "NET_MainLifeCycleStatus",
                            "type": "networkAttribute",
                            "operator": "notEqual",
                            "value": 4,
                            "combineUsingOr": true,
                            "isSpecificValue": true
                        },
                        {
                            "name": "NET_ELE_LevelController",
                            "type": "networkAttribute",
                            "operator": "equal",
                            "value": 1,
                            "combineUsingOr": true,
                            "isSpecificValue": true
                        },
                        {
                            "name": "NET_CurrentPosition",
                            "type": "networkAttribute",
                            "operator": "equal",
                            "value": 2,
                            "combineUsingOr": false,
                            "isSpecificValue": true
                        }
                    ],
                    "outputFilters": [
                        {
                            "networkSourceId": 9,
                            "assetGroupCode": 500,
                            "assetTypeCode": 572
                        }
                    ]
                },
                "title": "Find LV Service Points"
            }
        ],
        "$type": "utility-network-service-type"
    },

     

  • Sam De Lore

    Hi Daniel Carrion !

    Thanks for that, I'll give the undocumented workaround a go, this will make a great improvement for users!

    0
  • Daniel Carrion

    Hi Sam De Lore , just wanted to inform you that this feature will be available in the upcoming Networks Release 1.13, scheduled for September 17th.

    2
  • Sam De Lore

    That's great! Thanks Daniel Carrion !

    0
  • Daniel Carrion

    Hi Sam, 

    Starting with Networks 1.13, this functionality is now a core product feature.
    The logic works as follows:

    • We first check if there are any shared trace configurations in the web map.
    • If shared trace configurations are found, only those are displayed.
    • If none are found, we fall back to showing all available trace configurations from the utility network server, as before.
    0

Vous devez vous connecter pour laisser un commentaire.

Ce n’est pas ce que vous cherchez ?

Nouvelle publication