All posts by Kapanther

Custom Subassemblies

Custom Subassemblies Lesson 1 – Do I even need a custom subassembly?

You might be already well aware you need a custom subassembly (CS) because things are getting hectic, so you can skip this article

It is always a good idea to stop and determine “if I even need to” though. So, if you’re not sure, here are some general rules of thumb to follow to determine if you need a CS.

You should create a CS if:-

1. Your Corridor Model requires you to transition daylight slopes smoothly over distance. I.E 1:2 up to 1:6 and back to 1:2 over specified distances

2. Your corridor model has a complicated target list, say 5 or more targets you need to specify. Particularly elevation/grade targets. These can take longer to manage as they are usually all different targets, unlike surfaces which are typically all just EG and can be set all at once.

This list can grow long very quickly! Particularly when you start changing the targets between regions etc.

3. Managing your codes (point/link/shape) is becoming difficult to manage

4. You want to develop multiple stages to calculate volumes over time. Similar to above.

5. You wish to calculate internal materials that differ from the generic/road based subassemblies provided by the software. (plus making surfaces is difficult due to differing boundary conditions)

These are a few good signs that creating a CS will benefit you. However as an umbrella rule,

if it is taking too much time….. take some time… to create a CS.

Loading

Bugs, Points

Create Cogo User-Defined cogo point properties on the fly.

I am aware that if I define my user-defined properties in settings first. I can then import cogo points with user defined properties.

However what is the point of the “user-defined” field then in the Point File Format – Select Column Name box.

It seems to allow a user defined column name and everything.. But it just doesn’t work!

Or is it Just broken?

Loading

Future Posts

Labelling your sections views effectively

You can probably get what you want by using the surface selection “section 1 and 2”/configuring your styles and removing weeding.

First to help you understand the two section selections

image001

image004

Once you have this worked out you will want to make sure you have a style that is displaying elevations at “grade breaks and using the “section 2 elevations”

image002

image003

Then you should be laughing!

Loading

Bugs, Map 3D Functions

COGO Point Renumbering does not work unless selected individually from highest to lowest

Not sure if this is fixed in 2015.

if I select cogo points with points number 45,46,47 in that order.. It will prompt me to either (overwrite or <next>)

Overwriting will renumber the points in the incorrect order and sometimes it will delete points that overlap.

Using Next Skips to the next available number. Which is not what I want..

So the only way to do it is to select in the reverse order and it works.. however this is very time consuming if I have 200 points!!!!!! Can it not just start the renumbering from the highest number?

Loading