GITNUXSOFTWARE ADVICE
Science ResearchTop 8 Best Cave Survey Software of 2026
Compare the Top 10 Cave Survey Software picks for 2026 by features and workflows. Explore cave mapping tools like Survex and QGIS.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Survex
Survey adjustment with loop closure and station error estimates from text survey scripts
Built for cave survey teams needing repeatable adjustment and mapping from shot data.
QGIS
Custom Python processing tools for transforming survey attributes into spatial layers
Built for cave teams needing advanced mapping, validation, and scripting flexibility.
GeoJSON.io
Interactive map drawing with live GeoJSON export
Built for quick cave map sketching and GeoJSON preparation for GIS or custom tooling.
Related reading
Comparison Table
This comparison table evaluates cave survey and geospatial tooling across survey drafting, data preparation, and map export workflows. It covers dedicated cave surveying options alongside GIS and geospatial databases, including Survex, QGIS, GeoJSON.io, PostGIS, SQLite, and related tools, highlighting how each handles spatial data formats and editing. Readers can use the table to match tool capabilities to common tasks such as importing survey measurements, managing coordinates, storing features, and generating shareable map outputs.
| # | Tool | Category | Overall | Features | Ease of Use | Value |
|---|---|---|---|---|---|---|
| 1 | Survex Survex provides text-based cave surveying processing to compute survey traverses, adjust errors, and generate detailed cave maps. | survey processing | 8.3/10 | 8.9/10 | 7.4/10 | 8.4/10 |
| 2 | QGIS QGIS provides open tooling to visualize cave survey exports, manage layers, and generate map products from survey-derived data. | GIS mapping | 7.6/10 | 8.0/10 | 7.2/10 | 7.4/10 |
| 3 | GeoJSON.io GeoJSON.io supports interactive editing and validation of GeoJSON that can be used for cave survey outlines, survey traces, and derived features. | geodata editing | 7.4/10 | 7.1/10 | 8.3/10 | 6.8/10 |
| 4 | PostGIS PostGIS provides spatial database capabilities to store cave survey points, lines, and derived measurements in a research-grade backend. | spatial database | 7.5/10 | 8.0/10 | 6.7/10 | 7.6/10 |
| 5 | SQLite SQLite enables lightweight local storage of cave survey datasets in a single-file database for offline research workflows. | local storage | 7.6/10 | 8.0/10 | 7.0/10 | 7.5/10 |
| 6 | GitHub GitHub supports version control for cave survey scripts, exported data files, and reproducible mapping pipelines used in research. | version control | 8.1/10 | 8.6/10 | 7.8/10 | 7.6/10 |
| 7 | Google Sheets Google Sheets provides collaborative spreadsheets for organizing survey measurements, quality checks, and tabular exports. | collaborative tables | 7.5/10 | 7.6/10 | 8.1/10 | 6.7/10 |
| 8 | Notion Notion supports structured documentation and collaborative project pages for cave survey campaigns, methods, and data dictionaries. | research documentation | 7.1/10 | 7.3/10 | 8.1/10 | 5.9/10 |
Survex provides text-based cave surveying processing to compute survey traverses, adjust errors, and generate detailed cave maps.
QGIS provides open tooling to visualize cave survey exports, manage layers, and generate map products from survey-derived data.
GeoJSON.io supports interactive editing and validation of GeoJSON that can be used for cave survey outlines, survey traces, and derived features.
PostGIS provides spatial database capabilities to store cave survey points, lines, and derived measurements in a research-grade backend.
SQLite enables lightweight local storage of cave survey datasets in a single-file database for offline research workflows.
GitHub supports version control for cave survey scripts, exported data files, and reproducible mapping pipelines used in research.
Google Sheets provides collaborative spreadsheets for organizing survey measurements, quality checks, and tabular exports.
Notion supports structured documentation and collaborative project pages for cave survey campaigns, methods, and data dictionaries.
Survex
survey processingSurvex provides text-based cave surveying processing to compute survey traverses, adjust errors, and generate detailed cave maps.
Survey adjustment with loop closure and station error estimates from text survey scripts
Survex stands out for producing accurate cave survey adjustments and graphical cave maps from raw shot and station observations. It supports constrained survey computations, loop closure checking, and detailed station error reporting across large datasets. The workflow centers on a text-based survey scripting format that feeds computations and then exports usable plans and profiles. Visualization is built around repeatable map generation rather than manual drawing.
Pros
- Strong least-squares survey adjustment with loop-closure error reporting
- Text-based survey scripts make revisions and repeatable builds straightforward
- Flexible export outputs for plans, profiles, and annotated maps
- Built for large cave networks with station grouping and robust processing
Cons
- Steeper learning curve due to script-driven data entry and commands
- Visualization customization feels less GUI-driven than CAD-like tools
- Data validation feedback can require practice to interpret effectively
Best For
Cave survey teams needing repeatable adjustment and mapping from shot data
More related reading
QGIS
GIS mappingQGIS provides open tooling to visualize cave survey exports, manage layers, and generate map products from survey-derived data.
Custom Python processing tools for transforming survey attributes into spatial layers
QGIS stands out for turning cave surveying datasets into maps using a mature GIS toolchain, not a survey-only interface. It supports custom layers, field-based styling, and digitizing workflows that fit cave plan and profile outputs. With Python-based processing tools and extensive import options, QGIS can validate and visualize traverse, station, and depth attributes from common cave data formats. Its core strength is visualization and spatial analysis around georeferenced cave features, while cave-specific computation and error-checking require add-ons, plugins, or custom scripts.
Pros
- Rich layer styling and symbology for cave plan and profile visualization
- Flexible attribute tables enable station, survey leg, and error metrics tracking
- Python and processing framework support custom cave calculations and checks
Cons
- Cave-specific survey computations need plugins or custom scripting
- GIS-centric UI can feel heavy for purely tabular survey workflows
- Managing coordinate reference systems adds complexity for some cave projects
Best For
Cave teams needing advanced mapping, validation, and scripting flexibility
GeoJSON.io
geodata editingGeoJSON.io supports interactive editing and validation of GeoJSON that can be used for cave survey outlines, survey traces, and derived features.
Interactive map drawing with live GeoJSON export
GeoJSON.io stands out for fast, browser-based editing and validation of GeoJSON geometries. It supports drawing points, lines, and polygons on a map, then exporting valid GeoJSON for downstream cave visualization or analysis. The tool is effective for quick spatial sketching and attribute attachment, but it lacks cave-specific data structures like stations, shots, or survey computations. It fits best as a map editor in a larger cave survey workflow rather than as a complete survey system.
Pros
- Browser editing of points, lines, and polygons with immediate visual feedback
- GeoJSON export with preserved geometry structure for GIS workflows
- Text-based feature editing helps fix coordinates and properties quickly
Cons
- No cave survey domain model for stations, legs, and survey calculations
- Limited tools for topology management of connected cave networks
- Coordinate reference handling and transformation features are minimal
Best For
Quick cave map sketching and GeoJSON preparation for GIS or custom tooling
PostGIS
spatial databasePostGIS provides spatial database capabilities to store cave survey points, lines, and derived measurements in a research-grade backend.
GiST and SP-GiST spatial indexing for fast distance and intersection queries
PostGIS turns a database into a geospatial engine by adding geometry types and spatial indexes to PostgreSQL. Cave survey workflows benefit from SQL-driven storage of survey stations, line segments, and computed geometry, plus robust queries for nearest-neighbor and intersection logic. It also supports reprojection and geometry operations needed for transforming cave datasets across coordinate systems.
Pros
- Spatial indexes accelerate large cave geometry queries
- SQL supports repeatable survey computations and derived measurements
- Geometry and topology functions handle polylines and network logic
- Coordinate transforms enable consistent multi-system cave mapping
Cons
- Requires database setup, schema design, and SQL proficiency
- No built-in cave-specific survey UI for viewing shots and stations
- Data import and validation depend on custom tooling
Best For
Teams needing geospatial querying, storage, and computation without a niche UI
SQLite
local storageSQLite enables lightweight local storage of cave survey datasets in a single-file database for offline research workflows.
ACID-compliant transactions in an embeddable single-file database engine
SQLite is a lightweight, embeddable SQL database engine that stands in as the storage layer for cave survey software. It supports SQL queries, transactions, and indexes, which helps with reliable saving, fast filtering, and integrity checks for survey data. Cave survey tools built on SQLite can store points, stations, fixes, and computation outputs in a single database file that is easy to copy and version. Its core focus is data management rather than mapping, field navigation, or domain-specific UI workflows.
Pros
- Single-file database simplifies survey data portability and backup
- ACID transactions reduce corruption risk during field edits
- SQL querying enables flexible validation and export pipelines
- Indexes speed up station lookups and cross-reference queries
Cons
- No built-in cave survey visualization or topographic plotting
- App developers must implement the cave-domain data model and tools
- Geometry tooling is limited compared with dedicated GIS databases
Best For
Cave survey apps needing reliable embedded storage with SQL querying
More related reading
GitHub
version controlGitHub supports version control for cave survey scripts, exported data files, and reproducible mapping pipelines used in research.
Pull requests with code review for controlled changes to survey data workflows
GitHub stands out by combining Git repositories with collaboration features like pull requests and code reviews. Core capabilities include version control, branch workflows, issue tracking, and wiki documentation for managing survey datasets and processing scripts. Cave Survey Software teams can store raw measurements, processing code, and outputs as traceable artifacts with audit-friendly history. Integrations with GitHub Actions enable automated validation and transformation steps for surveying exports and derived calculations.
Pros
- Git history preserves every edit to survey data and derived outputs
- Pull requests add reviewable change control for processing pipelines
- GitHub Actions automates linting, validation, and export generation
- Issues and milestones track field tasks and data quality defects
- Web-based file browsing speeds inspection of datasets and results
Cons
- No native cave-survey UI for stations, shots, and closures
- Non-technical users often struggle with branching and merge workflows
- Large datasets can be cumbersome without careful storage strategy
- Data validation depends on custom tooling rather than built-in survey logic
Best For
Teams versioning cave survey data with code-driven processing and reviews
Google Sheets
collaborative tablesGoogle Sheets provides collaborative spreadsheets for organizing survey measurements, quality checks, and tabular exports.
Google Sheets formula engine for custom reduction calculations
Google Sheets stands out for turning cave survey workflows into editable, shareable tables with real-time collaboration. It supports structured data capture with validation, formulas, and pivot summaries for stations, shots, and computed fields. Cave-survey teams can implement coordinate and traverse calculations using custom formulas, scripts, and add-ons connected through Google Drive. It lacks purpose-built cave surveying modules, so survey reductions and plotting require more setup and careful template design.
Pros
- Real-time multi-user editing supports shared survey sheets
- Data validation and structured tables reduce input mistakes
- Formulas enable automatic traverse and coordinate computations
- Pivot tables and filters support fast survey QA views
- Google Drive versions help track survey sheet changes
Cons
- No native cave survey reduction or projection tooling
- Plotting and map exports require external steps and templates
- Complex calculations can become fragile and hard to audit
- Performance drops with very large station datasets
- Limited constraint checking for survey geometry and closures
Best For
Small to mid-size teams managing cave survey spreadsheets and calculations
Notion
research documentationNotion supports structured documentation and collaborative project pages for cave survey campaigns, methods, and data dictionaries.
Linked databases with templates and custom properties for station-to-segment relationships
Notion stands out for using flexible databases, pages, and templates to model cave surveys as a living knowledge base. It can store survey stations, passage attributes, and notes with linked records, while dashboards can surface QA checks and progress views. It does not provide native cave-specific survey computations, adjustment, or field-import workflows, so it relies on manual entry or external tooling for geometry and calculations.
Pros
- Configurable databases link stations, segments, and observations
- Templates speed repeatable survey forms and daily field checklists
- Dashboards aggregate status, completeness, and QA flags
Cons
- No native cave surveying computations like closures and adjustments
- Field-to-database capture needs custom forms and disciplined data entry
- Versioning and audit trails can be weaker for survey-critical workflows
Best For
Teams documenting cave surveys with relational notes and QA dashboards
How to Choose the Right Cave Survey Software
This buyer’s guide explains how to choose cave survey software workflows built around Survex, QGIS, GeoJSON.io, PostGIS, SQLite, GitHub, Google Sheets, and Notion. It also maps which tools fit which survey team goals for adjustment, mapping, storage, collaboration, and automation. Coverage includes both cave-specific processing tools and general-purpose platforms used as parts of a cave survey system.
What Is Cave Survey Software?
Cave survey software reduces shot and station observations into survey traverses, checks closures, and produces plan and profile outputs. Many teams treat cave mapping and computation as a pipeline where survey reduction tools feed GIS or editable map formats. Survex represents a cave-focused workflow built on text-based survey scripts for repeatable adjustments and exports. QGIS represents the mapping side of the pipeline by using spatial layers and Python processing to visualize cave-derived attributes.
Key Features to Look For
The best cave survey workflows depend on features that turn raw observations into validated geometry and usable map outputs.
Least-squares survey adjustment with loop-closure error reporting
Survex computes constrained survey traverses with loop closure checking and reports station error estimates. This matters when survey teams need traceable adjustment quality across large datasets with repeated builds.
Repeatable, text-based survey scripting for controlled recomputation
Survex uses text-based survey scripts to drive computations, which keeps revisions reproducible and reduces manual rework. This matters when teams rerun reductions after field corrections and want consistent plan and profile exports.
Export-ready cave plan and profile outputs with flexible visualization generation
Survex focuses on repeatable map generation that exports usable plans, profiles, and annotated maps. This matters when cave teams need outputs that align with survey structure rather than hand-drawn CAD maps.
Spatial layer workflows and Python-based processing for cave-derived visualization
QGIS provides custom layer styling and a Python processing framework to transform survey attributes into spatial layers. This matters when cave data must be validated visually and analyzed with GIS-centric spatial tools.
GeoJSON editing and geometry validation for fast cave map sketching
GeoJSON.io enables interactive drawing of points, lines, and polygons with live GeoJSON export. This matters when caves require quick spatial sketching for outlines or traces that feed downstream GIS workflows.
Geospatial storage, querying, and spatial indexing for large cave networks
PostGIS adds GiST and SP-GiST spatial indexing to PostgreSQL to accelerate distance and intersection queries on cave geometries. This matters when cave teams store stations and derived segments for efficient querying and geometry operations across coordinate transforms.
How to Choose the Right Cave Survey Software
Choosing the right tool starts with selecting which part of the cave survey pipeline needs to be solved directly and which parts can be assembled from other platforms.
Pick the core engine that must compute closures and station errors
If the required output includes survey adjustments with loop-closure checking and station error estimates, Survex is the direct match because it is built around least-squares adjustment from text survey scripts. If mapping needs dominate and computations can be delegated to scripts or external logic, QGIS can act as the visualization and attribute-processing layer around survey-derived data.
Choose the workflow style that matches field iteration and revision frequency
When survey corrections happen often and reductions must be rerun consistently, Survex’s text-based scripts support repeatable builds that reduce ad hoc manual steps. When the workflow needs collaborative editing of tabular measurements, Google Sheets can support structured station and shot tables with formulas for custom reduction calculations.
Decide how cave geometry and attributes will be stored and queried
For teams that need geospatial storage and fast spatial queries on cave polylines and network logic, PostGIS provides spatial indexes like GiST and SP-GiST. For teams building lightweight offline storage for a cave survey app, SQLite enables an embeddable single-file database with ACID transactions and SQL queries to support filtering and integrity checks.
Build a reproducible collaboration and automation layer for survey data changes
When version control for survey scripts and exported outputs is required, GitHub offers pull requests and code review so processing changes can be controlled. GitHub Actions can automate validation and export generation steps that transform survey inputs into derived cave mapping outputs.
Add mapping or sketching tools where survey reduction is not the main goal
If quick spatial sketching or outlines must be created and exported as valid GeoJSON for a GIS workflow, GeoJSON.io provides immediate drawing and live export. If the project needs structured documentation linking stations and passage notes, Notion supports linked databases and templates for repeatable survey forms and QA dashboards.
Who Needs Cave Survey Software?
Different cave survey roles need different parts of the workflow, from adjustment computations to GIS visualization and project coordination.
Cave survey teams running adjustment-and-map workflows from raw shots
Survex fits this group because it computes constrained survey traverses and reports loop-closure errors and station error estimates from text survey scripts. It also generates repeatable plans, profiles, and annotated map exports that support large cave networks.
Cave teams focused on advanced mapping, validation, and scripted visualization
QGIS fits this group because it provides rich symbology, attribute tables, and Python processing tools to transform survey attributes into spatial layers. This supports map validation and spatial analysis even when the survey computation engine is handled elsewhere.
Cave mapping teams that need a lightweight way to sketch traces and outlines and export geometry
GeoJSON.io fits this group because it enables interactive points, lines, and polygons with live GeoJSON export. This supports quick creation of cave outlines or traces that feed downstream visualization tools.
Engineering-style teams building scalable storage, querying, and computation pipelines
PostGIS fits this group because it adds spatial indexing and geometry operations in PostgreSQL for fast distance and intersection queries. For embedded app storage, SQLite fits because it provides single-file ACID transactions and SQL querying for survey data portability.
Common Mistakes to Avoid
Common failures come from picking tools that solve the wrong pipeline stage or from underestimating workflow gaps between computation, storage, and mapping.
Choosing a GIS tool without built-in cave survey reduction
QGIS excels at spatial visualization and Python-based layer processing but it does not provide native cave-specific survey computations like constrained adjustment and loop-closure error reporting. Survex avoids this mismatch by driving computations from text survey scripts with station error estimates and closure checks.
Relying on geometry editors without a cave domain model
GeoJSON.io exports points, lines, and polygons as GeoJSON but it lacks cave survey structures like stations, shots, and traversal computations. Survex avoids this by using a survey scripting format designed for shot and station observations and producing survey-adjusted outputs.
Treating a database backend as a complete survey application
PostGIS provides spatial indexing and geometry operations but it does not provide a cave survey UI for viewing shots, stations, and closures. Survex avoids this by centering the workflow on survey processing scripts and exporting plans and profiles.
Using spreadsheets or documentation tools for closure-grade computations without guardrails
Google Sheets can use formulas for custom reduction calculations but it lacks native constraint checking for survey geometry and closures. Notion can document and link stations and QA flags but it does not compute closures or adjustments, so Survex should remain the reduction engine for closure-grade outputs.
How We Selected and Ranked These Tools
we evaluated every tool on three sub-dimensions with weights of features at 0.4, ease of use at 0.3, and value at 0.3. The overall rating equals 0.40 × features plus 0.30 × ease of use plus 0.30 × value. Survex separated itself from lower-ranked tools primarily through features tied to survey adjustment quality, including loop closure checking and station error estimates produced directly from text survey scripts. Tools that focused on storage or visualization, like PostGIS and QGIS, scored well in their strengths but did not provide the same end-to-end cave adjustment computations that drive plans and profiles in a single workflow.
Frequently Asked Questions About Cave Survey Software
How does Survex compare with QGIS for producing cave plan and profile outputs from shot and station measurements?
Survex computes constrained survey adjustments and exports repeatable plans and profiles directly from text-based survey scripts. QGIS focuses on mapping and spatial visualization from imported datasets, so cave-specific reductions and error-checking typically require plugins or custom Python processing.
Which tool is best for validating loop closure and diagnosing station errors in a multi-loop cave survey?
Survex is built for loop closure checking and station error reporting across large datasets using its scripted adjustment workflow. QGIS can visualize misclosures and residuals once derived attributes exist, but it does not replace Survex-style adjustment computation.
What workflow fits teams that want to store survey data and computed geometry in a queryable backend?
PostGIS stores cave stations and segments as geometry types in PostgreSQL and supports spatial indexing with GiST and SP-GiST for fast intersection and proximity queries. SQLite offers lightweight embedded storage in a single database file with reliable SQL transactions and indexing, while PostGIS supports heavier spatial operations and multi-user database patterns.
How can GitHub be used to make cave survey processing reproducible and auditable?
GitHub supports version control for raw measurements, processing scripts, and generated outputs through repositories, branches, and pull requests. GitHub Actions can automate export validation and transformation steps, which helps keep Survex or QGIS processing runs consistent across changes to survey inputs.
When is GeoJSON.io a practical step in a cave survey pipeline?
GeoJSON.io is useful for quick editing and validation of GeoJSON points, lines, and polygons in a browser before importing into a GIS workflow. It lacks cave-specific structures like station networks and shot observations, so cave reduction and adjustment still need Survex or a custom pipeline built around QGIS.
What’s the difference between using PostGIS and SQLite for cave survey datasets with geometry-heavy operations?
PostGIS enables SQL-driven geometry operations with spatial indexes, which accelerates nearest-neighbor, intersection, and reprojection workflows on large spatial datasets. SQLite supports embedded storage and dependable transactions for survey data integrity, but it is not a full spatial engine for advanced geometry indexing at the scale and feature depth of PostGIS.
How can Google Sheets support a cave survey workflow that needs calculations beyond what a survey-only tool provides?
Google Sheets can store station and shot tables with formulas for custom reductions and derived fields, then share those spreadsheets for collaborative QA. It works well for template-driven computation, but plotting and geometry validation usually become a setup task compared with QGIS mapping and Survex adjustment outputs.
How can Notion be used alongside computational tools to manage survey notes and QA checks?
Notion can model stations, passage attributes, and linked notes as a relational database with dashboards for progress and QA status. It does not perform native cave survey computations, so station-to-segment calculations and adjustments typically come from Survex or spatial layers exported and styled in QGIS.
Which setup best supports custom spatial styling and automated attribute transformation for cave mapping in QGIS?
QGIS supports custom layer styling and Python-based processing tools, so it can transform station and traverse attributes into spatial layers for cave plans and sections. This pairs well with PostGIS for queryable storage and with GitHub for versioned processing scripts that regenerate styled outputs deterministically.
Conclusion
After evaluating 8 science research, Survex stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Science Research alternatives
See side-by-side comparisons of science research tools and pick the right one for your stack.
Compare science research tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.