Supported formats
Actual format availability depends on the adapter exposed by Catenivo and the runtime shipped with the distribution. A format being known to GDAL does not mean it is automatically exposed.
| Format | Read | Write | Notes |
|---|---|---|---|
| CSV | Yes | Yes | Tabular, UTF-8 for the dedicated adapter |
| Text | Yes | Yes | Text lines |
| GeoPackage | Yes | Yes | Multiple layers; DateTime on read |
| ESRI Shapefile | Yes | Yes | DBF/SHX companion files |
| ESRI File Geodatabase | Yes | Yes | .gdb directory, OpenFileGDB |
| GeoJSON | Yes | Yes | Vector |
| GeoJSONSeq | Yes | Yes | JSON sequence |
| GML | Yes | Yes | Vector |
| KML / KMZ | Yes | Yes | Geographic format constraints |
| MapInfo TAB / MIF-MID | Yes | Yes | Companion files depending on format |
| XLS | Yes | No | Legacy workbook |
| XLSX | Yes | Yes | Tabular sheets |
| ODS | Yes | Yes | Tabular sheets |
| FlatGeobuf | Yes | Yes | Vector |
| GPX | Yes | Yes | Specialized structure |
| DXF | Yes | No | CAD reading |
| DWG | Yes | No | Local LibreDWG conversion to internal DXF |
| DGN V7 | Yes | Yes | Specialized CAD schema |
| Parquet / GeoParquet | Yes | Yes | Shipped Parquet driver |
PostgreSQL/PostGIS is handled through database readers/writers and SQL operators rather than as a file format.
JSON and XML also have extraction and feature-creation operators.
Avoiding data loss
Geometry dimensions, attribute types, text widths, keys, indexes and write modes vary by format. Catenivo rejects conversions it cannot guarantee rather than silently dropping information.
See Supported features and limitations for the overall scope.