Jump to content

Katarina Ollikainen

Vectorworks, Inc Employee
  • Posts

    66
  • Joined

  • Last visited

Posts posted by Katarina Ollikainen

  1. I fully understand your need for a solid library with a limited palette. This is the reason I suggest creating your own library with Plant styles, just as you're saying you've moved to. This way you 'own' the plants and the data - they're' ready baked' and prepared to use in your design. This is the absolutely most efficient way of working with plants in Vectorworks and what I recommend to everyone.

    Just make sure you have a solid backup system for your library file, preferable both in the cloud and on a hard drive (separate from your working machine) - I know, this should be a no-brainer, but you would be surprised over how often this is forgotten 😉.

    • Like 1
  2. Peter, thank you for your input, the issue with plant data has long been a hot discussion point. I'll reiterate my request for everyone to also add any constructive comments you have regarding how to make these processes more suitable for your specific workflows to the roadmap - this is really the most efficient way to get your ideas through to the developing team. I would also be grateful for concrete examples on output so that we can take these into consideration. If you or anyone else is willing to share, please send examples directly to me, kollikainen@vectorworks.net. 

    This is really the crux - yes, it is important to identify what's not working, but it's even more important to look at where you want to go (as a skier I would say 'look at the space between the trees; where you look is where you'll go).

    • Like 1
  3. This is definitely towards the top of the list for improvements of the plant styles. However, it's connected to many other parts of how the plants are working and we want to make sure the benefits follow through all the way from data input to output of plans and schedules instead of just fixing one part of the workflow.

     

    Constructive input is very important - make sure your voice is heard by going to the roadmap and leave comments on what you think are the most important for us to focus on - https://www.vectorworks.net/en-US/public-roadmap . Everything posted there is being read and looked at and put into context of workflows and the bigger picture.

     

    • Like 1
  4. Hi Amanda,

    Nice looking planting plan.

    Are you using the plant tag or the data tag? If it's the data tag and you've added it to the viewport (as I would recommend), then you should be able edit the style itself and change the size, or scale it in the settings if that is set to 'by instance'.

    (And if you're using the data tag, they wouldn't scale - they would stay the same even if you're changing the scale of the viewport.)

    However, if you're using the built in plant tag (as I guess you are), then you have to go back to the design layer and change the size there (Text > Size) - you can't do that in the viewport. If you're scaling the viewport, then you're scaling the font as well - they're 'part of the image'.

     

     

    • Like 1
  5. I know this is a basic suggestion, but have you tried the f key to focus on the project (if nothing happens, sometimes you can go into the right-hand structure list and select one object and then use the f)? If you have a site model, it might be at a higher elevation, and sometimes (depending on how clean your file is) your main model won't be centred at import. 

    Site models imports beautifully into TM - plants are a bit more tricky - if you're using image props, they won't be useful in TM. I normally ignore importing trees until the last step and then replace them with TMs native trees (you can 'batch'-replace), as you then get both the growth-ability, seasons and movement.

     

    • Like 1
  6. Hi,

    The Plant tool has 'graduated' in 2022 so plants are now 'true styles' - this has changed a few workflows and you've got many new great possibilities with it.

    You can now use the worksheet to push data back to the plant style itself and hence work more actively with it instead of just using it for a report. This is a huge advantage, for example if you have sent out the plant schedule to a nursery and have received a list of subs or available scheduled sizes. You can then go in and edit the styles via the worksheet instead of having to go in to each individual plant style and change this. This is an important step in keeping the planting plan 'true' to what is being built and something that is often missed in a workflow. 

    You can even change the spread and height of a plant via the worksheet and this will then be adjusted in the drawing.

    However, this has removed the ability to (via the worksheet) put in info, different per each instance of the style - if you change something belonging to the style, it will 'push' to the style itself for all existing instances in the file - hence the warning. You can see the effect this has if you go in to the style and look in the 'Planting Schedule Comments' field - your number has become a part of the plant style itself in the file.

    The only difference for your workflow is that you have to respond 'yes' to the pop-up warning. We can discuss this with the developers and see if it's possible to add an opt-out for the warning, so you don't have to do this every time. Theoretically, this would be possible - however, this is such an important change in how the worksheet interacts with the styles, that it might have to be there. I'll keep you updated on what they say.

     

    I know change is always a bit cumbersome in the beginning, especially if it inflicts on a preferred, ingrained workflow. I do hope you'll find the changes to the plant styles positive as a whole, even if the numbering of the plant list has changed slightly.

    I'm also interested in how you're using the worksheet - I can't see any quantities in the list above, so maybe you're using it as a key or legend? 

    • Like 2
  7. Hi Tara,

    I've just made a quick test of the example you're describing and I only get 25 trees. Can you share your criteria for the selection, please? Maybe I'm missing something?

    You can see below what I've been using. I've summarised the items for Latin name and summed the values for count, hence only one line.

    Screenshot 2022-01-29 at 06.50.25.png

    Screenshot 2022-01-29 at 06.54.39.png

  8. Hi Laura,

     

    The plant tag has been included in the style after requests from many of our users. It also a part of making the plant styles work more like the other styles in Vectorworks. I understand that this new setup doesn’t suit everyone, and I would wholeheartedly recommend using the data tag instead if you find the new settings incompatible with your workflow.

    The data tag is super flexible, you can change the look and the content and you have much more control of the placing of the tags. 
    I was very doubtful to the data tag at the beginning, thinking that ‘I already have a tag in the plant tool’, but I had to eat my hat after using it for a while. 
    The biggest advantage is that you can place the tags in the viewport (where all annotations belong) instead of in the design layer. 
    You can also align the tags much easier working with the data tag. 
    I’ll post a link to a short recording of a good workflow a bit later today. If you still have any questions after that, let me know and we can set up a Zoom to go through it.

  9. Hi, what version are you working in? If you're before 2022, the issue is probably that you have set the Plant tool preferences to a size other than the style setting. The settings here are 'sticky', so if you've used them for one plant, they'll stay on until you manually change them. I suggest to always place all plants with the settings 'use plant style' for all available fields. If you later have to change some instances, you can then do it via the OIP.

    • Like 1
  10. You could use the pad with retaining edge. Set the pad to desired level and then the Landmark > send to surface command, the 'fit the retaining edge' mode. (see screenshot). This will create a nice and even edge at the top, draping the existing site model.

    Screenshot 2021-08-11 at 10.52.24.png

    Screenshot 2021-08-11 at 10.49.33.png

    • Like 1
  11. Hej Lisa,

     

    Yes, unfortunately, it's not possible to create non-vertical edges with the landscape area at the moment, but it's definitely on the wish list!

    At the moment, I resort to modelling. I've modelled some of the most common tree pits and added materials to these, so I can get a report on quantities. 

    If you're calculating C&F, you can then also add site modifiers (3D polygons placed in the Site-DTM-Modifier class) to the edges of the pit.

    I assume you wouldn't need all the detail in your model, i.e. membranes? 
    You can also add things like pipes going through and get the correct volume by subtracting the volume from the pit (the same way as the rootball)

    Screenshot 2021-02-25 at 15.35.02.png

    Screenshot 2021-02-25 at 15.44.28.png

    Screenshot 2021-02-25 at 15.44.02.png

    • Like 1
  12. There is a way to do this but it's a bit involved and everyone opening your file would have to have the same setup, otherwise it won't work (the fields in the plant catalogs and the Plant styles are separate 'entities' so even if you can add anything to the catalog, they'd need a corresponding field in the plant style as well). A better way to do this might be to use one of the existing fields for the specific kind of information that you want to use, even if the 'title' is wrong. (You can change the heading in the worksheet when reporting on the plants or just refer to the field in the data tag, if you're using them). Or, the best would be as Tony suggests, create a record and attach it.

    • Like 3
  13. Hi Scott,

     

    I don't know if you're still looking into this one. I would suggest that you're using Data Visualisation instead of viewport override.

    Attached is a screenshot of two landscape areas in three different viewports. The first one is without any DV, in the second one I've asked it to look at the individual names in the Landscape areas and coloured them different grey according to this.

    In the third one I've done the same thing but asked it to use hatches instead. Of course you can choose anything you want as the parameters, this is just an example.

     

    You have a much bigger scope with Data Visualisation - and from 2020 you can use it in design layers as well, not just viewports (I often use it for planting schemes where I want to see (while I'm working) how much of the planting is deciduous and how much is evergreen).

    Screenshot 2020-08-16 at 13.00.14.png

  14. Yes, you can set them up exactly as you want them. They're much more powerful, AND more future-proof as well - if the same tool is used through all the disciplines and for all different geometry, there will be more reason to develop it and fine tune it.

    Start by using the data tags that comes with Landmark, and when you know exactly what you want, create your own style.

    • Like 1
×
×
  • Create New...