Latest Contributions by JonDeRose

@JohnGaiot  It is possible to have multiple trace networks in the same feature dataset as long as the participating feature classes aren't the same; however, this appears to be a defect.  I apologize for the inconvenience.  We have been able to reproduce and have created an internal issue to be addressed. You can track this as BUG-000136866. ... View more

Good morning Tim, Selections sets are not honored on the class used as the input for either the Starting points or Barriers parameter in the Trace tool.  The best approach would be to create a layer file from the selection and use this as the input. This is briefly discussed here in the web help. ... View more

Copying this from a reply in another thread  to clarify when SOURECEID and FEATUREGLOBALID fields are used when working with starting points and barriers in a trace network trace. When placing starting points and barriers in a trace network, the SOURCEID / FEATUREGLOBALID are not required; however, these fields are honored if present and require the inclusion of valid values to be used.  Using SOURCEID and  FEATUREGLOBALID to specify trace locations in a feature class allows you to filter which features are used as trace locations.  Perhaps you have a feature class that contains features you want to use as barriers; however, you only want a certain type of feature, or specific set of features to serve as barriers...  In this case you could populate only the features you want to serve as barriers with SOURCEID/FEATUREGLOBALID information.  When the trace is executed, only these features would be used as either the starting point or barrier for the class.  To clarify, case, if your class has 20 records, but only 2 have SOURCEID/FEATUREGLOBALID populated with a valid value, only those 2 would be used as starting points or barriers in the trace. If these fields are not present, the geometry of the feature class will be used to intersect the network feature geometry and place either the starting point or barrier.    user-defined feature class used as a barrier feature without SOURCEID/FEATUREGLOBALID This is outlined here: https://pro.arcgis.com/en/pro-app/help/data/trace-network/starting-points.htm https://pro.arcgis.com/en/pro-app/help/data/trace-network/barriers.htm If this does not address the original use case above please reach out with additional details and I can review further. ... View more

Thank you again for the clear use case and data.  With your use case we were able to identify another issue and have implemented a fix related to placement of starting points in 2.7.  Another issue has been created to include barrier features in the trace result when using a network junction feature class as you were doing in your initial note. As you noted with case "a", interactive placement of trace locations using the Trace Locations pane will allow you to place starting points or barriers on an edge or junction feature.  This is the default method for placing trace locations For case "b" below, I am curious if the edge element selected is upstream or downstream of the junction feature that is not selected.  If you were to interactively place a starting point at the endpoint of a line from a small scale this could inadvertently place barriers on both adjacent endpoints which could explain why the junction feature is not included in the result set.  I d id notice in my testing that if I am zoomed out a bit, a barrier was placed on both the upstream and downstream edge surrounding the junction.  Alternatively, you could be placing the barrier on the endpoint of the edge upstream of the junction feature alone. Testing on my end using 2.6.3 shows that if the barrier is placed on the endpoint of the edge downstream from the junction, the junction is included in the result.  Juncitoin feature included in trace result Barrier interactively placed on endpoint of edge downstream of the junction feature Regarding your question about the need for SOURCEID / FEATUREGLOBALID fields when placing trace locations.  We have an open issue to address some issues that are encountered when using network features (such as WRProxyMZ) as barriers in a trace.  While these are honored as barrier features, there may be inconsistencies including these in the trace result as you have noticed.  The alternative solution for this is case "a" as you noted above.  Another approach would be use to another user defined class for the trace locations. When placing starting points and barriers in a trace network, the SOURCEID / FEATUREGLOBALID are not required; however, these are honored if present.  Using to determine trace locations allows you to filter which features are used as trace locations.  Perhaps you have a feature class that contains features you want to use as barriers; however, you only want a certain type of feature, or specific features to serve as barriers...  In this case you could populate only the features you want to serve as barriers with SOURCEID/FEATUREGLOBALID information.  When the trace is executed, only these features would be used as either the starting point or barrier from the class.  To clarify, case, if your class has 20 records, but only 2 have SOURCEID/FEATUREGLOBALID populated with a valid value, only those 2 would be used as starting points or barriers in the trace. If these fields are not present, the geometry of the feature class will be used to intersect the network feature geometry and place either the starting point or barrier.    user-defined feature class used as a barrier feature This is outlined here: https://pro.arcgis.com/en/pro-app/help/data/trace-network/starting-points.htm https://pro.arcgis.com/en/pro-app/help/data/trace-network/barriers.htm Thanks, Jon         ... View more

John Gaiot‌  A new result type option (Network Layers) will be available in the 2.7 release to provide this type of functionality. With this result type option selected, a new group layer will be created with a name you provide. The group layer will contain a collection of sub-layers (feature layers) corresponding to network sources belonging to the trace network with trace results. The actual trace results are selected in each of these sub-layers and only layers that have trace results in them are added to the output group layer. This should enable you to access information about the network features returned in the trace for use in other tools for iterative scripting. ... View more