AdminConsole
Enterprise geospatial integration planner

Choose the mGIS contract before mounting the map.

Separate the entitled widget wrapper, twelve Web JS dataset methods, durable dataset/API workflows, and sovereign MIGIST deployments. Each path keeps its own credentials, state, evidence, and production proof.

Plan an integration Run the retail analysis lab
4separate surfaces

Browser wrappers, data methods, workspaces, and sovereign deployments never collapse into one fake SDK.

12Web JS methods

Discovery, maps, feature info, styles, bounds, centroids, catalog, legend, and raster.

8workspace groups

From ingestion and validation to analysis, visualization, imagery, and governed export.

0secrets accepted

Browser-visible access values are placeholders; trusted operations stay behind an application adapter.

Integration contract

Select the surface you operate

No token, widget key, API key, or client secret input is accepted.

local reference

Mappls IGIST sovereign deployment

Evaluate the separate MIGIST SDK/API/Thin Client distribution for sovereign, defence, offline, and air-gapped GIS deployments.

Credential-safe integration boundary
type MigistProvider = "igist-backed" | "migist-native" | "hybrid" | "disabled";

interface MigistCapabilityRouter {
  discover(deploymentId: string): Promise<CapabilityManifest>;
  execute(command: DeploymentCommand, expectedManifest: string): Promise<AuditReceipt>;
}

// Keep engine choice behind MIGIST. The local architecture explicitly says
// uniform IGIST capability routing is not complete across every operation.
Read this plan as JSON
Four products, four truths

Cloud mGIS and sovereign MIGIST are adjacent—not interchangeable.

The browser wrapper and Web methods are short-lived runtimes. Workspace and deployment products carry durable versions, attempts, lineage, permissions, and audit.

01browser-runtime

mGIS integrated widget wrapper

Mount an entitled MGIS.Widget map/workview surface with 2D or 3D view, basemap selection, and basic map controls.

Tenant/workspace plus approved workViewName and application-owned embedding recordThe official page lists Map View 2D/3D, Workview, Basemap Option, and Basic Map Tools and documents MGIS.Widget(container, options). The public repository supplies the hosted widgets.js URL and additionally describes 3D Landmark, Real View, and Tour; those extra families require current contract confirmation.
02browser-runtime

mGIS methods for Web Maps JS

List, render, inspect, style, bound, and visualize entitled tenant or catalog datasets through the documented v1.0 browser module.

Dataset/workspace identity, style revision, view revision, and feature identity copied into application stateThe official method guide documents twelve discovery, visualization, info, style, bounds, centroid, catalog, and raster calls. Two examples contain naming drift and remain selection-required until confirmed.
03workspace-stateful

mGIS dataset and analysis workspace

Build durable ingestion, validation, publication, styling, query, visualization, raster, AI/ML, and export workflows around mGIS resources.

Workspace, immutable dataset version, style revision, analysis attempt, output version, and governed shareThe official overview and public repository establish API groups and lifecycle intent, but several exact operation contracts route to Swagger or API Support. This surface therefore provides a state machine and adapter seam, not manufactured URLs.
04deployment-stateful

Mappls IGIST sovereign deployment

Evaluate the separate MIGIST SDK/API/Thin Client distribution for sovereign, defence, offline, and air-gapped GIS deployments.

Deployment, license, node, release manifest, capability provider, workspace, actor, and audit eventThe local distribution explicitly positions MIGIST as a sovereign product layer over IGIST with SDK, API, Thin Client, licensing, offline assets, and air-gap deployment. Its architecture also states that uniform capability routing and full IGIST adapter coverage are not yet complete.
Web JS v1.0

Twelve documented method surfaces. Two names need confirmation.

The official guide's feature-info and set-style examples do not match their headings. Those rows are deliberately gated.

getLayerListdocumented

List tenant datasets

Fetch datasets visible to the entitled mGIS account.

getMapdocumented

Render a dataset map

Render point, line, or polygon tenant data as a WMS-backed map layer.

getFeatureInfoconfirm exported name

Inspect one dataset feature

Fetch feature attributes at a projected map pixel.

getLegendImagedocumented

Render a dataset legend

Attach the style legend for a rendered tenant dataset.

getStylesdocumented

Read dataset styles

Read the applied style definition for a dataset.

setStyleconfirm exported name

Apply a layer style

Create or update a basic, category, bubble, cluster, heat, chart, or rule-based style.

getBoundingBoxdocumented

Read a dataset extent

Fetch the bounding box of a tenant or scoped layer.

getFeatureCentroiddocumented

Read a feature centroid

Fetch the centroid of one tenant or catalog feature.

getCatalogMapdocumented

Render a Mappls catalog layer

Render an entitled Mappls administrative catalog dataset.

getCatalogFeatureInfodocumented

Inspect a catalog feature

Fetch attributes for one clicked Mappls catalog feature.

getCatalogLegendImagedocumented

Render a catalog legend

Attach the legend for a rendered Mappls catalog layer.

getRasterCatalogMapdocumented

Render a raster catalog layer

Visualize an entitled raster catalog dataset such as a night-light layer.

Durable workspace

Operate the dataset, not just the tile.

Exact URLs and auth come from the entitled account contract. The application persists every dataset version, analysis attempt, style revision, output, share, and export identity.

Study the complete state machine
  1. 01

    Search & navigation

    Batch geocode, reverse-geocode, and routing layers from tabular inputs.

    asynchronous derived dataset
  2. 02

    Data operations

    Save/append/truncate, describe, list, type, and read datasets.

    versioned dataset
  3. 03

    Layer styling

    Create and revise thematic visualization rules.

    style revision
  4. 04

    Dataset query & validation

    Filter, join, aggregate, transform, and save results.

    analysis attempt and output
  5. 05

    Layer visualization & info

    Render maps, feature info, and legends.

    view revision
  6. 06

    Raster catalogue

    Discover and visualize entitled raster datasets.

    catalog reference
  7. 07

    Satellite AI/ML

    Run entitled imagery segmentation workflows.

    long-running model job
  8. 08

    Feature export

    Export governed output into documented geospatial formats.

    export request and artifact
Six-state lifecycle

Every provider result remains a candidate until your application commits it.

01
Product and workspace owner

selected

Surface, account/tenant, region, entitlement, data class, and source contract are approved.

02
Application adapter

configuring

One bounded configuration references stable workspace/dataset/workview identity and no server secret enters the browser.

03
Host lifecycle

active

One instance or job owns listeners, requests, cancellation, retries, and observable health.

04
Application domain

candidate

Provider output is schema-checked and normalized; it has not silently replaced durable state.

05
Application repository

committed

A versioned record binds actor, source, provider identity, input revision, and event.

06
Application and workspace administrator

retired / disposed

Runtime resources are released; durable datasets, lineage, permissions, and audit follow policy.

Full journey, ready to inspect

Prioritize retail sites with governed evidence.

The maintained Retail Site Lab demonstrates dataset ingestion, analysis attempts, review, share, revocation, idempotency, and recovery across eight tests. It links the mGIS API and widget source guides instead of manufacturing a live entitlement.

Run and download the app Read the API source guideRead the widget source guide