Worksheet / Design Layer Viewports / Framing Members

[Assemblage]

Anyone know what Jeffrey's referring to by "the Space object"?

[Pat Stanford]

In VW Architect and Designer there is an object used for Space Planning called the Space Object. It is in the AEC menu under Space Planning.

It is basically a hybrid object of a polygon and a 3D polygon/Extrude and a fancy record attached.

In Top/Plan the poly will show selected fields as a text block.

[Jeffrey W Ouellette]

Peter, et al,

I recently had my knowledge of the limits of referencing refreshed by engineering staff.

Currently, and in the foreseeable future, VW does NOT support user created Record Formats in the "new" Workgroup Referencing/Design Layer Viewport Referencing. Why? The problem is that all resources (hatches, symbols, record formats, etc.) are renamed (preppended with the "NNA#x-) and hidden in the document to avoid naming conflicts with resources in current documents.

Since VW 2009, the "new" referencing, also know as "true" referencing, works without having to import all the information of the source file. In old style referencing (a.k.a. "layer import"), we don't rename objects/resources and we let the user resolve the conflicts.

The only situation in referenced DLVPs where we don't rename is when we are sure that the resource is unique, like embedded PIO Record Formats, that are hidden to the user to begin with and hard-coded into the PIO.

Now, it is hard to decide what to do with custom record formats that are created by the user. One idea could be to introduce a project preference that allow users to choose the type of import they want.

In your case, Peter, it is best to use the Space object to get the best results.

[Assemblage]

Tried the Space Object, and it's working - fantastic, many thanks.

A final question: we do urban design as well as architecture, and are starting to really utilise overlaid DLVPs, class overrides, and so forth. A multi-file structure is fundamental to us so a number of people can work on the project at the same time, hence working files are referenced into the design layers of a central file via DLVPs, whose sheet layers are then used for printing/issuing. Employing worksheets in this central file to report data is important to us, but the fields are quite different in urban design, eg Use, No. of Storeys, Character Area, Zone, etc, and can vary according to the project. We had been hopeful we could simply assign information to objects which the worksheets would pick up. The avoidance of conflicts is welcome, and we want to continue using 'true' referencing, but wondering if there is more suitable route for urban design than the Space Object which is really about architecture and actual rooms.