Flattens a FeatureCollection into a table. Properties become columns, taken as the union across every feature so that features with different fields still line up.
Geometry does not fit in a cell
In feature mode you get the first coordinate plus a point count, which is enough to place a marker and to know the shape's size. In coordinate mode you get every vertex as its own row, with the feature's properties repeated. Neither is a lossless round trip for complex geometry — a table simply cannot hold a polygon with holes.
Nested properties
Longitude comes first, and almost nothing else does that
coord_1 and coord_2, because the failure mode when they are swapped is not an error message. It is a map where every point sits in the wrong hemisphere, or in the Gulf of Guinea if one of them was zero.Other names for this
Also searched as “geojson to excel”, “geojson to spreadsheet”.
Questions
- Can I convert back to GeoJSON afterwards?
- Points, yes — use CSV to GeoJSON. Lines and polygons cannot be reconstructed from a table without a convention for grouping rows.
- Why is there JSON in one of my cells?
- That property was an object or an array. Writing it as JSON keeps it parseable rather than losing it.
- Is my file uploaded?
- No. Everything runs in this tab. That matters more here than almost anywhere else on the site — a calendar is your movements, an address book is other people’s personal data, and a GPS track is where you live and where you run. None of it is sent anywhere.