Skip to content

An Elbit Systems product

The map engine
inside mission systems.

One native engine for maps, terrain and analysis — built into your application, running on your data, online or fully offline.

WINDOWS · LINUX · ANDROID · WEBASSEMBLY · x86_64 + aarch64 (LINUX)

Built with MapCore

A real application, running the real engine.

Not a video and not a mock-up. The window below embeds a working application built on MapCore — the same native C++ core, compiled to WebAssembly and running in your browser. Pan it, tilt it, zoom into the terrain. Every frame goes through the same interfaces your own application would call.

demo.mapcore.com Live — MapCore WebAssembly Open in a new tab ↗

Loading the MapCore engine…

The live demo did not load.

The application may be temporarily unavailable, or a network policy may be blocking the embedded frame. Opening it in its own tab usually works.

Your browser is too old to show this.

Update your browser to its latest version, then open this page again.

The hosted demo is not published yet.

This application runs today, but it is not yet on a public address we can embed.

A reference application on the MapCore WebAssembly build, served from its own origin and embedded here unmodified.

The engine

What one map engine does

Not a suite of products. One native core and one API contract, mirrored into four languages — every capability below is part of the same engine, sharing the same data and the same coordinate system.

Rendering

One engine draws all three dimensions.

Raster, elevation and vector data render as 2D, 2.5D or full 3D from the same layers — no second engine, no second data path. The map lives inside a window your application owns, not beside it.

See the details
From the MapCore reference application

Elevation

From one height query to full terrain analysis.

Load a DTM and the scene becomes terrain you can question: heights, profiles, extremes, and what a sensor on a hill can really see. The same elevation that draws the ground answers the analysis.

See the details
From the MapCore reference application

Data

Your data, read where it lives.

Imagery, elevation and vector data load in place or convert to a fast native format — from local files, OGC services, PostGIS or the Map Layer Server. Existing SLD, ArcGIS LYRX, MapLibre and KML styles come with it, and a disk cache keeps remote layers working when the link drops.

See the details

3D models

Buildings and meshes as part of the scene.

3D Tiles models and buildings extruded from your vector footprints share one terrain with the rest of the map. Where a model covers the ground, the terrain beneath steps aside — no double surface.

See the details
From the MapCore reference application

Imagery

From raw imagery to measured ground.

Sharpen, balance and equalise imagery at display time, per viewport and per layer, without touching the pixels on disk. Camera models for frame and LOROP sensors, orthophoto and mosaic production, and DTM generation from point clouds are part of the same SDK.

See the details

Object world

Everything that moves, over everything that doesn't.

Tracks, symbols, sensor footprints and 3D models are live objects over a static map, styled once by a shared scheme. APP-6(D) and MIL-STD-2525(C) symbology is built in.

See the details
From the MapCore reference application

Overlay manager

One object database. Every window.

One object database renders in every window at once — 2D and 3D, any scale, any projection. Move a track once and every view agrees.

See the details
From the MapCore reference application

Calculations

Geospatial maths that runs with no map on screen.

Line of sight, area of sight, geometry and geodesy run with no map on screen — even in a calculations-only WebAssembly build. Put the analysis on a server, in a container, or behind a thin client.

See the details
From the MapCore reference application

Edit mode

The interaction layer you would otherwise write twice.

Measuring, panning, sight-line tools and shape-aware vertex editing, already built for 2D and 3D. Your rules stay in your code through callbacks, permissions and constraints.

See the details
From the MapCore reference application
Elbit Systems

Who builds it

Built by a defense company, for defense systems.

MapCore is an Elbit Systems product, made for defense and military applications — C4I, mission planning, simulators and navigation.

Its documentation, API reference and release history are open for you to check — 81 releases documented.

Where it runs

Four languages, one contract

The same 134 interfaces in every binding, named to each language’s idiom.

  • 134 interfaces, the same in every language
  • 4 languages, one API
  • 81 releases documented

See the API Name Map ↗ · Is the C++ API different on Windows and Linux? No.

Generally available

Host your map data once. Stream it to every client.

A standalone server that streams your map layers and answers spatial queries over HTTP. Optional — every client also runs on its own.

Tooling

Drive MapCore from the terminal or an AI agent

Preview Not generally available. Names, commands and packages shown in the documentation are illustrative and may change before release.

For developers

The rest of this is documentation, and it’s already written.

MapCore exposes one native C++ interface contract — the IMc* interfaces — mirrored into C#, TypeScript and Java. The Developer Center has the guides, the generated C++ and TypeScript API references, the name map showing how a single interface is spelled in each language, and runnable getting-started code with synchronized language tabs.

Documentation and the full API reference are open to everyone. SDK packages require access credentials.

Put a map inside your application.

Read the guides and the full API reference — everything you need to start building.