Hello,
I have a rather odd situation. I have input a small table of survey points (we don't have access to a data collector, so it had to be manual).
I have a properly located and back-sited setup, with all of the points located in 3 dimensions.
The Northing/Easting/Elevation data is calculated and displayed for all of the points in the "observations" table accurately.
Every point has the same display/labeling properties/settings, but only 2 points properly display the elevation as calculated.
The problem seems to be that the points aren't accurately retrieving the Elevation from the table.
For some reason, in the “Properties” dialogue for the points that display properly, the “Point Elevation” field actually contains a number; whereas the points that don’t, the same field reads “*PROPERTY NOT SET*”.
This makes no sense, because in the table that defines the points, the elevation is accurate for all of the points, and I can’t find a difference in the table- or in the point properties- between the correctly displayed points, and the ones that are missing the elevation label.
Any suggestions?
Thank you for your help!
~C
Solved! Go to Solution.
Solved by CovenStine. Go to Solution.
Can you post a sample of your point file? Also a drawing with a couple of points that display correctly and a couple that don't, if possible.
Allen Jessup
Allen Jessup
Engineering Specialist / CAD Manager
Attached is an image with the points as displayed, and the properties pane for a point that inherited the values properly (yellow), and one that didn't (red).
From looking at the point file before I uploaded it, things make even less sense, because the -99999 values for elevation are definitely not in the observations table, as shown.
Any suggestions would be most helpful, thanks!
This is confusing me too. We've been using a data collector for over 15 years. So I haven't entered anything manually for a long time. The point file was one you exported based on the Survey points?
Hopefully someone who is more familiar with the Survey Database will chime in.
Allen
Allen Jessup
Engineering Specialist / CAD Manager
Check all your point groups for overrides to the Elevation property.
Normally, I'd think there was something like a space in the elevation field of each point, however, this is how the points behave as soon as they're imported to the drawing- but yes, I checked, and all the failed points I checked have the same <not defined> message in the Elevation field.
I can override the "not defined" field with a value, but I'm sure I'd transpose something, and this is one of those irksome errors that are frustrating in that they have no obvious root- at least to me.
Any suggestions you have would be most helpful.
Sometimes I impress myself with my own stupidity.
The database wasn't updating properly, I don't know exactly why, or how I didn't notice that it wasn't updating, but that's all it was.
Once the automatic update/refresh was working right, this issue just disappeared.
Thanks for your help & patience!
~C
Thanks for posting the solution. We've all been there at one time or another. Since this is the solution to your problem. You can mark your post as the solution to help others searching for similar problems.
Allen Jessup
Allen Jessup
Engineering Specialist / CAD Manager
HI Jeff,
I'd like to quirie you answer here that civil3d ignore -99999. I tested this and it still included them in a surface (tin).
We have been trying to work out a way to null points. we have been using point groups for this. Is there another way e.g. use the "propery not set", but its not an editable option only in the properties box.
Thanks for any feedback on this.
Cheers
Allan
This solved it for me. My point elevations were shown as 0 in the annotation table. I had the points override elevation box ticked.