Thank you for the SP2 update ? it seems to resolve the bug report with the space object and net/gross area calculation, as well as the issue with showing line types correctly in viewports. (I?m sure it corrects a lot of other things too ? these were my issues).
I?d like to pose some requests that would improve the functionality of the space tool.
1. There seem to be some fields in the space tool that are not accessible in either Settings or OIP, for example, ?North Key?, ?South Key?, etc. Can these be made accessible?
2. Many architects use an additional finish category, Wainscot, in addition to Ceiling, Walls, Base, and Floor ? this addresses wall finishes that cover the lower part of a wall but have another finish above, which is most common. Ceramic tile in bathrooms is a common version of this. Consider adding as set of fields to address this.
3. Many architects use an additional field within each basic finish category to describe the kind of finish ? what VW calls ?Finish? we call ?Material?, and we add a field called ?Finish? to describe whether the material is painted, stained, demolished, unfinished, etc. This would require an additional field for each of the basic room finish categories ? the ?Finish Remark? field would not suffice for this function.
4. Many architects use the room key symbol to reference our interior elevations to north, east, south and west walls of the room. In our office, we reference interior elevations by indicating sheet number and drawing number of the set of elevations for the room, and use A, B, C, and D to key the actual elevations. It would be ideal if this data could be entered into the space object. It would require six fields ? InteriorElevationDrawingNumber, InteriorElevationSheetNumber, NorthElevationKey, EastElevationKey, SouthElevationKey, and WestElevationKey.
5. VW uses the term ?Occupancy? to describe what functional use is given to a room. This would be better described by the term ?Use?. Occupancy is used by the building code to describe the legal, fire-code related use of the room, which is importantly different from the programmatic or human use of a room. The code uses specific codes (B for Business or office; E for educational, etc.) which would be good to capture within the space object.
6. Similarly, the code defines an occupant load rating in Chapter 10 that would be useful to capture in the space object tool. Icing on the cake would be to have the space object tool divide the gross or net area (user selected, because it is different for different occupant load factors) by the occupant load factor, round up to the nearest whole integer, and put it in a field called OccupantLoad.
7. If it is not possible to add these features to the space object tool, can we at least get more user-definable fields? Ten doesn?t begin to cover what could be done with the space tool.