|
POST
|
@Anumita the most common approach we see for this is to create separate users and schemas for each utility network. Each utility network then also gets a dedicated feature service. It is possible to have multiple utility networks from different services in the same map, but there are some known issues with some of the tools in the UI with that setup.
... View more
09-03-2024
12:24 PM
|
1
|
4
|
4031
|
|
POST
|
In addition to using the batch trace tool, if you use the aggregated geometry result type you will get a feature back that you can use that has the shape length of all the lines returned by the trace. Edit: We currently don't allow you to access the function results as an output of the tool, but if that's something you'd like to see please create an idea for it. If you call the trace using the ArcGIS API for Python or the ArcGIS Pro SDK (or any other API) you will get access to the individual function results to do with as you see fit.
... View more
08-30-2024
06:39 AM
|
2
|
0
|
1981
|
|
POST
|
If you deploy it to a local geodatabase using the Asset Package to Geodatabase tool, do you receive a similar error?
... View more
08-29-2024
10:44 AM
|
0
|
0
|
1746
|
|
POST
|
I misread your original post. If you get that error when enabling your network topology, you should log an issue with support. Are you using one of the standard utility network foundations? Have you made any alterations to the schema or attribute rules?
... View more
08-29-2024
08:28 AM
|
0
|
1
|
1778
|
|
POST
|
Can you post a snippet from the script you are running? Specifically, everything from where you define the cursor to where you are receiving this error. When using a cursor you should just be creating it, iterating it, and closing it. If you are doing anything else between creating it and using it (like enabling the topology or running other gp tools) you run the risk of invalidating the cursor like this.
... View more
08-29-2024
08:02 AM
|
0
|
3
|
1788
|
|
POST
|
Yes, propagation affects traversability in a way similar to condition barriers like lifecycle and device status. When the function that propagates values returns false for a feature, the trace will stop at that feature and not include it in the network.
... View more
08-28-2024
02:53 PM
|
1
|
0
|
2201
|
|
POST
|
This article depicts how the bitwise and operator is used to manage phasing. It is also discussed in this presentation from last year's Esri User Conference. The second issue you asked about is also described in that presentation. To summarize: If a feature is expecting a specific set of phases and NONE of those phases make it to that feature, it will not be part of the subnetwork and its phases energized will be set to de-energized. If at least one of the expected phases makes it to the feature it will be energized and part of the subnetwork, but the phases energized will be less than the expected phases.
... View more
08-28-2024
01:33 PM
|
1
|
0
|
2231
|
|
POST
|
Instead of truncating the data, you can just delete the data using the Delete Rows tool. Another option you could consider is taking a backup of your database prior to loading the data that you can restore back to. Finally, if you make any schema or configuration changes you will likely want to drop and recreate the database.
... View more
08-28-2024
12:15 PM
|
1
|
0
|
1916
|
|
POST
|
What you want to do is create a containment association so the Meter Station contains the Service Connection. Junction-junction connectivity is a connectivity association used for connectivity between junction and devices. Assemblies don't have any connectivity, they only act as containers for content. If you want to know more about what restrictions we place on connectivity and containment, read the feature restrictions section of the online help.
... View more
08-28-2024
06:44 AM
|
0
|
0
|
909
|
|
POST
|
It's worth noting that if all you're trying to do is validate errors that occurred due to editing or data loading you should use the Validate Network Topology tool. Running something like Repair or Rebuild every night when all you need to do is validate causes a lot of extra wear and tear on the system.
... View more
08-27-2024
07:00 AM
|
0
|
0
|
2111
|
|
POST
|
The Terminal Path Configuration attribute needs to be populated when you append the data. If it is not populated when you validate it will not auto populate, it will instead create an error.
... View more
08-26-2024
02:00 PM
|
0
|
1
|
3444
|
|
POST
|
It looks like a bunch of your features have no terminalconfiguration (like in the last screenshot). Set their terminal configuration to be default, validate, and see if that fixes the issue. That value should be defaulted on every feature in the network, and when it is null or invalid it causes many other errors in the model to appear. Make sure that however data is/was being loaded that you initialize that field with the default value.
... View more
08-26-2024
01:37 PM
|
0
|
3
|
3456
|
|
POST
|
Can you post some screenshots of the error, features, and associations in question? What do you see in the dirty areas? What do you see in the modify associations tool?
... View more
08-26-2024
12:34 PM
|
0
|
1
|
3486
|
|
POST
|
The dirty area layer is a managed, system table used by the utility network to record topology and subnetwork errors. As such we don't allow you to write custom errors to it. If you have custom errors you want to write to the database, you should look at attribute rules. They allow you to do many things, but one of them allows to create Arcade scripts that are run whenever a feature validated to ensure that it meets certain critera. Features that fail validation will have a customer error message written to validation error in the database. You can find additional resources here: Geodatabase resource hub - Attribute Rules Geodatabase resource hub - Arcade Attribute Rule Resource Article
... View more
08-21-2024
09:05 AM
|
0
|
0
|
975
|
|
POST
|
If we're sticking to model builder, try using the dissolve tool on your point layer. Pick your foreign key fireld as the dissolve field, then pick the values you want to push as your statistic fields (min, max, etc). You can then use the join field tool on the dissolved layer. In situations like this where I've found my data to be inconsistent or strange, I have often resorted to writing a python script to handle my data strangeness. I use a search cursor to iterate through all the values in my source data, creating a dictionary to store the values I want to push to the target layer. This allows me to ignore or discard any values that aren't relevant to my analysis. I then use an update cursor to push the values onto their corresponding features. The benefit of this approach is that a) you have complete control over how data is pushed between the two datasets and b) you can keep detailed logs about any anomalies (how many features in the source had invalid values, how many features from the source didn't have a corresponding target, how many features in the target didn't have a corresponding source, etc).
... View more
08-21-2024
08:55 AM
|
1
|
0
|
2894
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Thursday | |
| 1 | Thursday | |
| 1 | Tuesday | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
3 hours ago
|