12d Model

I have created bug issue TD-26319.

Correction ... I can reproduce (sort of). No need to send data at this stage. I have a few service uprights missing these values in my data, but it seems to get further than the first link on each line for me.

Yes, please send data to support. I can't reproduce that with my data.

Happy to report that the above mentioned enhancement to the Water Long Section Plot PPF Editor, has passed testing and will be available with the release of 15C1u.

I can't promise either, but I will fight the good fight.

t became a quick replacement for s, which was pulled due to a survey issue. u is the new t.

There are technical issues with bumping up the number of allowable corridor models and cuts models. The plotting code is not ideal, either. It has a very long history.

The whole idea of the map file is entirely because nobody follows the rules and every job is mind numbingly different. The map file ...

Ideally, a different map file can be created for each job, to copy the data into consistently named corridor models for plotting (as few as possible). That way, all your PPFs can all be setup the same way on each job and they will always just work. The time saving is potentially immense.

(This is ...

Keep the original data however you need it. But make temporary copies of it, purely for corridor plotting purposes (renaming/recolouring/restyling to your heart's content, controlled via a map file, say). You can then delete the copies after the plot. The plotting process can be wrapped up in a ...

It didn't make 15C1s. I will push for it to be implemented for 15C1t.

CAD=>Fill=>Remove (for one at a time)

or

Utilities=>Super Strings=>Fills (with Action set to "clear")

Yes. It requires the Drainage module. But please register and login to the forum and post your question in the Drainage and Rivers section.

This 12d Practice Version section is intended only for trial versions of 12d Model.

I stopped being lazy and tested it. It works, viz:

The name lock is based on the presence of the Integer node attribute "name lock" with a non-zero value (zero means unlocked). I've not tried, but you may be able to apply this to all nodes with the Attribute Manipulator.

The wish was submitted to the programmers last month.