Skip to content

Help test RustGIS v0.6.0: new features and existing workflows #748

Open

Description

@deniial00

RustGIS v0.6.0 is out! We'd like your help checking the new features—and making sure the most important workflows from earlier releases still work reliably with real projects and data.

Start with your normal workflow. Open a project, add data, style or edit it, run an analysis, and export the result. You don't need to work through every area below. Projects created in v0.5.0 or earlier are especially useful for checking compatibility and regressions.

v0.6.0 keeps the app responsive and puts the work on paper: tools, exports and large reads run in the background with progress and Cancel, layouts export as vector PDF and SVG, maps gain pie and bar diagrams and label callouts, editing gains Cut Polygon, Reshape and Trace, new tools check and repair geometry, and CityJSON, ArcGIS protocol buffers and cloud-optimised GeoTIFFs read in place.

Use v0.6.0 as the release baseline. If you test a newer development build, include its version or commit so results can be distinguished.

This is a list of major testing areas, not an exhaustive changelog or a list of known bugs. The release notes contain the full change list.

New in v0.6.0

Area What to try Related PRs (examples)
Background work, Cancel and memory limits Run tools from the Tools pane and the Analysis pane (raster tools, Zonal Statistics, Viewshed, Interpolate), the Classification Wizard, Deep Learning, models and scripts, and gp.batch over many inputs. Add Data and the Export Features, Export Raster, Export Map and Export Layout commands read and write in the background too. Check that the window stays responsive, progress counts, Cancel stops the work (a cancelled tool adds nothing), and results match v0.5.0. Try data too big for your computer: it should stop with a message, not crash. #1317, #1404, #1458, #1372
Layouts and publication output Export layouts, reports and printed maps as vector PDF and SVG, with map frames and surrounds kept as vectors: zoom in on text, lines and frames, and open the SVG in a vector editor. Try legends in up to three columns, arrangements and a favourite for publication layouts, scale bars with a colour and a fill, and copying a layout's page to the clipboard. Compare PDF, PNG and SVG exports, then save/reopen and check placement and typography. #1359, #1367, #1494, #1392
Diagrams, labels and expressions Try pie and bar diagrams from several numeric fields (also on extruded and tilted layers); labels with callouts, Show All Labels, the Move Label tool, alternate places along lines, and text, size, colour and angle set by expression; Unique Values by expression; Invert Color Ramp. Measure areas and lengths in a chosen unit in expressions. Check different scales, exports and installed fonts, and queries with null values. #1048, #1128, #1309, #1314
Tile styles, terrain and 3D export Open MapLibre styles with raster-dem sources (drawn as hillshade and colour relief) and sprites, and check a tile layer's opacity fades its icons and labels. Use terrain from the active DEM layer (View › Scene). Export a layer as OBJ or binary STL. #1215, #1294, #1280, #1431
Editing and geometry tools Cut polygons, reshape features and trace along an edge while drawing. Run Check Geometry and Repair Geometry and compare what they report with the shapes. Try Tabulate Intersection, Points Along Lines, Rasterize onto a chosen grid, Polygon To Line, Split Line At Vertices, Feature Envelope To Polygon and Unsplit Line, and summary fields on Dissolve and Summarize Within, against results you can verify. Exercise undo/redo. #1351, #1417, #1443, #1293, #1306
More data, read in place Open CityJSON city models (footprints with heights), ArcGIS feature services (read as protocol buffers, in pages for large layers), cloud-optimised GeoTIFFs as raster layers (or a window of one by bounding box), a Shapefile by its .shp address, WFS layers past a server's page limit, and JAXA Earth's data cubes on the time slider. Find places with the PDOK Locatieserver geocoder. Check that the data lines up with a trusted source, and that notices say what an import left out (Z/M values, columns, field names). #1300, #1327, #1339, #1244, #1557
New exports Export the map view as a GeoTIFF placed on the ground, a tile layer's tiles as a GeoTIFF, and a layer into an existing GeoPackage as an added or replaced table. Open the files in another GIS—not only the preview—and check that notices say what an export approximated or wrote as null. #1566, #1619, #1403, #1281
Coordinate systems Compare alignment with trusted reference data for the newly read sinusoidal, Robinson, orthographic and Mercator systems, and for GeoPackages that give their system as WKT only. Check data near the poles and across the antimeridian, and that a system belonging to another body is refused rather than placed in the wrong spot. Check the status bar's UTM and MGRS readouts, copies and search. #1463, #1478, #1396, #1429
Web services and logins Log in to web services with basic auth or an API-key header (kept for the session), and check HTTPS servers against your system's certificate trust. Add layers from long service lists (past the first 2000, by name), and add and remove layers in Add From Service while the map keeps its zoom. Use test credentials; never include secrets in reports. #1223, #1282, #1526, #1195
Workspace, scripting and Assistant Try the History pane (tool runs and the session log, filtered, saved as CSV or JSON Lines, or copied back to the Script pane), custom themes as JSON files and the interface scale, hiding and reordering attribute table columns, and Check for Updates › Download and Install on Windows. Check translated interfaces (now including Greek and Lao). In Python, add_data returns a list when a file adds several layers. Try the Assistant with the new Requesty and TrustedRouter providers, and check approvals, denied permissions, and that a plugin command shows it has started. #1324, #1151, #1497, #1624, #1423, #1559

Still critical from earlier releases

Re-check these on v0.6.0; they are the workflows where a regression costs the most.

Area What to try Related PRs (examples)
Saved projects Open projects saved by v0.5.0, v0.4.0 or v0.3.0, then save and reopen: check layers, order, styles, labels, layouts, and any notice about what was repaired or skipped. Move a project and use Repair Data Source. #886, #1629
Edits saved to a source Edit a GeoPackage or PostGIS table, save the edits back, and check that a conflicting change is refused. Exercise undo/redo, then save and reopen. #1045, #671
Large datasets Open large Shapefile, GeoPackage, FlatGeobuf and GeoParquet files in place. Pan between areas, use Load All Features, and check that full-data operations include the expected features—not only the visible area or first service page. #1131, #1116
Map rendering Use GPU rendering, raster/vector tiles and tilted or terrain views. Pan and zoom repeatedly; look for missing features, stale tiles or labels, and thin or missing small polygons. #570, #1132
Coordinate alignment Compare with trusted reference data, including Shapefiles with missing or incorrect projection information. Try Define Projection, undo it, and save/reopen. Check exported coordinates and datum warnings. #850
QGIS import Import supported QGIS projects and styles, and compare appearance, labels, filters and import notes with QGIS. #876, #1421
Saved credentials Save connections, remembered database passwords, S3 keys, and ArcGIS and ChatGPT sign-ins. Restart, reconnect, replace and forget them. Use test credentials only. #915, #884, #1037

Availability and limits

  • Desktop and browser capabilities differ. Tools, models, scripts, Add Data and exports run in the background with progress and Cancel on the desktop; the browser has one thread. Native database/FileGDB access, OS keychain storage, autosave, installing updates, and saving edits back to GeoPackage and PostGIS tables are desktop-specific. Large Shapefiles open in place on the desktop only. Some formats require optional GDAL or DuckDB installations. Service loading still depends on server capabilities and limits.
  • Memory limits follow the computer's memory on the desktop. A raster, dataset or project too big for it is refused with a message; the web app uses fixed, smaller limits.
  • Large layers are read a view at a time. Editing, Define Projection and field calculations need Load All Features first, up to the read limit.
  • GPU rendering remains beta. Tilted/terrain views and extrusions are not a general-purpose 3D scene with full Z-coordinate support.
  • QGIS import is partial compatibility, not a complete project migration. Review import notes for approximated or skipped content; QGIS print layouts are not imported.
  • PDF and SVG layout exports keep vectors where they can. Text, shapes, map frames and surrounds stay vectors; rasters, web tile layers, tilted or globe frames, and hatch, dot and shapeburst fills are pictures, and a frame whose vectors would pass the size budget is drawn as a picture with a notice. Viewer font substitution can change text appearance in SVG.

Share your results

Found a problem? Please open a bug report rather than burying the reproduction in this thread. Include:

  • RustGIS version or commit, operating system, and browser if applicable;
  • workflow and steps to reproduce;
  • expected versus actual results, including whether it worked in v0.5.0 or v0.4.0;
  • a small shareable dataset or public data/service URL where possible;
  • relevant errors, logs or screenshots, with passwords, tokens and other sensitive information removed.

Link the report here so others can find it.

Successful tests are useful too. Comment with the build, platform, dataset format/approximate size, workflow you tried and how you checked the result. Real-world data, large datasets, unusual coordinate systems and comparisons with trusted results are especially valuable.

Thanks for helping test RustGIS.


This is a community testing hub. Keep it focused on major workflows; fold related updates into existing areas instead of adding a row for every feature or fix.

Activity

  1. pinned this issue on Oct 23, 2026
  2. elpidioassinaturas commented on Oct 24, 2026

    @elpidioassinaturas
    Contributor

    Thanks for putting this together. Some of mine merged after it was written (23 October), and a couple of rows could name what they cover. Suggested updates:

    Time-dependent data & analysis

    Layouts & publishing

    Smaller user-facing fixes, if you want them listed

    The rest of mine are listed and described correctly: #359, #386, #443, #482, #511, #518, #523, #573, #575, #590, #594, #601–#605, #675, #678, #696, #698, #706, #709.

  3. deniial00 commented on Oct 24, 2026

    @deniial00
    MemberAuthor

    Thanks @elpidioassinaturas for checking the list and providing these references—especially the clarification about #507.

    I've condensed the issue into a shorter set of broad testing areas rather than an expanding feature changelog. The aim is to highlight changes that affect shared behavior or substantial workflows.

    For your suggestions:

    I haven't given #751 or #477 separate entries under that narrower scope, but they're useful cases for remote-file loading and coordinate-system testing. #477 is linked in the coordinate-systems area; its handling of explicit datum shifts is relevant beyond the SIRGAS naming improvement.

    The shorter list doesn't reference every related PR, but keeps the broader workflows covered without adding a row for each feature or fix.

  4. changed the title [-]Help test RustGIS: major features since v0.3.0[/-] [+]Help test RustGIS v0.4.0: new features and existing workflows[/+] on Oct 25, 2026
  5. pskeffington commented on Oct 25, 2026

    @pskeffington

    Completed a reproducible, synthetic-only RustGIS CLI validation contribution for issue #748 and would welcome maintainer review of the optional test pack.

    Executed results

    • Official v0.4.0 Linux release: 16/16 synthetic CLI scenarios PASS, with independent Shapely/pyproj/Fiona reference checks.
    • Source-built development revision f3aaf35de7db4f1c394c7b69e314b0322fe6b3ec (Ubuntu 24.04, Rust 1.95): 16/16 synthetic cases PASS, plus 8/8 separate public McDowell GeoJSON/GeoPackage interoperability checks, with no observed semantic drift versus v0.4.0.
    • The public verification workflow passed: patch applicability to newer upstream source c7bf8e1f9ebe82d25ee56f76a1aa6c43b4cd98ec, 13/13 source-file hashes, 37/37 Python tests, independent reference/plan checks and the actual 16-case v0.4.0 CLI execution. The public run includes an aggregate evidence artifact. The executable at c7bf8e1 has not been tested; that revision was used only for patch applicability.

    Public, immediately reviewable contribution

    The generated fixtures cover projected CRS/CSV XY import, polygon boundary and spatial-join behavior, null/missing geometry, geodesic lengths, multipart/interior-ring fidelity, GeoJSON/GeoPackage round trips and PNG export. There are no actual household, utility or county geometries in this patch. It introduces no Rust crate or Cargo dependency and uses only four optional Python reference libraries.

    This is not a full validation of GUI editing, saved-project migration, GPU/raster workflows, databases or cloud integrations. The one known invalid source served-area polygon in the separate real-data test is a source-quality warning, not an established RustGIS defect.

    Would the maintainers prefer this as an additive optional regression-test PR, or as issue-linked test coverage? The patch is public for review; I have not modified RustGIS branches or opened an upstream PR.

  6. deniial00 commented on Oct 25, 2026

    @deniial00
    MemberAuthor

    @pskeffington Thanks for testing v0.4.0 and sharing the results, especially the comparisons with other GIS libraries and the clear coverage limits.

    For now, let’s keep this as issue-linked test coverage rather than bring the full validation pack into RustGIS. A separate Python testing framework and its dependencies would add more maintenance than we want to take on here.

    There’s no need to open a PR for the full pack. If you find a RustGIS failure or discrepancy, please open a focused bug report with a minimal synthetic dataset, the command you ran, and expected versus actual results. We can then add a targeted regression test within the existing test suite.

    The linked results are useful as a contribution to this testing effort—thanks again.

  7. changed the title [-]Help test RustGIS v0.4.0: new features and existing workflows[/-] [+]Help test RustGIS v0.5.0: new features and existing workflows[/+] on Nov 1, 2026
  8. changed the title [-]Help test RustGIS v0.5.0: new features and existing workflows[/-] [+]Help test RustGIS v0.6.0: new features and existing workflows[/+] on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions