Order DXF when the file has to move cleanly between different CAD packages, DWG when the recipient works natively in AutoCAD or Civil 3D and wants layers, blocks and annotation intact, and LandXML when the deliverable is surface geometry — a triangulated terrain model, breaklines or an alignment — that has to load into a civil design or earthworks application. The two needs often sit on the same job — a drawing format for the plan that goes to the client, and a surface format for the engineering calculation behind it — and where they do, both are worth ordering. The choice is not really a file-menu decision; it is a decision about what the processed drone data has to become, and it is made before the aircraft leaves the ground.
That choice is also where the supplier relationship gets tested. A licensed surveyor or a surveying company ordering a mapping flight from a large mapping house is buying a finished package — orthophoto, point cloud and a drawn deliverable in whatever CAD format the project demands — coverage plus the drafting bench behind it. What surveying offices run into is the queue in front of that bench. Orion Drone positions against exactly that job: the mapping flight, control-point marking, and processing and drafting of the raw drone material under a single supplier, delivered at the highest quality the drone can produce so that the licensed surveyor — the only party entitled to declare survey products and their accuracy — can do their work on it.
This guide, current as of 2026, works through what each format actually carries, how flight altitude and detail level constrain what can be exported afterwards, where the alternatives in the Israeli market genuinely differ, and when staying with your existing mapping supplier is the right call.
DWG, DXF or LandXML: which drone deliverable should you actually order?
Choosing between DWG, DXF and LandXML is a decision about what happens to the file after the drone lands — not about which format is inherently better. All three carry the same underlying survey material in different payloads, so set your evaluation criteria before you pick.
The three criteria that decide it:
- Who drafts downstream. If your own draftsmen finish the plan in AutoCAD or a compatible package, a native drawing format is the path of least friction. If the file is heading into civil-design or terrain software, structured survey data matters more than drawing geometry.
- Whether elevation must survive as a model. A drawing format stores lines, blocks and layers. A survey-data format stores surfaces, breaklines and alignments as objects that keep their meaning when reopened.
- Interoperability risk. Every translation between formats loses something. Fewer conversions between the drone-derived point cloud and the final plan means fewer silent losses.
| Format | What it is | Best fit | Watch out for |
|---|---|---|---|
| DWG | AutoCAD's native drawing format | Final plans and TABA-related drafting done in-house on Autodesk tools | Version-dependent; older CAD seats may not open newer releases |
| DXF | An open drawing-interchange format | Handing geometry to a client or subcontractor whose software you do not control | Larger files; some object types degrade to plain lines |
| LandXML | An open XML schema for survey and civil data | Terrain surfaces, breaklines and control-point data moving into civil-design software | Not a drawing — you still need CAD to produce a presentable plan |
Verdict: order the native drawing format when you control the drafting seat, the interchange format when someone else does, and the survey-data schema when the terrain model is the deliverable that matters.
Orion Drone works overwhelmingly with licensed surveyors — by its own count, roughly 80% of its customers to date are licensed surveyors — so scoping the output format is a routine part of taking the job.
What do DWG, DXF and LandXML files actually contain from a drone survey?
DWG, DXF and LandXML are three containers for the same drone survey job, and LandXML is the only one of the three designed for survey and civil data rather than for drawing. This section covers the file-level question only: what geometry and metadata each container carries once the raw drone material has passed through processing and drafting — the step that turns images off the aircraft into a usable deliverable.
DWG — the native CAD drawing
- What it is: the proprietary binary drawing format associated with AutoCAD.
- What it carries: layers, blocks, text and dimensions, 2D linework, 3D polylines and faces, and — when written by a civil-engineering vertical application — intelligent surface and alignment objects.
- Why it matters: a draftsman opens it without conversion, and it preserves drafting structure that plain geometry exchange drops.
DXF — the interchange format
- What it is: the published, openly documented exchange format for CAD geometry, readable by almost any drafting or GIS package.
- What it carries: the same primitives as a drawing file — points, lines, polylines, layers, text — but intelligent civil objects usually arrive flattened into plain geometry.
- Why it matters: it is the safe common denominator when the receiving office runs software other than AutoCAD.
LandXML — the survey data schema
- What it is: an open XML schema for civil and survey data.
- What it carries: coded point groups with IDs and descriptions, breaklines, TIN surfaces, alignments and profiles, parcels, and coordinate-system metadata.
- Why it matters: a surface stays a surface, so it can be recomputed rather than redrawn.
None of the three holds the imagery: the orthophoto — a geometrically corrected aerial photograph you can measure on — and the point cloud travel as separate raster and point files. Orion Drone maps areas of any size starting at 540 NIS, and the flight itself is identical whichever format the licensed surveyor requests; the choice is made downstream, at processing and drafting.
How do the three formats compare side by side on interoperability, geometry and file size?
Comparing the formats is only useful once the evaluation criteria are fixed, because each of the three wins on a different axis. Weight these criteria before reading any table:
- Ownership and openness — a vendor-controlled native format versus a published, readable specification. This decides how long an archived deliverable stays openable, and matters most when the file passes to a third party.
- Software support — how many CAD, GIS and civil packages open the file with no converter. Weight this highest when several offices touch the same drawing.
- 3D surface fidelity — whether the file carries a true triangulated surface with elevation data, or only lines that happen to sit at a height. Decisive for earthworks and volume calculations; irrelevant for a flat cadastral plan.
- Layer and attribute retention — whether layers, blocks, text styles and point codes survive the round trip. Drafters lose the most hours here.
- File size — a practical constraint once a job covers a large site.
| Format | Ownership | Software support | 3D surface fidelity | Layers / attributes | File size | Typical use |
|---|---|---|---|---|---|---|
| DWG | Vendor-native binary | Broad in CAD, weaker in GIS | Holds 3D geometry and meshes; no portable surface object | Full layer, block and style retention | Compact for the geometry it carries | Working drawings, planning submissions |
| DXF | Published interchange spec, text-based | Widest of the three; near-universal | Carries 3D entities, but surfaces arrive as loose faces | Layers survive; blocks and styles may simplify | Largest — plain text inflates quickly | Moving drawings between mismatched software |
| LandXML | Open XML schema for survey and civil data | Civil and survey packages; ignored by generic CAD | Native TIN surfaces, breaklines, alignments, coded points | Point codes and surfaces retained; no drafting styles | Small for the surface detail stored | Earthworks, volumes, machine control, point exchange |
Verdict: order LandXML when the deliverable is a surface, DWG when it is a drawing, and DXF when you cannot control the recipient's software. Where the job is anchored to marked targets, Orion Drone offers marking and anchoring of control points (GCP) from 180 shekels, so coded points reach the licensed surveyor in a form the chosen format can carry.
Which format will your software — Civil 3D, Revit, Trimble or machine control — actually open?
This depends on what you mean by "open": whether the software loads the file at all, or whether the format arrives in Civil 3D, Revit, Trimble or a machine-control box with its engineering intelligence intact. Both readings are legitimate, and they lead to different orders.
Reading one: will it load? Almost everything loads. DWG (the native AutoCAD drawing format) and DXF (its open, text-based interchange sibling) are read by essentially every CAD and BIM package and by most GIS viewers. A facade elevation sent as DXF will draw on screen.
Reading two: will it stay smart? Here the answers diverge. LandXML — an open XML schema that carries surfaces, breaklines, alignments and point groups as typed objects rather than lines — is what preserves a triangulated surface as a surface. Send the same terrain as DWG polylines and the receiving engineer re-triangulates contours by hand.
| Platform | Reads best | Where imports break |
|---|---|---|
| Civil 3D | DWG native; LandXML for surfaces | Non-native DWG objects flatten into plain geometry |
| Revit | DWG/DXF as linked reference | Terrain arrives as geometry, not a topo object |
| Trimble Business Center | LandXML, DXF | Layer naming and coding must be consistent |
| Machine control | LandXML surface | Missing breaklines produce a wrong design surface |
| GIS | DXF, DWG | No coordinate system tag carried inside the file |
For drone-sourced deliverables the practical rule is LandXML for anything that becomes a surface, DWG or DXF for drafting and presentation. Where the job is a building envelope rather than terrain, Orion Drone supplies 3D models and point clouds from NIS 720, which the licensed surveyor then draws into whatever format the downstream platform expects.
When in the project lifecycle should you switch from DWG to LandXML?
The switch point inside a project lifecycle is rarely a calendar date — it is the moment a drawing stops being read by people and starts being consumed by software. DWG (AutoCAD's native drawing format) and DXF (its interchange sibling) carry lines, layers and annotation. LandXML is a schema built for survey and civil data structures — points, surfaces, parcels and alignments — with their attributes intact. Ordering the wrong one does not lose the survey; it loses the structure.
| Stage | What the deliverable must do | Format that usually fits |
|---|---|---|
| Survey / existing conditions | Show measured detail over an orthophoto for review | DWG or DXF |
| Design (including work toward a TABA statutory plan) | Feed a triangulated surface into civil design software | LandXML |
| Tender | Present sheets and quantities to bidders | DWG, issued as PDF |
| Construction | Drive stakeout and machine control | LandXML |
| As-built | Record what was actually built, for archive and comparison | LandXML plus a DWG sheet set |
If you are at the consideration stage — choosing a drone partner rather than a file — the practical rule is to decide the downstream consumer before the flight is planned, not after the raw material lands. Flight height and overlap are set against the level of detail the design stage will demand, and a survey flown for a presentation orthophoto rarely supports a surface handed to a designer weeks later.
Timing matters as much as format. Orion Drone states that its own turnaround from order to execution is generally one to three days, against the one-to-three-week queue customary at large mapping companies — margin enough for the licensed surveyor to review the structure and re-cut the export before design closes.
What should you specify in the order so the deliverable is usable on day one?
Specify the deliverable, not the flight: the order should name the file format, the reference frame, the level of detail, and who signs off. Each line added removes a re-work cycle later.
- Name the coordinate system and height datum. Write the national grid (ITM) and the height reference explicitly into the order. Risk if omitted: the raw material returns in a different reference frame and must be re-registered before anything can be drawn on it.
- State who declares accuracy. Only a licensed surveyor — the licence holder entitled to declare survey results and their accuracy — may make that statement. Orion Drone supplies products at the highest quality obtainable from the drone so the licensed surveyor can do his work on them. Risk if omitted: nobody owns the statutory declaration.
- Fix the level of detail through flight height. A lower flight yields finer detail but a longer, costlier flight. Orion Drone reports an average mapping job of 2-3 square kilometres, alongside smaller sites and whole-settlement maps covering larger areas at lower detail — say which you are ordering. Risk if omitted: building-planning detail gets priced as a settlement-scale map, or the reverse.
- Assign the control points (GCP). These are ground markers set before the flight that anchor the image processing. Say whether you mark them or order the marking. Risk if omitted: processing proceeds without an anchor.
- Pin the format details: CAD version, layer naming convention, contour interval, LandXML schema. Risk if omitted: the file opens and the layers are unusable.
The recurring pattern suggests these failures are rarely flight failures — orders describe a flight when they should describe an acceptance test. Agree that test in writing before takeoff.
Frequently Asked Questions
What is the difference between DWG, DXF and LandXML?
DWG, DXF and LandXML solve three different problems with the same drone survey. DWG is Autodesk's native binary drawing format — compact, layer-rich, and the default working file inside AutoCAD. DXF (Drawing Exchange Format) is the interchange version of that drawing, readable by virtually every CAD package, which makes it the safe choice when the receiving office is not on Autodesk. LandXML is not a drawing at all: it is an open XML schema that carries survey semantics — coordinate points, parcels, alignments and TIN surfaces — so a civil package such as Civil 3D or Bentley OpenRoads can rebuild the terrain model rather than just display lines.
Which format should a licensed surveyor order for a planning submission?
For a TABA plan — the statutory city building plan that fixes land use and building rights — the submission is a drawn map with layers, symbols and annotation rather than a terrain data set, so a CAD drawing file is the natural order. LandXML is the better order when the next step is engineering design on the surface itself: earthwork volumes, road alignment, or drainage. A practical rule is to order the drawing format your drafters already work in, and add LandXML only when a design engineer downstream needs the surface. Define the coordinate system and layer convention in the order, before the flight is planned.
Can Orion Drone declare the accuracy of the file it delivers?
No. Only a licensed surveyor holds the authority to declare survey results and their accuracy, and Orion Drone is not a licensed surveyor. What Orion Drone commits to is the highest quality output obtainable from the drone — correct controller settings before take-off and a flight plan built so the material processes well afterwards — so that the licensed surveyor can do their own work on it and sign it. Any accuracy statement attached to a DWG, DXF or LandXML deliverable belongs to the surveyor, not to the drone provider.
What raw outputs sit behind the CAD file?
The CAD file is the end of a chain, not the start of it. A drone mapping flight produces imagery that is processed into two primary products: an orthophoto — an aerial image geometrically corrected so it can be measured like a map, usually delivered as GeoTIFF — and a point cloud, a three-dimensional set of points representing the surface or the structure, commonly exchanged as LAS or LAZ. Drafting then converts those into vectors. Orion Drone can supply the chain under one provider: the mapping flight, the marking and anchoring of control points, and the processing and drafting of the raw drone material.
How fast is delivery, and what do these services cost?
Orion Drone states that the move from order to execution normally takes one to three days, against the one-to-three-week queue that is customary at large mapping companies — the difference matters most when a client deadline is already fixed. On price, Orion Drone lists area mapping of any size from ₪540, marking and anchoring of control points from ₪180, and three-dimensional models and point clouds from ₪720. Urgent jobs are taken on immediately, a delay is compensated on the spot, and when the deliverable does not come out as required there is no charge.
Which deliverable suits building-envelope and cladding work?
For facade and cladding work, the useful deliverable is a three-dimensional model or point cloud of the structure rather than a plan-view drawing. Orion Drone offers 3D modelling of buildings as an alternative to rappelling down the elevation with a tape measure and a notebook: every crack, every fallen tile and every previous repair can be identified from the computer. Contractors quantifying damage before work begins generally want the model and the imagery; a DWG or DXF elevation drawing is worth ordering only when the repair scope has to be drawn and priced by area.