{"id":3370,"date":"2016-01-19T14:18:05","date_gmt":"2016-01-19T13:18:05","guid":{"rendered":"http:\/\/new.modelical.com\/?p=2673"},"modified":"2024-07-12T14:50:54","modified_gmt":"2024-07-12T12:50:54","slug":"facade-ii-visibility-and-deriverables","status":"publish","type":"post","link":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/","title":{"rendered":"Modelling Facades (II)"},"content":{"rendered":"

Visibility and deliverables<\/h2>\n

This guideline is created as an extension of the previous post “Modeling of Facade Elements”<\/em>. It details the visibility of fa\u00e7ade elements, which have already been created, and how best they can be transformed into project deliverables.<\/p>\n

1 Visibility<\/h3>\n

1.1\u00a0General considerations<\/h4>\n

The way Revit\u00a0is able to display\u00a0an element, enables you to modify this element in several ways, some having priority over others. In addition to the aforementioned, there is a hierarchy in place, which needs to be followed. For this reason, it is important to configure the visibility settings in any one view, thus enabling you to control it better.<\/p>\n

The visibility hierarchy is set out in order of priority\u00a0is:<\/p>\n

    \n
  • Line Work: Within this view: key “LW” and select the lines you wish to change and the linestyle you wish to apply.
    \n\"13\"<\/li>\n
  • Override Graphics in View > By Element<\/li>\n
  • View Filters<\/li>\n
  • View Depth \u2013 \u201cBeyond\u201d line style: When one element is placed betwen the Bottom Plane and the View Depth Plane,\u00a0the element\u00b4s\u00a0lines will be shown as the\u00a0“Beyond” line style configuration.<\/li>\n<\/ul>\n

    \"07\"<\/p>\n

    \"06b\"<\/p>\n

    \"09a\"<\/p>\n

      \n
    • Phasing Graphic Overrides: This changes the display settings of the elements, depending on the phase in which each element has been modeled.<\/li>\n<\/ul>\n

      \"12\"<\/p>\n

        \n
      • Visibility \/ Graphic Overrides > Override Host Layers > Cut Line Styles
        \n\"01\"<\/li>\n
      • Visibility \/ Graphic Overrides: General settings of the visibility of a view.<\/li>\n
      • Project Object Styles<\/li>\n<\/ul>\n

         <\/p>\n

        Bearing in mind\u00a0the hierarchy, the best way to\u00a0adjust these parameters is by selecting the last method in the list, and, if required you can scroll up to the other “methods” should you need to carry out further adjustments. In this way, the\u00a0parameters of many elements can be adjusted at the same time, resulting in a faster and easier approach when making subsequent changes.<\/p>\n

        Firstly we should adjust the object styles. We will find them going to\u00a0Manage > Settings > Object Styles<\/em>. From this section\u00a0we can modify the visibility of the elements modeled in all the views of the project. We are changing the way Revit shows the elements by default. If we make a good adjustment of this parameters, we will not have to make much modifications in the views. A good practice would be take\u00a0the adjustments we make in this section, and save it into a project template.<\/p>\n

        \"02\"<\/p>\n

        There are different subcategories of lines in each category. This is something to keep in mind\u00a0when we create families and we set different subcategories of lines. We will not see the lines in the project as we see them in the family, the family will show its lines as is configured in the object styles of the project.<\/p>\n

        \"05\"<\/p>\n

        Subsequently, we can use the visibility\/graphic overrides in view, usually through view templates to make the adjustment of the parameters faster and easier.<\/p>\n

        Finally, but less recommended, adjustments can be made with annotations or changes to the elements per view, that will only affect the visibility of this element in one view. This resource\u00a0should be always the last to use since\u00a0it creates modifications difficult to detect for subsequent adjustments.<\/p>\n

        1.2 Visibility\u00a0from the project template<\/h4>\n

        Project templates provide a initial environment for new projects. They are very useful to mantain standars betwen projects. This topic is long enough for a complete post, or several posts, but in this case we will focus in all the\u00a0aspects relating to the visibility, both of the elements modeled and annotations.<\/p>\n

        When creating a project template we should consider the following aspects and decide which ones we include:<\/p>\n

         <\/p>\n

          \n
        • Annotations:
          \nA project template should include the annotation families we plan to use in the project, already edited by ourselves.<\/li>\n<\/ul>\n

           <\/p>\n

          Going to Annotate > Tag > Loaded Tags and Symbols<\/em>\u00a0we can check the tags and symbols we have already loaded to the project by category, and we can add more.<\/p>\n

          \"04\"<\/p>\n

          View tags, (callout, section and elevation tags) are system families and are composed of nested annotation families. We can change them from\u00a0Manage > Additional Settings<\/em>.<\/p>\n

          We can load other annotation elements such as grid heads or level heads, or any other annotation we frequently use. We can create new ones from\u00a0New > Family > Annotations<\/em>.<\/p>\n

          Annotations also include text and dimensions. They are system families, and we can edit their type properties or we can create new types.<\/p>\n

            \n
          • Titleblocks<\/li>\n
          • Viewports in sheets<\/li>\n
          • Views, schedules, sheets<\/li>\n<\/ul>\n

             <\/p>\n

            We can create views we know we will use in the project, and leave them in the template already configured. This way we will not have to create them later in every project. We can also create schedules with the parameters we normally use for our measurements, or sheets with titleblocks included.<\/p>\n

             <\/p>\n

              \n
            • Filters<\/li>\n
            • Placeholder links<\/li>\n<\/ul>\n

               <\/p>\n

              We can use this resource when we work with linked models from other partners. We will create some empty models that we know we will later use (structure model, MEP model…) and then we link them in our template. After that we can adjust the visibility parameters for those links, what we want to show from them and how we want to see it. Once in the project, we have to replace those links from the template for the real ones of the project. We will do it going to “Manage links” and using “Reload from”. This way we will keep the visibility adjustments of the template.<\/p>\n

              Esto es \u00fatil cuando sabemos que vamos a trabajar con modelos vinculados de otros colaboradores. Crearemos en un principio una serie de modelos en blanco que pensamos que utilizaremos (estructura, arquitectura, instalaciones\u2026) y los vinculamos en la plantilla de proyecto. Establecemos los par\u00e1metros de visibilidad que queremos para cada archivo v\u00ednculado, qu\u00e9 queremos mostrar y c\u00f3mo lo queremos ver. Una vez en el proyecto, sustituimos cada link de la plantilla por los reales del proyecto, mediante el m\u00e9todo \u201cReload from\u201d en la pantalla \u201cManage links\u201d y permanecer\u00e1n los par\u00e1metros de visibilidad establecidos.<\/p>\n

               <\/p>\n

                \n
              • View templates<\/li>\n
              • Materials and patterns<\/li>\n
              • Line styles: Manage > Additional Settings > Line Styles<\/em><\/li>\n
              • Object styles\u00a0\/ line weights:\u00a0Manage > Additional Settings > Line Weights<\/em><\/li>\n<\/ul>\n

                 <\/p>\n

                1.3\u00a0View templates<\/h4>\n

                View templates are a Revit element that allows us to adjust the visibility of several views at the same time. We can control them from\u00a0View > View Templates > Manage View Templates<\/em>.<\/p>\n

                If we want a view template applied in a great number of views, is better not to include some parameters. It is not a good practice duplicate templates for views\u00a0that\u00a0only differ in terms of visibility in\u00a0the scale or in the view range. Is better not to include this fields and then adjust it in the views. This way we will have a great number of views with their visibility controlled by one template, and if we want to modify it we only have to do it once, in one template, instead of reviewing those adjustments in several templates. We will avoid having a lot of templates used in few views each one. If we want to know in how many views a template is applied we have to go to View > View Templates > Manage View Templates<\/em>, and then selecting one template we can see it.<\/p>\n

                \"14\"<\/p>\n

                The best way of working with view templates is modifying the visibility of one view by categories, and when we think is ok, we can create a template that will keep the modified parameters of this view we are working on. We can create this template from\u00a0View > View Templates > Create Template from Current View<\/em>.<\/p>\n

                1.3.1 Filters<\/h5>\n

                Sometimes when we are modeling, the number of filters created\u00a0grows, and that can become an issue to manage them. We propose a way of naming those filters to make them easier to find.<\/p>\n

                Cuando el modelo empieza a tener una gran cantidad de filtros, empieza a ser dif\u00edcil saber si el filtro que queremos usar est\u00e1 creado o no. Para ello proponemos una nomenclatura:<\/p>\n

                The name of the filter is based in three parts:<\/p>\n

                Example:<\/p>\n

                  \n
                1. 1_Doors_FR<\/li>\n
                2. 0_Sections_STR<\/li>\n<\/ol>\n
                    \n
                  1. The first part, indicates if we will act on the element showed in the name or not.\n
                      \n
                    1. 1 shows that we are acting on the element described in the name, in this case doors Fire Resistant. Here, the rule is positive: “Doors that are Fire Resistant”.<\/li>\n
                    2. 0 would indicate\u00a0that we are acting on elements that do not comply with the rule. Here, the rule is negative: \u201cSections no STR\u201d<\/li>\n<\/ol>\n<\/li>\n
                    3. Second part shows the category on which the filter is acting.\u00a0We recommend using a filter by category, it is more useful later for recognising it.<\/li>\n
                    4. Third part indicates the property of the elements we want to filter.<\/li>\n<\/ol>\n
                      1.3.2\u00a0Links<\/h5>\n

                      When we are in a view modifying the visibility\/graphic overrides, we can go to the “Revit Links” tab to change the visibility of the models linked. From there we can hide completely or show the link, we can assign the halftone or underlay mode, or we can make more specific adjustments in their visibility using the display settings. We can modify some aspects of the halftone and underlay modes from\u00a0Manage > Additional Settings > Halftone\/Underlay<\/em>.<\/p>\n

                      \"15\"<\/p>\n

                      Links are assigned by default the configuration “By Host View”. This means that all the adjustments we make to the categories of the model will affect the same way the categories of the linked model. If we press there, a new window will appear that will show as a similar appearance than the visibility\/graphic overrides of the view. Here we can change the visibility parameters of the linked model in this view or in this group of views if we are using a template. In the top of each tab, will appear three options, that will allow us to configure those parameters “By host view”, “By linked view”, or “Custom”. If we set “By linked view”, Revit will let us choose a view of the linked model, and will apply the visibility settings applied in that view in\u00a0the view we are working on. If we choose “Custome” we will be able to change the visibility of the elements of the link, by categories and worksets, but without filters.<\/p>\n

                      \"16\"<\/p>\n

                      Filters applied to the model, will affect also the elements of the linked models. If we want to filter an specific element of a link, Revit will not suggest us the information of that element, but we can write it and it will work the same way.<\/p>\n

                      Visibility adjustments of links will remain when we replace them, but we have to do it using “Reload” or “Reload from” in “Manage links” window.<\/p>\n

                      \"17\"<\/p>\n

                      2 Deliverables:\u00a0Sheets<\/h3>\n

                      2.1 Prepare views for sheets<\/h4>\n

                      Sheets are a normal way of giving the information that the model contains. To take the model to sheets we will drag views to the sheets. But one view cannot appear\u00a0in several sheets, so we will have to duplicate views. When duplicating views we have to think in the visibility of each one, and then assign them view templates.<\/p>\n

                      Sometimes happen that one floor does not fit in one sheet in the scale we want, and so, we have to split it\u00a0into smaller parts and take them to sheets. To do that we can use scope boxes. We create them from\u00a0View > Scope Box<\/em>. This element allows us to create regions that then will easily become the crop region of lots of views by selecting it in the view properties.<\/p>\n

                      \"18\"<\/p>\n

                      When we have one view that we have to split into smaller regions, the best way is duplicating this view as dependant. This way we assure that the duplicated views will have the same visibility configuration as the original one, and the adjustments we make in the original one will apply in the duplicated views. The duplicated views will appear linked to the original one in the project browser. Then we only have to apply to each view the correspondant scope box in the view properties.<\/p>\n

                      \"19\"<\/p>\n

                      2.2\u00a0Detailed views<\/h4>\n

                      When we increase the level of detail in views, sometimes is neccesary to add some draw and detail items to complete the model. Revit offers two options to do that: callouts and drafting views. Callouts are views that contains the model where we can add some details to it. Drafting views are views non related with the model where\u00a0we can draw details using 2D detailing tools.<\/p>\n

                      Callouts are a model view that can appear referred in other views as a callout or a section. This type of view usually presents a part of the model in a bigger scale than the main view it comes from. We can create a callout from a plan view, from an elevation and from a section and then we can add detail with the model as reference. We can create them from\u00a0View > Create > Callout<\/em>.<\/p>\n

                      \"20\"<\/p>\n

                      Once done the callout, we can go to the view (right click > go to view<\/em>) and there we can add annotations, detail items and 2D tools to complete the model. We have to be careful with these type of views, because they show the model, so if the model change, it will be shown in the callout, but the 2D elements will remain in the same place they were. When we drag this view to a sheet, the callout tag will show the number of the sheet is placed in the views where this detail is referred. If we want to change what the callout tag shows we can modify the tag family from the project browser, and then change it in the callout type from\u00a0Manage > Additional Settings > Callout Tags<\/em>.<\/p>\n

                      When we create a callout, we can refer to an existing view. This tool allows us to refer the same detail from different views. The same occurs when we create a section, it allows us to refer to other view and it draws a section in this view but does not create a new one, just refers to the selected one.<\/p>\n

                      \"21\"<\/p>\n

                      Along a project, sometimes is neccesary create details in a view that is not related with the model, and then we create a drafting view. These views do not show the model, and in them we use 2D tools: detail lines, regions, detail items, dimensions or text; or we can import a dwg file. Drafting views can be created from\u00a0View > Drafting View<\/em>, then we will name it and will set the scale.<\/p>\n

                      If we want to import details from CAD, we will go to\u00a0Insert > Import CAD<\/em>. We\u00a0must check that the scale of the view and the scale of the CAD is the same. In the import window we can modify some aspects, paying attention to the option “Current view only”, that should be marked.<\/p>\n

                      \"22\"<\/p>\n

                      2.3 Annotations<\/h4>\n

                      A good procedure to control the annotations that are placed in one view, is by changing the option “Display Model” option of the view that we can find in the view properties. If we change it to the options “Halftone” or “Do not display”, Revit will apply those options to the model and will leave the annotations the same as they were, so we will easily see where they are.<\/p>\n

                      \"23\"<\/p>\n

                      In case we need to place some annotations in several views, we can create a group with all of them. Then we can copy the group and paste with the option “Aligned to\u00a0Selected Views”, or we can go to\u00a0Annotate > Detail Group > Place Detail Group<\/em>, in the view.<\/p>\n

                      2.4\u00a0Sheet list<\/h4>\n

                      A sheet list will help us to manage all the information related with sheets. We can export this information to Excel from\u00a0R > Export > Reports > Schedule<\/em>, when we are placed in the schedule. It will create a .txt file that then we can drag to an excel file.<\/p>\n

                      If some sheets are not created in Revit, we can add them to the list as a placeholder to keep the complete list of sheets. In the sheet list (View > Schedule > Sheet List<\/em>) we\u00a0can insert rows that will have the information of the sheets created in other softwares by\u00a0Modify Schedule\/Quantities > Insert Data Row. <\/em>Then we can easily filter the sheets that are in Revit from the ones that are not from the menu\u00a0 Modify Schedule\/Quantities > Filter Placeholder Sheets.<\/em><\/p>\n

                      2.5\u00a0Placing views in sheets<\/h4>\n

                      Each view can be placed just in one sheet, that is why it will be neccesary duplicate them and assign templates to them depending on what we want them to show. Schedules and legends are an exception because they can appear in as much sheets as neccesary, but they will appear always the same way, with the same visibility.<\/p>\n

                      One sheet can contain lots of views, that can be overlapped.<\/p>\n

                      If we want to edit the shape of the crop region of the view, we have to make it visible, then select it, and then press “Edit Crop”. If we have annotation crop active, it will remain with rectangular shape surrounding the new crop region of the view.<\/p>\n

                      When we overlap views in one sheet, it is very important the order of placing them in the sheet. The first view placed in the view will be in the background, and the last placed will be in the foreground, hiding the others.<\/p>\n

                      \"10_a\"<\/p>\n

                      View 2 (brown) over view\u00a01<\/p>\n

                      If the view placed in the foreground has a crop region with no rectangular shape, a white space will appear surrounding its shape, hiding the views are under it. This is a strange situation because is just a problem of graphics on screen, but it disappears when we export or when we print the sheet. We can check it in the preview of the sheet, and there the view will appear cropped in the foreground without any strange white rectangle hiding other views.<\/p>\n

                      \"10_b\"<\/p>\n

                      View 1 cropped hides view 2 with a white rectangle, but it happens just on screen, it dissappears when we export or print.<\/p>\n

                      A good way of having different ways of displaying the model in the same sheet is playing with overlapping of several views with different view templates and adjust their range (“View range” in plan views and “Far clip offset” in elevations and sections). For example, we can place an elevation with greys in the background and then place the same view with a low level of “Far clip offset” and other visibility. This way, we can mark the elements that are nearer\u00a0in the view placed in the foreground, and the elements that are far will appear grey, showing some distance. We can adjust the “Far clip offset” in the view properties of the view, or placed in a plan view and selecting the section we can drag the limits of the view. The “View Range” can only be changed in the view properties of the plan view.<\/p>\n

                      \"24\"<\/p>\n","protected":false},"excerpt":{"rendered":"

                      This guideline is created as an extension of the previous post Modeling of Facade Elements. Here we will talk about the visibility of the fa\u00e7ade elements we have already created, and how we transform them into project deliverables.<\/p>\n","protected":false},"author":2,"featured_media":27096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[4],"tags":[411,781],"class_list":["post-3370","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guidelines","tag-technology-revit","tag-technology-revit-arc"],"acf":[],"yoast_head":"\nModelling Facades (II) - Modelical<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Modelling Facades (II) - Modelical\" \/>\n<meta property=\"og:description\" content=\"This guideline is created as an extension of the previous post Modeling of Facade Elements. Here we will talk about the visibility of the fa\u00e7ade elements we have already created, and how we transform them into project deliverables.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/\" \/>\n<meta property=\"og:site_name\" content=\"Modelical\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Modelical\/\" \/>\n<meta property=\"article:published_time\" content=\"2016-01-19T13:18:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-07-12T12:50:54+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.modelical.com\/wp-content\/uploads\/2016\/01\/Facades2-400x250-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"400\" \/>\n\t<meta property=\"og:image:height\" content=\"250\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Alberto Ramos\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@modelical\" \/>\n<meta name=\"twitter:site\" content=\"@modelical\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alberto Ramos\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/\"},\"author\":{\"name\":\"Alberto Ramos\",\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/#\\\/schema\\\/person\\\/2f0344005ef6a082ecf895c5359de5e1\"},\"headline\":\"Modelling Facades (II)\",\"datePublished\":\"2016-01-19T13:18:05+00:00\",\"dateModified\":\"2024-07-12T12:50:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/\"},\"wordCount\":3148,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.modelical.com\\\/wp-content\\\/uploads\\\/2016\\\/01\\\/Facades2-400x250-1.jpg\",\"keywords\":[\"Tec Revit\",\"Tec Revit ARC\"],\"articleSection\":[\"Guidelines\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/\",\"url\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/\",\"name\":\"Modelling Facades (II) - Modelical\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.modelical.com\\\/wp-content\\\/uploads\\\/2016\\\/01\\\/Facades2-400x250-1.jpg\",\"datePublished\":\"2016-01-19T13:18:05+00:00\",\"dateModified\":\"2024-07-12T12:50:54+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/#\\\/schema\\\/person\\\/2f0344005ef6a082ecf895c5359de5e1\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/facade-ii-visibility-and-deriverables\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.modelical.com\\\/wp-content\\\/uploads\\\/2016\\\/01\\\/Facades2-400x250-1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.modelical.com\\\/wp-content\\\/uploads\\\/2016\\\/01\\\/Facades2-400x250-1.jpg\",\"width\":400,\"height\":250},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/\",\"name\":\"Modelical\",\"description\":\"We build information\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/#\\\/schema\\\/person\\\/2f0344005ef6a082ecf895c5359de5e1\",\"name\":\"Alberto Ramos\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/af056ef31a42bf9ac399940d891b8b5d5ee09bdc4d82d4af53dcc22b3da3cd5b?s=96&d=initials&r=g&initials=al\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/af056ef31a42bf9ac399940d891b8b5d5ee09bdc4d82d4af53dcc22b3da3cd5b?s=96&d=initials&r=g&initials=al\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/af056ef31a42bf9ac399940d891b8b5d5ee09bdc4d82d4af53dcc22b3da3cd5b?s=96&d=initials&r=g&initials=al\",\"caption\":\"Alberto Ramos\"},\"sameAs\":[\"https:\\\/\\\/www.modelical.com\"],\"url\":\"https:\\\/\\\/www.modelical.com\\\/en\\\/author\\\/alberto\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Modelling Facades (II) - Modelical","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/","og_locale":"en_US","og_type":"article","og_title":"Modelling Facades (II) - Modelical","og_description":"This guideline is created as an extension of the previous post Modeling of Facade Elements. Here we will talk about the visibility of the fa\u00e7ade elements we have already created, and how we transform them into project deliverables.","og_url":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/","og_site_name":"Modelical","article_publisher":"https:\/\/www.facebook.com\/Modelical\/","article_published_time":"2016-01-19T13:18:05+00:00","article_modified_time":"2024-07-12T12:50:54+00:00","og_image":[{"width":400,"height":250,"url":"https:\/\/www.modelical.com\/wp-content\/uploads\/2016\/01\/Facades2-400x250-1.jpg","type":"image\/jpeg"}],"author":"Alberto Ramos","twitter_card":"summary_large_image","twitter_creator":"@modelical","twitter_site":"@modelical","twitter_misc":{"Written by":"Alberto Ramos","Est. reading time":"19 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/#article","isPartOf":{"@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/"},"author":{"name":"Alberto Ramos","@id":"https:\/\/www.modelical.com\/en\/#\/schema\/person\/2f0344005ef6a082ecf895c5359de5e1"},"headline":"Modelling Facades (II)","datePublished":"2016-01-19T13:18:05+00:00","dateModified":"2024-07-12T12:50:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/"},"wordCount":3148,"commentCount":0,"image":{"@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/#primaryimage"},"thumbnailUrl":"https:\/\/www.modelical.com\/wp-content\/uploads\/2016\/01\/Facades2-400x250-1.jpg","keywords":["Tec Revit","Tec Revit ARC"],"articleSection":["Guidelines"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/","url":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/","name":"Modelling Facades (II) - Modelical","isPartOf":{"@id":"https:\/\/www.modelical.com\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/#primaryimage"},"image":{"@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/#primaryimage"},"thumbnailUrl":"https:\/\/www.modelical.com\/wp-content\/uploads\/2016\/01\/Facades2-400x250-1.jpg","datePublished":"2016-01-19T13:18:05+00:00","dateModified":"2024-07-12T12:50:54+00:00","author":{"@id":"https:\/\/www.modelical.com\/en\/#\/schema\/person\/2f0344005ef6a082ecf895c5359de5e1"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.modelical.com\/en\/facade-ii-visibility-and-deriverables\/#primaryimage","url":"https:\/\/www.modelical.com\/wp-content\/uploads\/2016\/01\/Facades2-400x250-1.jpg","contentUrl":"https:\/\/www.modelical.com\/wp-content\/uploads\/2016\/01\/Facades2-400x250-1.jpg","width":400,"height":250},{"@type":"WebSite","@id":"https:\/\/www.modelical.com\/en\/#website","url":"https:\/\/www.modelical.com\/en\/","name":"Modelical","description":"We build information","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.modelical.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.modelical.com\/en\/#\/schema\/person\/2f0344005ef6a082ecf895c5359de5e1","name":"Alberto Ramos","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/af056ef31a42bf9ac399940d891b8b5d5ee09bdc4d82d4af53dcc22b3da3cd5b?s=96&d=initials&r=g&initials=al","url":"https:\/\/secure.gravatar.com\/avatar\/af056ef31a42bf9ac399940d891b8b5d5ee09bdc4d82d4af53dcc22b3da3cd5b?s=96&d=initials&r=g&initials=al","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/af056ef31a42bf9ac399940d891b8b5d5ee09bdc4d82d4af53dcc22b3da3cd5b?s=96&d=initials&r=g&initials=al","caption":"Alberto Ramos"},"sameAs":["https:\/\/www.modelical.com"],"url":"https:\/\/www.modelical.com\/en\/author\/alberto\/"}]}},"_links":{"self":[{"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/posts\/3370","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/comments?post=3370"}],"version-history":[{"count":0,"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/posts\/3370\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/media\/27096"}],"wp:attachment":[{"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/media?parent=3370"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/categories?post=3370"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.modelical.com\/en\/wp-json\/wp\/v2\/tags?post=3370"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}