When I do FTF I process the raw crd file in Carlson Survey and then export the points into a csv file and save the drawing without points in it.
Then I open the linework drawing in C3D and import the exported points and they match the linework exactly.
If I then export the points into a csv file from C3D and then reimport the points into C3D they miss the linework by up to 0.004'. This is not much of a problem but I can't figure why is it happening and was wondering if I need to change some settings I have in C3D. I think it may be a rounding problem the northings are exporting to two decimal places the eastings to three and the elevation to four.
What kind of program lets you export the Northing and Easting to a different number of decimal places?
NM...
I am exporting them from Carlson Survey from a processed CRD file and by using the point export function in C3D and that is just how many places show up.
It's just very weird that when I export then from Carlson and then into C3D they are in exactly the right place but when I export from C3D and then back into C3D they miss the linework by 0.004' or so.
I export from Carlson at the max. number of decimal places to avoid issues like this. Have you tried the Convert .CRD to LDD .MDB under the points menu? Sounds like it should do what you want with a little less contortion. JRL
Whatever coordinate decimal places shown on the screen Carlson keeps that point linked to the crd file and all it's decimal places. The non Carlson program is somehow truncating the point coordinates and/or removing the link to the data file.
BTW, why are you shipping them out and bringing them back anyway?
Personally if I could not find the source in the transfer, I would just tell Carlson to "Update Drawing (the screen points) From (the old) CRD File".
Paul in PA
If you are doing the Export Points, then that uses the precision set in the Point File Format you are using. Open the Point File Format and click on the Northing and Easting columns, and you can set the precision.
Which template are you using? I seem to remember seeing that problem at one point, but we use our own template, which does not have this problem. I just tried creating a drawing from the standard NCS template that ships with C3D 2011, and all the Point File Formats I looked at had both Northing and Easting set to 4 decimal places.
The main reason I ship them out is because we send topos to several different engineering companies and they all have different versions of acad. It works a lot better for us to send out a cad file without points and let them import the csv file into whatever version of cad they are using.
The reason I process in Carlson Standalone Cad is that I like to have my linework as 2D polylines with a 0 elevation and not 3d figures as C3D wants to do.
Sinc
Thanks as usual you hit the nail on the head, I increased the point format to 6 places and it worked perfect.
We also have our own templates so I will also make the change there.
thanks
tds
Just use tds instead of carlson
tds
No problem with Carlson, just operator error. This stuff takes awhile to get down
tds
We had a taste test and the guys picked Carlson 2 to 1 over TDS.
Glad I got this resolved. A lot of time has been spend looking for the 0.04' but try looking for 0.004'.
To Whom it May Concern
I checked and the reason the linework and points didn’t match by up to .004’ is that we had our p,n,e,z,d,.csv point format export set to 2 decimal places and it was rounding from the thousands creating a rounding error equal to the square root of the sum of the squares of the delta between the actual thousands and the rounded hundreds of a foot.
We have corrected this by increasing our output coordinates to 4 decimal places and in the future they should match the linework to the nearest four ten thousands of a foot.