Samples
Complete applications, one per surface, each doing the same core work — initialise, create a viewport, load a raster layer over a DTM, drive the camera — so you can read the one in your language and recognise the shape in any other.
Each is packaged as a ZIP on the portal. The sources live in the MapCore repository, and the ZIPs are built from them at release, so no repository access is needed. Downloads are credential-gated: sign in first.
Try it without installing anything
The Playground runs the real MapCore WebAssembly build in a browser tab — write against the live API with completion from the shipped type declarations, press Run, and watch it work. Two samples load with a click: a raster-over-DTM map drawn into a canvas, and coordinate conversion with geodesy that needs no map on screen at all.
It needs a desktop browser. The engine is a large download, fetched only when you ask for it, and the page reserves roughly a gigabyte once running.
C#
WPFMapCoreExample — a full WPF application: initialisation, viewport setup, raster layers, DTM terrain, overlays and coordinate operations. The one to read first if you are writing C#.
MapCoreWinFormExample — the same example in WinForms.
Both need Visual Studio 2022. See Install on Windows for the runtime prerequisites, and Language surfaces for the one thing a C# application must do per frame that C++ does not.
JavaScript / TypeScript
web-tester — a browser application consuming @mapcore/wasm-32, covering WebAssembly
start-up, layers, overlays and the edit modes. It is also the quickest way to confirm your
registry access works, because it runs from a published package rather than a build:
Run the web tester.
Needs Node 18 or newer.
Java
McDemo — an Android Studio project using MapCore through the JNI bridge, including the
Activity lifecycle integration that Android makes you get right. minSdkVersion 21; see
Install on Android.
Note the one platform-specific API difference while you read it: on Android ViewportResized()
must be passed the new width and height, because MapCore cannot obtain them from the window. On
every other platform passing a size is an error.
C++
The same MapCore calls on both platforms; only window and context creation differ.
MapCoreCppExample (Windows) — an MFC/Win32 application showing the OpenGL render loop, layer loading and overlays.
LinuxTester (Linux) — an X11/GLX application making the same calls, set up for GCC on AlmaLinux and Ubuntu.
Read Threading and lifecycle alongside either. C++ is the surface where the reference-counting rules — and the zero-initial-count rule for terrains and layers — are yours to get right rather than the wrapper's.
Also in the SDK
The Windows installer ships tools you can drive against your own data before writing any code: MCTester exercises most of the API interactively, and MCVectorEditor, McMapProductionTool and McObjectSchemeConverter cover vector editing, map production and object-scheme conversion. Install on Windows lists what lands where.