Guide: run locallysap data → geopackage

SAP Export to GeoPackage via CSV

SAP data is no GIS format. A CSV export with coordinate columns can be converted with GDAL; this guide shows how.

GDAL, and therefore this site, has no driver for SAP data. What works: export a table from SAP as CSV that contains coordinates (longitude/latitude or x/y) and convert that CSV. On this site the CSV to GeoJSON and CSV to Shapefile converters do it online; locally one ogr2ogr command writes a GeoPackage.

Guide: run this conversion locally with GDAL

GDAL has no SAP driver, so there is no SAP upload. Convert a CSV export with coordinate columns instead, online with the CSV converters or locally with the command below.

What the command does

  • ogrinfo --formats of GDAL 3.10.3 lists no SAP driver.
  • A CSV with coordinate columns can be read by GDAL's CSV driver; X_POSSIBLE_NAMES and Y_POSSIBLE_NAMES name the columns, -a_srs sets the coordinate system.
  • Without coordinate columns (e.g. only addresses) the CSV converters on this site cannot create geometries.

GDAL command to run locally

sh — gdal
$ogr2ogr -f GPKG output.gpkg export.csv -oo X_POSSIBLE_NAMES=lon -oo Y_POSSIBLE_NAMES=lat -a_srs EPSG:4326

Replace lon and lat with your column names and EPSG:4326 with the coordinate system of your values.

Tested with

Test fileResult
CSV with id, name, lat, lon (3 rows)GeoPackage layer with 3 points, EPSG:4326; lat and lon as Real columns

Tested on 24 Sep 2026 with GDAL 3.10.3 (conda-forge build on Windows).

Limits

  • Needs coordinate columns in the export; addresses alone are not enough.

Frequently Asked Questions

Can I upload the CSV here?

Yes: CSV to GeoJSON and CSV to Shapefile accept it and detect common coordinate column names.

Related conversions