FBK and Civil3D database corruption
Hi all, We are having a problem and I can’t seem to resolve it. Civil3D database corruption occurs after to many FBK imports and I am not finding anything out there to resolve it. to understand what I am about to share, I will explain our procedure.
Our procedure:
- Import JOB files from Trimble TCS to PC
- Convert JOB files to FBK with Trimble provided “ASCII File Generator” program, found here. I also am using Trimble recommended stylesheet converter found here.
- Make any known corrections to FBK coding and such.
- Import FBK to Civil3D database
- look for errors in drawing
- edit any visible errors in FBK and re-import (or delete and re-import)
- this process goes on until the FBK comes in with no errors
The situation:
ERRORS:
- PROCESS TOPO:
- Day one comes in perfect. All codes correct
- Bring in day two and a big giant “S” Survey Figure connects, as one line, all over the drawing, including points from day one.
- Check codes in day two FBK. All good
- Delete all FBK files from DWG
- Bring in day two alone and everything is perfect
- Bring in day one and a totally different Survey Figure connects all over the place
- Both files codes are perfect
- Combine the two into a single FBK file
- Process
- Try a second time with new database and drawing
- I decided to get screenshots of everything to post here, not wanting to mess up our actual project:
- I decided to create a new drawing and database.
- I impost my CSV of adjusted control
- I bring in the day one FBK
- I bring in the day two FBK
- Everything works perfect
- CONCLUSION:
- When you process FBK files over and over eliminating the errors in coding, rod heights, etc, it corrupts the database with each process. There must be some way around this.
- Choice #1: combine all FBK files and process at once
- This option can screw your database on a large job from way back as it will inevitably jack up your database should you ever add field data at a later date.
- Choice #2: Create a new database and drawing for every import of a FBK file, export a coordinate file and then import to main database. (Coordinate file seem to do less damage to the database)
- Choice #3: Fall prey to the forced proprietary regime of proprietary systems, of which I am not a proponent of (I am more for open source and decentralized resources), and buy Trimble Business Center.
- Choice #4: Make all edits in the data collector, then process and check for errors, which would start the cycle all over again.
- I decided to get screenshots of everything to post here, not wanting to mess up our actual project:
Any one experience these problems or have a solution?
SIDE NOTE: We have tried using TRIMBLE LINK from within Civil3D and found it to mess up the prism constants erroneously.
Log in to reply.