Projects

A Meratyn project captures your whole workspace in a single .meratyn.json file: the map view, the basemap, every layer with its source and style, map preferences, plugin state, and environment variables. Everything in this section lives under the Project menu.

New

Project → New… starts a fresh project. Meratyn offers to save the current project first, then resets the layers, map view, controls, and plugin state to defaults.

Open

Project → Open From contains three entries:

File… opens a .mappview, .meratyn.json, or compatible project .json file.
URL… opens a .meratyn.json project from HTTP or HTTPS. URL projects are not added to Open Recent and have no writable local path.
Gallery… opens the public Meratyn project gallery in the workspace. Choose Open to load a project from its published URL or Open a copy to detach it from the source before editing.

Project → Import contains the format-specific project importers:

QGIS Project… imports a .qgs or .qgz project into the current project.
ArcGIS Pro Map (.mapx)… imports supported layers and services into the current project.

Drop exactly one .mappview or .meratyn.json file onto the map to open it. If the current project is dirty, choose Save, Do not save, or Cancel before it is replaced. Mixed or multiple project drops are rejected as a whole, and a plain .json remains data. Desktop drops are remembered by path; browser drops have no reusable local path.

On desktop, both extensions are registered as Meratyn project files. Opening one from the operating system starts Meratyn with that path. An explicit url or data launch payload takes precedence; otherwise an OS-opened project takes precedence over the configured startup project.

Project → Open Recent lists remembered projects with their name, path, and the time they were last opened or saved. Click an entry to reopen it, use the small remove button to drop a single entry, or choose Clear Recent Projects to empty the list. Desktop entries with native paths can be reopened directly. URL loads are never recorded, and browser file opens or downloads have no reusable local path, so choose File… again when the browser cannot reopen one of those entries.

Loading a project at startup You can open a project directly by passing its URL with the url query parameter, for example ?url=https://share.example.com/you/project.mappview.json. See Embedding & Sharing.

Import QGIS and ArcGIS Pro projects

QGIS project import is desktop-only because browsers cannot read adjacent local data files. ArcGIS Pro .mapx files can be inspected in the browser and can import supported online services; resolving sibling local data requires the desktop app.

When an import skips layers, the completion dialog groups warnings by the message shown to you and sorts the largest group first. For groups with several layers, choose Show layer names to inspect the complete list; duplicate warnings are collapsed and the toggle remains keyboard-accessible. The status summary still reports the number of imported and skipped items.

ArcGIS Pro layers stored in a local File Geodatabase are identified separately from generic format failures. Add feature classes through Add Data → File Geodatabase (GDB); export geodatabase rasters to GeoTIFF before adding them. Warning details contain only sanitized layer names and short format/provider hints—source paths and parser errors are never retained in project state. The same grouped warning surface appears after a dropped vector import when the loader detects coordinates outside WGS84 bounds; review the source CRS before analysis instead of assuming that the values are geographic.

Save and Save As

Save writes back to the project’s existing file path when one is available.
Save As… prompts for a new name and location.

Both capture the current map view, basemap, layers, styles, preferences, and plugin state at the moment you save. In the browser, Save and Save As use the File System Access save picker when available and otherwise download the .meratyn.json file. Projects opened from a URL have no writable local path, so both actions use that save flow. The desktop app is only required for native filesystem integration such as persistent local paths, local MBTiles, and native file associations.

Project → Share… uploads the current project to the configured Meratyn Share service and returns a public URL you can send to anyone or open in the viewer. Sharing uses a personal API token, which you set once as the Meratyn API token in Settings → Environment Variables. The shared file is the same .meratyn.json the app saves locally, so anyone who opens the link sees the same layers, styles, and map view. See the Sharing & Embedding tutorial.

Print

Project → Print… opens the Print panel, which exports the current map to a PDF or image. Choose the page size and orientation, then export. The Print panel is backed by the MapLibre components plugin.

The project format

For the full schema of .meratyn.json, including how layers, styles, and plugin state are serialized, see Reference → Project Format.