topic Re: About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool. in ArcGIS Utility Network Questions

About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool.

Davis_Dad23 — Tue, 05 Nov 2024 15:01:00 GMT

I Want to migrate source data to UN Model, what is the best approach for this task for migrating source data to UN Model and Managing Topological Errors.

Also please, Let me know about UN Version 7 if it can be supported in ArcGIS Field Map. Because there is a documentation that says it is not supported. So best approach is to use UN Version 6?

Re: About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool.

JohnAlsup — Tue, 05 Nov 2024 13:46:59 GMT

Feild Maps does not support 64 bit objectID's at this time and UN version 7 uses 64 bit objectID's.

As for domains, can you clarify this question. May be provide an example.

Re: About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool.

RobertKrisher — Tue, 05 Nov 2024 14:05:56 GMT

Migration

I recommend you read the articles in this learning series to answer your questions: Migrating to the Utility Network. The first tutorial in the series shows you how to create a data migration starting with the simple data mappings tool. The simple data mappings tool helps create a migration workspace that does all the transformations for you, append with transformation requires you to create your own mappings with translations (a very tedious process!). If done properly they both can achieve the same results, but creating your own migration and transformations can take months, but using the simple data mappings tools processes takes hours.

Field Maps

Field maps is still working on supporting the utility network. Until it does you will need to select the option to deploy a v6 utility network when you deploy your utility network.

No Domain

If you deploy a utility network without a domain, you will only have structural features. This means you won't be able to represent any utility features for tracing or analysis.

Re: About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool.

Davis_Dad23 — Tue, 05 Nov 2024 14:51:36 GMT

@JohnAlsup Thank you for clarifying the Field Maps compatibility. I now understand that Version 6 is the one I should use to ensure the compatibility. I appreciate your guidance!

"To clarify my question above, my source data currently lacks Geodatabase domains; it consists of feature classes with attribute fields and values but no domain-defined constraints. I understand that for the Utility Network (UN) model, I will need to map these attributes to the appropriate domains, such as asset types, to align with the UN structure. I thank @RobertKrisher for giving me the helpful guidance. Thank you

Re: About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool.

Davis_Dad23 — Tue, 05 Nov 2024 14:55:28 GMT

Thank you @RobertKrisher i am going to follow the guidance on the best Data Migration tool for the approach to use, this is really helpful.

On the Field Map it is also clear, Now i understand that i will use Version 6 for deploying. Thank you

Re: About Migrating source data to UN Model , what is the difference between Append with Transformation and Create Simple data Migration tool.

RobertKrisher — Tue, 05 Nov 2024 15:17:21 GMT

Ooooh coded value domains / range domains. That's fine. You will create your own lookups to do translate from your freeform text/number fields into the expected coded value domains/data types required by the target models.

When we talk about a Domain in the utility network, we can either be referring to a geodatabase domain (coded value/range) or a Domain Network, which refers to a collection of rules and definitions used to model the network information model for a specific industry.