Import anything
Bring in a spreadsheet, CSV, Word or PDF file, a photo of a field sheet or a map file. The app proposes how to read it, converts every value itself, shows you the result beside the original, and stores nothing until you confirm.
- For
- Consultant foresters
- Time
- 8 minutes
- Where
- Web app — Stand › Field work › Imports, or the property page
- Updated
On this page
How it works
- The AI reads the file and proposes a mapping — how to read it — never the data itself. The app’s own engine then converts every value and shows the result next to the original cell.
- Nothing is guessed: units, girth vs diameter, date formats and coordinate systems become questions with pickers.
- Nothing is stored until a person confirms. Imported values keep the import as their origin.
- Save the mapping as a format, and the next file with the same headers is read without AI.
Upload a file
- 1 Choose the file
- 2 Saved format, or match by headers
- 3 Ask Claude to propose the mapping
- 4 Read the file
- Choose the file — spreadsheets (every sheet), CSV, JSON, Word, PDF, a photo of a field sheet, or a map file (GeoJSON, zipped Shapefile, KML/KMZ, GPX, GeoPackage).
- Pick a saved format, or leave Match by headers.
- Tick Ask Claude to propose the mapping (untick it to write the mapping yourself or use a format).
- Choose Read the file. The import opens below, as a draft.
Review the preview
- 1 Nothing is stored until you confirm
- 2 What confirming would store
- 3 Questions — nothing is guessed
- 4 Original → converted, row by row
- Nothing is stored yet — the notice says what to do next.
- Confirming would store — records, visits, new plots — and how many rows have errors. What changed lists the differences from the previous mapping version.
- Answer the questions. Here: “Larch” could be European, Japanese or hybrid larch — which is it? Each answer is a button; the preview updates.
- Read the table — each sheet, how each column is read (Girth (cm): DBH: GIRTH in cm → ÷ π → diameter, stored in m), and every row as original → converted, with its problems.
- 5 Ask for changes in plain words
- 6 Confirm — import these values
- 7 Save the mapping as a format
- Ask for changes in plain words — “Plot 8 was measured with a girth tape”, “skip the Notes column”. A new mapping version is proposed and the preview recomputed.
- Choose Confirm — import these values. Tick to create the new sample locations it found, or to leave out rows with errors. Confirming records you as the reviewer. Discard throws the import away.
- Save the mapping as a format with a name you will recognise.
Data that fits no method becomes a dataset
Cull records, habitat maps, bird and flora records fit no protocol. They become a dataset: a map layer with a style picker, a filterable table, and per-year totals beside the time series — context, never a score.
Standard imports
- 1 Format: tree tally CSV, GeoJSON, derived values
- 2 Diameter or girth, and the unit — never guessed
- 3 Upload for review (held as pending)
- Choose the format — tree tally CSV, GeoJSON, derived values from LiDAR, drone or satellite.
- Say which column holds the diameter or girth and in what unit — the app shows how it will read it (“DBH” read as DIAMETER in cm — no conversion).
- Choose Upload for review. The upload is held as pending until someone confirms it.
File content is sent to the AI provider
When Ask Claude is ticked, the file’s content is sent to Anthropic to propose the mapping. Untick it for files that must not leave your organisation, and use a saved format or write the mapping. See Your data.
What it doesn’t do (yet)
- If AI import is not configured on your site, the chat says so: answer the questions, pick a saved format or write the mapping — deterministic imports still work.
- There is a daily limit on AI-assisted imports per organisation; it resets each day.
- No tree counts from imagery (planned: proposed values from supplied orthophotos).