topic Re: DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations in ArcGIS Utility Network Questions

DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations

JayHodny — Wed, 14 May 2025 18:01:11 GMT

Hello. We are in the process of migrating to the Utility Network for our water, stormwater, and sanitary sewer utilities. We have spun up an Enterprise 11.3 test environment and are using ArcGIS Pro 3.4.3. Following great advice from another post, we are following the SS Foundation 2.2 online workflow and adapting it to the SW Foundation 1.4. It has been moving along, but questions arise as does confusion. My colleague has been working the SS foundation, which is progressing, while I work the SW foundation with less success.

In comparing the two DataMapping.xls tables, we noticed the SS table has several additional worksheets when compared to the SW table. Missing from the SW table are the Info, Associations, Mapping Table, and Source Types worksheets. We assume this has to do with the SS foundation being newer than the SW foundation. Can these sheets be manually added and populated with stormwater related information (assuming we can figure out that information)? Or do we move along with the current SW DataMapping.xls table with the existing worksheets?

Following along in the SS Foundation online help, Data Migration Tutorial....Migrate Data.....Create Migration Workspace step, we ran the Create Migration Workspace GP tool in the SW Pro project, which failed. I recall then having to download a newer version of the toolbox from GitHub (Utility Data Management Support 3.3.3) and installed it. Ran the tool again, worked but received a warning about a missing column in the DataMapping.xls....Data Mappings work sheet, a column named Source Subtype Name. I added the column with no values in the cells, and ran the tool again, succeeded with no error message. As part of the three key outputs noted in the tutorial (modified asset package, workspace, and csv), no 'assocations.csv' file was created. I don't know what to do about the missing .csv.

Has there been an update to the stormwater foundation Data Dictionary?

Thanks for any help and advice, Jay

Re: DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations

MikeMillerGIS — Wed, 14 May 2025 21:00:38 GMT

Can these sheets be manually added and populated with stormwater related information (assuming we can figure out that information)? Or do we move along with the current SW DataMapping.xls table with the existing worksheets?

- Unless you need them, should not affect anything

- You can run the Create Simple Data Mapping and include the old sheet to carry it forward into the new schema

- We ran the Create Migration Workspace GP tool in the SW Pro project, which failed.

- What was the failure?

The most recent version of the tools are here - https://github.com/Esri/Utility-Data-Management-Support-Tools

Re: DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations

JayHodny — Thu, 15 May 2025 12:52:17 GMT

Hello Mike,

Thank you for the quick response and information. Here is the error message:

EXCEPTION
Traceback (most recent call last):
File "driveletter\myfoldernetwork\StormWater\Stormwater Utility Network Foundation V1_4\Toolboxes\UtilityDataManagementSupport.atbx\udms_pt\common\wrappers.py", line 161, in wrapper
f = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "driveletter\myfoldernetwork\StormWater\Stormwater Utility Network Foundation V1_4\Toolboxes\UtilityDataManagementSupport.atbx\udms_pt\gptools\tools.py", line 117, in run
include = [t.table for t in AbstractPackage().package_tables(include_optional=True) if not t.is_data_table]

Downloading the updated tools from GitHub got us past this error.

Regards,

Jay

Re: DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations

MikeMillerGIS — Thu, 15 May 2025 13:05:45 GMT

That makes sense. The shipped version of the UDMS toolset was build for 3.1. A lot has changed since then and requires the new toolset. In upcoming versions of the foundations, we are removing the toolset and providing instructions on getting the appropriate version of the toolset from github. Writing tools that work in multiple versions of ArcGIS Pro with multiple different python versions has it's challenges and the best solution is to have a toolset per version of ArcGIS Pro.