Mapping Ripening Dates: A Practical Guide to Seed Collection Maps

Seed collection is part treasure hunt, part logistics puzzle. Across southeastern Australia, from the ironbarks of the Hunter Valley to the river red gums lining the Murray, volunteer bushcare groups spend countless hours scouring bushland for viable seed. The hardest part isn't finding a mature tree — it's returning at the right moment when capsules, pods, or fruits are ripe enough to harvest but not so far gone that they have already shed.

A seed collection map that tracks ripening dates transforms guesswork into a coordinated calendar. Rather than relying on memory or a single scout's observations, groups can visualise where each species is approaching maturity, share the workload across weekends, and align nursery drop-offs with peak viability. The result is healthier seedlings, fewer wasted trips down a muddy fire trail, and stronger ties between collectors, growers, and the waterways they are working to restore. The same approach scales neatly from a single Landcare sub-catchment to a multi-council corridor program.

Why ripening windows shift across a single catchment

Ripening is rarely uniform, even within a small patch of forest. A stand of swamp mahogany (Eucalyptus robusta) in a low-lying gully may shed its seed two to three weeks earlier than the same species clinging to a dry ridgeline. Aspect, elevation, soil moisture, and recent rainfall all nudge phenology forward or back. Brisbane bushcarers working the tidal stretch of Kedron Brook have noticed that trees on the northern bank often flower weeks ahead of those on the shaded southern side, simply because of sun exposure. A similar pattern shows up in Hobart's bushland reserves, where the frost-prone hollows hold ripening back well into late summer.

For volunteer programs juggling multiple sites, this variability is both a challenge and an asset. By recording the date when the first fruits begin to colour, when they reach peak ripeness, and when the bulk of the seed has dropped, collectors can plan repeat visits and stagger harvests to capture the widest genetic window. Without that timing data, even a beautiful, well-plotted map only tells you where to go — not when. The same point tree may need to be visited three or four times in a season, and a clear ripening record helps the volunteer team know which Sunday morning is worth the drive.

Building a base layer that supports phenology

The right base layer is the foundation of any useful seed atlas. Many Australian groups start with free public datasets, such as state vegetation maps or the national layers available through the Atlas of Living Australia, and then overlay their own observations. For small programs, Google My Maps or Avenza Maps on a phone offer a low-friction way to drop pins, attach photos, and share a live view with volunteers who may not own a GPS unit. Saturday morning trips to a local Bunnings for tape, flagging, and clipboards have outfitted more than one group's first field season.

More ambitious projects tend to graduate to QGIS, where multiple shapefiles can be combined, styled, and printed for field handouts. QGIS also handles time-stamped layers, which is essential once you begin encoding ripening stages. A common pattern is to keep one polygon layer for site boundaries, one point layer for individual mother trees, and a series of date-stamped annotations that record each visit's observations. Whichever platform you pick, commit to a single source of truth early on, because reconciling three different formats halfway through summer is a sure way to lose a season's worth of data.

Choosing a mapping platform that fits your group

Picking the right tool is less about bells and whistles and more about what your volunteers will actually use in the field. A bushcare group with five regulars and a single laptop has very different needs from a state-wide Landcare network coordinating sixty collectors. Phone-based apps like Avenza and Mergin Maps are ideal for tap-and-go point recording, while desktop software such as QGIS gives you the muscle to style complex legends and print beautiful A3 field sheets. Each option comes with trade-offs in cost, offline reliability, and how easily the data can be time-stamped for ripening analysis.

Tool	Best for	Cost	Offline use	Time-stamped layers
Avenza Maps	Phone-based field collection with PDF basemaps	Free tier, paid plans	Yes	Limited (manual notes)
Google My Maps	Quick collaborative planning across a small team	Free with Google account	Limited	No built-in support
Mergin Maps / QGIS	Detailed projects with multiple data layers	Free for community use, paid support	Yes	Yes, with form inputs
Kobo Toolbox + QGIS	Survey-style data capture feeding into GIS	Free open source	Yes	Yes, via form timestamps

Whichever combination you choose, run a small pilot across two or three sites before committing for the whole season. The pilot will surface quirks like slow phone GPS in steep gullies, basemaps that fail to load in the bush, and permission issues when multiple collectors edit the same point. Sorting these out on a handful of trees is much cheaper than discovering them on the day a hundred volunteers are out.

Encoding ripening stages and verifying in the field

Once the base map is solid, the next step is to design a symbology that communicates phenology at a glance. A simple approach uses a colour ramp for each species, shifting from pale green (early development) through yellow and orange (approaching ripeness) to deep red (peak harvest) and grey (post-shed). Symbols can be combined with letter codes for stages that are hard to colour-code reliably, such as "F" for flowering or "D" for dry capsules ready to fall. Some groups also annotate their maps with weather overlays, since a single heatwave can compress an entire ripening window by a week or more.

When designing the legend, consider how the map will be read in the field on a phone screen as well as on a printed A3 sheet. High contrast and minimal text help, especially for volunteers who may not know the species code. It also pays to be generous with date formats: Australian conventions vary between DD/MM/YYYY and MM/DD/YYYY, and a glance-confusing slip can reorder an entire season's planning. Sticking to one format across the project, and writing it on the legend itself, prevents costly misreads at a glance.

Phenology categories worth recording

Dormant — no visible activity; dormant buds present
Flowering — peak pollen or stigma activity
Maturing — fruit or cone enlarging but not yet coloured
Ripe — full colour, hard seed, ready to pick
Shed — capsules or pods opening, seed dispersing

Field observation checklist

Date and time of observation
GPS accuracy in metres
Weather in the past 48 hours
Estimated percentage of crop at each stage
Photographic reference and any notes on pests

A static map is a stale map. The most successful Australian seed networks treat their atlas as a living document, revisited at least once a fortnight during the harvest season. Volunteers photograph the same branch each visit, building a time-lapse that captures the colour change and can be checked against the recorded phenology code. In the Adelaide Hills, a Friends of Parks group has started uploading geotagged phone images directly into a shared cloud folder, so the map manager can update ripening stages from a desktop without having to visit every site. Melbourne-based groups working along Merri Creek have adopted a similar approach, with shared photo albums linked directly from each map point. For those curious about the silviculture roots of these techniques, the ripening-stage mapping programs trace how earlier generations of foresters approached the same challenge.

Sharing the map, growing the network, and staying compliant

A ripening map is only as useful as the people who can read it. Before publishing, walk through the legend with a new volunteer in person, and produce a one-page field guide summarising the symbols and codes. Print at least one laminated copy for the local library or community nursery, and keep a digital version accessible by QR code on your group's website or socials. New groups can use the Growing Native contact page to request printable templates and starter shapefiles. For cross-state partnerships, exporting both shapefiles and a GeoPDF keeps everyone working from the same ground truth, regardless of their software. A shared map also makes it easier to coordinate with school groups and TAFE horticulture classes who want predictable weekend activity.

Sharing also comes with responsibilities. In Australia, several species are protected under the Environment Protection and Biodiversity Conservation Act 1999, and states impose their own rules on what may be collected and from where. Always check with the relevant state department — for example, the NSW Department of Climate Change, Energy, the Environment and Water, or the Victorian Department of Energy, Environment and Climate Action — before taking seed from a new population, and seek permits where required. Indigenous cultural heritage is another layer to respect: some trees hold significant cultural value, and traditional owners should be consulted before any collection is logged in a shared map. Many Landcare networks now have formal agreements in place with local Aboriginal corporations that streamline this conversation.