{"id":801551,"date":"2020-05-19T07:42:38","date_gmt":"2020-05-19T14:42:38","guid":{"rendered":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&p=801551"},"modified":"2021-04-30T05:05:04","modified_gmt":"2021-04-30T12:05:04","slug":"exporting-subnetworks-using-data-interoperability-part2","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2","title":{"rendered":"Leveraging Data for External Systems – Automating Export Subnetwork using Data Interoperability – Part Two"},"author":20321,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[23851,25741],"tags":[605811,605801,615601,33401,35461],"industry":[],"product":[36561,36861,515312],"class_list":["post-801551","blog","type-blog","status-publish","format-standard","hentry","category-data-management","category-electric-gas","tag-data-interoperability","tag-export-subnetwork","tag-rest-api-rest","tag-un","tag-utility-network","product-arcgis-pro","product-api-rest","product-utility-network"],"acf":{"short_description":"Learn how the Data Interoperability extension in ArcGIS Pro can help you build an FME Workbench to Export Subnetworks","flexible_content":[{"acf_fc_layout":"content","content":"

In the first blog<\/a>, we completed the first four steps to build an automation sample for Export Subnetwork using the ArcGIS Data Interoperability<\/a> extension for ArcGIS Pro.\u00a0 As a refresher, below are the six steps to complete the workbench file.<\/p>\n

    \n
  1. Generate Token<\/span><\/span><\/strong><\/li>\n
  2. Export\u00a0<\/span>Subnetwork<\/span><\/span><\/strong><\/li>\n
  3. Download JSON<\/span><\/span><\/strong><\/li>\n
  4. Split the JSON<\/span><\/span><\/strong><\/li>\n
  5. Feature creation<\/span><\/span><\/strong><\/a><\/li>\n
  6. Data transformation, schema setting, <\/span><\/span>and\u00a0<\/span><\/span>writing the outputs<\/span><\/span>.\u00a0<\/span><\/span><\/strong><\/a><\/li>\n<\/ol>\n

    We will focus on the last two steps of the process and complete the sample in this blog.\u00a0 \u00a0After we finish the workbench file, we will create a Spatial ETL tool in ArcGIS Pro and embed this workbench file so it can be a part of your project.<\/p>\n

    Source of Export Subnetwork output<\/span><\/span><\/h2>\n

    The JSON output of Export Subnetwork is retrieved from elements of the network topology<\/a> index using a powerful tracing framework<\/a>. Using this framework, the return result is highly performant, network connectivity exists, and it has been validated and is consistent with features in the network topology.\u00a0 However, there is a limitation you need to be aware of to properly use the result.<\/p>\n

    As shown below,\u00a0JSON output attributes have coded domains, e.g. networkSourceId<\/em>, assetGroupCode,<\/em> and assetTypeCode<\/em>. By design, these attributes are integers in each element of the network index, thus, they perform faster in storage and retrieval, compared to the feature space of the geodatabase.<\/p>\n

    Since coded domains are not suitable for external systems that require the descriptions, we need a lookup table to convert them.<\/p>\n","image_reference":{"ID":797871,"id":797871,"title":"featureElementsArray","filename":"jsonOutput.png","filesize":15511,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability\/jsonoutput","alt":"featureElements Array","author":"20321","description":"","caption":"featureElements array after JSON flattening showing coded values","name":"jsonoutput","status":"inherit","uploaded_to":785451,"date":"2020-04-04 14:17:33","modified":"2020-04-04 14:17:58","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":939,"height":259,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","medium-width":464,"medium-height":128,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","medium_large-width":768,"medium_large-height":212,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","large-width":939,"large-height":259,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","1536x1536-width":939,"1536x1536-height":259,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","2048x2048-width":939,"2048x2048-height":259,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput-826x228.png","card_image-width":826,"card_image-height":228,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/jsonOutput.png","wide_image-width":939,"wide_image-height":259}},"layout":"image","image_reference_figure":"","snippet":"","spotlight_name":"","section_title":"","position":"Right","spotlight_image":false},{"acf_fc_layout":"content","content":"

    Step five,\u00a0 feature creation<\/strong><\/h2>\n

    The Export Subnetwork JSON output has all the information you need to build geometry when the resultTypes <\/em>parameter includes the connectivity<\/em> and featureElements<\/em>\u00a0types and the option includeGeometry<\/em> is set to true.<\/p>\n"},{"acf_fc_layout":"content","content":"

    We begin feature creation from the flattened and fragmented JSON output arrays of step four.\u00a0 There are three fragments from this JSON that has geometry – controllers<\/em>, featureElements,<\/em> and connectivity. <\/em><\/p>\n

    The inspection of these arrays show that we need to remove duplicates between the featureElements<\/em> and the connectivity<\/em> arrays. In addition, the featureElements <\/em>array also includes system junctions where networkSourceId = 2 <\/em>and that these objects do not have geometry. We will filter out these objects before we create geometry.<\/p>\n

    Using TestFilter<\/a> <\/strong>transformers we determine the duplicate features and associations and the number of system junctions in our featureElements<\/em> array.<\/p>\n

    Based on the screenshot below, Subnetwork RMT001 <\/em>has 281 system junctions and that there are 128 associations and 2,971 features that are duplicates.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854031,"id":854031,"title":"duplicates and system junctions","filename":"duplicates-and-system-junctions.png","filesize":32592,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/duplicates-and-system-junctions","alt":"Testfilters that remove duplicates","author":"20321","description":"","caption":"Transformers that filters features with networkSourceId = 2 or system junctiona and remove duplicates.","name":"duplicates-and-system-junctions","status":"inherit","uploaded_to":801551,"date":"2020-05-07 18:17:30","modified":"2020-05-07 18:19:01","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":432,"height":550,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","medium-width":205,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","medium_large-width":432,"medium_large-height":550,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","large-width":432,"large-height":550,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","1536x1536-width":432,"1536x1536-height":550,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","2048x2048-width":432,"2048x2048-height":550,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions-365x465.png","card_image-width":365,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/duplicates-and-system-junctions.png","wide_image-width":432,"wide_image-height":550}},"image_position":"left-center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    Now we are ready to create geometry for the rest of the objects of each array.<\/p>\n

    The geometry schema for controllers<\/em>, featureElements,<\/em> and connectivity<\/em> arrays are different. So I created separate data flow for each fragment to build their respective geometries. In each data flow, using a FeatureMerger<\/a><\/strong>, we merge the spatialReference<\/em> to each element so that they can be located in the world using the coordinate system in the feature after geometry is created.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854091,"id":854091,"title":"featureArrays","filename":"featureArrays-1.png","filesize":29891,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/featurearrays-2","alt":"Data flow of features, controllers and associations","author":"20321","description":"","caption":"Features, controllers, and associations arrays that require building geometry","name":"featurearrays-2","status":"inherit","uploaded_to":801551,"date":"2020-05-07 18:29:24","modified":"2020-05-07 18:31:03","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":687,"height":604,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","medium-width":297,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","medium_large-width":687,"medium_large-height":604,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","large-width":687,"large-height":604,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","1536x1536-width":687,"1536x1536-height":604,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","2048x2048-width":687,"2048x2048-height":604,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1-529x465.png","card_image-width":529,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/featureArrays-1.png","wide_image-width":687,"wide_image-height":604}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    A GeometryReplacer<\/a> transformer is added to each data flow to create the feature geometry.<\/p>\n

    For the featureElements array<\/em>, the geometry type of each feature could be either paths, rings<\/em>, or has x,y, <\/em>and z<\/em>. The GeometryReplacer knows which geometry to create based on the geometry type.<\/p>\n

    For the connectivity<\/em> array, we are interested only in objects with association connectivity where viaNetworkSourceId = 1. <\/em> There is no geometry type in the array but each object has a pair of x, y,<\/em> and z<\/em> attributes – prefixed by from <\/em>and to<\/em>. Connectivity will be drawn with these coordinates as vertices using the VertexCreator<\/a>. The association line will be drawn from these vertices using the LineBuilder<\/a> transformer.<\/p>\n

    The controllers<\/em> are point features and the geometry will be built from its x<\/em>, y<\/em>, and z<\/em> attributes.<\/p>\n

    Using the CoordinateSystemSetter<\/a> transformer, all features are tagged with the _coordsys<\/em> attribute provided by the spatialReference <\/em>object.<\/p>\n

    Below is the feature creation bookmark on my canvas.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854111,"id":854111,"title":"Feature Creation bookmark in Workbench canvas","filename":"Feature-Creation-bookmark-in-Workbench-canvas-1.png","filesize":97831,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/feature-creation-bookmark-in-workbench-canvas-2","alt":"Feature Creation bookmark in Workbench canvas","author":"20321","description":"","caption":"Feature Creation bookmark in Workbench canvas","name":"feature-creation-bookmark-in-workbench-canvas-2","status":"inherit","uploaded_to":801551,"date":"2020-05-07 18:33:56","modified":"2020-05-07 18:34:08","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1282,"height":610,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","medium-width":464,"medium-height":221,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","medium_large-width":768,"medium_large-height":365,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","large-width":1282,"large-height":610,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","1536x1536-width":1282,"1536x1536-height":610,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","2048x2048-width":1282,"2048x2048-height":610,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1-826x393.png","card_image-width":826,"card_image-height":393,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Feature-Creation-bookmark-in-Workbench-canvas-1.png","wide_image-width":1282,"wide_image-height":610}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    Exclusions<\/strong><\/h3>\n

    If networkAttributes<\/em> option is configured in resultTypes <\/em>parameter, the results will appear as another array of key-value pairs in each feature of the featureElements<\/em> array called networkAttributeValues<\/em>. The sample has network attributes configured and a sample result is shown below.\u00a0 For this blog, I chose not to process them.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854131,"id":854131,"title":"networkAttributeValues","filename":"networkAttributeValues.png","filesize":69144,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/networkattributevalues","alt":"NetworkAttributeValues array","author":"20321","description":"","caption":"Sample of networkAttributeValues result when Network Attributes are configured","name":"networkattributevalues","status":"inherit","uploaded_to":801551,"date":"2020-05-07 18:47:48","modified":"2020-05-07 18:48:13","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":629,"height":491,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","medium-width":334,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","medium_large-width":629,"medium_large-height":491,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","large-width":629,"large-height":491,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","1536x1536-width":629,"1536x1536-height":491,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","2048x2048-width":629,"2048x2048-height":491,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues-596x465.png","card_image-width":596,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/networkAttributeValues.png","wide_image-width":629,"wide_image-height":491}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    If fields<\/em> options are configured in resultTypes<\/em> parameter, a fieldValues <\/em>array will be added to each feature with an existing value on the field, like below. As I mentioned earlier, I did not include fields in my export.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854151,"id":854151,"title":"fieldValues","filename":"fieldValues.png","filesize":43950,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/fieldvalues","alt":"","author":"20321","description":"","caption":"Sample of fieldValues result when Result Fields are configured","name":"fieldvalues","status":"inherit","uploaded_to":801551,"date":"2020-05-07 18:50:57","modified":"2020-05-07 18:51:08","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":629,"height":317,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","medium-width":464,"medium-height":234,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","medium_large-width":629,"medium_large-height":317,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","large-width":629,"large-height":317,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","1536x1536-width":629,"1536x1536-height":317,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","2048x2048-width":629,"2048x2048-height":317,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","card_image-width":629,"card_image-height":317,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/fieldValues.png","wide_image-width":629,"wide_image-height":317}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"sidebar","content":"

    A look ahead to Export Subnetwork in 2.6<\/h2>\n

    Structural attachments and containments are not supported in Utility Network Version 3<\/a>. With the upcoming Utility Network Version 4 in ArcGIS Pro 2.6, these two association types will be supported. Additionally, support for nonspatial junction and edge objects will be included as part of Export Subnetwork.<\/p>\n","image_reference":false,"layout":"standard","image_reference_figure":"","snippet":"","spotlight_name":"","section_title":"","position":"Right","spotlight_image":false},{"acf_fc_layout":"content","content":"

    Note that the values for both networkAttributeValues<\/em> and fieldValues<\/em> are coded domains. To convert these coded values to description, another lookup process has to be added to this sample.\u00a0 Read the Extending the lookup table note<\/a> for additional help with this process.<\/p>\n

    With a few attribute cleanup in the canvas, our features are now created. I\u2019ve added a couple of Inspectors<\/a> so we can view our output in the Workbench.<\/p>\n

    Our current workspace now looks like this:<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854171,"id":854171,"title":"Current DIO Workspace Canvas","filename":"Current-DIO-Workspace-Canvas-1.png","filesize":87636,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/current-dio-workspace-canvas-2","alt":"Current workspace from steps one to five","author":"20321","description":"","caption":"The current workspace in canvas from steps one to five ","name":"current-dio-workspace-canvas-2","status":"inherit","uploaded_to":801551,"date":"2020-05-07 18:53:42","modified":"2020-05-07 18:54:39","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1282,"height":344,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","medium-width":464,"medium-height":125,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","medium_large-width":768,"medium_large-height":206,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","large-width":1282,"large-height":344,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","1536x1536-width":1282,"1536x1536-height":344,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","2048x2048-width":1282,"2048x2048-height":344,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1-826x222.png","card_image-width":826,"card_image-height":222,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Current-DIO-Workspace-Canvas-1.png","wide_image-width":1282,"wide_image-height":344}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    When I test this workspace, the example results below are displayed from the Visual preview tab of the Workbench.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":854671,"id":854671,"title":"visualPreview","filename":"visualPreview-2.png","filesize":260617,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/visualpreview-3","alt":"Visual preview of featureElements table in Workbench","author":"20321","description":"","caption":"Visual preview of featureElements table in Workbench","name":"visualpreview-3","status":"inherit","uploaded_to":801551,"date":"2020-05-07 23:21:31","modified":"2020-05-07 23:21:50","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":2000,"height":623,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2.png","medium-width":464,"medium-height":145,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2.png","medium_large-width":768,"medium_large-height":239,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2.png","large-width":1920,"large-height":598,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2-1536x478.png","1536x1536-width":1536,"1536x1536-height":478,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2.png","2048x2048-width":2000,"2048x2048-height":623,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2-826x257.png","card_image-width":826,"card_image-height":257,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/visualPreview-2-1920x598.png","wide_image-width":1920,"wide_image-height":598}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    To see the geometry on a larger map, you can launch the Data Inspector with CTRL-ALT-D or by clicking on the Inspector icon on the left vertical tab of the Visual Preview window in the Workbench shown above.<\/p>\n

    In FME Data Inspector<\/a>, Subnetwork RMT001 looks like below.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":797921,"id":797921,"title":"FMEDataInspector","filename":"FMEDataInspector.png","filesize":288218,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability\/fmedatainspector","alt":"FME Data Inspector view","author":"20321","description":"","caption":"FME Data Inspector app","name":"fmedatainspector","status":"inherit","uploaded_to":785451,"date":"2020-04-04 15:26:39","modified":"2020-04-04 15:27:03","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1263,"height":1020,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","medium-width":323,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","medium_large-width":768,"medium_large-height":620,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","large-width":1263,"large-height":1020,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","1536x1536-width":1263,"1536x1536-height":1020,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","2048x2048-width":1263,"2048x2048-height":1020,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector-576x465.png","card_image-width":576,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/FMEDataInspector.png","wide_image-width":1263,"wide_image-height":1020}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    We are getting close but we are not done yet! If you look at the table displayed above in the FME Data Inspector, you will notice that our attributes still show the coded domains. We need to change these to descriptions, set and modify the schema to make our output dynamic, and finally write the output to finish our sample.<\/p>\n

    Step six<\/strong>,\u00a0 data transformation, schema setting, and writing outputs<\/strong><\/h2>\n

    In a recent GeoNet article, our solutions team shared a toolbox for Adding Descriptions to the Export Subnetwork JSON<\/a>. \u00a0It includes a tool to create a lookup table and another tool to update the JSON output(s) of the Export Subnetwork with descriptions.\u00a0 This step follows the same patterns as the toolbox built in Python; however, in our sample, the lookup table is generated during run time to make the lookup table dynamic with regard to schema changes.<\/p>\n

    Before we build the lookup table, it is important to understand, the Source Mapping object from the JSON result and the data element of the utility network feature layer. If you are already familiar with these, feel free to skip the next two sections and proceed to Build the lookup table<\/a>.<\/p>\n"},{"acf_fc_layout":"content","content":"

    Source Mapping<\/strong><\/h3>\n

    The\u00a0sourceMapping<\/em>\u00a0object from the\u00a0_jsonOutput<\/em>\u00a0attribute is a table of unique network source ids and their corresponding feature class names in the geodatabase. Below is a sample of the source mapping array for subnetwork\u00a0RMT001<\/em>. Only unique\u00a0networkSourceId<\/em> from exported features in the\u00a0featureElements<\/em>\u00a0array are found on this JSON object.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":788771,"id":788771,"title":"fieldvalues array2","filename":"fieldvalues-array2.png","filesize":4199,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability\/fieldvalues-array2","alt":"Source Mapping","author":"9712","description":"","caption":"Sample of sourceMapping object","name":"fieldvalues-array2","status":"inherit","uploaded_to":785451,"date":"2020-03-30 11:24:44","modified":"2020-03-31 00:07:47","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":356,"height":279,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","medium-width":333,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","medium_large-width":356,"medium_large-height":279,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","large-width":356,"large-height":279,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","1536x1536-width":356,"1536x1536-height":279,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","2048x2048-width":356,"2048x2048-height":279,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","card_image-width":356,"card_image-height":279,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/fieldvalues-array2.png","wide_image-width":356,"wide_image-height":279}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    We need source mapping to group features by feature class names before we write them to the output and also as a reference for our lookup table to retrieve asset group and asset type values from the data element of the utility network.<\/p>\n

    Query Data Elements<\/strong><\/h3>\n

    The data element of the utility network is a repository of its rich metadata.\u00a0 In ArcGIS Pro, right-click the utility network layer<\/a> in the Contents pane and click Properties to access the Layer Properties dialog, then click on the Network Properties tab, to see the dialog below.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":797941,"id":797941,"title":"unLayerProperties","filename":"unLayerProperties.png","filesize":20115,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability\/unlayerproperties","alt":"Network Properties dialog","author":"20321","description":"","caption":"","name":"unlayerproperties","status":"inherit","uploaded_to":785451,"date":"2020-04-04 15:28:56","modified":"2020-04-04 15:29:02","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":881,"height":762,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","medium-width":302,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","medium_large-width":768,"medium_large-height":664,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","large-width":881,"large-height":762,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","1536x1536-width":881,"1536x1536-height":762,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","2048x2048-width":881,"2048x2048-height":762,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties-538x465.png","card_image-width":538,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/unLayerProperties.png","wide_image-width":881,"wide_image-height":762}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    Most of the network properties that you see in this dialog come from the JSON return of the query data elements of the utility network feature layer.<\/p>\n

    With the REST API, the utility network properties are returned using query data elements on the utility network feature layer. For my sample below, I entered [950]<\/em> for the Layers:<\/em> textbox, <\/em>to query the data element of the utility network. If I don\u2019t add a layer Id, the query will return the data elements of all layers of the feature service. To retrieve this layer id from a web query, see the Work with the utility network feature server<\/a> note below.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":797951,"id":797951,"title":"querDataElements","filename":"querDataElements.png","filesize":11192,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability\/querdataelements","alt":"Query Data Elements in REST API","author":"20321","description":"","caption":"Query Data Elements for feature layer ID 950 which is the utility network layerId for this sample","name":"querdataelements","status":"inherit","uploaded_to":785451,"date":"2020-04-04 15:29:30","modified":"2020-04-29 17:33:06","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":795,"height":641,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","medium-width":324,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","medium_large-width":768,"medium_large-height":619,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","large-width":795,"large-height":641,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","1536x1536-width":795,"1536x1536-height":641,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","2048x2048-width":795,"2048x2048-height":641,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements-577x465.png","card_image-width":577,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/03\/querDataElements.png","wide_image-width":795,"wide_image-height":641}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"image","image":{"ID":854291,"id":854291,"title":"dataElements","filename":"Picture1-2.png","filesize":122885,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/utility-network\/data-management\/exporting-subnetworks-using-data-interoperability-part2\/picture1-8","alt":"Query Data Elements JSON response","author":"20321","description":"","caption":"JSON response of query data element of utility network feature layer id 950","name":"picture1-8","status":"inherit","uploaded_to":801551,"date":"2020-05-07 20:48:01","modified":"2020-05-07 20:48:22","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":978,"height":1125,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2.png","medium-width":227,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2.png","medium_large-width":768,"medium_large-height":883,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2.png","large-width":939,"large-height":1080,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2.png","1536x1536-width":978,"1536x1536-height":1125,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2.png","2048x2048-width":978,"2048x2048-height":1125,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2-404x465.png","card_image-width":404,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2020\/04\/Picture1-2-939x1080.png","wide_image-width":939,"wide_image-height":1080}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    From the JSON result above, junctionSources<\/em> and edgeSources<\/em> (not shown) arrays in the data element have sourceId<\/em>, layerId<\/em>, assetGroupCodes<\/em> and assetTypeCodes<\/em> and their corresponding descriptions. We will need these as references for our lookup table.<\/p>\n

    The utility network data element contains a large amount of metadata and it is up to you to identify what you need for your own workflows.<\/p>\n

    We will follow three tasks in this last step to add into our workspace. These tasks are data transformation, schema setting, and writing the outputs.\u00a0 Let\u2019s begin with data transformation.<\/p>\n"},{"acf_fc_layout":"content","content":"

    Data transformation<\/strong><\/h3>\n

    We start this step by building a lookup table, that will be a reference table to convert coded domains to descriptions later in our data flow.<\/p>\n

    In our current workspace, we create a new data stream after the generate token bookmark by adding three web queries<\/span>.\u00a0 The purpose of each web query is described below. The details on why we need the results are explained later in each task.<\/p>\n

    Before we take a deep dive into feature creation, let’s learn the source of the output of export subnetwork on the note below. If you are familiar with the Utility Network API<\/a>, feel free to skip this and move on to feature creation.<\/p>\n"},{"acf_fc_layout":"sidebar","content":"