TraverseOps public app

Field operations map and work orders.

Sample-data, map-first asset workspace with inspections, work orders, import validation, reports, and role-aware mobile controls.

Status
Public sample-data prototype
Last updated
May 2026

Try this demo

Try this in 2 minutes.

Sample-data prototype. Review the workflow, not production readiness.

  1. Filter by status.Use Needs inspection, Open work, Healthy, and All.
  2. Select an asset.Click a marker and check status, priority, and open work.
  3. Open context.Use inspection/work-order actions or task tabs.
  4. Review imports/reports.Validate sample import, then open Reports.

Production readiness

Sample records, not deployment.

Review maps, inspections, work orders, imports, reports, and roles. Production needs auth, offline sync, audit logs, reliable data, QA, backups, and alerts.

Testing and QA notes

QA checks device and data state.

Automated: no public suite linked yet. Manual: sample data, tabs, marker selection, filters, forms, imports, reports, focus, mobile targets, and empty/reset states.

Limits: no production auth, offline conflicts, GIS services, bulk-import security, or field network loss.

Deployment and run notes

Sample-data app with no secrets.

GitHub Pages serves traverseops-demo.html, traverseops-demo.js, CSS, and assets. No env vars. Sample assets, inspections, work orders, and imports live in client-side JavaScript.

Local: run python -m http.server 8000 and open /traverseops-demo.html. Production data, keys, GIS credentials, and private imports stay out of public files.

Workspace

North Harbor zone

Tap through the tabs to inspect assets, create field records, validate imports, and review sample reports.

Sample workspace ready. Select a marker or open a task tab.

Map workspace

Tap an asset marker.

North Harbor

Next step

Compare the app with the case study.

The case study explains the architecture, data model, public limits, and production plan behind this mobile-friendly sample workspace.