Announcement

Collapse
No announcement yet.

Metric Beam labeling vs Imperial

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Metric Beam labeling vs Imperial

    Hello world,

    I've got a project I'm working on that is my first project that will have to be done completely in metric. Labeling of the beams is one of the hurdles I'm not entirely sure how to clear yet. The main part of the problem seems to be some inconsistency when it comes to labeling beam sizes. Various web searches have returned different names for members that are the same, for example one resource has a wide flange size of W250x18 while another will have it as W250x17.9. In this example the OOTB metric size that revit provides is a W250x17.9. The issue lies in the labeling and what the actual standards are for the region of the project. My initial first thought was to take our label family, copy over the part of the label for the actual member call out and setting up some yes/no parameters and if statements so that the label could be easily changed in the project environment by selecting the correct visibility parameter and adding the preferred callout in the comments for the member. That sounded great at first but as someone in my office pointed out if the member size changes the comment will still remain unchanged which could cause some errors down stream if the label doesn't update correctly. I'm wondering how others would tackle this issue without modifying the member family.

    #2
    Leave it as is
    create a beam schedule listing all the beams, and reduce the list down to say all beams with type name between W250X17 & W250X18
    you can then edit the type mark parameter (if thats the one you are tagging) & it will updated them all to suit whatever you want

    I'm basically recommending using schedules to change heaps of values all at once
    Dwane

    Comment


      #3
      Dwane,

      Unfortunately my office standard is to label the beam sizes on the plan, so all though a schedule would definitely work it wouldn't comply with that.

      Kyle

      Comment


        #4
        No need to place this schedule on an actual sheet
        just use it to edit parameters

        I have say 1000 beams
        lets say i have a parameter called "paint" & i have values all over the place for them. red paint, green, blue....
        the client then calls & says - i want black paint shown on all beams!
        I don't want to have to do this manually to 1000 beams, so i create a beam schedule, scheduling this parameter
        now i don't want to see a long schedule of 1000 beams, so i reduce this list down (not showing all instance) to a single value
        I can then edit that single value to "black paint" and the schedule will feed this out to the 1000 beams

        im using schedules to feed information out to families
        Dwane

        Comment


          #5
          Dwane,

          I've never thought of using the schedule that way. Thanks for the tip.

          Kyle

          Comment

          Related Topics

          Collapse

          Working...
          X