Glossary
Terms as this documentation uses them. Where a term names something in the API, the interface is given so you can find it in the API reference.
The object model
Device — IMcMapDevice. The engine instance: it owns the rendering device and every viewport
created from it, and releasing the last one tears MapCore down. Created first, released last.
See Architecture.
Viewport — IMcMapViewport. One rendered map surface, attached to a window. It owns its
cameras and holds the terrains mounted into it, and it decides the map type — 2D, 2.5D or 3D.
Terrain — IMcMapTerrain. A coordinate system plus a set of layers, mounted into one or more
viewports. Layers do not attach to a viewport directly; they attach to a terrain, and the terrain
is what a viewport shows. See Layers and terrain.
Layer — IMcMapLayer and its family. One source of map content: imagery, elevation, vector
features, 3D objects, a code or material grid. Six kinds, distinguished by ELayerKind.
Overlay — application graphics drawn on top of the map: markers, lines, polygons, text, pictures. Managed by the overlay manager rather than as map layers, because they are yours rather than the map's.
Zero initial reference count — no MapCore function adds a reference for its caller: a device,
a terrain or a layer arrives from its Create() with a reference count of zero. Mounting a
terrain or a layer into its owner is what gives it its first reference. This is the rule most
often missed; see Who owns what.
Rendering
2D / 2.5D / 3D — a viewport's map type. Flat map, imagery draped over elevation with a constrained camera, and a full 3D globe. One viewport can change between them.
Camera — IMcMapCamera. The eye: position, orientation and scale, orthographic or
perspective. A viewport can hold several and has one active at a time.
World, screen and window — the three coordinate frames. World is the terrain's own system, screen is pixels from the viewport's bottom-left, window is pixels from the window's top-left. Confusing the last two is a common source of off-by-a-height bugs; both are defined exactly in Coordinate systems.
Tile — a square piece of imagery or elevation, fetched and rendered on demand as the camera moves. The unit in which layers read, cache and report progress.
Data and geodesy
Raster layer — imagery: orthophotos, satellite, scanned maps. See Add a raster layer.
DTM (Digital Terrain Model) — the elevation surface. One per terrain, and what makes 2.5D and 3D possible. See Add elevation.
Vector layer — geometric features (points, lines, polygons) with attributes, drawn from data rather than from imagery, and styled at render time. See Add vector data.
Static objects — fixed 3D content: models converted from a 3D source, and buildings extruded from vector contours. See Add static objects.
Code and material layers — grids of classification values rather than pictures: a code per cell, or a material per cell driving traversability. See Code and material layers.
Geographic coordinates — latitude and longitude on a datum.
Geocentric (ECEF) coordinates — Earth-centred, Earth-fixed Cartesian X/Y/Z in metres.
Datum — the reference model of the Earth's shape that coordinates are measured against, WGS84 being the usual one. A vertical datum does the same for heights, and choosing the wrong one displaces elevation by a real amount rather than failing.
Projection — a transformation from the curved Earth to a plane, so a 2D map can be drawn.
Native server — MapCore's own Map Layer Server, serving converted layers to clients over HTTP. A layer that reads from it is a native-server layer, and Install the Map Layer Server on Linux is where its documentation starts today.
The web build
WebAssembly (WASM) — the compiled binary format MapCore ships in for the browser: a portable, near-native runtime.
embind — the Emscripten mechanism that exposes the C++ API to JavaScript/TypeScript, producing the global
MapCore namespace the @mapcore/wasm-* packages provide.