Help and support

Get from a rough site to a useful Terrain Preflight.

Start with the shortest path, understand what the evidence can and cannot tell you, and keep private site information out of support messages unless it is explicitly needed.

Start

Start a Terrain Preflight

  1. Open the app and search for a town, address or nearby landmark.
  2. Select a result and confirm the map is centered on the intended area.
  3. Create a rough 10-acre area around the selected point or draw an editable analysis boundary, then choose Review site preview.
  4. Review the source, area and limitations preview. Paid custom analysis is disabled for this release, so use the prepared example to inspect a complete result.
  5. In the prepared example, read the findings first, then open the report or an export when it helps the next conversation.

The point-elevation preview shown after location selection is orientation only. The bounded terrain analysis begins after you establish a site area.

Site setup

Draw a useful rough boundary

After selecting a location, use the rough 10-acre area for a quick editable start or use Boundary to place vertices around the area you want to screen. Finish with the visible action or Enter. Use Edit, Undo or Restart when the shape needs repair.

The boundary controls analysis scope; it is not a legal parcel line. Keep it modest enough for a quick overview, and split very large areas when local questions need more detail.

Understand the result

Read findings before technical layers

Begin with the three plain-language findings and the report. Then inspect slope, drainage, wetness-screen and terrain-candidate evidence where it changes what you will check next.

Each result should be read with its source, working-cell size, method, assumptions, limitations and suggested next checks. Modeled flow and wetness screens are not observed flooding or drainage design.

Save and share

Keep sharing private by default

The prepared example needs no account. A completed Single Site or Pro result is attached to the signed-in account for durable reopening. Private viewer links are the default and may use a separately shared password.

Treat editor and private viewer links as secrets. Public sharing is explicit. Use Revoke viewer access to stop existing private and public viewer links without deleting the project. Delete a project when you also want to remove its verified stored GeoTIFF.

Evidence quality

Check sources, resolution and uploads

Public terrain sources vary by location, age, model type, resolution and coverage. Review the displayed source and working-cell size before relying on site-scale patterns.

GeoTIFF terrain can be analyzed locally and stored only when you save a compatible project. Supported LAZ analysis stays local and is not promised to reopen from a shared project. Review all provider notices on the data sources page.

Takeaway

Use reports and exports for the next conversation

Print or download the Terrain Preflight report for a concise screening record. The prepared example exposes example exports. Completed Single Site and Pro results include the approved standard exports, including GeoJSON, KML, KMZ, PNG, CSV and a redacted project record.

Specialist exports preserve scope, provenance and method metadata, but an exported file does not turn screening evidence into survey or engineering evidence.

User control

Manage account, privacy and deletion

The account page lists saved account-owned projects, exports account data, manages separate optional communication preferences and deletes eligible accounts. Active existing subscriptions must be canceled in the billing portal first.

Browser-only projects remain on that browser until deleted or its storage is cleared. Read the privacy notice for storage and deletion details.

Billing recovery

Recover billing access without sharing payment data

Use the signed-in account page and Stripe billing portal for payment-method, renewal and cancellation changes. A failed renewal may pause new paid work, but completed projects remain available according to their current access.

Support may use a sanitized purchase or event identifier from approved operator tooling. Never send card details, payment screenshots, raw webhook bodies, passwords or account-session links. Review the privacy-safe billing recovery example.

Result recovery

Recover a durable result without sharing site data

If analysis finishes but secure result storage does not, keep the useful browser result open and use the visible retry after the stated condition changes. Do not pay again or redraw the boundary unless the product explicitly requires a new correction analysis.

Support can verify a sanitized project/run identifier and storage state. Do not email exact geometry, private links, reports, uploaded files or terrain findings. Review the privacy-safe result recovery example.

Troubleshooting

When a preflight does not complete

  • Confirm the browser supports WebGL terrain and has enough available memory and storage.
  • Try a smaller boundary when the site exceeds the quick-overview envelope.
  • Read the visible provider/source error and retry only after the stated condition changes.
  • Keep optional local detail paused until the bounded overview is useful.
  • Use the report's source and limitation details when describing a reproducible problem.

Contact support

Send the smallest useful problem report.

Include the browser/device, action attempted, visible error text, source type and whether a smaller or example site works. Do not send private viewer/editor links, exact addresses, boundaries, uploaded files or report contents unless support explicitly requests them.

The public incident-status path is manually maintained. Inbound support delivery, response targets, escalation ownership and incident drills still require verification before broad launch.

Email reference support