[advice on creating new plants]

On 8/15/2019 at 9:43 PM, Michal Zarzecki said:

In my previous practice, where we used another software, I used to create an array of squares with the associated specification of planting areas (i.e. wither individual species or mixes) and tree/shrub symbols which effectively was my swatch pallet. I would then use the 'Copy Specification' command to populate the planting areas and specimen plants in my project. It was like a blitzkrieg. 

 

Different soft, different methodologies. I would prefer it to be more flexible, but hey-ho! Working out a good and efficient workflow is essential with these tasks, therefore your option is a much appreciated time-saving tip.

 

 

Is a bit more labour-intensive to begin with but then you have your library forever! 🙂

[Landscape area challenges]

Thanks @J. Wallace for posting the question and @Tony Kostreski for find a solution. We just had the same and were able to fix the problem just by changing the layer's scale.  

[Send Objects to Surface...works sometimes, but not always]

I appreciate this is an old post, but in case is of any help to anyone finding this, layers can make a difference.

 

Despite having 'Show/Snap/Modify Others' as Layer Option, if I try to send to surface a mass model/landscape area from the  'Design' layer to the 'Site Model' layer, nothing happens. However if I change the layer of the mass model first, in the object palette, to 'Site Model' and then send it to surface, it does work. The 'Site model' layer also has to be selected as Active layer. Regardless of the 'Show/Snap/Modify Others' option.

[advice on creating new plants]

@bob cleaver and @Michal Zarzecki, not sure if it helps but this has been my own workflow since left college 7 years ago, and I am aware is used in other garden design practices, including the last two I worked with:

 

• I created a separate VWS file, which I am going to call 'Plant Database' file here.
• I collected all plants worth keeping from previous projects in that file.
• When creating a new plant, this can either be created on the new design file and then imported in the 'Plant Database' file or viceversa, depending on which workflow suit best. I prefer creating them in the 'Plant Database' file rather than in the new design file, but occasionally (i.e. in a rush) I do the opposite.
• When working on a planting plan I have the 'Plant Database' file open alongside the design project file, and I access the plant symbol I need from the resource manager palette. This leaves the original plant in the 'Plant Database' file and create a copy of it in the new design file. This is particularly beneficial when let's say one wants to keep the plant's original features (For example sizes at maturity) for future uses, but for a specific project a smaller size is needed. Let's say I have a crab apple with a 5m spread in the 'Plant Database' file but once the plant symbol is imported in the new design file (a small town garden where I know I will not let it grow more then 2.5m),  I can adjust the size accordingly in that project, while keeping the original symbol intact in the  'Plant Database' file for future use. In your case, @Michal Zarzecki you could have generical plant symbols in the  'Plant Database' file such 'Multistem tree', 'Deciduous tree' etc etc,  then amend the label in the new design file into 'Multistem tree 1', Multistem tree 2' etc etc to present the concept/initial design. Once the plants have been decided, you can simply select the generic plant symbol and replace it with a specific plant symbol in the Object Info palette through the 'Replace Plant Style' button.
• You can of course add the 'Plant Database' file in the vws library (Apps---> VWS 19--> Libraries ---> Favourites) , but I prefer to have it as a separate file on the cloud/server. 
• The 'Plant Database' file can be made into a shared working file if appropriate, just make sure everyone is up to speed on how shared projects work to avoid loss of data. You can also divide your 'Plant Database' in perennials/shrubs/trees and whatever category is appropriate to your work. 
• I love seeing the database growing from project to project, and creating planting plans become quicker and quicker each time

 

This is my workflow anyway....hope it make sense and is of any help. Would love to hear what other designers do. 

[Domestic sloped site. Best Workflow for 3D?]

Thank you @Tony Kostreski, will have a good look again at the guides. Currently struggling to create site model despite the survey being in 3D ! 

 

Will keep reading and trying! 

[Domestic sloped site. Best Workflow for 3D?]

Hi there, 

 

I just joined a new practice and moved from years of small, flat gardens (very easy to manipulate in 3D!) to bigger, sloped domestic sites and I am trying to find the best workflow to work into 3D.

 

I do have 2D + 3D surveys and 2D proposed plans. Now, what would be for you the best way to move into 3D? 

 

Perhaps adjust manually the 3D survey to model the land and then extrude from the 2D until they meet? I guess there is a best option and would love to hear about your workflow. 

 

Thank you !