|
| 1 | +## BatchTracingCoreHost |
| 2 | + |
| 3 | +<!-- TODO: Write a brief abstract explaining this sample --> |
| 4 | +Standalone application that batch traces a utility network |
| 5 | + |
| 6 | + |
| 7 | + |
| 8 | +<a href="https://pro.arcgis.com/en/pro-app/sdk/" target="_blank">View it live</a> |
| 9 | + |
| 10 | +<!-- TODO: Fill this section below with metadata about this sample--> |
| 11 | +``` |
| 12 | +Language: C# |
| 13 | +Subject: Console |
| 14 | +Contributor: ArcGIS Pro SDK Team <arcgisprosdk@esri.com> |
| 15 | +Organization: Esri, https://www.esri.com |
| 16 | +Date: 05/06/2025 |
| 17 | +ArcGIS Pro: 3.5 |
| 18 | +Visual Studio: 2022 |
| 19 | +.NET Target Framework: 4.6.1 |
| 20 | +``` |
| 21 | + |
| 22 | +## Resources |
| 23 | + |
| 24 | +[Community Sample Resources](https://github.com/Esri/arcgis-pro-sdk-community-samples#resources) |
| 25 | + |
| 26 | +### Samples Data |
| 27 | + |
| 28 | +* Sample data for ArcGIS Pro SDK Community Samples can be downloaded from the [Releases](https://github.com/Esri/arcgis-pro-sdk-community-samples/releases) page. |
| 29 | + |
| 30 | +## How to use the sample |
| 31 | +<!-- TODO: Explain how this sample can be used. To use images in this section, create the image file in your sample project's screenshots folder. Use relative url to link to this image using this syntax:  --> |
| 32 | +1. In Visual Studio click the Build menu. Then select Build Solution. |
| 33 | +2. Run the corresponding executable "BatchTracingCoreHost.exe" with a JSON file defining the configuration for the analysis you want to perform. |
| 34 | + |
| 35 | +## Sample Data |
| 36 | + |
| 37 | +All examples were configured using the [Utility Network Foundation](https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/utility-network-foundations/) data models from the ArcGIS Solutions team at the time the tools were developed. You will likely need to make adjustments to these files based on your own schema and data requirements. |
| 38 | + |
| 39 | +This repository includes several examples you can use to get started: |
| 40 | +- [JSON Configuration files](./JSON%20Configurations): This directory contains a series of configuration files for different use cases |
| 41 | +- [Named Trace Configurations](./Trace%20Configurations): This directory contains the named trace configuration referenced in each JSON Configuration File |
| 42 | + |
| 43 | +## Analysis Types |
| 44 | +Each JSON file defines the type of analysis to be performed, and depending on the type of analysis there are additional parameters that are required. The different types of analysis are: |
| 45 | +- [Trace](trace.md) - Identify all the features connected to specific devices in your network. |
| 46 | +- [Partition](partition.md) - Parition your network into unique zones that cover specific types of lines or devices. |
| 47 | +- [Infer Subnetworks](infer.md) - Identify potential subnetworks and controllers for a tier in your network. |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +# Output |
| 52 | + |
| 53 | +## Aggregated Geometry (Point, Line, Polygon) |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +When configured, these tables will hold the aggregated geometry of the features returned by the trace. It will respect the Output Asset Type and Output Conditions of the trace configuration. |
| 58 | + |
| 59 | +The corresponding table is cleared every time the tool is run, so if you configure multiple analysis each analysis should have its own table. Each trace has a single row containing all the geometries for that trace. |
| 60 | + |
| 61 | +Fields |
| 62 | +- AnalysisName: Name of the analysis performed |
| 63 | +- TraceName: Name of the trace configuration that was executed |
| 64 | + |
| 65 | +--- |
| 66 | + |
| 67 | +## Output Table |
| 68 | + |
| 69 | + |
| 70 | + |
| 71 | +When configured, this table will include the information of the features returned by the trace. It will respect the Output Asset Type and Output Conditions of the trace configuration. |
| 72 | + |
| 73 | +The output table is cleared every time the tool is run, so if you configure multiple analysis each analysis should have its own table. Each trace can produce many rows in this table. |
| 74 | + |
| 75 | +Fields |
| 76 | +- AnalysisName: Name of the analysis performed |
| 77 | +- TraceName: Unique identifier from the starting feature of the trace (Batch Trace and Parition network), sequence number of the trace (Infer Subnetwork) |
| 78 | +- SourceIdentifier: Unique identifier from the result feature (Infer Subnetwork only) |
| 79 | +- NetworkSourceID: ID of the network source for the result feature |
| 80 | +- NetworkSourceName: Name of the network source for the result feature |
| 81 | +- ElementObjectID: Object ID of the result feature |
| 82 | +- ElementGuid: Global ID of the result feature |
| 83 | +- AssetGroupCode: Asset group code of the result feature |
| 84 | +- AssetGroupName: Asset group name of the result feature |
| 85 | +- AssetTypeCode: Asset type code of the result feature |
| 86 | +- AssetTypeName: Asset type name of the result feature |
| 87 | +- TerminalID: Terminal ID of the result feature, if applicable |
| 88 | +- TerminalName: Terminal name of the result feature, if applicable |
| 89 | + |
| 90 | + |
| 91 | +<!-- End --> |
| 92 | + |
| 93 | + <img src="https://esri.github.io/arcgis-pro-sdk/images/ArcGISPro.png" alt="ArcGIS Pro SDK for Microsoft .NET Framework" height = "20" width = "20" align="top" > |
| 94 | + |
| 95 | +[Home](https://github.com/Esri/arcgis-pro-sdk/wiki) | <a href="https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference" target="_blank">API Reference</a> | [Requirements](https://github.com/Esri/arcgis-pro-sdk/wiki#requirements) | [Download](https://github.com/Esri/arcgis-pro-sdk/wiki#installing-arcgis-pro-sdk-for-net) | <a href="https://github.com/esri/arcgis-pro-sdk-community-samples" target="_blank">Samples</a> |
0 commit comments