v2.33.0 (2026-09-10)

Overview

Vite Horizon 2.33.0 adds GeoJSON as a fourth export format in the Filter tool, Road Analysis and the Map Editor.

It also fixes an export failure that had been affecting the Filter tool for some layers, where pressing Export produced only a generic "Export failed" message.

Breaking Changes

None in this release.

New Features and Improvements

Export as GeoJSON

The Export dropdown in the Filter tool, Road Analysis and the Map Editor now offers GeoJSON alongside Shapefile, GeoPackage and KML.

GeoJSON is a single plain-text file, and it is the format most web maps and scripting tools read directly, so it is usually the easiest option if the data is going somewhere other than desktop GIS.

The full list now reads:

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
GeoJSON	A single .geojson text file for web maps and scripting
KML	Google Earth format

GeoJSON and KML are written in WGS 84

The two are grouped together at the bottom of the menu for that reason. GeoJSON and KML are always reprojected to WGS 84 (longitude/latitude), because both formats expect it. Shapefile and GeoPackage keep the map's own projection, GDA94 / MGA Zone 55.

If you need the data in the map's projection, choose Shapefile or GeoPackage.

Like GeoPackage, GeoJSON has no 10-character limit on field names, so long attribute names survive the export intact.

Export from the Filter tool works again on more layers

Exporting filtered features to Shapefile, GeoPackage or GeoJSON could fail on some layers, showing only "Export failed. Please check your filter results and try again." with no indication of what was wrong. That has been fixed.

The cause was internal: for these formats Horizon asks the layer's own service for the full-precision geometry rather than sending what the browser had already drawn, and the identifier it needed to make that request was being removed before the request was built. KML exports were never affected, because they do not use that path.

If you have hit this before, it is worth retrying the export — no change to your filter is needed.

A missing tooltip in the Map Editor

The FIRS button in the Map Editor's Export section had lost its tooltip in the previous release, so hovering it showed nothing. The tooltip is back.

Export options that have not changed

As in 2.32.0, the AI Segmentation tool, My Layers, and the export actions in a layer's three-dots menu in the Layer Panel still offer only Shapefile and KML. FIRS remains a separate button in the Map Editor — a different destination rather than a file format.

Under the Hood

• Adding a format to the Export menu needs matching support on the Horizon server, which writes the file. Both halves shipped together in this release.
• GeoJSON is written to the RFC 7946 standard, which is what guarantees the coordinates are WGS 84 and readable by other tools without extra configuration.