Skip to content

v2.20.0 (2026-07-16) ​

Overview ​

Vite Horizon 2.20.0 catches two mistakes that used to pass silently: exporting shapes that overlap each other, and uploading a bare .shp file with the wrong coordinate system selected.

Breaking Changes ​

None in this release. Both checks are no-ops when nothing is wrong.

New Features and Improvements ​

Overlapping geometry is detected before export or save ​

Drawing the same shape twice in the Map Editor used to export or save duplicated, stacked geometry with no warning. Before an export (SHP, KML, FIRS) or a save to a My Layer, the editor now checks whether any shapes overlap each other at the same location and, if they do, opens an Overlapping Geometry Detected dialog offering:

  • Merge — combine each overlapping group into a single feature; non-overlapping shapes are untouched
  • Keep Separate — proceed with every shape exactly as drawn
  • Cancel — go back and edit

Only like-with-like shapes are compared, and edge-touching polygons or lines that merely cross at a point are not flagged. If nothing overlaps, the dialog never appears.

See the Map Editor guide.

Uploads check the coordinate system of a bare .shp ​

A standalone .shp file carries no coordinate-system information — that lives in the .prj file, which is only present in a ZIP. Horizon now samples the coordinates of a bare .shp and reports what it found:

  • Coordinate system auto-corrected — your selection did not fit but another system placed the data correctly in Tasmania; the dropdown is updated and the corrected system is used
  • Selected coordinate system looks wrong — the coordinates are the wrong kind for your selection (degrees where metres were expected, or the reverse)
  • Shapes appear outside Tasmania — usually the wrong MGA zone
  • Coordinate system taken from your selection — nothing looked wrong

ZIP uploads containing a .prj are unchanged; they already read the coordinate system from the file.

See the Uploader guide.

One case cannot be detected

Two systems for the same zone that differ only by datum — GDA94 / MGA Zone 55 and GDA2020 / MGA Zone 55, about 1.8 m apart — both place the data correctly in Tasmania, so your selection is kept. Only a ZIP with a .prj resolves this.

Under the Hood ​

  • Overlap detection compares bounding boxes first and only then computes exact intersections, so an export of many shapes is not slowed down noticeably.
  • Whichever choice you make in the dialog, each remaining shape is saved as its own feature, so non-overlapping work is never merged as a side effect.

Horizon Help Documentation