- last edited on by
Gordana Radonic
meaning:
1. need to be able to change font style.
2. as the pline changes slope, the text changes along with the pline.
3. can be increased and decreased in size.
4. pens can also be adjusted to thickness.
Thanks Randy,
I like that it figures the surface area correctly too. It seems like I used to have a label that would report the true length of the hips and valleys too.
I need a label for the true length of the hips, valleys, ridge, and eave so that it can be used to help understand what the roof schedule reports. Be careful of things like this that seem inconsistent in the way they are reported.
For example ridge will show in the schedule as 1/2 the true length for the sake of a correct total of ridge. But hips will show the full true length of the hips and still show the correct total length of hip.
I like that it figures the surface area correctly too. It seems like I used to have a label that would report the true length of the hips and valleys too.
I need a label for the true length of the hips, valleys, ridge, and eave so that it can be used to help understand what the roof schedule reports. Be careful of things like this that seem inconsistent in the way they are reported.
For example ridge will show in the schedule as 1/2 the true length for the sake of a correct total of ridge. But hips will show the full true length of the hips and still show the correct total length of hip.
You might need to change the tiles in the schedule to reflect the data - more like the attached image. There is nothing wrong with the total Sums but to be consistent the schedule should be able to report the hips and the ridge in the same way I think. The Schedule are not just for reporting useful quantities, its primary purpose for many projects is as a way to check and make sure things that should be the same, are the same. It also makes a convenient way track down and edit things that are not modeled exactly right.
Barry wrote:The roof is a rectangular hip roof. The roof has (4) hips and (1) ridge. The schedule shows the true length of all (4) hips correctly, and the correct total length of hip.
Steve,
I think you will find your hip lengths are halved as well just like the ridge.
It is just that you have 2 hips on each roof plane so it looks as if it is showing the full length of one hip.
Barry.
However, the schedule can only show 1/2 the length of the ridge but still shows the total length of ridge correctly. Just something to be careful of.
Now delete three of the 4 roof surfaces so there is only one roof surface with two hip edges, one ridge, and one eave and look at the schedule.
The ridge is still reported as 1/2 the length of the ridge, and the total length of ridge ( sum) shows only 1/2 of what it should be. However, the hip lengths are still correct and and the sum of hip lengths is correct.
It is important to understand what the schedule is showing. Lengths of hip and ridge, or the Length of the hip or ridge. Hip and Ridge Lengths of The roof or hip and ridge lengths of the roof surfaces. All subtle differences that need to be understood by the person using the schedule. This is why it might take some renaming of the schedule header/category names in order to explain to the schedule user exactly what the data reported means.
There are many situations like this using the Interactive Schedules that can generate very risky to show data because it may not be the data that is expected or useful to the person using the schedule. Becareful.
Yes our post did cross.
I agree it is a bit confusing and the scheduler needs to be careful they are getting the correct figures.
I think in most instances it should be fine.
But if you want to see something a little scary look at the attached image.
A simple multi-plane roof with a hole in it - the hole edges at "undefined" but they get counted as eaves.
Same roof converted to single roof planes - same results but the edges are now classified as "eaves".
Same basic hip roof with no hole converted to single roof planes. Then edited to add nodes and move ridge to create the same hole.
The edges remain as "ridge".
So which is correct?
Should the "undefined" edges schedule at all?
Should the hole be automatically classified as an eave when split?
Should it be a "ridge" or is "side wall", "end wall" or "peak" better as these can be scheduled as well.
So for anything but the simplest of roofs the user will have to start looking very carefully at what is happening.
Especially when using single roof planes and editing them.
Barry.
I agree it is a bit confusing and the scheduler needs to be careful they are getting the correct figures.
I think in most instances it should be fine.
But if you want to see something a little scary look at the attached image.
A simple multi-plane roof with a hole in it - the hole edges at "undefined" but they get counted as eaves.
Same roof converted to single roof planes - same results but the edges are now classified as "eaves".
Same basic hip roof with no hole converted to single roof planes. Then edited to add nodes and move ridge to create the same hole.
The edges remain as "ridge".
So which is correct?
Should the "undefined" edges schedule at all?
Should the hole be automatically classified as an eave when split?
Should it be a "ridge" or is "side wall", "end wall" or "peak" better as these can be scheduled as well.
So for anything but the simplest of roofs the user will have to start looking very carefully at what is happening.
Especially when using single roof planes and editing them.
Barry.
Still looking?
