I have a 3 mile long route and site topo that has sadly stuck with me over the last few months. The actual client prefers MicroStation and the drawings were prepared as such. The main drawing contains surface info (contours) that were generated with Eagle Point. (I may be the last human on Earth that still has a functioning MS/EP system.)
The client's engineering consultant is of the C3D/ AutoCAD persuasion. This has not been a problem over the course of the project. I have delivered several drawing files to them that were native MS files "saved as" AutoCAD.
A month or so ago they requested a topo of an additional 40 acres adjacent to the site along with a half mile of section line road. This info was incorporated into the file with EP/MS with a separate surface being generated for the new data. I saved it as an AutoCAD file and sent it on its way.
The consultant contacted me Monday and the AutoCAD file graphically shows the "older" contours (polylines) in the drawing with their correct elevation value. When you tag an end-point it has a positive elevation. But when you query the entire polyline it indicates that same elevation, only a negative value. This happened on the older "first" surface in the file, not the newer surface data.
Just to see WTF I "dropped complexity" (exploded) the polylines to see what would happen. It slammed all the line data down to a negative value, but when queried it showed a positive value. The only way to make the contours get "up" to the proper elevation was to change them to the negative elevation and they would then be at the positive elevation in the drawing file. Further investigation indicated this only happened on older contours I had "joined" with the more recently generated contours.
Long story short I completely redid the entire job as one surface. Has anybody else ever seen such a thing? This was one for the books.
Is it possible somebody inverted the original model?
Paul in PA
Paul in PA, post: 399244, member: 236 wrote: Is it possible somebody inverted the original model?
Paul in PA
Nope. All that resides on the drive right here on my desk. Several people have told me an entity cannot be shown on the screen at an elevation with its dB info at a different location. I've begged to differ with them in this case. It's resolved, but in the back of my mind I would really like to know what happened. Most of the "higher intelligence" I have talked with seem to think Eagle Point is the culprit.