Remote profile

profile is a composition preset. It is not a thirteenth style, a third mode, or a theme. It names default overlays and hides buildings so customer data stays visually dominant.

import { Unmap } from "@unmap/sdk";
 
const unmap = new Unmap({
  key: "um_live_...",
  container: "map",
  style: "muted",
  profile: "remote",
  center: [-114.3718, 62.454],
  zoom: 6,
});

import { Unmap } from "@unmap/sdk";

const unmap = new Unmap({
  key: "um_live_...",
  container: "map",
  style: "muted",
  overlays: ["remote.airports"],
  center: [-114.44, 62.46],
  zoom: 8,
});

?profile=remote on /styles/{style}.json expands to the same overlay set. Prefer muted. Unknown profile values are a 400. When both profile and overlays= are set, explicit overlays win: the profile list is replaced, not merged.

A key without the remote add-on still gets the basemap and the core layers in the preset (parks, aboriginal-lands). remote.airports is 403 addon_required when asked for explicitly. survey.nts still needs legal-land. profile does not change geocode or search routing.

Catalog

Remote 0.2 adds remote.airports. Parks, water, rail, legislative aboriginal lands, and NTS already exist: the profile composes them. It does not duplicate them.

Attribution: Contains information licensed under the Open Government Licence – Canada.

GET /layers is the machine-readable source. Incomplete coverage is never hidden. remote.airports is overlay-only. It is not identify-capable.

See Layers for the catalog contract and Remote map for a live example.