Quite often you want to use the same generic subassembly twice but you need the ability to distinguish between them with codes. It would be excellent if we could prefix or suffix all the codes used in the default subassemblies as shown below.
This enables a lot of flexibility for the styling of codesets and creating separated surfaces. It can resolve issues with codes overlapping each other.
Things like different options, left right, center etc. can all be established within the one corridor. Making it easier to link things together and create surfaces etc…
It would be incredibly useful to allow certain aspects of Civil 3D styles to change dependent on the scale they are visible at. (other than just the size, which happens already of course!)
This could be done at style level or object level or even better both? one overrides the other.
Fox example
Contour Intervals could change depending on the scale
Alignment Intervals could change dependant on scale.
Style could also allow visibility of certain objects only at certain scales.
Components could display different information at different scales (labels could become more or less complex)
Dragged states could have different locations for different scales (similar to annotative scaling already for regular autocad objects)
I particularly like the way arcgis handles this with scale ranges that make sense, like room, county, building,continent etc..
I would like to see this command available for every civil 3d object. In both the toolspace and on right click menu’s/context sensitive ribbon. This is similar to the way styles can be replaced with another style in the settings tab. But instead, the C3D object would be replaced with the geometry/data of another Civil 3D objects. But more importantly, all the links would be maintained.
Example – Corridor Modelling (replacing objects instead of retargeting)
This would be particularly useful with corridor modelling. As it would mean targets would not need to be respecified, just the geometry of the target object is replaced and then the corridor can be rebuilt.
So for example below, I have a corridor that targets a feature line, this feature line is used as a conditional horizontal target as well as a target for its horizontal position and vertical elevation.
There are maybe 15 regions that use this one feature line and each region has 4 targets each. Some of the regions use a different subassembly. So using the “Match Parameters” command is not going to work.
Using the “replace object with” would solve this in two clicks. Instead of many clicks in the target parameters box.
Other Uses
Replacing Design Profile Geometry
Replacing Alignment Geometry
Replace Surface geometry with another surface. (rather than promoting and pasting in)
Replacing Point Data or Point Groups with another point group.
The list really goes on..
The Current Style Replace with.
Not available on all styles. But useful none the less.
I think it’s safe to say that the intersection object (that is not really an object) and the wizard that creates them are from a different age, they are dinosaurs that should have died a long time ago.
Check out 12D’s “Create Roads” functionality. It creates “multiple intersections” at once, as well as creating the cul-de-sacs automatically. Why can’t civil 3d leave the dark ages and develop some functionality like this?
When using Plan Production Tools. Pipe network styles and labels in plan view do not get carried through to the new drawing. It simply defaults back to the default styles in command settings.
Can we please add a way to use the styles and profile labels specified in the drawing that we create the sheets from. Particularly on larger projects, its really annoying to have to open all the sheets a respecify all the labels we already specified.
Projection sets would allow you to create a dynamic editable “query” to group desired objects that you want to use for projection. This query also defines how these objects should be displayed in profile/section views/exaggerated views?.
I’ll let the image below explain itself. But generally a few key points.
ALL Objects are Available for Projection!!!
ALL Objects can be assigned labels as well as projections styles
BOTH Profile Views/Sections views have similar projection options (Crossing/Superimposed/Bounding Box limit etc, explained further below)
Queries can be assigned to objects so that they can be assigned default styles based on the point group or there layer or whatever.
The same projection set can be used for multiple profile views etc.. Its dynamic..When it updates it updates the profile view/section nview etc.
Projection Options/Types
It’s really important that we have options to filter how objects are selected/cut/displayed in section/profile views.
I’m thinking there could be two/three types.
These would be saved as styles and can be changed/updated.
Crossing Only Only objects that intersect the line are displayed
Bounded Parameters Only objects within specified parameters can be seen. I.E 25m either side of alignment. Similar to how the sample line projections work now. This should be enabled for profiles views as well of course!
Bounded Objec Only objects within a selected polygon are sampled. This would allow flexibility for users to limit things by stage boundaries etc..
