I have a client that insists that all his deliverables be in the form of an ASCII list file. This was not a problem when working with SS2 GeoPak, but we have moved forward to ss4 OpenRoads and are hitting a road block.
The client wants to see a file that looks like:
100,5000.00,6000.00,100.00,ST_EPB1;COMMENT
101,5000.00,6010.00,101.00,EPB1;COMMENT
Et cetera.
I can use the 'export to csv' routine available by right-clicking on the top left box in the 'Survey Details' dialog box to get all the information I'm looking for except the line number. The output looks like:
100,5000.00,6000.00,100.00,ST_EPB;COMMENT
101,5000.00,6010.00,101.00,EPB;COMMENT
The problem is that our Leica data collectors and OpenRoads now store lines as a list of points, where previously lines were assembled from ASCII points with special identifying characters. We would load an ASCII file with the code EPB and the attributes LINKING CODE _ST, NUMBER 1, NOTE COMMENT, which we used an excel spreadsheet to mash together into ST_EPB1;COMMENT. GeoPak would then store the point with the feature EPB1 and the description COMMENT, which made getting it back out in the desired format relatively simple.
Now we dump the Leica job file into OpenRoads Survey without the ASCII interface. This then produces points 100 and 101 with the feature EPB, the linework operator Start and _blank_ respectively, and the attribute NOTE=COMMENT. It also produces line EPB001 which is defined as including points 100 and 101, because that's how it was created in the data collector.
What I need is a process where I can have the line write its identifying number (or even its name) to an information field in any point in its point list. That way, when I go to export a csv from the Survey Details box, it will spit out EPB001 rather than just EPB. Anybody know of a way to do this?
would editing the csv in excel and adding what you need work?
https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/169759/write-line-numbers-to-points-for-ascii-export
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Sure it would work. The problem is the man-hours involved that solution. I deal with files with a minimum of 50 lines each, some of which are two points, others have thirty or more. I’d have to open or export each line, then manually enter the line number descriptor to the code in the point list file. It’s time-consuming, monotonous, and prone to error as the operator gets fatigued and starts to make mistakes.
I’d prefer a script or macro or something that would do the same thing before it hits the csv stage.
I understand. I filed an enhancement request Enhancement 960138: