Jump to content

Is there any way to add in additional fields in a Plant symbol?

Flora 9088

Recommended Posts

  • Vectorworks, Inc Employee

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
Link to comment
  • 2 weeks later...
Just now, hollister design Studio said:

I'm using "Water Range" field right now, but to have a dedicated place for WUCOLS would be ideal.


Agreed. Additionally, in WUCOLS a plant can have up to 6 different WUCOLS classifications depending on the designated climate zone, so ideally I would like to be able to reproduce all 6 designations in 6 different fields and then just have a worksheet query the one specific to the given project. We currently work across 3-4 of the different climate zones within WUCOLS, but also want to store ready-to-use plants. Without this, we are constantly changing the WUCOLS information for every project depending on the climate zone.

Link to comment

We have been using the 3 default comment entries in the plant style:

comment 1: CA Native (Y or space)  we like the positive Y and no negative entries 😉

comment 2: Evergreen (Y or space)

comment 3: WUCOLS (VL, L M, H)

different climate zones with different WUCOL ratings would be best handled with a record ??? then is the record attached to a plant database ??? 


Link to comment

@bob cleaver I would like a way to add/reassign/classify custom fields in the Plant Database for each of the 6 different WUCOLS regions.


An example would be

  • Quercus agrifolia
    • WUCOLS Region 1 - North-Central Coastal = LOW
    • WUCOLS Region 2 - Central Valley = LOW

    • WUCOLS Region 3- South Coastal = LOW

    • WUCOLS Region 4 - South Inland = LOW

    • WUCOLS Region 5 - High and Intermediate Desert = INAPPROPRIATE

    • WUCOLS Region 6 - Low Desert = MODERATE

With this data entered in the plant database, theoretically you could then set up a worksheet to just query the correct WUCOLS Region field and all the plants in the project would then display their WUCOLS rating for that region.


Our current workflow is similar to yours where we use COMMENT to adjust the WUCOLS given the current project's location. But if we then use that same plant in another project/region, we have to change the WUCOLS information to suit the project for each plant. The suggested workflow would simply be changing the field query to the correct region, all plants would update.


For WUCOLS research, this type of database customization would also be extremely effective for searching for compliant plants in the database/VW as well, generating a "potential" list depending on WUCOLS and other criteria.

  • Like 1
Link to comment

Would you consider a separate record to hold the WUCOLS data? If so we should be able to get what you need with a nested IF, but a simple worksheet script would probably be better. The WUCOLS record could be connected to just the Symbol Definition and the worksheet script could read it from there. That way you don't have to keep the record  up to date on multiple symbol instances.

  • Like 1
Link to comment

@Pat Stanford I think this could work okay, but I'm not sure if it works as a long-term repository of the WUCOLS data. The WUCOLS data is static, per plant, for each region. It just makes more sense to me if this could be added to the Plant Database for long-term storage of that particular data. We could do the additional record strategy if we're storing the Plants, pre-created, in a Library file (which we do already), but it seems secondary to the Plant Database.

Link to comment

I don't know enough about the Plant Database to know if the data can be stored there or not. Someone with more Landmark/Plant experience that I will have to comment on that.


The Record.Field option is something that can be implemented now (days or weeks, not versions in the future).


I will leave it to the group to tell me if it is worth my time to try an implement or not.

Link to comment

@ericjhberg Filemaker Pro will allow you to do whatever you want to the Vectorworks plant database...

Add fields of data, create custom layouts for printing plant sheets, change the way images look and their quantity, etc..

All of this is then available when browsing plants from Vectorwork's provided Filemaker Runtime reading your database file (.USR)

Doesn't really solve the OP's question, but it is a way to manage the data.


In this example, I created a set of WUCOLS regions as fields.  Each region field can then take on the value from a dropdown.  You can then search for plants for a particular region that have the desired water use classification.


1137390442_ScreenShot2020-09-21at1_24_58PM.thumb.png.27ddf74cceb8963581cb05e139a670cc.png       531064865_ScreenShot2020-09-21at1_40_11PM.thumb.png.a7ffbcbfba851d2bda8b3f06506c8660.png


  • Like 3
Link to comment
  • 7 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...