I am using Civil3D 2011, and we have an issue importing survey data via the Autodesk Field Book file, when it records atmospheric conditions.
The process for importing the data is as follows:
Result:
Civil3D changes distances as though the option for “Atmospheric conditions” was set to “Yes”
Note:
Can be worked aroudn by editing the contents of the .FBK file and removing atmospheric data, but this is NOT elegant at all.
Any suggestions?
Possibly that's not the reason the distances are changing...
Be sure both Survey Database Settings and Drawing Settings are set to US Survey Foot or both to International Foot. Having this setting different in survey than in the drawing file will cause data to change. I don't know that this is your problem, but I've seen it before.
I am working in Australia, and as such working in meters. The units setting in the AutoCAD drawing is set to meters, and the distances in the Survey database are also set to meters.
The software seems still to adjust for Atmospheric conditions, even when in the Survey database I set this option to "No"
Yeah, if you're working in meters, that's definitely not the cause of your problem.
I can't think of what else it might be other than an error in the program. If you are on subscription, please make a bug report through tech support. Autodesk is more likely to take note if you make an official case. A post here doesn't necessarily register with those who matter.
As far as how to handle your immediate situation, can you tell your Trimble software not to transfer the atmospheric data to the FBK in the first place? I'm grasping for straws here.
Best regards,
Tim
We in Support do monitor the forums, and after researching this issue it seems your Reseller has logged a case for your company on your behalf and we currently have a specialist looking into it for you. If a resolution is determined we will be sure to post it here as well.
Have a great weekend!
Thanks Tim for your contribution here. Yes I have come to the conclusion that the software is not performign as it should in this case. A case has been logged, and I guess I'll work through this with our reselelr and Autodesk now.
Regards, Jim