What source data means

A project starts as a selected area, then becomes useful when it receives source data. MapToPlay uses three main input data types: terrain elevation, OSM vector data, and optional imagery.

These inputs are not the finished map. They are raw or processed ingredients that become project assets, then Editor layers, then finally game-ready files through exports.

The three inputs

Terrain elevation, often called DTM in the UI, describes ground height across the selected area. It drives the terrain layer and gives the map its hills, valleys, slopes, and base relief.

OSM vector data describes map features such as roads, fields, forests, water, buildings, railways, and power lines. The vector file stores geometry and tags. A vector mapping collection turns those tags into usable editor layers and categories.

Imagery is an optional raster image for the selected area. It is usually satellite imagery and is most useful as a visual reference or base texture while you edit.

How data enters a project

For each input, the project setup flow can either ask a provider to fetch data for the selected area or accept a file you upload yourself. Provider mode is convenient when you want MapToPlay to pull data from known sources. Upload mode is for prepared files, private datasets, corrected data, or workflows where you already have the source material.

Provider and upload choices are saved in the project metadata. That is why the project detail page can later show DTM setup, vector setup, and imagery setup, retry failed work, or queue replacement processing for a specific input type.

What processing produces

When a provider fetch or upload processing job succeeds, it creates one or more project assets. DTM processing creates terrain assets, OSM processing creates vector assets, and imagery processing creates raster assets.

Assets are the boundary between source data and editing. The Editor reads assets to create layers, but editing happens in project/editor state rather than by mutating the original provider download directly.

Processing statuses

Provider fetches and upload processing run as background tasks. The dashboard shows the same lifecycle for DTM, OSM, and imagery work.

• Queued: accepted and waiting for a processing slot.
• Running: actively being fetched or processed.
• Retrying: a failed attempt is being tried again automatically.
• Completed: finished and produced usable output assets.
• Failed: no usable output was produced after the allowed attempts. Open the task detail or project setup panel to read the error and retry when available.