GIS Tools

Language

Made withfor the GIS community

Attribute Table Exporter

Export feature attributes to CSV or Excel format

Import & Export

Drop GeoJSON file here

Export attributes to spreadsheet formats

Load a GeoJSON file to preview attributes

Export Formats

  • CSV: Opens in Excel, Google Sheets, LibreOffice
  • TSV: Tab-delimited, better for data with commas
  • JSON: Array of objects, good for programming

What Is an Attribute Table Exporter?

Every vector GIS layer has two parts: the geometry (where the features are) and the attributes (what they are). The attribute table holds the per-feature data β€” names, codes, populations, dates, statuses, measurements β€” and is often the part you actually want to analyse. The Attribute Table Exporter on gis.tools is a free, browser-based tool that strips the geometry away and exports just the attribute table as CSV or Excel-friendly format, ready for opening in spreadsheets, importing into databases, or feeding into statistical software.

For anyone working with shapefiles, GeoJSON, KML, or any other vector format, separating attributes from geometry is one of the most common needs. You might want to:

  • Email a colleague the data without the spatial overhead
  • Open the table in Excel for editing or pivot analysis
  • Import the data into a SQL database alongside non-spatial tables
  • Run statistical analysis in R, Python, or SPSS
  • Generate a report or dashboard from the attribute values
  • Audit data quality without needing GIS software

How the Exporter Works

The exporter parses your input file, walks every feature, and writes a row per feature with one column per property. It also adds optional columns for derived geometric values like centroid coordinates, area, length, or bounding box, so you don't lose all spatial information when going to a flat table. The output is standard CSV (RFC 4180) with UTF-8 encoding, suitable for Excel, Google Sheets, LibreOffice Calc, or any database import tool.

Geometry Summary Columns

Optionally, the exporter adds:

  • Centroid coordinates β€” Lat and lon of each feature's centroid
  • Area β€” In square meters (geodesic) for polygons
  • Length β€” In meters (geodesic) for lines
  • Bounding box β€” minX, minY, maxX, maxY
  • Vertex count β€” Useful for QA

These are computed during export, so you don't need a separate geometry tool.

Excel Compatibility

The exporter produces a UTF-8 BOM-prefixed CSV that Excel opens correctly without misinterpreting non-ASCII characters. For native Excel format, an .xlsx option produces a single-sheet workbook.

Practical Applications

Spreadsheet Analysis

A planner has a parcels shapefile and wants to pivot owners by zoning category in Excel. Exporting the attribute table is the fastest path.

Database Import

A developer needs to load 10,000 city points into a SQL database alongside other reference tables. CSV is the lowest-common-denominator format every database can read.

Statistical Analysis

Researchers running regressions in R or Python often need only the attributes, not the geometry. CSV is the universal interchange format for statistical software.

Reporting

Dashboards built in Power BI, Tableau, or Google Data Studio start from tabular data. Exporting attributes lets the dashboard developer skip the GIS layer entirely.

Data QA

Finding null values, duplicates, or outliers in a large attribute table is easier in a spreadsheet or database than in a GIS attribute table viewer.

Email and Collaboration

A colleague who doesn't use GIS software can still review a CSV in Excel.

Batch Editing

For mass attribute updates (e.g., correcting typos in 500 city names), exporting to CSV, editing in a spreadsheet, and re-importing is often the fastest workflow.

Step-by-Step Workflow in gis.tools

  1. Open the Attribute Table Exporter page.
  2. Drag your GIS file (shapefile, GeoJSON, KML, etc.) into the drop zone.
  3. The exporter parses the file and previews the attribute table.
  4. Select which columns to include (defaults to all).
  5. Optionally add geometry summary columns (centroid, area, length).
  6. Choose output format: CSV (UTF-8 BOM) or XLSX.
  7. Click Download to save the file.

Worked Example

A city analyst has a parcels shapefile with 12,000 features and 28 attribute columns. They want to do a market analysis in Excel based on owner type and assessed value. They drop the shapefile into the exporter, deselect the columns they don't need (keeping only owner_name, owner_type, assessed_value, area_sqft, zoning, year_built, and the centroid coordinates), and export to XLSX. The resulting workbook is 2.4 MB and opens instantly in Excel. They build a pivot table grouping by owner_type and zoning, summing the assessed_value, and have an answer in five minutes.

Common Pitfalls and Gotchas

  • Encoding issues β€” Non-ASCII characters in attribute values can become mojibake if the destination tool doesn't handle UTF-8. The BOM helps Excel.
  • Field name truncation β€” Shapefile attributes are limited to 10 characters; the exported CSV inherits this limitation.
  • Date format inconsistency β€” Different GIS formats encode dates differently. The exporter normalises to ISO 8601.
  • Loss of spatial context β€” Without geometry, you can't do spatial queries downstream. Add geometry summary columns to preserve some context.
  • Numeric precision β€” Excel may display very large or very small numbers in scientific notation, which can confuse non-technical users.
  • Multi-value attributes β€” Some formats allow array-valued attributes; CSV doesn't support nesting, so they get serialised as JSON strings.
  • Trailing whitespace β€” Attribute values with leading or trailing whitespace can cause join failures downstream.

Tips for Best Results

  • Always export to UTF-8 with BOM for Excel compatibility.
  • Include centroid columns if you might need to re-map the data later.
  • Strip whitespace from string columns before export.
  • Validate the source GeoJSON with the GeoJSON Validator & Fixer before export.
  • Use semantic, descriptive column names if you're going to share the file.
  • For very wide tables (50+ columns), select only what you need.
  • Document the export date and source so the file's lineage is clear.

Comparison with Other GIS Approaches

QGIS has Save Features As β†’ CSV which produces a similar output. ArcGIS Pro has Table to Excel and Table to dBASE. ogr2ogr can convert any vector format to CSV with -f CSV. The browser-based gis.tools exporter is the most accessible option for non-developers and works on any vector format the loader supports.

Performance Considerations

Export is fast β€” even a million features can be written in a few seconds. The bottleneck is the destination tool: Excel struggles with more than ~1 million rows, while CSV files have no practical limit.

Data Privacy and Browser-Based Processing

The entire export operation runs in your browser tab. Your attribute data β€” which often includes personally identifiable information, addresses, and financial figures β€” never leaves your machine.

Related GIS Concepts

Attribute Table β€” The tabular companion to a vector layer, with one row per feature.

Field Type β€” The data type of an attribute column (string, integer, float, date). CSV is typed by convention only.

RFC 4180 β€” The IETF specification for CSV files, including quoting and escape rules.

XLSX β€” Microsoft Excel's modern XML-based workbook format.

Frequently Asked Questions

Will the export include the geometry?

Not by default β€” only attributes. You can optionally add centroid, area, and length columns.

What about non-ASCII characters?

The exporter writes UTF-8 with BOM, which Excel interprets correctly.

Can I export multiple files at once?

This tool processes one file at a time. For batch jobs, use ogr2ogr.

What's the row limit?

No practical limit for CSV. XLSX is capped at about 1 million rows by Excel.

Related Tools on gis.tools

100% client-side processing - your data stays private and never leaves your device