![]() ![]() I never did figure out where the software was pulling That made it impossible toĬreate an arrangement of section views that would allow the use of map booksįor sheet creation. In my case the problem was not on all of the section views, but itĭid show up in several consecutive sections at several different parts of Consequently, those section views were insanely 'tall' and hadīetween 20 and several hundred feet of empty grid between the visible The corridor, some of the section views had a datum surface minimumĮlevation that was way below the lowest elevation that showed up in the When multiple section views were created drawing both surfaces and ![]() The sample lines sampled:Įxisting Ground, a datum surface created from a corridor, and the corridor Wrote in message posted a similar question some months ago. What we did after I found out he had twoĭifferent corridors was to make a different section group for both of hisĬorridors and after we redid our sections everything worked smoothly. Was trying to have one section group cut all the way down both of them. The guy I was helping had two corridors in his drawing and I did figure out why it was shooting all myĭatums to Zero. I believe that I'll really miss sheet manager some day. As for sheet creation, I exported the project to LDDT and used sheet manager for plans production. I'm now using 2007, but haven't experimented to see if the problem persists. That provided section views that were consistent and didn't have all that empty grid space below the sections. My solution was to create new sample lines that did not sample the datum surface. I never did figure out where the software was pulling those absurd datum elevations from and couldn't find a way to control it. That made it impossible to create an arrangement of section views that would allow the use of map books for sheet creation. In my case the problem was not on all of the section views, but it did show up in several consecutive sections at several different parts of the corridor. Consequently, those section views were insanely 'tall' and had between 20 and several hundred feet of empty grid between the visible sections. When multiple section views were created drawing both surfaces and the corridor, some of the section views had a datum surface minimum elevation that was way below the lowest elevation that showed up in the section view. The sample lines sampled: Existing Ground, a datum surface created from a corridor, and the corridor itself. I posted a similar question some months ago. I have cut my sections and have drawn them on screen only to haveĮvery single one of them with a datum of 0. "Thomas Glidewell" wrote in noticed a while back that someone posted a question about the datum of You possibly may have a Volume Surface as "wfb" wrote in what memory I may have left. Select the resample button, and select OK. Surface) or any other data element that may be at zero elevation. That were sampled by the sample line group, uncheck the one for the volume At the top of this window should be a list of the Civil 3D elements ![]() The sites collection in prospector - need to dig down into the alignment toĮdit the properties of the sample line group, and the select the Sections To check to see if this is the problem, select the sample line group from
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |