Export Inroads survey data to Civil 3D

[rwaldroupJNAKH]

Good afternoon,

I'm looking for any insight on exporting survey data that was processed in Inroads and importing it into a Civil 3D Survey database. The short version of why I need to do this is: we completed a topo survey in Inroads/Microstation  (per Louisiana DOTD standards) and our internal design team wants it in Civil 3D.

We are hoping to find a way to take the survey data we have processed and cleaned up and import it into a Civil 3d survey database so that it creates the figures in linestyles that our design team knows how to use.

Issue 1: We exported all the points from Inroads (right-click on the .fwd, export as text file, in PNEZDA format) which creates a csv. The points are not exported in the same order they are organized in the .fwd which when imported into a civil 3d survey data base, the survey figures are not drawing/connecting to the points in the order that they should. We have also tried running the geometry report which creates an xml of the same data, all survey points...which again are not in the correct order.

Issue 2: In InRoads, you can JPT a line up to three different points. The code would be formatted like such: 

300 JPT 5001 5002 5003       (300 is a code, and 5001 5002 and 5003 are three different point numbers)

In Civil 3D, I know we have to remove the space between the JPT and the point number.....but is it possible to have it JPT to 3 points total and if so, what is the correct formatting?

If anyone has any experience taking a fully processed survey from inroads to civil 3d, I'd love to hear from you! I can also provide more details if needed. Thanks.

[rl_jackson]

First, I don't know a dang thing about uStation. But I know enough about C3D to resolve you issue I believe.

Issue #1: You probably processed the data by Point Order vs. Import Order. (see image)

Issue #2:  I would assume JPT is Join Point, which would be complement C3D's CPN or Connect Point however I don't believe it will allow multiples on a single CPN. So you might try CPN5001 CPN5002 CPN5003 (just guessing). If I were to do the coding in C3d I'd go to point #5002 and place a 300 CPN5003 behind it, to continue the chain.

Now in C3D you can also change CPN so that it uses JPT, which would make any edits a little easier, in the Linework Code Set.

HTH

[rwaldroupJNAKH]

For issue 1, we are processing by import order, but the export of our survey points from Inroads is not exporting in the order they are in, in the .fwd. I've tried two different methods of exporting all points from the fwd into a csv file but neither method results in the points exporting in the correct order. This is unfortunate for us because we COGO in a number of office created points for a few reasons, including adding additional points along a curve because Inroads needs a minimum # of points between the PC and PT to generate a curve, and we also "create circles" for certain features (such as the circular slab a light pole is on), and these office created points are inserted in the .fwd between actual shots so when we load planimetrics (process linework) in Inroads, it draws through the points "in order" since we forced the office created points to be in order.

For issue 2, you're absolutely right, and thankfully Civil 3D allows you to customize those linework code sets so instead of using CPN we can keep JPT where it is. I will have to try coding a point with several instances of JPT as you said to see if it will work, but I think we may have tried it already to no avail.

I also asked this question to the Bentley communities with no luck (yet). I appreciate you taking the time to help me find a solution! Our current unglamorous workaround is to import the points through the survey database but not process linework or insert survey figures. Then we exported the linework from Microstation and brought it into Civil 3D and are painstakingly changing the linework to the appropriate C3D layer/linestyle.

[rl_jackson]

That's very unfortunate for the curves. I can actually code a curve with a single shot using OC. No PC or PT, just the in-coming and out-going tangent (2 shot on each, don't need to be the PC or PT) and it will compute a tangent curve. Circles are no issue, just code CIR (take 3 shots) or CIR2.0 for the concrete base of the Light Pole. So that code might look something like LP CIR2.0 it inserts the light pole symbol and draws the circle for the base of the pole.

So, from what you're explaining if you can get Bentley to export the "modified" data you edited in the "modified" order, you'd be golden, and all it wants to do is a numeric order, seems odd it wouldn't do that but C3D won't either. We are both screwed there. Leica linework from the DC comes to me out of order but in the chaining order that it was shot in. Real PITA!

For the drawing you might look at doing an XML Out of the linework that might get you in a better position. And then make a DWS (Drawing Standards File that would translate from uSta levels to C3D Layers (I do this with FDOT work, it works quite well) using the Layer Translator (Manage Tab on the Ribbon) Once you have this DWS file, it's just a click of a button and the data is mapped to the layers, linetype etc.... This is just if you need to go through this routine again 😉

Also, you might type Seed File in the Help on C3D, there quite a bit of help on doing DGN/DWG conversion there as well.

HTH

[rwaldroupJNAKH]

Interesting about the OC. We may have to try that out sometime. Any insight on coding curves with a non-tangent side? (such as a semicircle curb situation)

I will definitely take a look at exporting an xml of the line work and see if that makes things easier. Hopefully we won't have to go through this routine again.....but never say never! Thanks for your reply!