Why MapCore
A map engine that does the work, not just the drawing.
MapCore shows the world, measures it, analyses it and keeps working when the network is gone. Here is why programs choose it.
-
A library, not a service.
MapCore runs inside your application, on your machines, with the data you supply. There is no MapCore server to call and no tile provider behind it, so it keeps working when the network does not.
Proof Remote layers are cached to disk and stay usable after the link is gone.
See it on the platform page → -
Calculations, not just pixels.
The terrain on screen is the terrain the analysis runs on. Line of sight, area of sight, best observer positions and traversability come from the same engine and the same data — no export, no second tool.
Proof Many spatial queries run on the GPU.
See it on the platform page → -
From imagery to intelligence.
Sensor imagery becomes measured ground inside the same SDK. Camera models for frame and LOROP sensors, orthophoto and mosaic production, image correlation and DTM generation from point clouds sit next to the map, not in a separate toolchain.
Proof Display-side image processing — filters, colour tables and histograms that follow the visible area — per viewport and per layer, with the pixels on disk untouched.
See it on the platform page → -
Speaks the language of the mission.
Military symbols and nautical charts are standards, not drawings. MapCore builds them in, so an operator sees the symbology their doctrine defines.
Proof APP-6(D) and MIL-STD-2525(C) symbology, and S-52 styling for S-57 nautical charts.
See it on the platform page → -
One API, every platform.
The same interfaces, the same methods and the same behaviour in C++, C#, Java and TypeScript. Code and knowledge move between desktop, server, mobile and browser teams instead of being rewritten.
Proof The same 134 interfaces in every language, on Windows, Linux, Android and WebAssembly.
See the API Name Map ↗ -
Works without a screen.
Create MapCore with no rendering at all and everything except the viewports still works — no GPU, no display. Run the same analysis in a container, a build step or a browser worker.
Proof A separate calculations-only WebAssembly package, considerably smaller, for spatial queries without a map.
See it on the platform page →
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.
Put a map inside your application.
Read the guides and the full API reference — everything you need to start building.