Until recently I've always avoided using alpha-numeric point names. Due to the complexity of the site I'm working on I finally gave in and started using alpha prefixes on my point numbers to organize control, design, as-built, etc.
I've run into a snag with Carlson Survey 2013 on AutoCAD not recognizing special codes like JPN when they're used in conjunction with alpha point names. For example my code might be "CONC7 JPNAB274" if I were using numeric point names the code would be "CONC7 JPN274". SurvCE handles this and draws the line correctly, but F2F in Carlson is ignoring the JPN code when used with point names with alpha prefixes.
It won't be the end of the world if I have go in and manually connect the lines but if any of you know of a solution or workaround, I'd appreciate the help.
Try adding a space between the JPN and the alpha point name. The extra letters confuse the software so it is not reading JPN as the join command.
"EA+7 JPN AB2374"
I tried adding a space before I originally posted but F2F still didn't know what to do with it. I'll have to take a slow methodical pass through the settings to see what I'm overlooking.
This looks to be a bug. I've been told a fix has been made for the next build of Carlson 2014 (and Carlson 2015, too).
Thank you Ladd.
I ran into a similar issue in SurvCE 4 today in the Manual Traverse screen. I had a series of points named D1, D2, D3, etc. and I was trying to calculate the bearing/azimuth between two by keying in "D1,D2" in the input box and getting no where. I figured out that pressing the d key in any of the input fields toggles the data type to the right of that input box. Obviously D and likely several other letters are used as toggles. Do you know if there is an alternate way to enter point names that begin with these characters so that SurvCE knows that you're entering point names rather than data type toggles? Or is there another screen where I can calc the bearing or distance and then paste the result into the input box?
A possible fix for such a complex job might be to place your alpha designator as the first item in your descriptor. (OR use the multi-code option that will allow separation of features and still do your field to finish things.) That way you would have the "clean" numbers but still be able to split out the data via the descriptor. You could separate all the design points from the as-built points, etc. by using point groups built on the descriptors.
Just my 2 shekels.
Hello,
I was just wondering if a fix had ever been identified for this issue. I am working on Carlson Survey 2016 OEM & seem to have run across the same problem.
Thanks
It's not an elegant solution, but you could always export your linework as a dxf from SurvCE then import it as a block in Carlson without specifying an insertion point so it will align with the points.
Stephen Ward, post: 268989, member: 1206 wrote: Until recently I've always avoided using alpha-numeric point names. Due to the complexity of the site I'm working on I finally gave in and started using alpha prefixes on my point numbers to organize control, design, as-built, etc.
I've run into a snag with Carlson Survey 2013 on AutoCAD not recognizing special codes like JPN when they're used in conjunction with alpha point names. For example my code might be "CONC7 JPNAB274" if I were using numeric point names the code would be "CONC7 JPN274". SurvCE handles this and draws the line correctly, but F2F in Carlson is ignoring the JPN code when used with point names with alpha prefixes.
It won't be the end of the world if I have go in and manually connect the lines but if any of you know of a solution or workaround, I'd appreciate the help.
A different approach here.
I never used the JPN code because you have to remember/lookup the pointnr. I Always started an additional line in this point. (for ex. CONC7 CONC11 ST).
So we just keep track of open line codes, not of pointnrs.
Chr.
