HI,
Is a patch / fix / solution has been provided to make this information available in a sync-out (database) ? This relational information is important and the Excel spreadsheet ‘export’ option does not appear relevant as a long term solution.
Personally, although the description of the problem below only implies STOP_NODE, the transfer problem only applies to START_NODE which remains NULL.
Start_node is synchronized properly.
Refer to ;
Start and stop nodes are not exported in "Sync Out" using ArcGIS Geodatabase features with ModelBuilder
Product(s):
WaterGEMS, SewerGEMS, HAMMER
Version(s):
10.00.xx.xx, 08.11.xx.xx
Area:
Modeling
Problem
While using data source type "ArcGIS Geodatabase Features" using ModelBuilder in ArcGIS, 'Start Node' and 'Stop node' are not exported in "sync out". All other properties come. Why is this occurring? Problem ID#: 65482
Solution
The Sync Out function will update every element in the target source that also exists in the model. The data used to update the target source is all based on the mapped fields established in Modelbuilder. This does not include the start and stop nodes, as these are not properties that can be mapped to in Modelbuilder when using the ArcGIS Geodatabase Feature. With this source file type, the ends of a pipe have a certain coordinate and as long a node is within the tolerance of that end point, the pipe will attach to the end node.
If you need to include start and stop nodes in the Sync Out function, try syncing out to a different file type, like an Excel spreadsheet. The spreadsheet would need to be set up with column headers for data you want to sync out, or you will not be map the model data to the spreadsheet.
Hi,
Thanks Yashodhan,
As, started before the same article, stop_node have been mapped in modelbuilder and adequately sync as a ArcGIS geodatabase feature. Only START_NODE is the problem.
I understand that the node, in a line feature, will be automatically attached to an adjacent line according to a proximity rule i.e. tolerance. However, the attribute value of the node, notwithstanding its proximity to attachment, corresponds to the manhole upstream of the pipe. Considering that the option is present in the software, STOP_NODE is synchronized adequately, it would be relevant, in the context of support, to try to solve the problem.
The proposed solution, to send this informaiton in an Excel spreadsheet, is incompatible with application development in a DBMS environment.
Hello Thomas,
I have filed a Service Request (#7001017579) on your behalf and assigned the defect (#1074553) for this issue. I will communicate via the Service Request with you for this issue.
Regards,
Yashodhan Joshi
Perfect, thanks for the details. I remain waiting for service request communications to share contact info.
I sent a link for the Cumulative Patch to resolve this issue in an email from the Service Request. Please install it over the latest WaterGEMS version (10.02.03.06) and reply to the email message if you have any other questions.
Thank-you,Larry
Perfet, i try the build and i keep you informed. The same fix is planned for SewerGEMS ?
Thomas Rousseau-Beaumier said:The same fix is planned for SewerGEMS ?
Yes. I have sent you the latest cumulative patch set for SewerGEMS 10.02.03.03 via your Service Request This resolves the same issue, in that product. We will look into updating the related wiki article based on the outcome of this discussion.
Jesse DringoliTechnical Support Manager, OpenFlowsBentley Communities Site AdministratorBentley Systems, Inc.