v2.30.0 (2026-08-12)

Overview

Vite Horizon 2.30.0 makes the Style Editor a tool you can simply open. Until now, clicking its toolbar button did nothing unless you had already picked a layer somewhere else — it showed a "No Layer Selected" message and refused to open. The panel now opens on its own and offers a Layer dropdown listing every layer it can style.

The release also restores State Growth Routing, adds GeoJSON to the file types you can upload, and makes several Style Editor messages visible that were never actually being shown.

Breaking Changes

The "Symbol Preset" picker has been removed

A Symbol Preset dropdown has been removed from the Style Editor. It required a combination of conditions that could never both be true, so in practice it never appeared on screen and never applied anything when it did — nothing you could do before is now impossible.

Preset handling for editor layers is unchanged: the Style Editor still detects the matching preset and says which one it is using, still marks complex server-defined symbols as read-only, and still offers a preset dropdown for server-defined symbols on non-Sketch editor layers.

See Editor Layer Symbols in the Style Editor guide.

New Features and Improvements

The Style Editor opens on its own and picks its own layer

Open the Style tool from the toolbar and the panel now opens straight away, with a Layer dropdown at the top. Choose a layer from that list and the styling controls fill in for it.

Nothing about the old route has changed — Change Style on a layer in the Layer Panel still opens the Style Editor and pre-selects that layer, and choosing a different layer while the panel is open re-points the panel at it.

Two messages tell you where you are before a layer is chosen:

No Layer Selected — Pick a layer from the dropdown above to edit its symbols and labels.

No Styleable Layers — No visible feature or map image layer is on the map. Turn a layer on, then reopen this dropdown.

Which layers appear in the list

The dropdown lists the layers the Style Editor can genuinely style — feature layers, map image layers, and uploaded CSV and WFS layers — and only those that are actually drawn on the map. A layer sitting inside a switched-off group is not offered, because styling it would change something you cannot see.

The list is re-read from the map each time you open it, so layers you add, remove, or switch to a different layer type appear and disappear as you would expect. If the layer you are styling is removed from the map altogether, the selection clears rather than leaving the panel pointed at something that is no longer there.

Layer types that cannot be styled here

Imagery and raster layers, tile layers, WMS layers and graphics layers are not offered, and choosing Change Style on one of them now explains why instead of opening an empty panel:

Cannot Style This Layer — This panel edits vector symbology for feature, map image, CSV and WFS layers. Raster symbology is set in the Imagery Tool, under Report Tools.

Raster symbology belongs to the Imagery Tool.

Editor layers

FPP, Plan Burn, Wildfire and Cart Route layers are system-managed — their symbols are predefined — so they are not in the dropdown at all, and Change Style on one of them reports:

Style Panel Restricted — Style editing is disabled for this editor layer. Symbols are predefined and managed by the system. Only Sketch editor layers support custom styling.

Sketch layers are deliberately the exception: they can be styled.

TIP

If you switch off a layer while you are styling it, it stays selected so the panel does not empty out underneath you.

Messages that were never being shown now appear

Several explanations inside the Style Editor were silently invisible. They are now displayed:

• the notice that a map image layer contains no sublayers that can be styled;
• the server-defined symbol and read-only complex-symbol notices;
• the confirmation after you click Update Style;
• the explanation of why Update Style is switched off.

That last one is now two separate messages, because there are two different reasons. A system-managed editor layer cannot be styled at all. A layer that failed to load is a different, retryable problem, and says so:

This layer could not be loaded, so its style cannot be edited. Check that the service is reachable, then pick the layer again.

State Growth Routing works again

The State Growth Routing tool was pointing at the wrong address for the State Growth road-network service and failed to start, reporting "Cannot load route service." It now uses the working address, and routing, distances and turn-by-turn directions work as before.

See the State Growth Routing guide.

Uploading GeoJSON

The Upload tool now accepts GeoJSON files (.geojson and .json) alongside Shapefile, ZIP, KML, GPX and CSV. Drag one onto the upload dialog, or browse for it, exactly as with any other format.

The coordinate system is worked out for you. Standard GeoJSON is always latitude/longitude (WGS 84); older files that name their own coordinate system are read too, and Horizon tells you which system it used — including when a file's declaration contradicts its own coordinates and had to be ignored.

Uploads that finish with less than you handed over now say so instead of reporting plain success. If part of a file could not be used, a warning appears above the result:

Some features were skipped — 12 of 300 features had no geometry, or a geometry type Horizon doesn't recognise, and were skipped. The remaining 288 were added to the map.

And when nothing in the file can be drawn, the map is left exactly where it was rather than jumping to an empty result:

Nothing to add to the map — This file was read successfully but produced no shapes Horizon can draw — every geometry in it was empty or of a kind Horizon has no equivalent for. The map has been left where it was.

Files that are not valid JSON, are not GeoJSON at all, or contain no features with geometry each get their own message naming the problem.

See the Upload guide.

Under the Hood

• Switching the Advanced Editor between docked and floating no longer stalls. Because every editor stays loaded once opened, a single dock click was previously moving all of them at once, which briefly froze the interface — noticeably so with snapping switched on over many layers. Only the editor you are actually looking at is moved now.
• The Style Editor's layer list watches the map's layers directly, so it keeps up with a layer being replaced — for example when its type is switched, or when a bookmark rebuilds the map — instead of quietly styling a layer that is no longer on screen.
• Both ways into the Style Editor now apply the same rule about which layers can be styled, so the panel can no longer be opened onto a layer with no controls in it.