Latest Contributions by Jens_Dalsgaard

Fully agree, Robert.  Yet, working with utilities I bet you know that not all questions are fit for standard configurations. Network categories is for standard config's and we are currently working with Elvia til finalize network categories and attributes. This - counting downstream meters - is a standard question.  For more ad-hoc questions, other approaches likely will be pursued. ... View more

Thanks for taking the time to clarify this, Mike. So batch tracing requires you to create and assign a network category (or network attributes?) to the asset types to be counted?!? Aiming for a more flexible way to analyze the grid, the way ahead might doing regular tracing returning JSON and then following up with custom analyzes on this output set. Now I now.    ... View more

The trace configuration is being applied against a mobile geodatabase (whilst testing stuff out). What I want to count is the number of meters reached in the downstream trace.  ------------------------------------------------------------------------------------------------------------------------------- Let me start by first add a trace configuration returning downstream meters as a selection: The above trace configuration correctly return the downstream low voltage meters as a selection: All good so far. ___________________________________________________________________________________ Next, let me add a trace configuration returning the COUNT of downstream meters only: Now, this is where I get lost ;): What I aim to count is the number of low voltage meters reached - blue rectangle.  But, should I fill out any of the parameters with yellow highlighting above? And if so, should I simply count occurrences of an arbitrary network attribute, that I know will be filled out?: And how about Result type? ??? Hope for further patience on my fumbling around here 🙂 Perhaps even a video walk-through ...   ... View more

That the returned results must be stored in a text field is fine - I just create a string field for the result returned instead.   I was under the impression that it was the batch trace that did the count, but now understand that it is the trace configuration doing so. So, I create a new trace configuration returning the count of low voltage meters downstream: Trying to execute this new trace configuration (returning the count) returns an error though: ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds. What am I doing wrong here? ... View more

I need to ask you for some clarifying questions here, @VenkataKondepati - or maybe @MikeMillerGIS should bring clarity.   The Group Field has already been set to Start_ID as described above: This is what is already populated onto the Trace Name attribute on the generated Aggregated Points: This really doesn't relate to the calculation as such, does it? Now, as I want to calculate the count onto the trace starting points and not generate aggregated geometries, I disable Aggregated Results and enable Calculate: This engages a new section in the GP-configuration, and I am asked to specify the attribute to which the calculated information is to be written: I notice that the attributes shown come from the JD_BatcgTraceStartingPoints feature class - that's good. But I also notice that apparently I am only allowed to write the calculated results to attributes with data type TEXT - and hence not to the intended attribute Meter_Count  It seems I will have to update the schema but for now I just choose DisplayName as target: I believe, by this I have set up writing trace results to the DISPLAYNAME field on the starting point features.   It is after this that it becomes blurry to me.   What do you mean, Mr @VenkataKondepati, when stating: pick your downstream meter layer as the source choose COUNT(OBJECTID) and write the result into the Meter_Count field I simply don't get it.  ----------------------------------------------------------- The Fields to update drop-down reveals fields from the trace starting point feature class, so I'd assume, this is where I specify storing results on the JD_BatchTraceStartingPoints:DISPLAYNAME fields. But - what is this compared to the Store Summary Information on Starting Points information (red ellipse above)? Generally, this section is a complete mystery to me:  And the built-in documentation doesn't help me out: Assistance will be appreciated.   Best regards Jens Dalsgaard   ... View more

Following Esri Inc recommendations, which is typically wise, and using partitioned tiers for your electric grid, there might be a way around your need for 'denoting each LV asset with EHV, HV and LV tier it belongs to'. The answer, I believe, lies in in not actually writing the EHV- and HV tier names onto the low voltage feature yet still offering this information to the end user using attribute (Arcade) expressions - results of an Arcade script appearing to the user just as any other attribute in the popup. https://developers.arcgis.com/javascript/latest/sample-code/popuptemplate-arcade/  You would then add such Arcade attributes revealing the names of the EHV- and HV tier feeding the LV tier feeding the relevant feature. ... View more

Reading some of your other posts, I get the impression that you're already well into UN. You have a fully functional UN and 'simply' want to replicate this. Or what. My answer was given - sorry about that - based on the assumption that you thought - as I do find some thinking - that you can simply move data into ArcGIS UN and utility network will work. You're not there. 🙂 ... View more

Re-reading your question I ask myself whether you're actually asking about migrating from one UN database to another UN database. In that case, why wouldn't you use standard ArcGIS GP's? E.g. https://doc.arcgis.com/en/arcgis-solutions/latest/tool-reference/utility-network-package/export-asset-package.htm ... View more

Migrating to ArcGIS Utility Network is COMPLEX and it seems unlikely that a dump will accommodate ArcGIS UN requirements. A dump at best would be the start of a migration process where data is transformed to comply to UN requirements. ... View more

Certainly, I have sent you a mail allowing you to immediately test what works and what apparently seems to not to be working. ... View more

Creating network categories and assigning these as relevant to asset types representing cables and overhead lines works out - to some extent. For example - I have created a new network category Volue_LV_OHUG and have assigned this to low voltage cables and overhead lines asset types. And setting up a named trace configuration doing a connected traced yet using this network category (Volue_LV_OHUG) as conditional barrier seems to work as intended. the trace stops at low voltage cables and overhead lines. But if I create a named trace configuration (or simply perform a trace) downstream from a medium voltage trace starting point  to continue into low voltage (because I want the low voltage part of the substation included in the trace result) yet using the same network category as a conditional barrier the trace still seems to continue into the low voltage grid. What should I look for when debugging? ... View more

Of course, obviously. Should have seen this myself.    Despite this, do you see any arguments against adding an idea for allowing grouping as was my initial proposal? Adding categories will work fine in this specific case, yet in may other cases it would seem unflexible.  ... View more