MilX Layers: the .milxlyz Military Overlay Format

Layers are how map.army keeps a tactical situation organised, and MilX® is the format those layers are saved in. This page explains what a MilX layer is, how to set one active so you can draw on it, how saved files are named, and what happens to your layers during a session. The operations themselves — creating, saving, loading and deleting — live in Layer-Manager.

What a MilX layer is

A MilX layer holds the military symbols you draw for one part of a situation — typically grouped by phase, unit, or sector. MilX is an XML-based format built around MIL-STD-2525 symbology, so a saved layer keeps every symbol’s geometry and its editable attributes (affiliation, echelon, status, labels) — not just a flat picture.

MilX layers are only one kind of map overlay. The Layers menu also carries vector layers and image layers such as orthophotos, and a MilX file does not contain any of them — they sit alongside your MilX layers in the app but are left behind when you save as MilX. An online one travels in a share with the project settings; one from a local file does not. See Import Overlays for how each layer type is handled.

The map.army Layers panel with the demo layers listed, including the Vector and Image layer groups

The active layer

Exactly one MilX layer is active at a time, and the layer list marks it with a pencil icon. The active layer is the one you are working on: new symbols are placed onto it, and it is the layer whose symbols you can move or delete.

The MilX layer list with the pencil icon marking 'New Layer' as the active layer
  • Click a layer name to select it, and read the icon you get back: a pencil means the layer is active and editable (its tooltip is Active (editing) layer), while a checkmark means the layer is selected but read-only (Selected layer is Read-Only). Only the selected layer carries an icon at all — the other rows show none.

    The selected read-only layer Boundaries shows a checkmark instead of a pencil
  • A layer you have just created becomes active immediately, so the next symbol you draw lands there. A layer created from a template may start without the pencil; click it once before placing symbols.

  • Switching the map to 3D view and back deactivates the working layer. Re-activate it after returning to 2D.

Hint: If the Add Symbol button looks greyed out, or a symbol you are trying to move or delete will not respond, no layer is active — or the wrong one is. Check which row carries the pencil before looking any further — and if that row shows a checkmark instead, the layer is read-only and nothing will draw on it until you select an editable one.

How saved files are named

When you save your work, map.army writes it to a local file on your own device with the .milxlyz extension — the compressed MilX variant. Loading reads a local file back the same way; nothing is stored server-side unless you deliberately create a MilX Share. The name is generated for you and carries a date-time group, so repeated saves never overwrite each other.

A saved file name has three parts: the layer name, a date-time group and the file extension.

In the diagram: 1 the layer name (for several layers, a collection name); 2 the date-time group; 3 the file extension. Two examples:

  • One layer — the layer’s own name plus the timestamp, e.g. New Layer_16095317ZApr26.milxlyz.
  • Several layers at once — bundled into a single file, e.g. LayerCollection_17114814ZAug26.milxlyz.

The timestamp reads as day, hours, minutes, seconds Zulu, then month and year — 17114814ZAug26 is the 17th of August 2026 at 11:48:14 Z. You can replace the suggested name with your own before confirming the save.

Because the layer’s own name becomes part of the filename, naming layers well pays off twice: once in the layer list, and again in your file system months later.

Layers in an open session

While map.army is open your layers live in the page, and closing or reloading the page loses them — there is no autosave. Treat an open session exactly like an unsaved document.

Closing the browser tab discards the work in it; exporting to a file keeps it.

In the diagram: 1 closing the tab without exporting loses the work; 2 exporting to a .milxlyz file keeps it.

What the application can remember is where your work came from, not the work itself: the last share link, a web address, or a folder you granted it access to. It then offers to fetch the content again. The full picture — which of the three applies to you, and what each one does not cover — is on Session persistence.

Hint: A saved local .milxlyz file is your only durable copy — it can be re-loaded later, moved to another machine, or sent to another map.army user. Save early and often; see Layer-Manager for how.

Where to go next

When you need a copy that lives server-side instead of on your device — for sharing, or as an extra backup — create a MilX Share instead of (or in addition to) saving locally; see How to create a share.

Last updated: