No announcement yet.

[All Verticals] - System Family - Spot Elevation Parameters

This topic is closed.
  • Filter
  • Time
  • Show
Clear All
new posts

    [All Verticals] - System Family - Spot Elevation Parameters

    Applies to: - All Verticals

    New Feature / Problem:
    Add instance based text input to the spot elevation system tool.

    Why do you need this Feature / Why is it a Problem:
    This would allow for user input, similar to the way dimentions work now. (The ability to replace text, add prefix/sufix, uder line text, ect.)
    We are unable to add extra text to the spot elevation. The only way around this is with many visibily parameters and types.

    We would use this for identify what element in the model the spot elevation symbol is calling out. IE. TOS, TOF, TOC, Typcial, ABV FF... basically allowing us better conveyance of the spot elevation symbol.

    Currently I have a modified symbol family with 26 visibility parameters and 13 types. This clutters the type pull down and inhibits updating the family.

    Greatly increase the usability of the tool and consistance of spot elevations.

    Attachment comments:
    Attached Files
    -Alex Cunningham

    Alex, I´m probably missing something here... But my spot elevations DO have both a prefix and suffix... and it´s even documented in the help files.

    So, what am I missing?
    Klaus Munkholm
    "Do. Or do not. There is no try."


      This can also already be done. In two ways actually:

      1. Per Spot Elevation. Once you placed a SE you can select it and in the properties window place an instance text as prefix or suffix. (these are the Single Upper/Lower Value Prefix/Suffix)
      2. Per SE type. Using the Edit Type button you can create prefixes and suffixes for all SE's from that specific type. You also can create different prefixes and suffixes, depending on the measuring point you choose when selecting an element to tag (you can place a SE for the Upper Value, Lower Value, Both Upper and Lower or the Actual measured height (be aware that in elevation views only the last one works).

      When you have both, instance and type, they are placed in that order: first instance, then type.
      The one thing you CAN'T do though is place text on multiple lines. It would be nice if you could select the placement of the labels.
      Martijn de Riet
      Professional Revit Consultant | Revit API Developer
      MdR Advies
      Planta1 Revit Online Consulting


        Originally posted by Munkholm View Post
        Alex, I´m probably missing something here... But my spot elevations DO have both a prefix and suffix... and it´s even documented in the help files.

        So, what am I missing?
        Yes the prefix and suffix work as described in the help file.

        What I am trying to convey is to have the spot elevation system family work more like the dimention system family. Double click on a dim... you will see what I mean. (Replace Text, Above, Below, Prefix, Suffix - all in a nice window)

        I would also like to have it have the ability to have the 2nd line of text under the leader line.

        After all the spot elevation symbol is a dimention of some sort, its a spot dimention that only shows the height at one point, it would work like the dimentions do.
        -Alex Cunningham


          I agree with Alex...

          I like to use spot elevations as "Levels" instead of creating tons of levels so I can tag T.O. Sill and things like that...


            Another thing that I thought was interesting when I first found out, but may be something well know now is that you can use spot elevations on non-model elements. So if I have a detail line showing a joint or a detail component of a lintel or something like that in section or elevation you can use the spot elevations on them as well...


              I think the current tool works pretty much as it should.

              I am certainly not keen on the idea of a text driven spot elevation as I could end up with something which might be mistaken for a real elevation when it is in fact simply text. I understand the similar function in dimensions and again, for my work, I use this function as rarely as practicable. One of the things which I absolutely love about revit is the confidence I have with dimensions and heights.

              Because I do them so rarely, if I found there is a need in the design and documentation process to put an approximate height, I would do so either as text or create a completely different looking generic family for the purpose.
              Ian Kidston


              Related Topics