KML vs GeoJSON vs CSV: Which Export Format to Use for Photo GPS Data
When you have extracted GPS coordinates from a set of geotagged photos, the next decision is what format to export them in. GeoMeta Pro offers four options: KML, GeoJSON, CSV, and PDF. Each serves a different downstream use, and picking the right one saves time when you get to your next step — whether that is opening the data in Google Earth, importing it into GIS software, cleaning it in a spreadsheet, or sharing it in a report.
This guide explains exactly what each format is, what software opens it, when it is the right choice, and when it is not.
KML — Keyhole Markup Language
What it is
KML is an XML-based file format developed originally for Google Earth (previously called Keyhole EarthViewer, which is where the name comes from). It is now an open standard maintained by the Open Geospatial Consortium. A KML file describes geographic features — points, lines, polygons, and overlays — along with their visual style, descriptions, and optional metadata.
What opens it
- Google Earth (desktop and web): the primary use case. Drag the file into Google Earth to see your photo locations as placemarks on satellite imagery.
- Google My Maps: import a KML to create a shareable custom map.
- QGIS: opens KML files natively as a vector layer.
- ArcGIS: supports KML import via the KML to Layer tool.
- Garmin GPS devices: many units accept KML or the closely related KMZ format.
When to use KML
KML is the right choice when your goal is a visual map presentation. If you need to show a client where photos were taken on a site, share a coverage map with a project manager, or explore your photo locations on satellite imagery for your own analysis, KML opens instantly in Google Earth with placemarks labelled by filename.
KML is also a good handover format when working with teams that use Google Earth as their everyday mapping tool but do not have desktop GIS software installed. It requires no technical setup — double-click and it opens.
When not to use KML
KML is not well-suited for import into modern web mapping applications or for programmatic processing. If you are building a web-based map or need to process coordinates in code, GeoJSON is the better choice. KML is also verbose — it can become large for very big datasets.
GeoJSON — Geographic JavaScript Object Notation
What it is
GeoJSON is a JSON-based open standard for encoding geographic data structures. It represents points, lines, polygons, and collections of features using standard JSON syntax. It has become the dominant format for geographic data in web applications and modern GIS tools because it is compact, human-readable, and natively supported by virtually every JavaScript mapping library.
What opens it
- Any text editor: it is plain JSON, so it is readable without special software.
- Leaflet, Mapbox, OpenLayers: load GeoJSON directly with a single function call.
- QGIS: opens GeoJSON as a vector layer natively.
- ArcGIS: supports GeoJSON import.
- GitHub: automatically renders GeoJSON files on a map when viewed in a repository.
- geojson.io: paste or drag a GeoJSON file for instant online visualisation.
When to use GeoJSON
GeoJSON is the right choice for any technical workflow. If the data will be processed by code, imported into a web map, fed into a GIS analysis pipeline, or stored in a geographic database, GeoJSON is the standard format to use. It is also appropriate when data will be shared with a developer or GIS analyst who will work with it programmatically.
For environmental and scientific work where data is submitted to open geographic databases or repositories, GeoJSON is generally preferred over KML because it integrates more cleanly with data processing toolchains.
When not to use GeoJSON
GeoJSON is not the best choice for non-technical stakeholders who just need a visual map. Google Earth does not open GeoJSON natively — it must be converted to KML first. For presentations or client handover where simplicity matters, KML is easier.
CSV — Comma-Separated Values
What it is
CSV is the simplest of the four formats. It is a plain text file with one row per image, where columns are separated by commas. Each row contains the image filename, GPS latitude, GPS longitude, altitude if available, capture timestamp, camera make, camera model, and other detected EXIF fields. There is no geographic structure — it is purely tabular data.
What opens it
- Microsoft Excel and Google Sheets: open directly and display as a table.
- Any database system: CSV is the universal import format for SQL databases, data warehouses, and asset management systems.
- Python and R: loaded with a single pandas or read.csv command for programmatic analysis.
- QGIS: imports CSV as a point layer when latitude and longitude columns are specified.
When to use CSV
CSV is the right choice when the data needs to go into a spreadsheet, a database, or a reporting system. For inspection workflows where each image record needs to be entered into a project management system, asset tracker, or field reporting database, CSV provides the cleanest import path. It is also the format to use when you need to combine photo metadata with other tabular data — asset lists, inspection checklists, or project schedules — in Excel or Google Sheets.
When not to use CSV
CSV has no geographic structure, so it cannot be used directly as a map layer without conversion. If your next step involves placing points on a map in GIS software or a web application, export GeoJSON or KML instead (or export CSV and import it into QGIS specifying the latitude and longitude columns).
PDF — Portable Document Format
What it is
The PDF export from GeoMeta Pro generates a structured report containing the image metadata table, the GPS summary statistics, and basic batch information. It is formatted for printing and for document management archiving.
When to use PDF
PDF is the right choice for any situation where the audience does not have technical tools and needs a document they can view, print, or file. Client reports, inspection sign-off documents, insurance claim records, and audit trail documentation are all appropriate use cases. If you need to submit a field visit record to a client or to a document management system alongside the original image files, PDF provides a clean, professional-looking summary that anyone can open.
When not to use PDF
PDF data cannot be directly imported into GIS, spreadsheet, or database systems. It is a presentation format, not a data exchange format. If you need the data to be processed further, export CSV or GeoJSON alongside the PDF.
For most professional field workflows, export both CSV and KML from the same batch. Use the CSV for your records database and the KML for site coverage review in Google Earth. The two exports take seconds and cover the most common downstream needs.
Quick decision guide
- Need to show locations in Google Earth? → KML
- Building a web map or using GIS software? → GeoJSON
- Importing to Excel, a database, or a project system? → CSV
- Creating a client report or filing an inspection record? → PDF
- Not sure? → Export CSV and KML together — they cover most use cases.
All four formats can be exported in the same session from the GeoMeta Pro tool after loading your images. There is no limit on how many formats you export from a single batch.