Missing features after running asset package to geodatabase

268
4
Jump to solution
02-21-2024 08:23 AM
mshanaghan
Occasional Contributor

I am working on migrating my electric utility data to the the electric utility network data model. 

After running the "Asset Package to Geodatabase" tool and looking through the data in the newly created file geodatabase, I noticed that not all features were migrated from the asset package to the geodatabase after running this tool.

For example, I had mapped my light pole features to the utility network layer "Electric device", asset group "low voltage lighting", asset type "lighting". None of these features were migrated to the file geodatabase. They are missing from the map entirely.

It should be noted that I mapped some of my source data features, including light poles, to two layers in the utility network: light poles were mapped to electric device and structure junction. I preserved the source global IDs for only one of these two layers, so as to not have duplicate global IDs. So for the light poles, I retained the global IDs in the electric device layer, and created new global IDs for the structure junction layer. 

Are there any common reasons why not all data would be migrated from the asset package to the file geodatabase after running the asset package to geodatabase tool? Is it problematic to have source features mapped to more than one layer in the utility network?

Thanks in advance.

0 Kudos
1 Solution

Accepted Solutions
MikeMillerGIS
Esri Frequent Contributor

The issue is because you have a configuration table.  That configuration table, with all check boxes checked, is removing asset groups/type from the target.  This results in a SQL filter on the input data to ensure it is not copying AG/AT that does not exist in target.

 

Delete or rename the D_Configuration table

View solution in original post

0 Kudos
4 Replies
MikeMillerGIS
Esri Frequent Contributor

Can you verify those features do exist in the Asset Package?  Want to ensure it is not a Data Loading issue.  Any chance we can get the source, data loading workspace and asset package?  

0 Kudos
mshanaghan
Occasional Contributor

Would I be able to email those items to just you?

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

sure, mmiller@esri.com

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

The issue is because you have a configuration table.  That configuration table, with all check boxes checked, is removing asset groups/type from the target.  This results in a SQL filter on the input data to ensure it is not copying AG/AT that does not exist in target.

 

Delete or rename the D_Configuration table

0 Kudos