Optimal Formats for RTK Field Data: CSV / SHP / DXF / LandXML

Table of Contents

• Introduction

• Features, Advantages, and Disadvantages of CSV Format

• Features, Advantages, and Disadvantages of SHP (Shapefile) Format

• Features, Advantages, and Disadvantages of DXF Format

• Features, Advantages, and Disadvantages of LandXML Format

• Comparison of Formats and Selection by Use Case

• Characteristics and Convenience of Simple Surveying with LRTK

• FAQ

Introduction

RTK (Real-Time Kinematic) positioning is a high-precision surveying method using GNSS, and because it can acquire positional coordinates more quickly and with centimeter-level accuracy (half-inch accuracy) compared to conventional surveying, it is widely used in civil engineering surveying and topographic surveys. To make effective use of field data acquired by RTK afterward, it is important to decide in which format to save the coordinate data and feature information collected on site. The choice of storage format can significantly affect subsequent data processing, sharing, and preservation of accuracy.

However, surveying data can be stored in various formats. Representative examples include the simple tabular CSV, the vector format widely used in GIS SHP (shapefile), the CAD-compatible DXF, and the XML-based format for survey and design data exchange LandXML. Each format differs in data structure and the information it can represent, and they vary in terms of compatible software, use cases, interoperability, and ease of handling.

This article explains in detail the characteristics of these four representative formats (CSV, SHP, DXF, LandXML) for saving and using RTK survey field data, and compares their advantages and disadvantages. It also delves into which use cases each format is suitable for, differences in data accuracy and expressiveness, and impacts on operational efficiency and field usability. At the end of the article, we introduce the features and convenience of simple surveying using the increasingly notable LRTK, and touch on new ways to utilize high-precision positioning. Now, let’s look at the details of each data format.

Features, Advantages, and Disadvantages of CSV Format

CSV stands for "Comma-Separated Values" and is one of the simplest formats for saving data as comma-delimited text files. In surveying, it is often used to record observed point coordinates and measurement values in tabular form. For example, if you save a table with columns such as point ID, latitude/longitude or planar coordinates (X, Y), elevation (Z), and point name or attribute information as a CSV file, you can easily accumulate many point data acquired by RTK.

Advantages:

• High versatility: Because CSV is plain text, it can be used in many environments without specialized software. You can open and edit it directly with spreadsheet software or a text editor, enabling quick data checking on site with just a laptop.

• Lightweight and simple: The data structure is simple, allowing you to store a list of coordinate points as-is, resulting in relatively small file sizes. Because the format is simple, read/write operations are fast. It is also easy to extend by adding columns for required information.

• Easy conversion to other formats: Coordinate data saved in CSV can be imported into many GIS and CAD programs. As a generic format, CSV is often used as an intermediary file for conversion to other specialized formats.

Disadvantages:

• No spatial structure: CSV is just a tabular format and cannot directly retain geometric information such as lines or polygons that connect points. For example, to represent feature boundaries or area polygons, you must separately define how coordinate points are combined. Thus, its capability for map or drawing representation is limited.

• Attribute management requires care: If you want to attach various attributes (e.g., point type or description) to each point, CSV represents each attribute as a separate column. As data volume grows, the number of columns can increase and management may become cumbersome. Also, CSV does not clearly enforce data types (numeric, string, etc.), making inconsistencies due to input errors more likely.

• Attention needed to preserve accuracy: When recording coordinate values in decimal notation, some software or settings may limit decimal places or perform rounding. For RTK-level high-precision positioning data, failing to save sufficient decimal places can result in loss of millimeter-level information. Also, common spreadsheet software may automatically change number formats when opening a file (e.g., scientific notation or rounding), so careful handling is required.

CSV is mainly useful as a list of observed points and is suitable for simple sharing of observations or computation. For example, a workflow might be to first save the raw observed point set as CSV, then later import it into GIS for mapping or into CAD for drafting. However, because it lacks shape structure, CSV is not suitable as the final deliverable format. In practice, use CSV for temporary on-site backups or as a transfer format to other software, and convert or integrate into other formats as needed.

Features, Advantages, and Disadvantages of SHP (Shapefile) Format

The SHP format (shapefile) is a vector data format used mainly in GIS. In addition to the ".shp" file, it comprises multiple files such as ".shx" (index file) and ".dbf" (attribute table), and is designed so that spatial data and attribute data are handled together. Shapefiles are widely used to save and share point clouds, drawn lines, and polygons obtained by RTK positioning as geospatial information.

Advantages:

• Integrated management of spatial data and attributes: Shapefiles can link attribute information to each geometry (point, line, polygon). For example, if you save an observed point with its feature type or name, you can manage location and attributes together in a GIS. Attributes are stored in the table (.dbf), with field types defined for numbers, strings, logical values, etc., enabling more organized data management than CSV.

• Broad support in GIS software: Shapefiles have been used as a standard format in the industry for many years and are natively supported by many GIS applications. They are often used for spatial data delivery in local governments and public works, allowing RTK-acquired data to be incorporated into various systems as geographic information. Some CAD software and surveying instruments also support shapefile import/export, making interoperability relatively high.

• Suitable for spatial analysis and visualization: Shapefiles are well suited for map display and spatial analysis. For instance, loading numerous RTK-observed points as shapefile points allows instant rendering of distribution maps, and lines saved as line data make distance and area measurements easy in GIS. Spatial indexing (.shx) enables efficient querying and display, so shapefiles handle relatively large datasets well.

Disadvantages:

• Multiple files and size limits: Shapefiles are managed as a set of multiple files rather than a single physical file, so careful handling is required. If some files are missing during copy or transfer, the data may not open correctly. Also, under older specifications, each file is limited to 2GB, making shapefiles unsuitable for extremely large datasets.

• Attribute constraints: Because attributes are stored in DBF format, there are constraints such as field names limited to 10 characters, limits on the number of fields and string lengths. If you want to include long Japanese field names or detailed text information, you need to devise workarounds. Additionally, supported data types are limited, and older formats do not directly support date/time or Unicode, reflecting limitations due to aging specifications.

• Limited expressiveness for advanced geometry: Shapefiles represent points, polylines, and polygons as sets of linear vertices. They cannot natively handle smooth curves like circular arcs or Bézier curves, so precise shape representation like in CAD drawings is limited. Similarly, advanced 3D information (e.g., curved surfaces or complex solids) cannot be retained; while points with elevation or contour lines can be handled, shapefiles are not suitable for full 3D design data exchange.

• Effort required for editing and updates: Once a shapefile is created, its structure (such as adding or changing fields) is not easily modified, which can be inconvenient in practice. When updating data, inadvertently changing the attribute table’s column definitions may require re-exporting to another format. Compared to flexible databases or newer formats, shapefiles are less convenient to manipulate.

Shapefile format is established as a reliable format for handling spatial data across many types of work. It is suitable when organizing RTK survey results as map data, for example, when importing them into road registries or facility management systems. If observed points on site are assembled into shapefiles, later personnel can easily visualize and append data in GIS. However, due to the aforementioned limitations in expressiveness and capacity, you may need to migrate to formats like DXF or LandXML when dealing with more complex 3D data or precise design information.

Features, Advantages, and Disadvantages of DXF Format

DXF is a data exchange format used in CAD (computer-aided design) software. Standing for "Drawing Exchange Format," it has been widely used to transfer drawing information between different programs. It describes geometric elements in text format (ASCII), which requires specialized knowledge to edit or interpret directly, but many CAD programs support it, making DXF a de facto common language for CAD drawings. DXF is useful when importing terrain maps or as-built drawings obtained by RTK positioning into design drawings.

Advantages:

• High compatibility with CAD: DXF was originally developed for CAD data exchange and can represent a variety of elements used in drawings such as lines, points, polylines, polygons, circles, curves, and text annotations. If you want to reflect surveyed features in CAD drawings, outputting them as DXF makes it easy for recipients to open them in major CAD software. Layer information, line types, and colors can also be preserved to some extent, enabling data exchange while maintaining drawing appearance.

• Preservation of curves and complex shapes: Unlike GIS shapefiles, DXF can directly describe curve elements such as circles, arcs, and splines. Therefore, it can accurately store and reproduce shapes that include curves, such as road curves or circular structures. When smoothing lines drawn from RTK-acquired points or handing them to designers as-is, DXF is advantageous.

• Wide software support: In addition to CAD software, some GIS and 3D visualization tools support DXF import, giving it broad applicability. DXF has a long history, and many legacy DXF drawings may be archived as data assets, making it easy to ensure future compatibility.

Disadvantages:

• Files can become large: Because DXF records coordinates and geometry in text form, file sizes tend to be larger compared to binary formats. Saving site measurement data with many points and line segments in DXF can cause file sizes to grow, making email attachments or transfers inconvenient. Including unnecessary intermediate points or property information can make the data redundant.

• Limited support for attribute information: DXF is primarily for exchanging geometry and basic layer information and is not suited for storing the kind of rich attribute data found in GIS. For example, adding metadata like observation timestamps or operator names to survey points has no standardized method for direct storage in DXF (although block attributes or extended data can be embedded, compatibility is not guaranteed). Thus, DXF is not ideal when sharing data beyond drawing content.

• Not suited for advanced analysis: DXF mainly contains geometric information and lacks features for spatial analysis or topology that GIS provides. Therefore, to analyze spatial relationships between figures in DXF or automatically generate polygons, you often need to convert the data to a GIS format first. Also, coordinate systems or unit systems are not explicitly included, so exchange between different geodetic systems requires caution.

DXF is an essential format in the design and drafting field and is especially useful for data sharing with civil designers and CAD operators. If you deliver as-built drawings created from RTK surveys as DXF, recipients can use them directly in design drawings. However, if you only handle simple point data, DXF may be overkill; in such cases, CSV or shapefile may suffice. Conversely, when line design or complex structure layouts require precision in drawings, preserving curve information in DXF and handing it over is best practice.

Features, Advantages, and Disadvantages of LandXML Format

LandXML is an XML-based data exchange format developed for the civil engineering and surveying industries. As the name implies, it is "XML for land," and it is notable for being able to describe not only coordinate sets but also structured design elements and survey results. For example, it can represent three-dimensional terrain models (DTM) such as elevation point clouds and triangulated irregular networks (TIN), road alignments (centerline stations and curve elements), cross-section shapes, and even utilities and structure layouts, all within a single XML file.

Advantages:

• Comprehensive information storage: LandXML can retain surveying and design elements in a hierarchical structure. A single file can contain observed point lists, surface triangular mesh models, design alignments, profiles, cross-sections, annotation information, and more, enabling project-wide data exchange. Storing RTK-derived terrain data together with related design data helps prevent information loss during handover to downstream processes.

• Explicit precision and unit systems: LandXML explicitly describes unit systems (meter/foot systems, etc.) and coordinate reference systems (datums and projections) for numeric values such as coordinates, distances, and areas. This reduces the risk of misinterpretation when exchanging data between different reference systems. Numeric values can also be saved as text with high precision, preserving RTK centimeter-level accuracy (half-inch accuracy).

• Industry-standard interoperability: LandXML is an open standard developed and maintained by international consortia, and it is supported by major civil CAD, 3D modeling, and surveying calculation software. Exchanging data in LandXML allows you to convey not just geometry but also design intent such as alignments and profiles. In public works CIM (Construction Information Modeling), LandXML is positioned as one of the standards for 3D design data exchange.

Disadvantages:

• Complex file contents: Because it is XML-based, LandXML is not easy for humans to read directly; tag hierarchies can be deep, making manual editing impractical. Therefore, handling LandXML requires compatible software, and you cannot easily inspect contents with generic tools as you might with CSV or DXF. File sizes can also become large, and LandXML files for large projects may be very big.

• Limited scope of use: Although LandXML has advanced capabilities, it can be unwieldy where such capabilities are unnecessary. For example, if you only need to share a few coordinates, CSV or shapefile is sufficient and creating LandXML is unnecessary overhead. In other words, LandXML is primarily suited to design stages and deliverables, and is not ideal for simple on-site data exchange of raw survey data.

• Differences in software implementations: Even as a standard format, software differs in how it interprets or supports LandXML. A LandXML file exported by one program may have certain elements (e.g., detailed style information or metadata) ignored or unsupported when imported into another program. Expecting perfect compatibility can occasionally lead to unexpected results, so mutual validation between systems is essential for important data exchanges.

LandXML is suited for 3D design data exchange and delivery of advanced surveying results. For example, in large road construction projects, managing both surveyed terrain (as-built) and design models (planned) in LandXML enables applications such as earthwork calculations, construction control, and lifecycle management. However, for routine field operations, LandXML is often overkill, so it is practical to generate LandXML only when needed (for public surveying projects, LandXML deliverables are typically prepared when requested).

Comparison of Formats and Selection by Use Case

So far we have examined CSV, SHP, DXF, and LandXML individually. In practice, it is important to choose the appropriate format based on the type of survey data and the intended use. Here are key comparison points and recommendations by use case.

• Comparison of data structure and expressiveness: Simple point data is adequately handled by CSV, but representing features as lines or polygons requires SHP or DXF. If you need to handle curves accurately, DXF is appropriate; if you want to manage attribute-rich area information, SHP is advantageous. LandXML can include higher-level structured data (3D models and alignment info), making it far more expressive for design stages.

• Accuracy and file reliability: RTK-level high-precision data can be stored adequately in any of these formats, but attention differs by format. With CSV, be careful to preserve decimal places; with SHP and DXF, manage coordinate systems (e.g., using a separate .prj file or drawing unit settings). LandXML can embed units and coordinate system information, reducing the risk of misinterpretation, though it demands more expertise to operate.

• Supported software and compatibility: CSV is highly versatile but spatial usage generally requires conversion to other formats. SHP is the de facto standard in GIS and facilitates smooth data exchange between municipalities and survey firms. DXF is convenient for design and construction workflows, particularly for drawing-centric communication. LandXML offers rich information exchange for advanced workflows but requires pre-coordination between supported software to ensure compatibility.

• Operational efficiency and usability: CSV’s convenience for immediate on-site checking and editing is appealing, but final deliverable preparation requires additional work. SHP can often serve directly as deliverable data and is efficient as a basis for maps or registries. DXF reduces drafting effort and smooths communication with designers. LandXML enhances reuse across a project lifecycle but requires planned generation of only the necessary parts for daily operations.

Overall, no single format is perfect, and choosing an appropriate format according to purpose is essential. For example, a hybrid workflow is realistic: record daily observations as CSV, convert to shapefile for internal GIS use, prepare DXF for designers, and archive comprehensive project data as LandXML upon completion. The important point is to select formats that allow efficient use while ensuring that accuracy and information are not lost.

Characteristics and Convenience of Simple Surveying with LRTK

Recently, RTK positioning technology has become more accessible and easier to use. A representative approach is called LRTK. LRTK combines high-precision GNSS antennas and dedicated apps with convenient devices such as smartphones, enabling RTK positioning—formerly requiring specialized equipment—to be used as simple surveying by anyone.

Using LRTK, for example, centimeter-level positioning (half-inch accuracy) with one smartphone per person becomes possible even without dedicated surveying instruments, allowing quick on-site measurements whenever needed. Real-time correction functions and cloud or network services automate the previously complex base station communication setup, so technicians with limited surveying expertise can operate it relatively easily. Acquired position information can be saved and managed on the cloud, enabling flexible workflows where you can later export required formats (CSV or map data) without worrying about data formats at collection time.

In this way, simple surveying with LRTK offers significant benefits as an inexpensive, fast, and easy-to-use high-precision positioning method. It is powerful for a wide range of scenarios, from minor everyday surveying needs to rapid situational assessment during disasters. If you want to adopt RTK positioning for your operations but find traditional equipment too burdensome, consider LRTK. With the latest technologies, the processes from data acquisition to utilization are being dramatically streamlined, and an era is approaching where you can immediately leverage necessary information without worrying about format differences.

（※LRTK: A generic term for a form of Real-Time Kinematic positioning that can be used with convenient devices; not tied to any particular brand）

FAQ

Q1. Do RTK positioning data necessarily require expensive software to use? A1. No, expensive specialized software is not always necessary. Basic coordinate data can be exported as CSV and analyzed with general spreadsheet software. Free GIS software can handle shapefiles, and open-source tools can read DXF or LandXML. Depending on the use case, it’s good to start with simple tools.

Q2. Which format best preserves RTK positioning accuracy? A2. All formats can basically preserve sufficient accuracy. That said, with CSV pay attention to decimal place settings; with DXF or SHP explicitly manage the original geodetic information (coordinate system or projection). LandXML can include unit and coordinate system information, reducing the chance of misinterpretation, though it is more complex to handle. The key is to operate so that the original data accuracy is preserved (appropriate format settings and verification during conversion).

Q3. Which format is convenient to carry out from the field? A3. For field convenience, exporting data as CSV for quick checks on a small PC or tablet is practical. Shapefiles are convenient for direct map display but require dedicated apps. DXF has good visual clarity as drawings but needs a CAD viewer. Depending on the situation, a typical approach is CSV for quick checks, SHP for map display, and DXF for sharing as drawings.

Q4. Which format is recommended for future data utilization? A4. For long-term data retention, saving in multiple formats is recommended. For example, archive raw data as CSV, keep spatial data as SHP, and save design-used information as DXF or LandXML. Storing redundantly makes it easier to extract necessary information regardless of future software environments. Also, preserving key 3D information in the international standard LandXML helps ensure system interoperability in the future.