Procedure to make a seamless model-Building and Sync -Out Using GIS-ID in Model-Builder

Joseph,

Here is an article that explains how to build a model using GIS data (including the GIS-ID).

Importing external data using ModelBuilder - Building and updating

The following article explains how to update the GIS source files with changes made to the hydraulic model.

Using the Sync Out function to update source files using ModelBuilder

As you mentioned, after importing the GIS data and then splitting a pipe, both pipes will have the original GIS-ID.

Then when syncing back out to the GIS Shapefile it will only update the original GIS Data with one of the split pipes from the hydraulic model and ModelBuilder will return the following.

This is because the GIS-ID should be unique. ModelBuilder will not assign a unique GIS-ID to elements. Typically system designs and extensions created in the model would not be added to the GIS until they are constructed. The GIS team gets new as-built additions and adds them to the GIS which is when GIS-IDs are assigned.

See the following article.

Expected workflows when keeping a model in sync with GIS

Dear Craig,

I reviewed all the above links and I found that all the examples are depending on the LABLE as a key field not the GIS-ID.

I know that when I depend on the LABEL everything will in his place because it is a one to one relation but in the case of the GIS-ID it is One in the source to many in the target. and as I mentioned in my post that when I sync-out to the ArcGIS the Model-builder uses only the last item in the updated group which sharing the same ID and that not was expected for the tool.

So, how to do the update when I am using the GIS-ID as a key field not the LABEL.

Thank you

Best Regards

Joseph Atef

Hi Joseph,

The first two links are indeed more general, but the last one is relevant to this GIS-ID workflow.

As Craig mentioned, typically you would not be syncing model changes out to a GIS, for various reasons. If you split a pipe and change the diameter of one of the new pipes, then you have two different pipe sizes for the same GIS-ID, so the program would have no way to know which one is correct for the single pipe in the GIS. What would you want to occur in such a case?

Typically GIS changes would flow in one way; as the GIS changes, those changes can "trickle down" to the hydraulic model by running ModelBuilder to sync the GIS changes to the model. So, in the case of the split pipe, if the pipe in the GIS changes and you update the model, both pipes will get the same change.