Jump to content

shorter

Member
  • Posts

    1,663
  • Joined

  • Last visited

Reputation

415 Spectacular

2 Followers

Personal Information

  • Occupation
    CAD and BIM Management, Vectorworks Sales, Customisation, and Training
  • Homepage
    www.stevenshorter.com www.modelity.co.uk https://www.linkedin.com/in/stevenshorter
  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. yes. It does.Any vector graphic can be placed inside a Vectorworks tile.
  2. Are you using FileMaker to generate the specification? FM is great for setting up tables. You can set up a table that exports to vw. We used to do that in one office until they Revit. A button in FileMaker to ‘export to vectorworks’.
  3. RLB provide a specification consultancy service, or at least did. The system started life as a service provided by a company called 'Schumann and Smith'. The 'SRS' system is simply a way of annotation drawings with descriptive codes. The idea being that the code rarely changes and therefore you don't need to chase your tail updating drawings when specification clauses change. If you change a code on a drawing it is because you have changed the component proposed, but if you were to change stone to brick, for example, the note on the drawing would remain 'EWS-001', but the NBS clause associated to 'EWS-001' would change in the 'SRS database', which is essentially an Excel spreadsheet issued with the tender documentation. It is a very efficient, if manual, way to annotation drawings, and can also be used with custom property sets and the data tag, or entered into a BIM component in the Classification data fields. There is currently no way of linking the SRS system to BIM components directly like the NBS Chorus system. Would be great if there were. In some offices we created a drawing, with the SRS codes, and NBS clauses listed and called it 'Technical Reference Sheet' or 'T-Sheet' for short, and gave it drawing number '000'. It also contained all the markers used on the drawings, etc; a sort of guide to the annotation on the drawings, so things like 'overhead' lines we defined, but also how a concrete boardmark was annotated.
  4. The NBS Chorus plugin for Vectorworks is also only available if you have a Service Select contract. That said, if you use NBS Chorus, you can export a txt file, and use that, with a small amoiunt of modification in Excel, to a Notes Manager Database. Can send instructions for anyone interested. Similarly, if you use Word, and do things long-hand, using the historic version of the NBS like the ones we used to get on floppy disk...!...I can show you how to extract the information you need to generate the Notes Manager Database. That said, I can whole-heartedly recommend the SRS system from RLB. It is a system based on abbreviations, rather than specification clauses so that the item annotated has 'DRS-001' next to it rather than 'L10/100 Door', which means that if you change the clause you don't need to go around every drawing and update the note. If you prefer, you can annotate the item with 'DRS-001' and then have 'DRS-001' listed as a keynote with it's associated NBS clause. Again, we create Notes Manager Database files to enable this in Vectorworks.
  5. Use a viewport of the grid layer and crop the viewport.
  6. UK = NBS Some have their own specification writers, like Mark Schumann and his SRS system but ultimately that’s based on the NBS. Some have been known to write their own because the NBS is not exacting enough.
  7. Is there a reason why 'Stair' has no 'classification' data mapping entry? If we were to associate 'Stair' to 'Classification' 'Uniclass 2015' and 'Item Reference' 'Ss_35_10' for example as we can with other objects, how do we do that through data mapping? The IFC data mapping tables are excellent and a great way to standardise classification and item reference, but some objects are missing this option. Currently working on a Data Mapping table to automatically map VW objects to Uniclass codes, to compliment the class libraries we have recently issued, (watch this space!) but getting stuck on a couple of key objects.
  8. Running the Migration Manager (not on startup) will create a new workspace based on an existing workspace from a previous version, although is not quite what I had in mind because I might already have a workspace I am using and I want to import shortcuts from another.
  9. How many times have you wished you could import shortcuts from another workspace? Matching a custom workspace is quite a time-consuming process. In addition to the 'Export' button, it would be great to have an 'Import' button, to either create a new workspace based on the tools, commands, and shortcuts of an existing workspace (e.g. when migrating from one version of Vectorworks to another since historic workspaces tend to cause issues), or simply the shortcuts to map any changes in shortcut in a custom workspace to another.
  10. Out of interest, why wouldn't you set all attributes 'by class'? Configuring space styles, the dialog to edit 'graphic attributes' needs a 'set all attributes by class' button, as per wall and slab styles.
  11. Publish… use saved views and sheets Select Folder and export every sheet and every saved view from any file anywhere it’s not that complicated. Just make sure the export options are set correctly for each file type.
  12. This is a wish!!!! It’s in the ‘Wishlist’ section!!!
  13. I do not want to modify the original. A viewport will still bring the geometry with it. It is just turned off. This is very different from it not being there at all. The original file is not mine to modify. I could opt to not reference the file at all! That would do part of what I am asking for. There are lots of workarounds. I am not looking for a workaround. In this instance the file I am referencing is impossible to use. I cannot open it. I am referencing it in order to create a copy since there is no way of opening the original hoping the original will be better behaved. in doing so it would be very useful to choose what to reference and not have the whole file referenced with whatever class I choose not to reference ignored and not imported by the reference. am I not explaining this very well?
  14. We are developing a class mapping table to convert 'VW Arch' classes to the BS1192/ISO19650 classes we have recently released. We will be happy to share this when it's finished. The mapping table will work when using the 'Class and Layer Mapping' command, but also when exporting DWG by selecting the appropriate class/layer mapping table in the DWG export dialog. It would be great if Vectorworks would also provide this function within the IFC export settings too. For the time-being you will have to continue to use the class/layer mapping command, despite this being more long-winded.
  15. Yes. It would not resolve this issue, would it? We don't use viewport referencing for a long, long list of reasons. The question was in relation to layer referencing. Viewport referencing would not remove the unwanted data from the referenced file, which is what I want. I have site model. The site model is huge. It contains trees. I don't want to reference the trees in at all. But I also do not want to delete them from the original or make a copy of the original file. Having an option to 'ignore' the objects in the class 'Trees' would make the file I am referencing lighter. The only analogy I can think of is the list of elements you get when importing an IFC. I can tick all elements, or opt to not import 'ifcFlowTerminal' objects thereby making the resulting vectorworks file lighter.
×
×
  • Create New...