> For the complete documentation index, see [llms.txt](https://codifi-fdm.gitbook.io/codifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codifi-fdm.gitbook.io/codifi-docs/web-app/gis-exports.md).

# GIS Exports

You can export the spatial data in a Codifi Project as a standalone GIS file — for sharing with stakeholders, importing into ArcGIS Pro or QGIS, or attaching to a deliverable.

> The export contains **Record geometries plus their associated field data**. Media files are not embedded in the GIS export; for those, use the separate media export from the Project workspace.

***

## Supported formats

| Format                    | Extension                                     | Best for                                                                                                          |
| ------------------------- | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **GeoPackage**            | `.gpkg`                                       | Modern GIS workflows; preserves complex geometries, mixed geometry types, and attribute richness in a single file |
| **Shapefile**             | `.shp` (with sidecars `.shx`, `.dbf`, `.prj`) | Wide compatibility, including older agency systems that haven't moved past Shapefile                              |
| **GeoJSON**               | `.geojson`                                    | Web tooling, scripting workflows, lightweight inspection                                                          |
| **Esri File Geodatabase** | `.gdb`                                        | Agencies and clients who require a native Esri deliverable                                                        |

{% hint style="success" %}
**File Geodatabase export is new in v3.3.** Previously `.gdb` had to be produced by exporting GeoPackage or Shapefile and converting in ArcGIS Pro or QGIS. That step is no longer necessary.
{% endhint %}

***

## Exporting What You Are Looking At

The Records list used to offer two GeoPackage options that were easy to confuse. As of v3.3 there is a single **Export as GeoPackage** action, and it exports exactly what you currently have selected and filtered.

Filter the Records list down to what you want, tick the Records if you want a subset, and export. What lands in the file is what was on your screen. Shapefile and File Geodatabase behave the same way.

***

## What's in an export

For each archetype with geometry, the export produces a layer (in GeoPackage / Shapefile) or a FeatureCollection (in GeoJSON) containing one feature per Record, with:

* **The geometry** — point, line, or polygon as configured on the archetype.
* **Attributes** — every field on the Record, named by field label.
* **Calculated fields** — Ripple-computed values are exported as their evaluated values, not as formulas.
* **Metadata** — Record ID, archetype name, creation/modification timestamps, assignee.

### Records Without a Location

Records with no geometry cannot go into a spatial layer. Rather than dropping them silently or letting them corrupt the output, v3.3 writes them to a **companion CSV inside the same zip**.

That means two things. Nothing is lost: every Record you selected is accounted for, either in the spatial layer or in the CSV beside it. And the spatial layer stays valid, so the file opens cleanly in ArcGIS and QGIS rather than failing on a geometry-less feature.

This applies to GeoPackage, Shapefile, and File Geodatabase alike.

***

## How to export

1. Open the Project workspace.
2. Click the **Exports** menu in the top toolbar.
3. Choose **GIS Export**.
4. Pick a format (GeoPackage / Shapefile / GeoJSON).
5. (Optional) Pick which archetypes to include — by default, all archetypes with geometry are exported.
6. (Optional) Apply a filter — only export Records matching certain criteria, e.g., status = Approved.
7. Click **Export**. The file is generated server-side; you'll be notified when it's ready to download.

> **Screenshot placeholder:** *The GIS Export modal showing format, archetype, and filter selectors.*

***

## Coordinate reference system

All exports are in **WGS84** (EPSG:4326) — the same projection Codifi uses internally for storage and rendering.

If your downstream tool needs a different projection (UTM zone for the Project area, NAD83, state-plane), reproject after export using ArcGIS Pro, QGIS, or a scripted tool like `ogr2ogr`.

***

## Datum: NAD83 vs WGS84

For most Projects in the continental US, the difference between WGS84 and NAD83 is sub-meter and doesn't affect typical workflows.

If you're working with high-precision survey data where the datum matters (e.g., centimeter-grade GPS), be aware that:

* Codifi stores and exports coordinates as captured (WGS84 by default).
* The mobile app supports **datum conversion** during manual coordinate entry — if a crew member types NAD83 or NAD27 coordinates, the app converts at save time.
* Once stored, coordinates are WGS84 regardless of how they were entered.

***

## Mobile vs Web differences

The export workflows are identical in output — same formats, same attribute schema. The only difference is where you initiate them:

* **Web** — full filter + archetype-selection UI in the Project workspace.
* **Mobile** — limited; typically used only for pulling a recent copy of the Project's geometry to share by email or AirDrop. Most teams export from web.

***

## File size and limits

Spatial exports are generally small — even a Project with 10,000 STPs produces a Shapefile under 5 MB. The main size driver is the number of fields per archetype, not the number of Records.

If an export takes a long time:

* Check that you haven't accidentally included a huge Composition with hundreds of fields you don't need.
* Use the archetype selector to limit to just the layers you need.
* Apply a filter to narrow the Records.

For Projects with **>50,000 Records of one archetype**, exports may take several minutes. Consider exporting by archetype to keep file sizes manageable.

***

## Common pitfalls

* **Exporting to Shapefile with long field names.** Shapefile truncates field names to 10 characters. Long fields become `Project__1` etc. GeoPackage and GeoJSON have no length limit.
* **Multi-select dropdown values in Shapefile.** Shapefile attribute cells are limited length; large multi-select arrays may truncate. Prefer GeoPackage for these.
* **Mixing geometry types in one Shapefile.** Shapefile requires one geometry type per file — points and polygons can't share a Shapefile. GeoPackage and GeoJSON handle mixed geometry without issue.
* **Assuming `.gdb` still needs converting.** It doesn't, as of v3.3. File Geodatabase is a native export format now, so there's no reason to go out through GeoPackage and back in through ArcGIS Pro.

***

## Related

* [The Project Workspace](/codifi-docs/web-app/the-project-workspace.md) — where exports are kicked off
* [Map Setup & Offline Areas](/codifi-docs/web-app/map-setup-and-offline-areas.md) — how overlays you exported are configured back into a Codifi Project
* [Reports](/codifi-docs/reports/how-to-use-the-documentation.md) — the other major export workflow (Word/Excel)