Share Vector and Image Layers from Online Sources

Beyond MilX symbology, map.army can publish vector and image layers that point at an online source (a URL) through the standard MilX Share workflow. Recipients of the share link see the layer with no file upload — the application fetches the content from the URL each time the share is opened. This is the path for KML / GeoJSON endpoints and for online-hosted raster overlays.

Add a layer from an online source

  1. Open the Layers Menu → Add Layer → Online.
  2. Paste the URL of the vector or image asset and confirm.
  3. The layer is added to the current map. Configure transparency / visibility as for any other layer.

Supported online sources include:

  • Vector layers — public KML / GeoJSON endpoints, or any URL that returns a supported vector format.
  • Image layers — direct URLs to PNG, JPG, or WebP assets, plus the matching world file (e.g. .pgw / .jgw) for georeferencing.

Share the online-source layer

Once the online-source layer is on the map, the standard MilX Share workflow applies:

  1. Open Map Overlays → Share Military Map → Create New MilX Share as for any layer.
  2. Move the online-source layer into the Share MilX Layer section via Layer Manager (see How to create a share — Add layers to your share).
  3. Save the share. Recipients now see the online-sourced content via the same link.
Hint: Because the layer content is fetched live from the URL each time, the original host must remain reachable for recipients to see it. If the source URL changes or goes offline, the shared layer becomes broken for everyone. For more stable sharing of a one-off map, export the layer to a local MilX file and share it as a normal MilX layer instead.

When to prefer this over a MilX-only share

A regular MilX share embeds your MilX symbology in the share itself; an online-source share leaves the underlying content at the URL. Use the online-source path when:

  • The data is already published at a stable URL by someone else (a public KML feed of unit positions, a hosted overlay image).
  • The data changes over time and you want recipients to always see the latest version without your having to push updates.
  • The image overlay is too large to be practical to embed.

For static one-off maps, a plain MilX share is simpler and survives the source going offline.