File Conversion Overview

Status: Research brief below. Replace this entire body with finished MDX when research is complete. Update description in frontmatter.

Paired tools: /tools/converters/gsi-to-csv, /tools/converters/csv-to-gsi, /tools/converters/csv-to-dxf

AI research prompt

You are writing a Learn article for Surveying Core. Produce a single MDX-ready document (article body only). Published at /learn/tools/file-conversion-overview, paired with the browser file converters (sign-in required for conversion; files never uploaded to server).

Paired tools (link to all three)

• GSI → CSV — /tools/converters/gsi-to-csv
• CSV → GSI — /tools/converters/csv-to-gsi
• CSV → DXF — /tools/converters/csv-to-dxf

Also cross-link the GSI Format Guide reference (when published): /reference/data-formats/gsi

Audience

• Field surveyors moving data between total station, office CSV, and CAD stakeout
• Office technicians who historically used Excel macros or legacy DOS tools
• Students learning why “formats” matter in survey data exchange

Platform context (must be accurate)

Surveying Core MVP converters:

• Run entirely in the browser — files are not uploaded to a server
• Internal representation is USDM v1 (Universal Survey Data Model): points with id, easting, northing, elevation, description/code
• Credit metering applies to converter use (free tier); calculators remain free
• Supported MVP chain: GSI ↔ CSV, CSV → DXF (2D POINT entities for stakeout)
• CSV import: auto-detect ENZ / PNEZD headers; ambiguous layouts require user column mapping before parse
• GSI: GSI-8 and GSI-16 variants (see GSI reference guide — do not duplicate full GSI byte spec here; summarise and link)

Scope — must cover

1. Why format conversion exists in surveying workflows (instrument → office → CAD → back to instrument)
2. Conceptual pipeline: File → parse → canonical point model → export → file (explain USDM idea in plain language)
3. CSV in survey offices: common column layouts (ENZ, PNEZD), delimiters, header row pitfalls
4. GSI in brief: Leica exchange format; point to /reference/data-formats/gsi for depth
5. DXF in brief: why CSV→DXF for CAD stakeout; 2D points with Z optional; not DWG
6. Per-converter section (one subsection each): typical use case, input expectations, output you get, link to tool
7. Browser-private processing: privacy and offline-adjacent benefits; what is not stored on server (file contents)
8. Quality checks after conversion: point count, bounding box sanity, spot-check one point, re-export round-trip where applicable
9. What MVP does not do (manage expectations): batch conversion, DWG, LandXML, Excel, cloud storage pipelines

Out of scope

• Full GSI word-by-word specification (belongs in reference guide)
• DXF entity catalogue beyond POINT export
• Pro tier / Azure pipelines / R2 storage
• Detailed credit pricing (mention credits exist; no numbers unless citing public spec)

Quality bar

• Cite primary sources: Leica GSI documentation pointers, Open Design Alliance / DXF references for POINT, CSV as de facto exchange
• Workflow-oriented, not marketing fluff
• At least one end-to-end workflow narrative (e.g. download GSI from TS → convert to CSV → edit in Excel → convert to DXF for AutoCAD)
• Troubleshooting table (symptom → likely cause → action) for common conversion failures
• WCAG-friendly headings from ##

Deliverable format

Return MDX body only. Suggested outline:

1. Introduction (links to three converters)
2. Formats in the survey workflow
3. The conversion pipeline (USDM)
4. CSV conventions
5. GSI overview (link to reference guide)
6. DXF stakeout export
7. Tool guide: GSI → CSV
8. Tool guide: CSV → GSI
9. Tool guide: CSV → DXF
10. Privacy and browser processing
11. Quality checks and round-trip tips
12. MVP limits and what’s next
13. References
14. Next steps (tool links)

Target length: 1,800–2,500 words.