JiAngelo

Would have taken less time if you'd posted your plan. I agree Chief could provide a simpler way to create a CSV table of elevation points. I used a Plot Plan Note, added custom fields to match yours, and added some custom macros that /12 and round(4) decimal places for macro values elevationf, x_position & y_position. The Plan Notes Schedule allows you to specify 4 trailing zeros. Everything is now shown in feet, so I didn't bother to call that out. Each Note has an arrow to read an elevation point's data. Once you have one created and showing the correct values, you can copy & paste/move the note+arrow to the next point and it will auto populate the schedule if you uncheck "group similar objects". They will incrementally number themselves with each copy/paste, then on the schedule you can drag them into the order you want and they will renumber again automatically. (I actually added an extra field to know which was #1, #2, etc. which made it easier to order the POINTNO field. After I exported to CSV, I added some calculations to the right to get perimeter distances between the points 1-4 and doublecheck everything.. If your macro is 10 years old, it probably needs adjusted like @Alaskan_Son indicated above.

When you select the table there is an "export text" icon (circled green below) that is also on the right-click menu. selecting the icon opens up options for TXT, CSV and XML exports. For CSV I normally check "open in default spreadsheet editor" and it automatically opens in XLS after export. You can then resave in XLS format or keep it as CSV. When I save it in XLS format, I can add columns to the right that calculate on the data in the imported columns. On subsequent exports to a new CSV filename, I can cut and paste the new imported data over the old imported columns in my XLS format and the calculations will update themselves based on the new data provided.

Building upon what @Larry_Sweeney said, you can't mull an entire array of windows (x rows, y columns). Here that equals [3,2] You must mull either the same row or same column windows first into one unit, then you can mull the units all together. Mulling only each column of windows will eliminate the trim between AND Chief will still locate the center of each window column. Chief will only locate the center of the middle window once rows are mulled.

Are you sure you didn't check "Ignore Top (Second) Floor? Uncheck that if you did.

An attic room isn't a 3rd story. It is inside the required roof pitches and your use is non-habitable, for mechanical equipment only. City will allow this use. Exactly what are your overhangs required to be? Spanning the entire 1186cm likely will require a 60cm floor truss system. Send out the plans and find out.

To keep a 7/12 pitch (30 degrees) And stay under 950cm, per your authority Change first floor to 285cm, net 265cm after your drop ceiling for MEPs.. Change second floor to 265cm and move MEP's to attic area. This should have you at 947.6cm entrance to ridge. You should have enough room to create an insulated attic room 430cm wide by 250cm tall in a hipped roof. The attic room can run the full length of a gable roof w/ windows on either end. The attc room could be only 125cm tall if you like, like below (from a building I'd drawn for another client) Or, at 250cm's it looks like this on another project we are constructing now. Personally I would choose the above to eliminate the need for any flat roof areas. The attic room only needs to be large enough for equipment and access - this would save money too.

I can't speak to shipping with a the 2% sloped top chord, I'll ask our truss guys about this next week. But we are currently doing a job now where we needed to stay under 35' and the truss company was building them with a flat top for piggyback trusses to be installed above. They did this so that the trusses wouldn't be too tall, which requires extra expense to ship across our state. We ended up changing the pitch from 10/12 to 9/12 and this allowed our piggybacks & shingles to fit under the 35' maximum. But, we were prepared to install plywood flat over the top of the trusses, then add a tapered iso to give us the required 1/4" per foot minimum slope. That equals 1.18 degrees, so 2 degrees is definitely above the minimum. here's an example of the tapered iso. Here's a flat roof transition to sloped roof detail. Ignore the gravel, a flat rubber roof doesn't need it. The 2 degree slope will have water running off onto the shingles all the way around. The good thing is this design has you 35.9cm under the authority's 950cm - in case they change their definition of ground level at the entrance. With the flat roof, I'd prefer the gable design so that I could install gable vents on the ends rather than hat vents on the 7/12 slopes or anything piercing the flat roof itself. Hope this helps.

I didn't say you did. I was saying the rails are decorative and not required unless there is access there. Here's your trusses with a 2 degree flat peak. This is hipped with a girder (circled in green.) Flat top trusses start further back and above the garage trusses. Below is gable ends, 7/12 front to back main house and 7/12 left to right over garage. I think you could raise the front pitch maybe 5 degrees and not impact the flat roof? Every number you've requested is represented in the story pole below and I'm under 950cm (500mm) I can't believe this doesn't put a smile on your face.

Standard 7/12 hip trusses without their piggy backs above 9000mm would give you the look. Instead of piggybacks you could install tapered plywood at the 10 degrees. Its actually called a widows walk and the railing is decorative, not required unless there is rooftop access to the flat area from within.

I think Poland permits mansard roofs. I specified 2900mm for each floor, 400mm for the second deck and changed the roof pitch to 2 degrees at 9000mm. I added a decorative perimeter rail above the 9000mm point that still manages to be under 9500mm from the first floor deck. The roof itself allows grade to be 430mm below the front door and you will still meet the authority requirements.

It appears the 950cm is to be measured from ground level outside the entrance, not the sill of the entrance itself. If that is true, what is the elevation difference between ground level and top of the first floor deck (entrance sill.)?

Where's the problem? 30-45 degrees equals 7/12 to 12/12. Side elevation 1186 ÷ 2 = 593 run And 370 rise ÷ 593 run = 7-1/2 pitch. A 7/12 pitch = 342.37 rise. This gives you room for lumber and shingles. Try 7/12 front to back and make the front gable 7/12 as well initially. Then increase the front gable pitch without the ridge exceeding the 7/12 ridge. Here's an image in case the above isn't clear. A 7/12 all hipped roof should work fine too. Girder over the heated floor areas so that all trusses bear on ex. outside foundation walls.

Your rafters are 2x10s. On an 8/12 pitch, the vertical plumb cut depth is approximately 11 1/8" Forgot to add that you didn't show the plan. You may have some other roof intersections that are raising the roof planes so that the facia plane out all around the building.

I think the only thing the surveyor cleaned up was the boundary on BDRY2. Points() layer is still grouped as a cad block.in Layer 0. I forgot that if you don't specify anything as a terrain, but you do specify a Layer that does have elevation data present, Chief will automatically add a terrain that encompasses all the elevation data. Import the file and only specify contours as elevation data. I work on a white background, most Surveyors use black. I've changed the Terrain Layer to Color Orange with Line Weight 1000. On the BDRY2 layer, I change it to Color Blue & Line Weight 1000 (which initially does nothiing because every surveyor has this unchecked and yellow individually.) Select each BDRY2 lot perimeter line and in the dbx check Line Style boxes Color, Style & Weight. Close dbx and the lines should change to Blue & 1000. You should see this. With regard to the green circles, The bottom arc doesn't run to the end, it straightens out and you need to change that line to Blue 1000 too. At the upper left circler there are two lines that I'd seen in the file earlier. You can ignore them, or move them out of the way temporarily. Now that the perimeter has all blue lines with the same Styles checked, select on at the corners and it will connect to the adjacent blue lines automatically. Do this at each disconnected corner until you see a closed boundary for your lot perimeter. Notice the Terrain perimeter doesn't cover the entire lot - because there is no elevation data in those corners. Notice below your contour lines don't reach the ends of your lot. Chief guesses (extrapolates) what to do where no data is present and it rarely guesses what you'd like to see. Typically I'd reshape my terrain perimeter to match the lot + 5-10 feet at the sides and rear, maybe 30-60' at the front to show the road. The easiest way is to first drag each corner to a lot corner. Which then becomes this. Note you could have simply deleted the terrain, copied the lot perimeter in place and changed that polygon to a terrain if you wanted the curves to match. Open a 3D Camera and Chief will generate the contours as best it can with the data thus far. When you go back to the 2D drawing you will see these contours. At this point I'd probably give up on my surveyor and since I didn't import the Points() layer as data, I would place some elevation points on those X's. I don't care if they are slightly off. Make sure CAD is set to Ft, decimal feet, with precision 3 decimal places (I usually have quadrant bearing turn on as well.) and add the macro to show elevation label. Here's what you should see. I'm not so concerned with the rear lot contours. But the 52' contour line that is running under the Makalulu text I extended past the perimeter edges so that it wouldn't create a circle. these random extensions cross one another. Below is all layers off with contours, bdry2 and terrain perimeter turned on. (easier to see what you are doing) Now, wherever I'm planning to build and I need finer point data (or at the lot corners & road, where it is missing data, I would copy the elev point to those locations and change the value. I copy it because it already is set up for how I want to see the data formatted & displayed. Place as many points as you actually need. I also add a 1' tall fence along the side property lines and the road so that my 3D view looks like this. This way when i start drawing a building I have some perspective on how close it is to the road and side lot lines in 3D views. I hope this helps.

Actually, import with Contours as elevation data and you will find the data is there on Contours. The one I selected says 49' If you zoom in you will see your points(4-13-24) fall between the correct contours. Unfortunately, your going to need to call him back and tell him "unblock everything" includes everything, not just some things. Everything on Points(4-13-24) is still in blocks on Layer 0. And Chief doesn't assign elevation data to a block. Red circle is his block of points(4-13-24) data, still blocked up on Layer 0.. Green circle is after I unblocked one group. It contains 4 objects. Chief needs them unblocked to read the data. Technically the elevation "X" point & Point.ELEVATION data (49.505) should be on its own layer. Point.NUMBER (129) and Point.NAME (GD) should be on separate layers. At least that's how my equipment exports them and Chief loves it. And if he doesn't move Point.NUMBER to another layer, you may find an elevation 129' and 49.505' right beside one another. If you tell Chief Points(4-13-24) is elevation data, when you import now the "X" disappears, but no values are set because the data is in a block In case he still doesn't get it, show him this. This is a block of points(4-13-24) data. Notice it is also on Layer 0 (as a Cad block). You can only turn it off by selecting Layer 0. Selecting the points() does nothing. And show him this. This is after I unblocked the group. Notice they all now exist individually on only the points(4-13-24) layer. Pro Tip - the Boundary is on BDRY2, and true to form, it isn't closed. In fact it's nowhere close. The BLACK and RED lines don't share a common point, so they can't join with one another. The GREEN line has no "Polylines, Label" Layer so it can't join with either Black or Red, which do have a "Polylines, Label" Layer. And I don't know if the YELLOW line means this is two lots, but it has no "Polylines, Label" Layer either and neither BLACK or RED have breaks in their lines where YELLOW meets them.. Chief requires all to be the same to connect automatically. This just means you are going to have to draw that terrain perimeter yourself. Not the end of the world, but just maddening when surveying is all about precision. Hope this helps.