16 May 2026

How To

Custom Types and Custom Attributes

Custom Types and Attributes

Why this matters

Every garden records information a little differently.

You may want a plant type called “Herbaceous”, a landmark type called “Water Feature”, or extra fields such as “Soil pH”, or “Last pruned”.

BotanicalMapper gives you two ways to shape your workspace: Custom Types and Custom Attributes.

In short
  • Types are category labels and colours for plants and landmarks
  • Attributes are extra fields for plants, landmarks, areas, and shapes
  • Definitions are set up once per workspace
  • Values are filled in on each individual record

Where to manage definitions

Go to:

Settings → Customise

You need to be signed in and using an active workspace.

The Customise tab has two main sections:

  • Custom Types
  • Custom Attributes

Definitions belong to the active workspace. If you switch workspace, you may see a different set of types and attributes.

Custom Types

Use Custom Types when the default plant or landmark categories are not specific enough.

Plant Types

Default plant types are read-only:

  • Tree
  • Conifer
  • Shrub
  • Perennial
  • Other

You can add your own, such as:

  • Herbaceous
  • Fruit Tree
  • Fern
  • Rhododendron

Landmark Types

Default landmark types are also read-only:

  • Place
  • Amenity
  • Building
  • Other

You might add:

  • Event space
  • Water point
  • Sculpture
  • Compost area

Custom types include a name and colour. Plant type swatches appear round on the map and in filters. Landmark type swatches appear square.

Adding a type

  1. Open Settings → Customise
  2. Go to Custom Types
  3. Choose Plant Types or Landmark Types
  4. Click Add Type
  5. Enter a name and choose a colour
  6. Save

You can click an existing custom type to edit its name or colour.

Deleting a type

If you delete a custom type, BotanicalMapper asks you to confirm.

Any records using that type are moved to Other. The records themselves are not deleted, but the change cannot be undone automatically.

Custom Attributes

Use Custom Attributes when you need extra fields on your records.

They can apply to:

  • Plants
  • Landmarks
  • Areas
  • Shapes

In Settings → Customise, open Custom Attributes. You will see tabs for:

  • Plants
  • Landmarks
  • Areas
  • Shapes

Each tab has its own definitions. A plant attribute does not automatically appear on landmarks or areas.

Attribute data types

When creating a custom attribute, choose the data type carefully. You cannot change it later.

  • Text - Flexible notes, codes, sources-“Hillier 2022”, “Raised from seed”
  • Date - A specific date-“12/03/2025”
  • Number - Measurements or scores-“6.5”, “120”
  • Selectable List - A fixed set of choices-“Low / Medium / High”

Creating an attribute

  1. Open Settings → Customise
  2. Go to Custom Attributes
  3. Choose the correct tab, for example Plants or Areas
  4. Click Add New Custom Attribute
  5. Enter Attribute Name
  6. Choose Data Type
  7. For Selectable List, add at least one option
  8. Save

Attribute names must be unique within that entity type.

After creation, you can rename an attribute. For Selectable List attributes, you can also add, edit, or remove options.

You cannot change the data type. If you choose the wrong type, delete the attribute and create a new one.

Definitions vs values

This is the most important distinction.

A definition is the field you create, such as “Soil pH”.

A value is what you enter on a specific record, such as “6.8” for one bed or “7.2” for another.

Filling in values on the map

Once attributes exist, they appear when you edit records.

On the Map page:

  1. Select a plant, landmark, area, or shape
  2. Open its details panel
  3. Edit the record
  4. Find CUSTOM ATTRIBUTES
  5. Fill in the values
  6. Save

The custom attributes section appears only when at least one attribute has been defined for that entity type.

In edit mode, Manage Custom Attributes opens the definition panel if you need to add or adjust fields.

Filling in values in the Spreadsheet

Custom attributes also appear as columns in the Spreadsheet after definitions exist.

You can:

  • Edit values inline
  • Use Bulk Edit for many rows
  • Review custom fields alongside built-in fields

You may need to refresh the page after creating new definitions.

For plants and landmarks, import can also map spreadsheet columns to custom attributes, which is useful when migrating from an existing spreadsheet.

A good workflow is:

  1. Create your custom attributes first
  2. Prepare your CSV or Excel file
  3. Import plants or landmarks
  4. Map columns to the correct custom attributes

Using custom types on records

Custom types appear in the Type dropdown when editing plants or landmarks.

The selected type affects:

  • Marker colour on the map
  • Filter chips
  • Spreadsheet type values
  • How records are grouped visually

Custom plant types appear only on plants. Custom landmark types appear only on landmarks.

Who can change definitions in teams

In team workspaces, definitions are controlled by workspace admins.

Workspace admins can:

  • Add, edit, and delete custom types
  • Add, edit, and delete custom attributes

Other members may see a read-only message explaining that only Team Admins can change definitions.

However, members can still fill in values on individual records if they have permission to edit those records.

So the rule is:

  • Admins manage the schema
  • Team members can enter data into that schema

Solo use is treated as admin for your own workspace data.

Workspace scope

Custom types and attributes belong to the active workspace.

That means:

  • A “Soil pH” field in one workspace does not automatically appear in another
  • Custom types are shared with teammates in that workspace
  • Values are stored on the individual records in that workspace

If you switch workspace and something seems to disappear, check that you are in the workspace where it was created.

Public maps

If your workspace uses public map publishing, you can control which custom attributes visitors see.

On Your Public Map, you can choose custom attribute visibility per entity type:

  • Plants
  • Landmarks
  • Areas
  • Shapes

This controls public display only. It does not delete the attribute or change the private workspace data.

Importing a legacy spreadsheet

  1. Review your existing columns
  2. Decide which should become custom attributes
  3. Create those attributes first (or while mapping columns)
  4. Import plants or landmarks
  5. Map the columns during import

Tips and pitfalls

  • Plan your data types before importing large files
  • Use Selectable List for controlled terms, such as condition or priority
  • Use Text when values vary widely
  • Deleting a custom type moves records to Other
  • Deleting an attribute removes that field from the UI
  • Duplicate attribute names are rejected
  • Members should ask an admin to add new fields, but can still fill values

Troubleshooting

Can't add Custom Types or Custom Attributes

Likely cause - Only Workspace Admins can create or edit Custom Types and Custom Attributes.

Custom Attribute isn't shown on the record

Likely cause - No Custom Attributes have been defined for that entity type, or the Custom Attributes section is currently collapsed.

Wrong field format

Likely cause - The attribute's data type was chosen when it was created and cannot be changed afterwards. Create a new attribute if you need a different field type.

Custom Type isn't available in the list

Likely cause - The type may have been created for a different entity (for example, under Plants instead of Landmarks), or it hasn't been created yet.

Import column won't map to a Custom Attribute

Likely cause - The Custom Attribute must exist before you import your data. Create the attribute first, then run the import again.

Closing checklist

  • Opened Settings → Customise
  • Added needed plant or landmark types with colours
  • Created custom attributes under the correct entity tab
  • Chosen suitable data types before importing
  • Filled values on the Map or in the Spreadsheet
  • Configured public attribute visibility if publishing a map

Schema planning worksheet

Before adding fields, ask:

  1. Is this a type, or an extra field?
  2. Which entity needs it, plants, landmarks, areas, or shapes?
  3. Should values be free text or a fixed list?
  4. Will this be imported from an existing spreadsheet?
  5. Should visitors see this on the public map?
Articles