This release is a pre-release and may not be stable for production use.
NDS MapViewer CLI
Visualize NDS.Live, NDS.Classic, and GeoJSON map data on a deck.gl-based map
with live style editing, feature inspection, and layer management — all from
a single mapviewer command. No container-runtime knowledge required.
Beta — This Python package is in early development. The CLI interface may change between releases. Feedback and bug reports are welcome via the NDS developer portal.
Full documentation: https://developer.nds.live/tools/mapviewer
Features
- Map visualization powered by deck.gl via erdblick
- Multiple data formats — NDS.Live, GeoJSON, NDS.Classic (member edition)
- Live style editing — modify map styles in real time with YAML-based rules
- Feature inspection — click any map feature to explore its attributes and relations
- Local and remote data — view SmartLayer folders, FileStore files, or remote services
- Guided setup — interactive wizard for creating data source configs
- Config management — save, switch, and delete configs from the RunScreen (
c)
Getting Started
The recommended way to set up your NDS.Live environment (credentials, container registry, pip index) is via ndslive-setup:
pip install ndslive-setup
ndslive-setup
This interactive wizard configures everything you need in one step, including installing nds-mapviewer.
Either Docker or Podman works as the container runtime — Podman is a free alternative if you cannot use Docker Desktop's commercial license.
Usage
mapviewer # HomeScreen (or auto-loads ~/.nds/config.yaml)
mapviewer /path/to/data.ndslive # View a local FileStore
mapviewer /path/to/folder # View a local SmartLayer folder
mapviewer /path/to/geojson/ # View a GeoJSON folder
mapviewer https://host/openapi.json # Connect to a remote service (unauthenticated)
mapviewer --demo # Try it with NDS Islands sample data
mapviewer mywork # Load a saved config by name
mapviewer /path/a.ndslive /path/b # Multiple sources at once
mapviewer --demo --debug # Enable debug logging in the container
mapviewer --demo --env KEY=VALUE # Set a custom container env var (repeatable)
mapviewer --demo --network host # Run the container on the host network
All commands accept -e community|member and -i VERSION.
Remote service URLs
A source can be an http(s) service URL (e.g. mapviewer https://my-host/openapi.json),
which is turned into a SmartLayerTileService. The bare-URL form configures no
authentication — for protected services, proxy them through ndslive-server or
declare the service in a config.yaml with an http-settings block (api-key, basic,
bearer, OAuth2, proxy).
For a service running on your own machine, use localhost/127.0.0.1
(e.g. mapviewer http://127.0.0.1:8080/openapi.json) — it is automatically
rewritten to host.docker.internal so the container can reach it. You do not
need --network host for this.
Container environment variables
--debug turns on verbose logging in the MapViewer container (shorthand for
--env HTTP_LOG_LEVEL=debug). Use --env KEY=VALUE (repeatable, short form
-E) to pass arbitrary environment variables into the container; explicit
--env entries override --debug on key collision. The resulting -e flags
appear in the Docker screen's "Copy Command" output.
Container network
--network NAME attaches the container to a specific network (e.g. a custom
bridge or host). With --network host the container binds the host's port
directly, so --port/--bind are ignored and the MapViewer is reached on its
internal port (8089). Host networking behaves differently across platforms and
runtimes — it is intended as a connectivity workaround.
If ~/.nds/config.yaml exists, mapviewer (with no arguments) loads it
automatically and goes straight to the RunScreen.
If you edit ~/.nds/config.yaml manually, use host paths there, not container
paths. The CLI translates them into the correct container mounts when it starts
the container runtime.
The run screen shows, below the info banner, the source you passed (a config
file or a directly-given data-source path such as a *.ndslive filestore) and
the mapped config that was generated and mounted into the container.
That mapped YAML is a disposable, one-way transformed copy. Map-preset catalogs
configured under erdblick.mapPresets are passed through, but the browser marks
their management surface read-only in CLI-launched sessions; edits are not written
back to the original host config. Edit the host YAML and let the normal config sync
reload it instead. Enabling allow-post-config does not make this generated copy a
durable map-preset write target.
Editions
| Edition | Formats | Access |
|---|---|---|
| community | NDS.Live, GeoJSON, open formats | Free — nds.live |
| member | + NDS.Classic | NDS membership |
Open-Source Building Blocks
- mapget — tile-based map data server with caching
- erdblick — deck.gl-based web frontend with live style editing and inspection tools
License
The MapViewer is a proprietary product of the NDS Association. License terms and conditions are governed by the account type used to access the Docker image — registering for a community or member account includes accepting the applicable licensing terms for the MapViewer and its components.
1 maintainer
Release files for nds-mapviewer 2026.3.2.dev171
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nds_mapviewer-2026.3.2.dev171.tar.gz | 77.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nds_mapviewer-2026.3.2.dev171-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 137.9 kB
Release files / nds_mapviewer-2026.3.2.dev171.tar.gz
| Download URL | nds_mapviewer-2026.3.2.dev171.tar.gz |
|---|---|
| Size | 77.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff01d77ee364ea6301022605e7d45302ed0bfef0aa2a45f58091458b99cecb98
|
|
BLAKE2b-256 checksum How to use checksums |
060d970a6955f4f71068b416163e18a0488617ea82417f2ceaabf5b9eb35570a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logRelease files / nds_mapviewer-2026.3.2.dev171-py3-none-any.whl
| Download URL | nds_mapviewer-2026.3.2.dev171-py3-none-any.whl |
|---|---|
| Size | 60.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8906147789307507a91c9dc7494eb4d0d27066ed45a870c60f0a49a4fd131225
|
|
BLAKE2b-256 checksum How to use checksums |
9b1071d0ccb2a6fc0cb5ebcd381059beae1be77623af20d3869a7589bd94589c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency log
