Database and WaterGEMS integration: PostgreSQL or Modelbuilder/GIS-ID?

Is it possible to integrate a hydraulic model in WaterGEMS with a PostgreSQL database? I have a water supply systems as a project in QGIS using PostGIS, and I would like to integrate it so that both systems use the same database. In other words, if I make a change in QGIS, it will be reflected in WaterGEMS, and if I make a change in WaterGEMS, it will be reflected in QGIS.

As far as I know there is no way to use database in WaterGEMS. So what is the closest i can get for this solution? The main goal is to have just one plataform to update. Because nowadays I need to change/update/add/remove elements in my QGIS project and also in WaterGEMS model. And I want a smarter way to work.

The only way is to use modelbuilder with QGIS's shapefiles and GIS-ID? If I use that to bring auto upgraded information from GIS by GIS-ID in, can I use the other way around by GIS-ID-out?

Parents
  • Eduardo, indeed you would need to accomplish this using sync-in and sync-out in ModelBuilder. Using GIS-ID as the key field is also indeed recommend as this would enable you to continue establishing the link between the model and the GIS even if you perform model simplification operations such as skeletonization and pipe splits. A Sync-out is indeed possibly to send model updates back to the GIS although this is very rare in my experience. Typically the GIS is considered the "source of truth" for asset information so any changes would be made first in the GIS and then cascaded down to the model using a Sync-in in ModelBuilder.

    I also recommend making use of the Snapshots feature in ModelBuilder to track changes. See more tips to help with your model sync workflow here: Keeping a Hydraulic Model in Sync with a GIS


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.

Reply
  • Eduardo, indeed you would need to accomplish this using sync-in and sync-out in ModelBuilder. Using GIS-ID as the key field is also indeed recommend as this would enable you to continue establishing the link between the model and the GIS even if you perform model simplification operations such as skeletonization and pipe splits. A Sync-out is indeed possibly to send model updates back to the GIS although this is very rare in my experience. Typically the GIS is considered the "source of truth" for asset information so any changes would be made first in the GIS and then cascaded down to the model using a Sync-in in ModelBuilder.

    I also recommend making use of the Snapshots feature in ModelBuilder to track changes. See more tips to help with your model sync workflow here: Keeping a Hydraulic Model in Sync with a GIS


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.

Children
No Data