In 2012, the survey cogo points no longer seem to update after browsing to the observation data, making an edit and then saving. It worked fine in 2010. Anyone else running into this?
Solved! Go to Solution.
Here is what I'm doing:
1.Select a cogo point created from a survey database import event, specifically an .FBK file with total station data.
2.Right click and select "Browse to Observation Data"
3.In the panorama vista change a "Target Height" for one or more points.
4.Save the changes and dismiss the panorama vista.
Normally this would update the elevation of the point in my drawing, but this is not happening for me in 2012. Changes to a point description update like normal, though.
No, normally I never do that. Once you unlock a point it disconnects it from the Survey Database and edits to the database will not get pushed into the drawing. I just tested it and the point became a simple cogo point and right-cllicking no longer gives the option to browse to survey data. See attached.
Scale factor is not being pushed to the drawing points either. In the second attached pick I've changed the scale factor for all points and the targed height for point 9146. You can see the survey preview lines in green staking out the calculated positions for the points landing short of the initial points imported with a scale factor of one.
No, they do not. If I check the points listed in the survey database they don't show any different change in elevation, despite target height edits. It's as if there is a disconnect between the survey observations and the point coordinates in the survey database. The only way I can see to update it is to delete the import event, edit the FBK and make a new import event. I wanted to avoid doing that, since I've already made edits to descriptions, but I'll just have to copy those into the FBK as well.
Are you saving to the survey database from the observation editor?
I tested this using the FBK shipped with the tutorial files and change the height to something rediculous like 50.00'. After saving the change back to the database, then resinserting the points, the elevation was updated.
Tested on a coworkers machine with 2012 and got the same result: point elevation is not updating.