The issue that we are having is that we are working on a large subdivision drawing, with several different planting mixes. Each planting mix is applied to numerous different landscape areas, so many separate landscape areas have the same planting mix, as defined in the ‘landscape areas settings’ > ‘plant information’ dialogue box. When a design decision is made to alter a mix (which is happening regularly due to an iterative design process), that change needs to be propagated across several independent landscape areas.
In order to update the mix to all relevant landscape areas, we have been updating the mix in the ‘landscape areas settings’ > ‘plant information’ dialogue box of one of the landscape areas associated with that mix and then using the eyedropper tool to match attributes to the other landscape areas intended to have the same mix.
When we do this, not only does this update the species mix in the recipient landscape area, but the landscape area tag positions also take on the attributes of the landscape area that is used to propagate the changed plant mix.
The landscape areas’ tag positions seem to be controlled by the ‘plug in parameters’ attribute, which seems to encompass many of the attributes of the landscape areas (eg. the planting mix associated with the landscape areas, as well as relative tag positions etc).
In terms of the eyedropper attribute control, this seems to be all ‘lumped in’ to the eyedropper ‘plugin parameters’ attribute, which mean we cannot propagate the change to the planting mix from one landscape area to another, without it changing the tag positions also. It becomes laborious and time consuming to correct numerous tag positions every time a change is made to a planting mix. It seems to be a limitation that has a fairly major consequence for our work flow efficiency…
In short:
1/ We need to be able to match the attribute of updated plant mix information in one landscape area, and propagate this to several other landscape areas without it affecting the individual landscape area tag positions. How can we achieve this?
2/ Have we got our workflow wrong here? Is there a way of creating a particular plant mix or plant schedule that can be associated with several landscape areas, whereby changes to the mix are centrally controlled by one mix schedule and these are linked or associated with multiple landscape areas? – in essence avoiding the matching attributes issue?
Appreciate your advice, help and input. Happy to clarify the issue further, if not clear.