Skip to main content

Quickstart

This quickstart walks a new customer from sign-up to having a populated map and a first field submission. It assumes you have a Stratumly tenant. If you don't, contact us for an evaluation account.

Before you start​

You'll want:

  • An email address you control (used for the OWNER account on your organisation).
  • An asset register file (CSV, GeoJSON, or zipped Shapefile) for whichever assets you want to track first. Pipes, bridges, signals, poles, manholes, easements, flood zones: anything goes. If you don't have one to hand, Stratumly ships demo data so you can skip ahead and explore.
  • (Optional, for inspections) A .las or .laz point-cloud file from a recent survey.

1. Create your organisation​

The first user on your organisation is the OWNER. They can invite the rest of the team and assign roles.

  1. Open your tenant URL (e.g. https://app.stratumly.com or your sovereign deployment URL).
  2. Click Register.
  3. Fill in your name, email, password, and your organisation name.

You'll be issued an access token + refresh token automatically and dropped onto the map.

2. Invite your team​

From the Admin → Team page (visible to OWNER and ADMIN roles):

  1. Click Add user.
  2. Enter their email, first name, last name, and pick a role:
    • OWNER: full control, can manage billing and other OWNERs.
    • ADMIN: can invite users and manage non-privileged roles.
    • ENGINEER / SURVEYOR: full operational access without admin powers.
    • VIEWER: read-only.
  3. The dialog generates a one-time temporary password. Copy it and share it out-of-band (Teams, Slack, secure handoff). Your colleague will be prompted to change it on first login.

3. Create your first project​

Projects are the top-level container for surveys, inspections, and reports.

  1. Open Projects → New project.
  2. Give it a name (e.g. "Northwest Pipe Renewals 2026") and pick an industry from the list (UTILITIES, RAIL, HIGHWAYS, MINING, CONSTRUCTION, FORESTRY, TELECOMS, INSURANCE, ARCHAEOLOGY, OTHER).

The industry choice helps Stratumly pre-pick sensible defaults later (form templates, dashboard widgets) but doesn't lock you into anything.

4. Load an asset register​

Stratumly's map is populated from feature classes, your asset registers. There are three ways to get data in.

Option A: Bulk import a file​

From the layers panel:

  1. Click New layer.
  2. Pick the geometry type (POINT, LINESTRING, or POLYGON), or let Stratumly infer it from the file.
  3. Drag a file in. Supported:
    • CSV: POINT only, expects lon / lat columns. Other columns become attributes.
    • GeoJSON: Feature or FeatureCollection, any geometry.
    • Shapefile: zipped .shp + .dbf + .shx, optional .prj / .cpg. Native parser, no GeoTools dependency.
  4. Click Import. Files upload directly to object storage from your browser (the API server never sees the bytes), and you get a resumable session if your connection drops mid-upload.

Partial successes land. Validation failures become per-row error entries in the import report; only genuinely unexpected errors roll back.

Option B: Draw on the map​

For small datasets or one-off additions:

  1. Pick a target layer in the Draw section of the map sidebar.
  2. Pick a tool (point, line, or polygon; the tool list filters to layers whose geometry type matches).
  3. Click to place vertices. Single-click commits a point; double-click commits a line or polygon. Escape cancels.
  4. Fill in the attribute dialog (rendered from the layer's schema) and save, or hit Skip & save to land the feature with empty properties.

Option C: Capture from the field via a Form​

If you want to grow the layer organically as field engineers walk the network, point a Form at the layer (see Forms). Every submission auto-creates a feature with the correct geometry and properties.

5. Build a Form​

Forms are how the field captures back into the platform. Build them once, run them on web or mobile, online or offline.

  1. Forms → New template.
  2. Give it a name and slug.
  3. Choose whether geometry is required (and if so, POINT / LINESTRING / POLYGON).
  4. Optionally set a linked feature class so submissions auto-create features in that layer.
  5. Define the schema (JSON Schema 2020-12 dialect, the same one @rjsf/core uses), so the live preview matches the field experience exactly.
  6. Add the fields you want: text, number, dropdown, checkbox, radio, date, photo, GPS point, QR / barcode scan, signature, rating, linked-feature picker.
  7. Publish when ready. Submissions can only be filed against published versions; further edits create V2, V3, … with old submissions still readable.

6. Run an inspection​

If you have a survey file (point cloud, mesh, or orthoimagery):

  1. Open the project, then Surveys → New survey.
  2. Pick a sensor type (LIDAR, PHOTOGRAMMETRY, THERMAL, HYBRID).
  3. Initiate the upload. Stratumly returns a presigned URL; your browser PUTs the file directly to object storage.
  4. Once the upload completes, the processing pipeline (PDAL + py3dtiles for LiDAR, OpenDroneMap for photogrammetry) kicks off automatically.

Status moves: PENDING → UPLOADING → PROCESSING → READY (or FAILED if the worker errors).

When status hits READY, open the survey to view the tileset in 3D and start annotating defects (manually for now; AI-assisted defect detection is on our roadmap, see Spatial analysis).

7. Build a dashboard​

Make Stratumly a daily operational tool, not a one-off survey deliverable:

  1. Dashboards → New dashboard.
  2. Drag widgets onto the grid: KPI cards, charts, gauges, embedded maps, lists, tables.
  3. Bind each widget to a data source: a feature layer, a form's submissions, a live IoT stream, or an analysis result.
  4. Cross-widget filters cascade: click a bar segment to filter the embedded map and table.
  5. Share publicly with an expiring token, or embed as an iframe in your council partner's portal.

What next?​

  • Maps: feature layers, basemaps, vector tiles, drawing and editing tools.
  • Forms: schema-driven capture templates and the auto-feature-creation contract.
  • Submissions: the immutable capture event, offline idempotency, media attachment.
  • Dashboards: widget kit, data sources, real-time refresh, sharing.
  • Spatial analysis: buffer / intersect / proximity / heatmap / isochrone, all chainable.
  • Authentication: JWT, refresh tokens, role model, session management.

If a section you need isn't filled out yet, contact us and we'll send the source material directly.