Getting started2 min read
Formats and connections
What GeoDoctor can read, and the limits on each.
| Format | Notes |
|---|---|
| Esri Shapefile | Multi-file, zipped, or a whole folder of them; companion files checked on intake |
| GeoPackage | Multi-layer, single file |
| Esri File Geodatabase | Multi-layer; curved geometry is linearised on read |
| GeoJSON | Single layer |
| GeoParquet | Efficient for very large extracts |
| KML / KMZ | Including compressed archives |
| CSV and Excel | Point data from coordinate columns, with CRS selection |
| AutoCAD DXF and DWG | Layers come from CAD layer names; a drawing without a coordinate system asks for one. DWG is converted on upload, and coverage varies by AutoCAD version |
Live connections#
- PostgreSQL / PostGIS — read tables with no export step
- SQL Server, Oracle, MySQL and enterprise geodatabases (ArcSDE) on those databases, on request. Versioned (the DEFAULT version) and archived feature classes are read, and one GeoDoctor cannot read is named with the reason
- OGC WFS, OGC API Features and Esri REST — pull layers from an existing data infrastructure
- Folders and network shares — saved once, read again by each scheduled run
Stuck on something not covered here? Email [email protected] — a person replies within one business day.