Does this work with large site inventories?

Yes. There's no hard limit on export size. Geocoding takes a bit longer for large sets but processes fully. For very large inventories it helps to split your Google Maps lists by project or phase before exporting.

How accurate is the geocoding for industrial or rural sites?

Accuracy is high for named locations with a clear Google Maps listing or street address. It drops for generic descriptions or remote sites without a named location. Review the export and correct any mismatches before using the data in analysis.

Can I load the export directly into QGIS?

Yes. QGIS imports GeoJSON natively via the Add Vector Layer dialog. You can also drag and drop a GeoJSON file directly into the QGIS canvas.

Can field teams use this on mobile?

Yes. The export runs in any browser. A project lead can run the export centrally and distribute the GPX file to field teams via email or a shared drive. Field teams load it into OsmAnd or their GPS device without needing to run the export themselves.

Back

Export Google Maps Location Data to GeoJSON and KML for Spatial Projects

Spatial project teams often start location discovery in Google Maps but need the data in GIS tools for planning. Takeout Tools handles the conversion, with coordinates.

For spatial project management teams

Export your project locations Browse all tools →

Where the friction starts

Location discovery happens in consumer tools. A project lead pins candidate sites in Google Maps, a field team saves access points and inspection locations, a planning team builds a shortlist from satellite imagery. Google Maps is fast, familiar, and works on any device.

The friction starts when the project moves from discovery to planning. QGIS, ArcGIS, and most project management tools that handle spatial data don't read Google Maps exports. And Google Takeout, the official way to get your data out, exports place names without coordinates. That leaves teams manually re-entering location data or rebuilding maps from scratch.

What spatial workflows actually need

Once a project moves into planning, location data needs to be in a format that GIS and operational tools can consume:

GIS analysis: QGIS and ArcGIS work natively with GeoJSON and KML. Loading your candidate sites or inspection points as a layer lets you run proximity analysis, overlay infrastructure data, and do the spatial reasoning that drives project decisions.
Field coordination: Field teams need offline-capable formats. GPX files load into OsmAnd, Gaia GPS, and Garmin devices and work without a data connection. Getting a surveyor or field inspector to the right location is simpler with a GPX waypoint than a Google Maps link.
Reporting and handoff: Stakeholders and contractors who aren't working in GIS often need a visual map or a spreadsheet. KML renders in Google Earth without any software installation; CSV goes into any reporting tool.

The Takeout Tools workflow

Google Takeout exports your saved places as a CSV, names and categories, no coordinates. That's not enough for any spatial analysis tool.

Takeout Tools geocodes each place in your export, recovering latitude and longitude from the place name and address. The result is a structured dataset in whatever format your project workflow requires.

Which format fits which stage

GeoJSON

The right format for QGIS, ArcGIS, Felt, and any modern web-based GIS tool. Load directly as a layer, join with other datasets, and run spatial analysis without any conversion step. The best choice for teams doing active spatial work. Validate your file with the free GeoJSON validator.

KML

The right format for Google Earth and stakeholder deliverables. KML renders cleanly without GIS software and lets you share a styled visual map with people outside the project team. Convert from GeoJSON to KML or GPX to KML as needed.

GPX

The right format for field teams. Load waypoints onto any GPS-capable device or app for offline navigation to site locations. Works on Garmin devices, OsmAnd, and Gaia GPS without a data connection. Convert KML to GPX or GeoJSON to GPX if you're working from an existing file.

CSV

The right format for reporting, Airtable project tracking, and any workflow that needs coordinates as plain data columns alongside other project attributes. Convert GPX to CSV, KML to CSV, or GeoJSON to CSV as needed.

Managing updates across project phases

Spatial projects change. New access points get identified, candidate sites get added or removed, inspection locations shift as the field team works. Rather than re-entering data each time the project moves forward, keep a single Google Maps list per project phase and re-export when it changes. Export to GeoJSON, replace the layer in your GIS tool, and the spatial context stays current without rebuilding your project file.

Distributing location data to contractors

External contractors, surveyors, environmental consultants, construction teams, often need location data without access to your internal GIS environment. A GPX file is the lowest-friction format to share with a field contractor: it works on any GPS device or navigation app, requires no software installation, and doesn't expose other project data. Export the specific locations the contractor needs, send the file, and they can navigate to each point without a data connection.

Naming conventions for project organisation

If your project involves multiple workstreams, use your Google Maps list names to encode that structure before you export. "Phase 1, access routes", "Phase 2, inspection points", "Rejected sites", those names carry through into the exported CSV as a filterable column. A consistent naming convention means the exported dataset is already partially organised, and you can segment by phase or workstream without any manual tagging after export.

Convert between formats

Already have a geo file and need it in a different format? Use the free online converters: