# View Placement - Size Error

**URL:** <https://forum.dynamobim.com/t/view-placement-size-error/15635>\
**Category:** Revit\
**Created:** [October 13, 2017, 5:36pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635 "2017-10-13T17:36:22Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 13, 2017, 5:36pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/1 "2017-10-13T17:36:22Z")

</div>

Hey all,

So I know the deal with the Sheet.ByNameNumberTitleBlockAndView placement, and why the error pops up (say your view at the current scale is too big for the sheet). All of the previous posts I’ve seen reference trying to place the view manually to check the size. My view is tiny compared to the sheet, yet Dynamo still says the view is too big for the sheet. See below:

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/f/f/ff0b4f93cea884827a04c0ca515f19d64435004b.png)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/6/9/69572e72d7c27828bcde760e460c22d534d61d4e.png)

I placed it in this location. The only thing I can think of is that since it is generated and placed off of the sheet (down and to the right), maybe that is why. any ideas?

---

<div class="post-metadata">

**Author:** ![awilliams](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/awilliams/32/114496_2.png) [@awilliams](https://forum.dynamobim.com/u/awilliams)\
**Post date:** [October 13, 2017, 5:44pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/2 "2017-10-13T17:44:53Z")

</div>

@cnealy Do you have a Crop Region on the view?

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 13, 2017, 5:45pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/3 "2017-10-13T17:45:42Z")

</div>

@awilliams I do not – I tried going that route, but resizing it proved problematic.

---

<div class="post-metadata">

**Author:** ![awilliams](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/awilliams/32/114496_2.png) [@awilliams](https://forum.dynamobim.com/u/awilliams)\
**Post date:** [October 13, 2017, 5:50pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/4 "2017-10-13T17:50:23Z")

</div>

> [@cnealy](#):
>
> resizing it proved problematic.

Can you elaborate on how it was problematic? The reason I asked about crop region is because I’m thinking its possible the view _is_ actually too large since it looks like this is an axo of a single element with the rest of the model elements hidden out, so maybe the view’s size is technically as large as your model. But this could be an incorrect assumption if the viewport box when selecting the view on the sheet doesn’t appear to be very large.

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 13, 2017, 5:59pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/5 "2017-10-13T17:59:39Z")

</div>

That’s very possible! The only nodes I’ve seen to resize the crop box require x,y,z inputs and I’m building 40-60 of these views/sheets at the same time. Maybe there’s a package I don’t have downloaded.

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [October 13, 2017, 6:15pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/6 "2017-10-13T18:15:03Z")

</div>

I think what @awilliams is saying is that turning on the crop region might help to confirm the size isn’t too big. Often these axons include the hard coded origin, project base point, or survey point which can be quite a way off from the geometry you’re isolating.

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 13, 2017, 6:21pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/7 "2017-10-13T18:21:39Z")

</div>

Absolutely. When I incorporate the crop view, the size is still too large, as the default crop area (using SpringNodes View.CropView) is much larger than the isolated part. So I think you’re right as far as to say that the uncropped region is propbably bounding the whole model. Any way to auto resize the crop box to fit each part?

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/f/c/fceb7ae767168b844d173f4e378f175f1a15c413.jpg)

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [October 13, 2017, 6:23pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/8 "2017-10-13T18:23:14Z")

</div>

Have you seen this:

> [@Element.Create 3d Cropped View (Steam Nodes) - How To Make It Work Consistently?](https://forum.dynamobim.com/t/element-create-3d-cropped-view-steam-nodes-how-to-make-it-work-consistently/3458):
>
> Trying to use ElementCreate 3d Cropped View from the Steam Nodes Package Sometimes it works and sometimes it doesn’t. Can someone explain what conditions will make it work consistently? Usually the output for the Node is “Null” Is it a transaction sequence issue? Do I need to shut down revit and open it again for re-use? On the other hand, creating floor plan by room node seem to work consistently.

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 13, 2017, 7:16pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/9 "2017-10-13T19:16:09Z")

</div>

I checked it out, unfortunately, it doesn’t fit the workflow as the views are generated by a list of parameter values and then filters applied (built by the same list).

I’ll have to figure out some way to resize the crop box once I create the view.

---

<div class="post-metadata">

**Author:** ![awilliams](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/awilliams/32/114496_2.png) [@awilliams](https://forum.dynamobim.com/u/awilliams)\
**Post date:** [October 13, 2017, 7:22pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/10 "2017-10-13T19:22:39Z")

</div>

@cnealy Hmm you probably could filter the output of generated views in some way to pass the views that _would_ need crop boxes through the Steam Nodes View.CropView node

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 13, 2017, 8:06pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/11 "2017-10-13T20:06:11Z")

</div>

Yeah, I’ve run them through that node but the crop box is huuuge.

---

<div class="post-metadata">

**Author:** ![Nick\_Boyts](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/nick_boyts/32/76313_2.png) [@Nick\_Boyts](https://forum.dynamobim.com/u/Nick_Boyts)\
**Post date:** [October 13, 2017, 9:00pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/12 "2017-10-13T21:00:31Z")

</div>

Are they assigned to a scope box? Or maybe they have a section box since they’re 3D views?

---

<div class="post-metadata">

**Author:** ![awilliams](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/awilliams/32/114496_2.png) [@awilliams](https://forum.dynamobim.com/u/awilliams)\
**Post date:** [October 13, 2017, 9:00pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/13 "2017-10-13T21:00:50Z")

</div>

Are all the views similar to the one you’ve shown - basically an axo of a single element? If so there is likely a way to modify the crop box to fit the bounding box of the element.

---

<div class="post-metadata">

**Author:** ![awilliams](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/awilliams/32/114496_2.png) [@awilliams](https://forum.dynamobim.com/u/awilliams)\
**Post date:** [October 13, 2017, 9:05pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/14 "2017-10-13T21:05:41Z")

</div>

@Nick_Boyts I hadn’t even thought about section box! I would think if there was one, running the views through the View.CropBox would produce a much smaller crop

---

<div class="post-metadata">

**Author:** ![Nick\_Boyts](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/nick_boyts/32/76313_2.png) [@Nick\_Boyts](https://forum.dynamobim.com/u/Nick_Boyts)\
**Post date:** [October 13, 2017, 9:13pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/15 "2017-10-13T21:13:22Z")

</div>

I think section box and crop box use different methods so one wouldn’t fix the other. And showing the crop region wouldn’t turn on the section box like it did in the image above so I’m a little confused. But it could just be that both were too big and the crop box is fixed (or turned off) and the section box is the one still causing trouble.

---

<div class="post-metadata">

**Author:** ![awilliams](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/awilliams/32/114496_2.png) [@awilliams](https://forum.dynamobim.com/u/awilliams)\
**Post date:** [October 13, 2017, 9:31pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/16 "2017-10-13T21:31:18Z")

</div>

Ah! @cnealy I think I know what you need to do now that I remembered seeing these two posts of yours:

> [@Axonometric View Creator Naming Issue](https://forum.dynamobim.com/t/axonometric-view-creator-naming-issue/15569/3):
>
> Sure, this is the relevant information – the rest of the script creates schedules, filters, etc that are all names correctly. The error is only applying to the views. Thanks for the response!

> [@Creating Filter Rules - List Manipulation](https://forum.dynamobim.com/t/creating-filter-rules-list-manipulation/15011/10):
>
> Of course, see my full script below: The premise is that it reads any element of “category:Part” in the model (our company uses Parts to make pour drawings for concrete), reads the value of the shared parameter Pour ID that we made, filters it by unique ID, removed the empty ones, and creates a filter where you apply it, turn off the visibility, and all parts that don’t have the requisite Pour ID are hidden. For example, if you want to only see Base Slab 101 (BS-101), you make a filter called …

I would try replacing your **AxonometricView.ByEyePointAndTarget** node with **AxonometricView.ByEyePointTargetAndBoundingBox** and use the elements’ bounding boxes min and max points to get your eye points and target points (maybe not depending on the geometry of the elements but I don’t think you will want to use the same points for each item), and the elements’ bounding boxes for the axo view bounding box, and set the toggle for “isolateElement” to true. See below example

 ![axo view bounding box](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/a/c/ac24ede15229ed155a30d203873b615b4dae8c32.png)  
This produced 2 of these with the crop region sized correctly on elements in different locations:  
 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/1/b/1bec136dfb80cfcf904a73622e8daf79759dcf49.png)

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [October 17, 2017, 7:52pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/17 "2017-10-17T19:52:12Z")

</div>

So folks, it’s all for naught. I switched the node to **Anonometrix.ByNameNumberTitleBlockAndViews** and all of a sudden it worked. No clue why.

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/4/2/4203e62792bb62e7ce0a7d0bd4fb263a6cf39990.png)

---

<div class="post-metadata">

**Author:** ![SteveG](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/steveg/32/54295_2.png) [@SteveG](https://forum.dynamobim.com/u/SteveG)\
**Post date:** [November 5, 2018, 7:48pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/18 "2018-11-05T19:48:09Z")

</div>

> [@cnealy](#):
>
> Anonometrix.ByNameNumberTitleBlockAndViews

What package is that part of?

---

<div class="post-metadata">

**Author:** ![cnealy](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/cnealy/32/41186_2.png) [@cnealy](https://forum.dynamobim.com/u/cnealy)\
**Post date:** [November 5, 2018, 8:06pm UTC](https://forum.dynamobim.com/t/view-placement-size-error/15635/19 "2018-11-05T20:06:20Z")

</div>

My apologies – after looking back over this post, my typos were rampant.

The two nodes I was using were **AxonometricView.ByEyePointAndTarget** (OOTB Revit dropdown) and **Sheet.ByNameNumberTitleBlockAndViews** (Revit OOTB dropdown).
