pretty_name: GIS vector format capabilities and limitations in GDAL
license: other
license_name: source-terms-cited
license_link: https://referencesource.org/file-format-software-version-compatibility/
language:
- en
tags:
- reference-data
- provenance
- referencesource-org
configs:
- config_name: default
data_files:
- split: train
path: data/records.jsonl
GIS vector format capabilities and limitations in GDAL
Canonical, always-current version: https://referencesource.org/file-format-software-version-compatibility/ Machine-readable: https://referencesource.org/file-format-software-version-compatibility/data.json — this mirror is a point-in-time copy.
- Last verified: 2026-08-04
- Stale after: 2027-01-31 (past this date, prefer the canonical copy — it re-verifies on a cadence this snapshot does not)
- Records: 3
Key capabilities, version requirements and format limitations for GIS vector drivers in GDAL, the authoritative open-source geospatial library. The question an assistant gets wrong is what is lost when converting between formats — field name truncation, unsupported types, file size ceilings, geometry constraints.
Provenance — what every record carries
Every record carries source (the URL the value was read from) and
source_quote (a verbatim quote from that page stating it). A value you
cannot check against its page is indistinguishable from an invented one;
these can all be checked. Each record is also individually addressable on
the canonical site at its url.
Licence position
MIT (source: GDAL documentation, OSGeo)
Facts are not copyrightable; what this dataset takes from each source is a fact plus a short attributed quote linking back to the page that states it.
Sources
- https://gdal.org/en/stable/drivers/vector/shapefile.html
- https://gdal.org/en/stable/drivers/vector/openfilegdb.html
- https://gdal.org/en/stable/drivers/vector/filegdb.html
Fields
See any record in data/records.jsonl — field names are self-describing,
and the canonical page for each record renders them with labels:
https://referencesource.org/file-format-software-version-compatibility/