Get started
What MapCore is
MapCore is a map engine you embed in your own application: a rendering engine for geospatial data, plus the calculations that go with it — line of sight, spatial queries, coordinate conversion, photogrammetry.
It is a library, not a service. There is no MapCore server to call and no tile provider behind it: you supply the data, and it renders on the machine it runs on, offline if that is what you need. You also keep control of the things a library should not take from you — you own the window and you own the frame loop. Nothing is drawn until your code asks for a frame.
What you get for that:
- 2D and 3D from the same data. One terrain, viewed as a flat map or a perspective scene, with elevation, 3D models and extruded buildings when you have them.
- Many sources, one model. Raster imagery, vector data, elevation, 3D models and static objects, either read where they sit or converted to MapCore's own format for speed. Local files and OGC web services alike.
- Symbology and interaction on top of the map, in a layer of overlays that is separate from the terrain, so annotating a map never means rewriting it.
- Calculations, not just pixels. Visibility, intersections, distances and grid conversions, against the same terrain you are displaying, using the GPU where it pays.
- The same API on four platforms, which is the next section.
Five object types carry almost everything: a device is the engine, a viewport is one view into the world with its cameras, a terrain groups the layers that hold your data. Architecture is the ten-minute version of how they relate; the Quickstart puts them on screen.
Choose your platform
| Platform | You write | Install |
|---|---|---|
| Windows | C++, or C# on .NET | Install on Windows |
| Linux | C++ | Install on Linux |
| Browser | JavaScript or TypeScript, via WebAssembly | Install for the web |
| Android | Java (Kotlin interoperates), or C++ through the NDK | Install on Android |
The engine is the same C++ on all four. What differs is how you get a drawing surface — a window
handle, a canvas, a GLSurfaceView — and, on the web, that start-up is asynchronous.
Server-side and batch work is a case worth knowing about early: a device created with ERS_NONE
has no rendering system at all, so it needs no GPU and no display, and everything except viewports
and GPU queries still works. That is how you run MapCore's data handling and geometry in a
container or a headless build step.
Choose your language
There is one API, defined by the C++ interfaces, and three wrappers that mirror it. The
interface names, the object model and the call order are the same everywhere, which means an
example in another language is still a useful example: IMcMapViewport in C++ and Java is
IDNMcMapViewport in C#, and the sequence of calls does not change.
What genuinely differs is worth knowing before you start, because it is the part that does not translate line by line:
| C++ | C# | Java | JavaScript / TypeScript | |
|---|---|---|---|---|
| Errors | returned as IMcErrors::ECode | thrown | thrown | thrown |
| A single or main output | an out-parameter | returned | returned | returned — a list comes back as a JS array |
| Additional outputs | out-parameters | out and ref parameters | ObjectRef<T> | .Value holder objects — a list arrives in .Value as an array or typed array, or fills an array you pass; see each method's declaration |
| Lifetime | AddRef() / Release() | Dispose(), plus a collector to drive | Release(); no AddRef() | AddRef() / Release() |
Porting therefore removes code rather than translating it: the error check after every call
becomes a try/catch around a block of them. Language surfaces
covers all of it, including which parts of the API are not exposed everywhere.
Where to go next
- Quickstart — device, viewport, layer, camera and a frame, in four languages. Start here if you have MapCore installed.
- Architecture — the five object types and how they fit together.
- Coordinate systems — world, screen, window and image frames, and the units of each. The most common source of "it renders, but in the wrong place".
- Threading and lifecycle — MapCore's main thread, what may be called from where, and who owns what.