| Just a brief alert for those of you using AutoCAD | | | | with survey figures being created. |
| Civil 3D 2009 survey databases. I've encountered | | | | The folks at Autodesk are currently working on |
| a problem where if I try to import a survey field | | | | this problem with me and I expect a resolution to |
| book into a new survey network that uses | | | | this issue shortly. However, in the meantime I |
| existing setup and backsight points from another | | | | recommend the following: |
| survey network, things go wrong. Please note | | | | |
| that I am not using Vault to manage my survey | | | | 1. Make sure your survey field books are edited, |
| databases, therefore I don't know if this is also an | | | | appropriately corrected and ready to run. You can |
| issue for those of you using Vault. The program | | | | check this by setting up a "scratch" or temporary |
| won't recognize the existing points you are trying | | | | survey database (and drawing file) to test the |
| to occupy, apparently because they are in | | | | input of your field book. Common issues are: |
| another survey network (but within the same | | | | incorrect setup/backsight points, duplicate point |
| survey database of course), and will result in the | | | | numbers, incorrect descriptions, incorrect rod |
| following error message: | | | | heights and corrections to survey figure |
| The reason I am alerting you to this, other than | | | | commands and descriptions. Basically, look where |
| it's not working correctly, is that I have had the | | | | there is human input at the data collector |
| field book input into the wrong survey network | | | | prompts. |
| (the one where the existing occupied point | | | | 2. Before you add anything to your project |
| number resided). This happened when I hit | | | | survey database, make complete copies of all the |
| "cancel". Having your data end up in the wrong | | | | project files, particularly the survey database |
| survey network is one thing, but it's very difficult | | | | itself, so that if something goes wrong you can |
| to undo this process if this new data is intermixed | | | | easily go back in time to where you started. |
| with your older survey data (particularly if your | | | | I will give you an update when I have more |
| field data has issues and was not completely | | | | information and please leave a comment if you |
| corrected prior to being input). Also note that you | | | | have experienced these problems or if you have |
| may get unexpected results even if you click yes | | | | anything to offer for a solution. |
| or no. And this also seems to create problems | | | | |