Export API

Export project geometries by format, feature type and map extent.

Last updated: 10 November 2026

On this page

Endpoint and formats Parameters Download example Coordinate system CAD round trip Permissions and empty results

Endpoint and formats

GET /api/p/{pid}/export downloads project data accessible to the user. Select fmt for geometry output:

`fmt`	Content type	Contents
`geojson`	`application/geo+json`	Geometry and attributes
`kml`	`application/vnd.google-earth.kml+xml`	Map features
`xlsx`	`application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`	Feature and attribute table
`dxf`	`application/dxf`	CAD layers and drawing output
`bundle`	`application/gzip`	Structured project bundle

fmt defaults to geojson. csv, shp, kmz, gpkg and FileGDB are not output options for this endpoint. GeoPackage and FileGDB support is for import. CSV and PDF field reports are available through the separate Outputs API.

Parameters

Parameter	Use
`types`	Comma-separated feature types, such as `cable,duct`
`refs`	`1` includes reference features; `0` excludes them; default `1`
`bbox`	WGS 84 bounds: `minLongitude,minLatitude,maxLongitude,maxLatitude`
`kapali`	Authorised administrator request to read disabled-module data
`crs`	Target coordinate system for DXF
`olcek`	DXF drawing scale; `0` selects automatically
`etiket`	DXF label selection; default `1`
`egri`	Whether to use the original DXF curve definition; default `1`

bbox selects features by their geometry bounding boxes; it does not clip geometries at the box edge. Send technical catalogue keys in types. With refs=1, reference features may be added to the type filter. Use refs=0 to receive only selected infrastructure types.

Download example

This request downloads fiber cables and ducts as GeoJSON:

GET /api/p/{pid}/export?fmt=geojson&types=cable,duct&refs=0

Replace {pid} with the project identifier. The response body is the file itself, not a file inside a JSON API envelope. Read the download name from Content-Disposition. The response includes Cache-Control: no-store.

GeoJSON export carries feature identifier in _id, type in _type and displayed type name in _type_name. It differs from the map read API's properties.v version envelope. Reimporting without a source selection creates new records. To compare and update existing data, use the source-based reimport workflow.

Coordinate system

GeoJSON and KML use the stored WGS 84 geometry. crs controls DXF conversion. DXF selection uses the request crs, then the project coordinate system, then the default EPSG:5255. Use crs=local for a project-defined local transformation.

DXF rejects EPSG:4326 with 400. For technical drawings, choose a metric coordinate system appropriate to the data's location. Import specifies the source system; export specifies the target system.

CAD round trip

DXF output can carry feature identifiers in CAD metadata. A supported original curve definition is written again if the geometry is unchanged and the output coordinate system matches the source. Use egri=0 for linear geometry; do not assume the original curve remains unchanged when geometry or coordinate system changes.

Review field mappings and identifier candidates when uploading the exported file again. An ordinary import does not automatically update the existing project; select source comparison separately.

Permissions and empty results

A Viewer with read permission can export too. kapali=1 does not grant permission; disabled-module data remains subject to authorised administrator scope. If active filters leave no features to export, the endpoint returns 400.

Geometry formats do not transfer equipment, fiber connections, circuits and all relationships as a complete project. Use Project bundle for a full project transfer. fmt=bundle behaves separately and does not produce partial bundles using bbox or types filters.