Import and export data in Emlid Flow and Emlid Flow 360

In this support tip, we will discuss data import and export in Emlid Flow and Emlid Flow 360 to help you transfer data between the field and the office effectively. Understanding which file formats are supported and what the requirements are for them can help you to prevent data errors and ensure a smoother workflow. Let’s cover the main points to keep your data import and export fast and straightforward.

Importing data

Importing allows you to add external data, such as control points, geometries, CAD drawings, and surface files to your project. This is often the first step in linking your office data with fieldwork, so it’s essential to get it right.

Please note that you need a Survey Plan to work with lines and polygons. Without it, your project will be limited to points only; other geometries will be ignored during the import. Similarly, DXF as CAD drawings and LandXML are only available with a subscription and can only be imported through Emlid Flow 360 before accessing them in Emlid Flow.

Format requirements

  • CSV: This format should include headers such as Point, Easting, Northing, and Elevation to ensure data imports correctly.
  • PENZD / PNEZD: Use these formats when importing data without headers. Columns must follow the exact order: Point, Easting, Northing, Elevation, and Description or Point, Northing, Easting, Elevation, and Description.
  • KML Files: This format can include points, lines, and polygons.
  • DXF: This format can include points, lines, and polygons. Curves and splines will be automatically converted into polylines. Solid 3D objects, like volumes or meshes, and TIN surfaces will be ignored.
  • Shapefile: This format can include points, lines, and polygons. Curves and splines will be automatically converted into polylines. Your file must be a ZIP archive with a set of files for each geometry type. For each type, the three required files are SHP, SHX, and DBF, all with the same name. From the attributes, we preserve only the name and description. All the others will be ignored.
  • CAD drawings (DXF): This format should include lines, polylines, and blocks for smoother CAD-to-field workflows. Curves and splines will be automatically converted into polylines. The stylings will be preserved, thus you can use the file as a background and for stakeout. This format can only be imported through Emlid Flow 360.
  • LandXML surfaces: You can import terrain models for cut/fill tasks in the field. This format can only be imported through Emlid Flow 360.

General requirements

  • Coordinate system: Make sure the file’s CS matches the project’s CS so points are correctly placed.
  • Decimal separators: Emlid Flow and Emlid Flow 360 expect periods (.) for decimal points. Confirm your numbers use the correct format. To separate columns, always use commas.
  • Encoding: Special or non-Latin characters (accents, Cyrillic letters, slashes, or dots) can affect import. Saving the file in UTF-8 ensures compatibility.
  • File size: You can upload files with a maximum of 15,000 points at once. For DXF files as CAD drawings, use version 2010 or newer and keep the file under 25 MB. LandXML surface files also have a 25 MB limit, and if your file contains multiple surfaces, only the first one will be imported.

Exporting data

Exporting lets you transfer your collected data from Flow for use in CAD, GIS, or reporting tools.

When exporting a project in Emlid Flow or Flow 360, you can adjust several settings depending on the selected format:

Format adjustments

  • CSV / Custom CSV: For coordinate lists or data exchange. Keep field names clear and consistent—renaming or removing required fields may cause compatibility issues. Choose a preset template or create a custom one to set field order and content. Keep in mind that custom templates are only available with the Survey Plan.
  • DXF: For CAD environments. Choose to export points or lines, set the coordinate system to local to ensure smooth workflow, and define linear units such as meters or feet.
  • KML: For visualization in Google Earth or GIS. Export points, lines, or polygons with names and descriptions. All KML files are automatically created in WGS84.
  • Shapefile: For GIS and mapping workflows. Select geometry types (points, lines, or polygons), confirm the project CRS, and choose which attributes to include. All files share the same export name.

General requirements

  • Coordinate systems and linear units: Always pay attention to the coordinate system and linear units when exporting data. Using the correct CRS and matching units ensures points are placed correctly in CAD or GIS software. For example, when exporting a DXF file from a project in a local coordinate system, select the Local Coordinates option to ensure the drawing aligns properly in CAD.
  • Large project size: Exporting projects with thousands of points or long linework can take several minutes. Wait for the process to finish before closing the app.

Tips for successful data import and export

Let’s summarize the key points to ensure a smooth, successful workflow:

Before you import

  1. Make sure that the CS of the imported file and the created project are the same.
  2. Prepare imported data by making sure it corresponds to the format requirements.
  3. Make sure you import your data using the correct platform—Emlid Flow or Emlid Flow 360. Keep in mind that you can import DXF and LandXML through Emlid Flow 360 only.
  4. If you import your data through Emlid Flow 360, make sure that it’s synced in Emlid Flow, so the data is available for field work.

When you export

  1. Make sure you meet the requirements of your software.
  2. Open the exported file in your target CAD/GIS to validate:
    • Coordinates & units (CS, meters/feet).
    • Geometry (points/lines/polygons render as expected).

By understanding the supported formats, limitations, and common pitfalls, you’ll save time and avoid frustration. With Emlid Flow and Flow 360, data management is smooth and reliable—when you know the rules of the road. Learn more in the Create and Import project and Export Projects guides. Do you have any tips or workflows that make data management easier for you? We’d love to hear how you use Flow and Flow 360 in your projects.

Thanks for the intricate summary

boston

Thanks for the thorough rundown. Just taking the opportunity to reiterate the need for unique shp export filenames instead of hardwired, non-descriptive ones like “points”. Something like the project name with a timestamp would work well, ie “myproject_points_20251105_173427”. Or at least give us the option to specify our own filenames.

Thank you!

Hi @piampietro

Yeah, I agree on this. I believe it can be helpful in file identification and organization. I added your input as a +1 on this feature request. We have no ETAs on this at the moment, and if anything changes, I will let you know.

Hello Keith ,

Please add me as +1.

I would also suggest notching this up a level more than just being helpful and consider it proactive problem avoidance.

With the same names on a growing collection of files I’m already starting to lose track and in some cases overwriting them.

The more customers love the product and use it, conversely the more likely they might also come unstuck and have a bad experience which is not what you want!

Cheers

Thank you @keith.mwangi !

This was requested in at least one earlier thread as well.

@Wombo

Noted! I have gone ahead to add yours as well. We appreciate your thoughts on this as we continuously work to meet our users’ needs, and we keep this thread posted with any news on this.

I would like for Emlid to include more variables then east, north and name for polygons. When I am prepering for fieldwork I sometime need to have older data, like some points I took earlier this year, or data showing parcels of land and i find it really limiting not to have more data in Emlid Flow. I have to look stuff up online and in the field that is just annoying.

Hi @AdamHz ,

Do I understand correctly that you would like to add additional labels to polygons, or for Emlid Flow to be able to read them out from the imported shapefile? So, if you select them, it display all the additional information regarding them?

Also, if you can share any file examples with us, it would help a lot. You can send it to [email protected].

This way, I can provide all the necessary information to our developers.

I would like Emlid to read them from the imported shapefile so I can select them and see all information
and would like to to be able have some control over the symbols, f. ex a simple fill and outline.

The picture is a screenshot from Qfield. If I press a polygon, point or line I can read the attributes.

Hi @AdamHz ,

Thank you for the clarification and examples!

I provided all the information to our developers.

Just wanted to chime in and give a million thumbs up for adding LandXml as an export as well. :sweat_smile:
Currently, I would say, the best format to exchange data between CAD and GIS.

ref. This thread (Issue users have moving data)
Edit: I know export is a tough one because the software needs to maintain and keep a complete object model and hierarchy

Hi,

Got it and passed it to the developers! Have a nice rest of your day.