<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Method for exchanging MX Drainage data with Watercom Drains</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/103218/method-for-exchanging-mx-drainage-data-with-watercom-drains</link><description>Since we lost our 12D drainage designer ,I have tried resurrecting MX Drainage to integrate road and drainage design. Our drainage engineer uses Watercom Drains and MX Drainage has menu options for both importing and exporting data to/from Drains. 
 However</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Method for exchanging MX Drainage data with Watercom Drains</title><link>https://communities.bentley.com/thread/308723?ContentTypeID=1</link><pubDate>Mon, 15 Dec 2014 11:00:53 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:ee3b439b-fe1f-4cf3-9a2a-01dca3971130</guid><dc:creator>Jason Walsh</dc:creator><description>Enhancement 159674 has been logged to request compatibilty with Drains DB1 file format.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Method for exchanging MX Drainage data with Watercom Drains</title><link>https://communities.bentley.com/thread/308721?ContentTypeID=1</link><pubDate>Mon, 15 Dec 2014 10:32:15 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:55c2d3aa-8eb5-4396-a0a8-8a872e86e17a</guid><dc:creator>Jason Walsh</dc:creator><description>That workaround should be OK. With regard to data loss the best advice I can give is to use the process on a test drainage design and compare the  exported drainage design.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Method for exchanging MX Drainage data with Watercom Drains</title><link>https://communities.bentley.com/thread/308683?ContentTypeID=1</link><pubDate>Sun, 14 Dec 2014 04:15:43 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:cdf9f704-2455-4c3a-a674-0d12b2a70a81</guid><dc:creator>Grant Stewart</dc:creator><description>Thanks Jason, would appreciate it if you could log the feature request.&lt;br /&gt;
&lt;br /&gt;
We did contact Watercom last week as their manual indicates to use the same import process for MX Drainage as they do for a local product called Advanced Road Design (their drainage module has a common ancestor to MX Drainage, ie InfraDrainage from the days prior to Bentley&amp;#39;s acquisition).  Watercom has worked pretty closely with ARD and they now exchange data via xml.  However, I will make further inquiries about their DB1 format.&lt;br /&gt;
&lt;br /&gt;
After a bit of reading, I am thinking of exporting from MX Drainage to StormCAD and then exporting a shapefile, as Drains can apparently import shapefiles.  I am hoping that we can then go the opposite way back from Drains to StormCAD and through to MX Drainage.  Any idea if this is feasible (ie wont be too much data loss)?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Method for exchanging MX Drainage data with Watercom Drains</title><link>https://communities.bentley.com/thread/308513?ContentTypeID=1</link><pubDate>Fri, 12 Dec 2014 10:07:21 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:1c304335-544e-45e5-ba33-2f6552b7af6d</guid><dc:creator>Jason Walsh</dc:creator><description>I can log a feature request for MX Draiange to be updated to support the current DRAINS database file format .db1. &lt;br /&gt;
&lt;br /&gt;
As DRAINS used to support .mdb database file format it may be worthwhile contacting Watercom to check if they a method to convert a .mdb file to the new database file .db1 so it can be imported.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>