Select to view content in your preferred language

Starting steps for ArcGIS Utility Network

893
3
Jump to solution
09-13-2023 08:23 PM
DeepikaJain01
New Contributor III

Dear Community

I have downloaded the solution for ArcGIS UN for Telco from ArcGIS Solutions. I will be reprojecting it and building it with the data that I have. Eventually, the UN has to move from File db to Postgre SQL. I am not sure, whether shall I build my UN in file db first and then migrate it to PostGres or I should first migrate the sample solution to Postgre SQL and then reproject and pump my data into it.

PS: Right now, the data sits in Postgre SQL, If I am building it in file db, I will be exporting the data into file db FC first. Also, please help me with the steps to migrate UN data into Postgre SQL.

Appreciate the help!

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

There is an online learning series specifically about Migrating to the Utility Network learning series that will help you understand the process and tools. You should also consider taking the full Getting Started with the Utility Network learning series since it covers the core concepts of the product, along with some important aspects of how to manage the topology and subnetworks.

If this is your first utility network, and it sounds like it is, I recommend you use a mobile geodatabase or file geodatabase until you get very comfortable with the entire migration process. There are two reasons for this:

  1. Data migration is an iterative process. When you make a mistake, it's much easier to create a new file/mobile geodatabase and start over again (rerun your conversion, deploy your asset package, etc).
  2. It's possible to run a fully functional, single-user utility network in a mobile or file geodatabase, meaning you can convert the data into a local geodatabase and do all your quality assurance and testing without needing to do anything with ArcGIS Enterprise. In order to edit or analyze data in an SDE environment you need to register your data with ArcGIS Enterprise and publish/use feature services for all your work. Since you're just starting out, I'd recommend you start with the simpler approach (mobile gdb) until you are comfortable with adding additional steps to the process (or you need to share your data with others).

Other final notes:

  • When using a local geodatabase, I recommend you use a mobile geodatabase over a file geodatabase, especially if you have a lot of non-spatial objects or associations (which telco models typically do).
  • You can always copy/paste a utility network between databases, so once you have everything up and running in a mobile geodatabase you can always just copy it to a new database in Postgres.

View solution in original post

3 Replies
ArchitSrivastava
Occasional Contributor II

 Hello @DeepikaJain01 ,

I would you should start where you feel most comfortable in working weather FGDB or eGDB. It possible for us to move the data around from FGDB to eGDB or vise-versa.

For more details about migration you can refer to this documentation "Migrate a utility network dataset 

I would also suggest going through this eBook by SSP innovations "UTILITY NETWORK: A TO Z ". This helped me a lot in understanding what is needed. It explains details nicely and simple manner also available to download.

Hope it helps!

-Archit

RobertKrisher
Esri Regular Contributor

There is an online learning series specifically about Migrating to the Utility Network learning series that will help you understand the process and tools. You should also consider taking the full Getting Started with the Utility Network learning series since it covers the core concepts of the product, along with some important aspects of how to manage the topology and subnetworks.

If this is your first utility network, and it sounds like it is, I recommend you use a mobile geodatabase or file geodatabase until you get very comfortable with the entire migration process. There are two reasons for this:

  1. Data migration is an iterative process. When you make a mistake, it's much easier to create a new file/mobile geodatabase and start over again (rerun your conversion, deploy your asset package, etc).
  2. It's possible to run a fully functional, single-user utility network in a mobile or file geodatabase, meaning you can convert the data into a local geodatabase and do all your quality assurance and testing without needing to do anything with ArcGIS Enterprise. In order to edit or analyze data in an SDE environment you need to register your data with ArcGIS Enterprise and publish/use feature services for all your work. Since you're just starting out, I'd recommend you start with the simpler approach (mobile gdb) until you are comfortable with adding additional steps to the process (or you need to share your data with others).

Other final notes:

  • When using a local geodatabase, I recommend you use a mobile geodatabase over a file geodatabase, especially if you have a lot of non-spatial objects or associations (which telco models typically do).
  • You can always copy/paste a utility network between databases, so once you have everything up and running in a mobile geodatabase you can always just copy it to a new database in Postgres.
DeepikaJain01
New Contributor III

Dear @RobertKrisher and @ArchitSrivastava 

Thank you for providing me the direction, def a great help!