Back to Converter Index
CLI GuideChannel: sap export → geojson

SAP Export to GeoJSON Converter

Translate enterprise table dumps into interactive geo-objects.

Corporate database dumps exported from enterprise systems like SAP often need processing to be visualized in lightweight web maps. This document explains how to safely parse ERP records into structured GeoJSON files.

Indirect Mapping Execution Required

Because database connection attributes or local attributes parsing is required, direct web streams are disabled. Use the GDAL CLI script below for precise terminal conversions.

Specification Rules

  • Incorporate ERP asset coordinates directly into interactive client dashboards
  • Build real-time supply chain maps with up-to-date business data
  • Enable rapid geographical reviews of corporate utility assets
  • Data exports must be sanitized to exclude sensitive corporate secrets
  • Massive databases can cause browser performance bottlenecks
  • Requires intermediate export steps before spatial mapping is possible

GDAL Direct Equivalent Terminal Command

sh — gdalready
$ogr2ogr -f GeoJSON output.geojson sap_extract.csv -oo X_POSSIBLE_NAMES=Easting -oo Y_POSSIBLE_NAMES=Northing -a_srs EPSG:25832

When to use this conversion

Use this workflow when an SAP-extracted CSV containing spatial data needs to feed a web dashboard, a client-side analytics tool, or a REST API rather than a desktop GIS. GeoJSON is the right pivot for any browser-bound destination.

Technical Details

After SAP exports a CSV with coordinate columns, ogr2ogr reads it with explicit -oo X/Y_POSSIBLE_NAMES, applies the documented source CRS with -a_srs, reprojects to WGS 84 for web compatibility with -t_srs EPSG:4326, and emits an RFC 7946 FeatureCollection. Non-coordinate columns become Feature properties; SAP's structured codes are preserved as text.
Output file size

GeoJSON is typically 1.5–3× the size of the source CSV. The blow-up comes from per-feature property key repetition and JSON structural markup; reduce with -lco COORDINATE_PRECISION=6 and aggressive -select.

Common Errors & Fixes

  • Coordinates in projected CRS but output assumes lat/lon: web map shows points in the wrong continent. Fix: identify the source EPSG (often 25832 for German data) and reproject to 4326 explicitly.
  • PII leakage in property fields: SAP exports often include personal data that shouldn't reach a web map. Fix: use -select to whitelist only the columns the dashboard needs.
  • Encoding mismatch: German umlauts arrive garbled. Fix: pass -oo ENCODING=UTF-8 (or the source encoding) and verify the file BOM.
  • Numeric IDs converted to scientific notation: large customer numbers become 1.23E+15. Fix: pre-process the CSV with column types or quote the numeric strings.

Alternative Tools

  • pandas + geopandas: read_csv, build a GeoDataFrame, to_file as GeoJSON — the most flexible for downstream cleaning
  • ogr2ogr CLI with -lco RFC7946=YES -lco COORDINATE_PRECISION=6
  • PostGIS as staging: COPY the CSV into a table, then ST_AsGeoJSON for export
  • Felt or Mapbox Studio for upload-and-render pipelines that handle CSV directly

Frequently Asked Questions

What is the fastest way to extract spatial records from SAP?

Export the target tables in CSV or DBF formats including coordinates, then apply local GDAL scripting for processing.

Are nested properties preserved in the JSON output?

Flat field columns map directly. Complex nested properties are flattened into standard string key-value pairs.

How do I secure the data pipeline?

Run all commands locally inside your private firewall using standard GDAL packages.

Related Transformations Map

Sap To GeopackageCsv To GeojsonGeojson To Csv