Import and Export Data
FSQ Spatial Desktop supports secure local and remote data access for high-performance spatial analysis. Load large local datasets, including GeoParquet and PMTiles, for fully offline workflows, or connect directly to cloud storage such as cloud storage (S3), HTTPS URLs, and MotherDuck.
Supported File Formats
FSQ Spatial Desktop can import a wide range of tabular, spatial, and columnar file formats, either from your local computer or from remote sources such as cloud storage (S3), HTTPS URLs, and MotherDuck. Once imported, files are stored inside your project database and available for querying, visualization, and analysis.
Import Formats
| Format | Extension | Description |
|---|---|---|
| CSV | .csv | Comma-separated tabular data |
| TSV | .tsv | Tab-separated tabular data |
| JSON | .json | Structured data in row or column form |
| GeoJSON | .geojson | Geographic features in JSON format (points, lines, polygons) |
| Parquet | .parquet | High-performance columnar data format |
| GeoParquet | .geoparquet | Parquet extended with geometry columns |
| Apache Arrow | .arrow | In-memory columnar binary format |
| Shapefile | .shp | ESRI vector format (include the accompanying .dbf, .shx, and .prj files) |
| KML | .kml | Keyhole Markup Language, used by Google Earth |
| Spatial Project | .spatial | FSQ Spatial Desktop project file |
Additional geospatial formats supported by DuckDB and GDAL — including GeoPackage (.gpkg), FlatGeobuf (.fgb), GML, and others — can also be loaded by selecting the file directly.
Exporting Data
FSQ Spatial Desktop lets you export your data, query results, and map views to a range of file formats for use in other tools
or for sharing with collaborators. Exports run locally and never leave your machine unless you choose to upload them.
What You Can Export
You can export from three places in the app:
- Tables — Export any table in your project (raw or derived).
- Query results — Export the output of a query straight from the SQL Editor.
- Map views — Export the current map as an image.
- Full projects — Export your entire workspace, including data, layers, filters, and settings.
Supported Export Formats
| Format | Extension | Best For |
|---|---|---|
| CSV | .csv | Spreadsheets, general-purpose analytics tools |
| JSON | .json | APIs, web apps, structured data exchange |
| Parquet | .parquet | Large datasets, downstream data pipelines |
| Map Image | .png, .jpeg | Presentations, reports, quick sharing |
| Spatial Project | .spatial | Sharing a complete workspace with another user |
Note: Excel (
.xlsx) export is not currently supported.
Exporting a Table
- Open the Data Sources panel.
- Right-click a table (or open its context menu) and choose Export.
- Select a format (CSV, JSON, or Parquet).
- Choose a destination on your computer and confirm.
Exporting Query Results
- Run a query in the SQL Editor.
- Click the Export button above the results grid.
- Pick a format (CSV or Parquet) and save the file.
Useful for extracting a filtered subset of data without creating a new table.
Exporting a Map Image
- Open the map view you want to export.
- Click the Export Image button in the map controls.
- Choose resolution (standard or high-DPI) and image format (PNG or JPEG).
- Save the file.
Exporting a Full Project
Exporting a project produces a single .spatial file containing all data, layers, filters, saved queries, and AI
conversations. Anyone with FSQ Spatial Desktop can open it and see the exact same workspace.
- Open the File menu.
- Choose Export Project.
- Select a location and save the
.spatialfile.
Exporting via SQL
For advanced or scripted exports, you can use DuckDB's COPY statement directly in the SQL Editor:
COPY (SELECT * FROM my_table)
TO '/path/to/output.parquet' (FORMAT PARQUET);
COPY (SELECT * FROM my_table)
TO '/path/to/output.csv' (HEADER, DELIMITER ',');
COPY (SELECT * FROM my_table)
TO '/path/to/output.json' (FORMAT JSON);Updated about 7 hours ago
