Settings & Preferences
The Settings menu holds the workspace preferences: how the map behaves, which panels are visible, runtime environment variables, project settings, and the entry point to Manage Plugins.
Map Preferences
Settings → Map Preferences controls how the map can be navigated:
| Setting | Description |
|---|---|
| Restrict map bounds | Limit panning to a bounding box. |
| Bounds | The west, south, east, and north limits of that box. |
| Min zoom / Max zoom | The allowed zoom range (0 to 24). |
| Max pitch | The maximum tilt angle (0 to 85 degrees). |
| Render world copies | Show repeated copies of the world when zoomed out. |
Use Use Current View to set the bounds from where the map is now, or Reset to restore the defaults. These preferences are saved in the project file.
Layout
Settings → Layout toggles the chrome around the map:
- Show toolbar labels: text labels next to toolbar buttons, or icon-only.
- Show project info: the project name and path in the toolbar.
- Show Layers panel, Show Style panel, Show Attribute panel: per-panel visibility.
Panels also auto-hide on small screens for a responsive layout.
Startup workspace
On the desktop app, Startup workspace controls what opens when Meratyn starts. Choose a blank workspace, reopen the last local project, or pin a specific project path. Remote URLs are not fetched by the “last project” mode. When a blank workspace is used, set its default globe/Mercator projection, center, and zoom. An explicit project or data deep link always takes precedence over these device-local preferences. A missing or unreadable startup file is forgotten safely and leaves a blank workspace available.
Environment Variables
Settings → Environment Variables (the Environment tab in the Settings dialog) holds the share token and the runtime key-value pairs that Meratyn and its plugins read, such as API keys:
- Meratyn API token: the personal API token used by Project → Share to upload to the configured Meratyn Share service. See Projects.
- Environment variables: named key-value pairs (for example, API keys for Earth Engine, Street View, and other integrations). You can enable or disable individual variables, and secret values are masked. Variable names must start with a letter or underscore and contain only letters, numbers, and underscores.
Where credentials go Provider credentials for integrations like Earth Engine, Street View, Google Photorealistic 3D Tiles, or other keyed services belong here. See Data Integrations.
Reading AI keys from your system environment (desktop) On the desktop app, the AI Assistant also reads its own allowlisted keys (
OPENAI_API_KEY,ANTHROPIC_API_KEY,GEMINI_API_KEY, and the other provider variables) straight from your operating system’s environment variables — so you can keep API keys out of the saved project file entirely. A value entered here always takes precedence over the OS environment. See AI Assistant → Reading keys from your system environment for the full list.
Protomaps basemaps Protomaps basemaps appear in the New map dialog when a Protomaps API key has been configured for your deployment; when no key is set, that section stays hidden.
Project Settings
Settings → Project Settings (the Project tab) holds project-level options saved with the .meratyn.json file:
- Project name: the name shown in the toolbar and saved in the project file.
- Project file: the read-only path the project was opened from or last saved to.
- Project format: the read-only project format version.
Manage Plugins
Settings → Manage Plugins opens the plugin marketplace. See Plugins & Marketplace.