|
POST
|
Are you attempting this on an Enterprise GDB? If so, is it versioned and does it have data in it(assembly class)?
... View more
05-23-2022
05:03 PM
|
0
|
1
|
3534
|
|
POST
|
You could leverage the terminal paths of a device. For instance, you have a selectable switch. Which has three terminals, A, B and C. When defining the terminal configuration, you set terminal paths of None, A-B, A-C, and A-B & A-C. The device can be set to be in one of these states. So if you wanted to disconnect C, you would set the device to A-B.
... View more
05-23-2022
05:48 AM
|
0
|
1
|
1331
|
|
POST
|
The Utility Network in the output GDB is not usable. The Change Asset Package Spatial Reference tool should fail when there is a controller dataset like the Utility Network in the input GDB. We have a backlog item to handle these scenarios and exit early. The tool is designed to change the spatial reference of the asset package, which you then apply to a GDB and it creates the UN.
... View more
05-16-2022
06:45 AM
|
0
|
1
|
2452
|
|
POST
|
When you say Exclude Transformers from the result, are you using an output filters? These occur after trace and all the selection has happened. So since a terminal device is always returned in a trace, when it is a barrier, that means it container will be returned even if it is filtered out in an output filter.
... View more
04-30-2022
07:25 AM
|
0
|
1
|
1603
|
|
POST
|
I cannot comment on the barrier issue, your use of the network attribute is correct, maybe there is a connectivity issue to the xfrs that are not being returned. Another weird behavior is I don't see any difference when checking or unchecking "Include barrier features". I think it should include or not the transformers, which are barriers... - This is a known issue on terminal devices. They are not removed when they are barriers and the include barrier features is unchecked.
... View more
04-29-2022
06:38 AM
|
0
|
1
|
1620
|
|
POST
|
ok, my guess was wrong then. Let us know what support says and I will keep digging too.
... View more
04-25-2022
11:37 AM
|
1
|
0
|
1007
|
|
POST
|
My only guess is it is trying to add the SupportedSubnetwork field to assembly as allow null equal false with data. Assembly: MikeMillerGIS_0-1650910877232.png
... View more
04-25-2022
11:23 AM
|
0
|
5
|
3608
|
|
POST
|
If a subnetwork name field is added without data, it is added with Allow Null = False. It appears a tier was added after data, which means the subnetwork field has to be added with Allow Null = True. So Update is expecting this field to Allow Null = False is my guess.
... View more
04-25-2022
09:43 AM
|
0
|
1
|
3622
|
|
POST
|
Please log an incident with Tech Support. I have not seen this issue before.
... View more
04-25-2022
07:16 AM
|
0
|
1
|
3630
|
|
POST
|
Up and Downstream traces require a subnetwork controller. For example, in sewer, this would be the treatment plant. More info on how up and downstream work: https://pro.arcgis.com/en/pro-app/2.7/help/data/utility-network/utility-network-trace-types.htm#:~:text=Upstream%20trace&text=Once%20identified%2C%20upstream%20traces%20travel,)%20in%20sink%2Dbased%20networks.
... View more
04-21-2022
06:00 AM
|
0
|
2
|
3972
|
|
POST
|
You can create a new subnetwork at the lower station, but that will require those breakers to be directional in a partitioned network.
... View more
04-19-2022
03:05 AM
|
0
|
0
|
2372
|
|
POST
|
It appears to be a change in the Text representation of a geometry. The M used to be reported as NaN and we were filtering these as the Point constructor fails with a NaN M. The M is not being returned as Null, so I had to extend the filter logic to also pop null Ms. Line 71 is the only change in case you just want to add that to your code. // Assigned To: StructureJunction
// Type: Calculation
// Name: StructureJunction - Manhole Elevation Attributes
// Description: Set rim elevation, invert elevation, and depth on Sewer Storm Vault - Manhole from the Z value. Update Manhole Channel content feature z value if needed.
// Subtypes: Sewer Storm Vault
// Field:
// Trigger: Insert, Update
// Exclude From Client: True
// Disable: False
// Related Rules: Some rules rely on additional rules for execution. If this rule works in conjunction with another, they are listed below:
// - None
// Duplicated in: This rule may be implemented on other classes, they are listed here to aid you in adjusting those rules when a code change is required.
// - None
// ************* User Variables *************
// This section has the functions and variables that need to be adjusted based on your implementation
// Limit the rule to valid asset types
// ** Implementation Note: Instead of recreating this rule for each asset type, this rules uses a list of domains and exits if not valid
var asset_type = $feature.assettype;
var valid_asset_types = [9];
// The rim elevation, invert elevation and depth field names
var rimelev_fld = "rimelev";
var invertelev_fld = "invertelev";
var depth_fld = "depth";
var depth = $feature.depth;
// The class names of the Manhole Channels
// ** Implementation Note: These are just the class/table name and should not be fully qualified.
var device_class = "SewerDevice";
// Sewer Device - Manhole Channel sql clause
// ** Implementation Note: Sql expression used to find content Manhole Channels to update z value with Invert Elevation value
var manhole_chan_sql = 'AssetGroup in (32) and AssetType in (301, 302)';
// ************* End User Variables Section *************
// ************* Functions *************
// monikerize FeatureSetByName function
var get_features_switch_yard = FeatureSetByName;
function get_content_manhole_chan() {
// find Manhole Channel globalid that is content of $feature
var associations = FeatureSetByAssociation($feature, 'content');
var filtered = Filter(associations, "className = @device_class");
var associated_ids = [];
for (var row in filtered) {
push(associated_ids, row.globalId)
}
if (Count(associated_ids) < 1) return null;
var device_fs = get_features_switch_yard($datastore, device_class, ["globalid", "assetgroup", 'assettype'], true);
var content_man_chan = First(Filter(device_fs, "GLOBALID in @associated_ids and " + manhole_chan_sql));
return iif(IsEmpty(content_man_chan), null, content_man_chan)
}
function update_geom(geo, new_z) {
// Set z on point to new value
var geo_dict = Dictionary(Text(geo));
geo_dict['z'] = new_z;
return Point(drop_nans(geo_dict))
}
function drop_nans(dict_with_nans) {
// drop any keys with a value of NaN
var new_dict = {};
for (var k in dict_with_nans) {
if (!IsNan(dict_with_nans[k]) && dict_with_nans[k] !=null ) {
new_dict[k] = dict_with_nans[k]
}
}
return new_dict
}
// ************* End Functions Section ******************
// Limit the rule to valid asset types
if (!Includes(valid_asset_types, asset_type)) {
return;
}
// Round z to 2 sigfigs
var geo_z = Geometry($feature).z;
geo_z = Round(geo_z, 2);
// build payload to update rim elevation, invert elevation, depth
if (IsEmpty(depth)) depth = 0;
var res = {"attributes": Dictionary(rimelev_fld, geo_z, invertelev_fld, geo_z - depth, depth_fld, depth)};
var ret = {"result": res};
// Get manhole channel and update z to invertelev
var man_chan = get_content_manhole_chan();
if (!IsEmpty(man_chan)) {
// if invertelev of Manhole does not match Z of Manhole Channel, update the Manhole Channel
if (Geometry(man_chan).z != res["attributes"][invertelev_fld]){
var update_manhole_chan = {
"globalid": man_chan.globalid,
'geometry': update_geom(Geometry(man_chan), res["attributes"][invertelev_fld])
};
var edit_payload = [{
'className': device_class,
'updates': [update_manhole_chan]
}];
ret["edit"] = edit_payload
}
}
return ret;
... View more
04-06-2022
07:59 AM
|
1
|
1
|
1278
|
|
POST
|
I would have to look it up, but I believe you could not modify the shape of a feature till 2.7 or 2.8 or since you were able to update Y, maybe it is something specific with M's.
... View more
04-03-2022
11:11 AM
|
0
|
0
|
1515
|
|
POST
|
Modeling 3 domains in 1 UN will provide the ability to share structures and trace through domains. The only tracing between domains at the moment is Find Connected, which does not use the domain parameter. You can chain traces, such as a downstream water trace, get it results and add flags there and then an upstream Sewer trace(can do this with two UNs too). When modeling multiple domains in the same UN, the only item you need to be careful about is how many inline network attributes you use as there is a limit(21) to how many bits you have. Another note, when modeling multiple domains in the same UN, all those layers/domains are required to be in the feature service. So permissions are set at service level, so if you do require User A to only edit Sewer and User B to only edit water and manage the Utility Network capabilities, you do not have this level of permission at the service level.
... View more
03-31-2022
03:15 AM
|
3
|
0
|
2701
|
|
POST
|
This line will have to be split. You could script it. Find those lines and get a vertex midway through and use that as the split point.
... View more
03-31-2022
03:08 AM
|
1
|
0
|
2371
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 3 weeks ago | |
| 2 | 07-07-2026 06:45 AM | |
| 1 | 06-26-2026 09:15 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|