Geospatial

The map,and everything behind it

QGIS, on a Void Linux desktop of your own.Vector and raster layers, the processing toolbox, and a print layout.

QGIS 4.2.24 cores · 8 GBOpens in a browser tab

hub://qgis

$ dxflow workflow create --identity qgis hub://qgis --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

Layers,then analysis

A desktop GIS with GDAL and GRASS doing the work underneath.

Read almost anything

Shapefiles, GeoPackage, PostGIS, GeoTIFF and WMS or WFS services, in one project.

The processing toolbox

Hundreds of algorithms, chained into a model that repeats on new data.

Print layouts

Scale bars, legends and grids arranged for a page, exported to PDF on the volume.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.

PANEL and TASKBARBoth hidden, so the map canvas has the whole screen. Show either one when a layout window is open beside it.

AUDIOOff here. Turn it on and the desktop sound is streamed beside the picture.

start it your way

$ dxflow workflow start qgis --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start qgis --override env.app.PANEL=show --link

The session

The map canvasfills the screen

Streamed to your browser, with QGIS already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStorageyour files, kept between runs

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

GDAL and GRASSare behind it

The processing toolbox is not QGIS alone. Most of the heavy algorithms come from the libraries underneath.

Formats are GDAL's problem

Shapefiles, GeoPackage, GeoTIFF, NetCDF and the rest open because GDAL is there, not because of a plugin.

Rasters want memory

A large mosaic or a national DEM is a memory problem first. Choose the machine for RAM before cores.

Projects belong on the volume

Keep the data and the project file under /volume so the layer paths still resolve at the next start.

The image

Pulled once,then it stays

QGIS arrives as one image. This is what comes down the first time, and what the disk should have free for it.

936Mamd64compressed, the way the registry counts it

743Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/qgis:latestPublished from the hub, pulled on the first start and kept for the ones after it.

Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.

What it asks for

What it wants,and what it needs

The definition asks for 4 cores and 8 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

4 cores · 8 GBAsks forwhat the definition writes down

2 cores · 4 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

QGIS asks for 4 cores and 8 GB. Cheapest first.

E2 Standard-4

$0.168/ hour4 cores · 16 GBStart this machine

T4g XLarge

$0.168/ hour4 cores · 16 GBStart this machine

C7g XLarge

$0.181/ hour4 cores · 8 GBStart this machine

Run QGIS on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start QGIS Browse workflows