v2.32.0 (2026-09-03)

Overview

Vite Horizon 2.32.0 adds GeoPackage support in both directions: you can now upload a .gpkg file to the map, and export to .gpkg from the Filter tool, Road Analysis and the Map Editor.

The per-format export buttons in those three panels have also been replaced by a single Export dropdown, which describes each format as you choose it instead of leaving you to work out the difference between them.

Breaking Changes

None in this release. Existing Shapefile and KML exports are unchanged, and every file type you could upload before can still be uploaded.

New Features and Improvements

Upload a GeoPackage

The Upload tool accepts .gpkg alongside Shapefile, KML, GPX, GeoJSON and CSV.

A GeoPackage can hold several feature tables in one file, and Horizon adds each one as its own map layer. When there is more than one, the layers are named <file name> - <table name> so you can tell them apart in the Layer Panel.

GeoPackage has a smaller size limit than other formats

Every other upload format is capped at 100 MB. A GeoPackage is capped at 55 MB, because it is read on the server rather than in your browser. A larger file is refused straight away with a message saying so, rather than failing part-way through the upload.

Every table must declare its own coordinate system. Horizon never guesses one — a GeoPackage is expected to record its spatial reference, so a table without a usable one is skipped and reported rather than being placed at a guessed location, which could put it thousands of kilometres from where it belongs.

If some tables cannot be mapped, Horizon now tells you which ones and why in a single summary message, instead of quietly adding fewer layers than the file contained. If none of them can be mapped, the upload reports that clearly.

One Export dropdown instead of a row of buttons

In the Filter tool, Road Analysis and the Map Editor, the separate SHP / KML / GeoPackage buttons have been replaced by one Export button that opens a list of formats.

Each entry now explains itself, so the choice is made in the menu rather than by trial and error:

Format	What you get
Shapefile	A zipped .shp bundle — the most widely compatible option
GeoPackage	A single .gpkg file that keeps full attribute types and long field names
KML	Google Earth format, always written in WGS 84

Why you might pick GeoPackage over Shapefile

A Shapefile stores its attributes in the older DBF format, which shortens every field name to 10 characters and supports a limited set of column types. A GeoPackage has neither restriction, so a field called ConservationStatus stays ConservationStatus instead of becoming Conservati.

Shapefile and GeoPackage keep the map's projection (GDA94 / MGA Zone 55). KML is always written in WGS 84, because that is what the format requires.

Export options that have not changed

Three places that export geometry still offer only Shapefile and KML: the AI Segmentation tool, My Layers, and the export actions in a layer's three-dots menu in the Layer Panel. This is deliberate rather than an oversight — those routes were left as they were in this release.

FIRS remains its own button in the Map Editor. It is a different destination rather than a file format: it sends the shapes to the FIRS system in WGS 84.

Under the Hood

• A GeoPackage is a binary SQLite database, so unlike the other upload formats there is nothing for the browser to parse. The file is sent to the server, read there, and each feature table comes back with its own coordinate system for Horizon to reproject — which is why it resolves far more coordinate systems than the browser-side formats can.
• A multi-table import no longer counts a table that failed to load as one that succeeded, so a file whose tables all failed reports the failure instead of reporting success.