Plan4Better

← All changes

What changed in October 2026

15 changes

New26 October 2026

Add workflow results to a dataset you already have

The Save as dataset step of a workflow can now add its rows to a dataset you already have. Choose Existing dataset instead of New dataset and pick the target. Each run adds its rows to that dataset, and the step shows how many were added.

You need edit rights on the target dataset. The step tells you if you do not have them.

Fix26 October 2026

Fixes in v3.0.10

  • Dashboards without a consent banner no longer store cookies in visitors’ browsers. Visits are still counted. With the banner on, nothing changes.
Enhancement13 October 2026

Closest-average heatmaps without a travel time limit

When you set a Reference area in Heatmap - Closest Average, the travel cost Limit no longer applies for walking, cycling, pedelec and car. Destinations outside the area count too, and every cell gets its real average travel cost, however far away the destinations are. Cells that are not reached within a limit no longer drop out of the result.

Public transport still uses the Limit. A reference area can cover at most 200,000 cells for walking, cycling and pedelec, and 40,000 for car.

Fix13 October 2026

Fixes in v3.0.9

  • Accepting an invitation to an organization no longer keeps the roles you held before. You get the role you were invited with, and a user who already belongs to an organization can’t accept a second invitation.
New11 October 2026

Number fields that count up on their own, and unique IDs

Two new field types let GOAT fill in a value for every new feature, whether you draw it, add it in a table or create it in a batch. A serial field gives each feature the next running number, starting where you choose, and never hands out a number twice, even after a feature is deleted. A UUID field gives each feature a unique ID.

New11 October 2026

Templates can give every user their own copy of a dataset

When you save a template, you now choose for each dataset how the people who use it receive it. A dataset can still be shared read-only. It can also be copied, so that every user gets their own editable version, either with all its rows or empty, with only the fields, field settings and style.

Enhancement11 October 2026

Shared templates show up under the space they were shared into

A template shared with your organization or team used to appear only under Everyone in the template list, although Content showed it inside the organization space. The Organization and Team filters now find it too, whether it was shared on the template itself or on a folder above it.

A new source, Shared with me, lists templates that were shared with you alone. Each template is listed under the space it was shared into. This works in the workflow, layout and Home template pickers.

Enhancement11 October 2026

Zoom the workflow canvas out much further

The workflow canvas used to stop zooming out at half size, which is too close to see a large workflow as a whole. It now zooms out to a tenth.

Enhancement11 October 2026

Workflow variables can have a label and a description

A workflow variable keeps its technical name for references such as {{@name}}. It can now also have a display label and a short description, so people who run your workflow see what each value is for.

Fix11 October 2026

Fixes in v3.0.8

  • Copying or importing a project no longer changes numbers in the Dashboard that only looked like layer IDs, such as shadow or opacity. These copies could not be opened before.
  • Dashboard interaction rules, such as visibility sync and tab switching, work in a copy or import of a project. They used to keep pointing at the original.
  • Blank lines in a Dashboard’s rich text are kept instead of disappearing.
  • The first run of a workflow in a copied project, or a project made from a template, keeps the description, tags and column settings of the layer it replaces.
  • An empty layer, such as one you draw your planning into, keeps its geometry through export and import. It can be shown again and used in workflows.
  • A custom SQL node no longer fails on an empty intermediate result when it uses spatial functions.
  • Stray bounding-box columns from older GOAT versions no longer show up in field lists or get carried into joins, SQL and tool results.
  • The workflow preview of a join lists the columns the run really writes, with the join_ prefix. A SQL node written against the preview no longer fails.
  • Using a template inside a project shows the layers it adds right away, without a reload.
  • Someone who may use a template that was shared through a folder can now read the datasets it ships. Projects made from it no longer miss those layers.
  • Sharing a template with a person, team or organization outside your own organization is refused before anything is saved.
  • In a print layout, Verdana, Garamond and Consolas print in fonts of similar width, so text wraps as it does in the editor.
  • Legend labels you edit in place wrap at spaces, so a title no longer pushes the last legend entry out of its box in print.
  • Opportunity inputs in workflow tools show a proper label as tooltip instead of a generated title.
  • More of the German interface is translated, and dates in the header, job list and time picker follow the language.
New7 October 2026

Ask for help and follow your support tickets inside GOAT

You can now open a support ticket from the support menu in the GOAT header, attach files, and follow the conversation inside GOAT. When our team replies, you get an email with a link back to the ticket.

You can answer, mark a ticket as solved, reopen it, and rate the help you got. Owners and admins of an organization see all of its tickets. The link to the documentation has moved into the same menu.

Enhancement7 October 2026

See which steps of a workflow you cannot run, and why

In a shared project, a workflow can use datasets you are not allowed to read. Until now the run failed with “Resource not found” and nothing more.

Now the workflow editor marks the affected nodes as failed, names them, and suggests what to do: ask the owner to share the datasets, or use Replace datasets… to choose your own.

Enhancement7 October 2026

Workflow templates keep the style of their results

When you save a workflow as a template, GOAT now remembers how you styled each exported result. Anyone who uses the template gets the same colours and symbols on their first run, instead of the tool’s default style.

Project templates already worked this way. An export that never ran before you saved the template still uses the default style.

Fix7 October 2026

Fixes in v3.0.7

  • Workflows run again when their network is left on the default network.
  • ÖV-Güteklassen use the name and position of the main station, not of one of its platforms.
  • When you export a project, its workflows take along the datasets they use, as long as you can read them. A dataset you cannot read is left out, and the workflow asks for a new one after the import.
Fix6 October 2026

Fixes in v3.0.6

  • A project’s custom basemap now always shows when you open the project. You no longer briefly see the previous project’s basemap.
  • In a folder with many datasets, folders and projects are listed first instead of moving to later pages.
  • Styling and filtering by a yes/no field now works correctly.
  • Datasets shared with a team or organization now appear when you add a layer from that space, not only on the Content page.
  • Uploading a dataset is called Upload dataset everywhere, with the same icon.
  • Searching the Catalog with an area filter uses the exact shape of the area instead of a rectangle around it, so the results fit the area better.

Looking for the technical log? github.com/plan4better/goat/releases

Ready to make sense of your data?

Ask GOAT your first planning question, or build the analysis yourself. No GIS expertise needed.