Good morning,
Wondering if anyone else has come across this issue with the export tool built into Bentley Map?
I use the tool to create shapefiles to submit to our Environmental section, and also sometimes to create exhibits in ArcMap, but if the CAD alignment has curves in it, somewhere in the process of creating the shapefile, the curves are removed, leaving a straight line in between the begin and end of the curved alignment, edge of pavement, ROW, and any other lines that are curved within the CAD dgn.
I'm using this tool from Power GEOPAK. I first go to the GEOPAK menu and select "Activate Map". Then the File menu-->Export-->GIS Data Types...
From there, I create a new Export as a shapefile and select the file location. I select the layer that I am interested in exporting to a shapefile, and then Export. Before bringing it into an ArcMap map, I have to first view the file in ArcCatalog to set the appropriate coordinate system, as ArcGIS needs a coordinate system set in order to bring it into the map.
This is a snip of just the alignment and station tics. Any help given would be greatly appreciated!!
Thanks!
Stephanie
This was a new one. I thought the missing curve was reloved by exporting to a geodatabase instead of a shapefile but now i have extra curves
Interesting jomac. What were the original graphic elements prior to Exporting? If they were complex shapes, try using the Drop command before exporting.
Can you tell us the versions of MicroStation, Bentley Map, and InRoads or GEOPAK that are in-use? I believe a defect related to this issue was looked and and corrected in a recent version (more recent than three years ago when this thread started).
I'm using MAP v8i (ss4) v08.11.09.864 and after we chatted the other day one of the elements that had translated correctly did the same thing again the next time I exported it.
did this ever get resolved? 2+ years later and i am having the same problem in Power Inroads.
I don't see where anything was resolved here.
I have not tried it again in a long time now, but I don't think this has been resolved, based on all the comments since my original post about this almost 5 years ago. The issue was supposed to be addressed in updated versions, but doesn't sound like it has been.
I do have a workaround I can share with you, if you need to get this done--there are more steps, but holds all your arcs in the linework. Open up your .dgn and save a copy of it somewhere, in case you need to clean it up to only show the features in the CAD that you need for the shapefile, or feature class. If you want to show only the features you need to create a GIS file for, delete out any un-needed features the .dgn file first, and then save the .dgn as a .dwg.
Open ArcCatalog, and go to your saved .dwg file to set the Coordinate System to the one you need for your project area. Open an ArcMap GIS map that has some other reference features in it, like roads, maybe parcels, and any other boundaries that will verify if the CAD file comes in to the map in the correct location. After you have verified it is in the correct location, from the Table of Contents, double-click the CAD layer you added to get to the Properties, and go to the Symbology tab. Under Categories, choose Unique values, and choose Layer as the Value Field to symbolize it by. Now you can use the Select by Attribute tool to select your linework that you need to create a shapefile, or geodatabase feature class from, and the GIS features created will include the arcs in the linework.
Hope this helps, and good luck.
Testing this morning with Map V8i (SELECTseries 10) show that setting the stroking variable provides a suitable export. In the graphic below the white element is the Shapefile referenced under the original Centerline (red arc).
The issue was reported on 04/25/2016, and fixed in Map V8i (SELECTseries 4) version 08.11.09.862 in 2018. Use the 'About Bentley Map V8i' option to see which version is in-use within your Power InRoads product.
As has been commented on and just like Google earth interoperability, Bentley claims a version works now when in fact it does not.