Convert TOPOJSON to FILEGDB

Turn TOPOJSON files into FILEGDB. A zipped Esri file geodatabase with one feature class for each kind of geometry among points, lines and polygons, in the source's coordinate system with the attributes as fields.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop TOPOJSON files on the dialor turn it to pick what to do

A zipped geodatabase from your TopoJSON.One feature class for each kind of geometry, with attributes as fields.

  1. What you get

    One zipped Esri file geodatabase. It holds one feature class for each kind of geometry found among points, lines and polygons. The coordinate system of the source is kept, and the attributes become fields.

    When the file has more than one kind of geometry, each kind gets its own .gdb folder.

  2. What changes

    A column named OBJECTID or SHAPE is renamed with _1. Lists and nested values become JSON text.

    Features without a geometry are left out.

  3. Several layers

    When the TopoJSON has several layers, they are joined into one. A layer column names where each feature came from, so you can still tell the layers apart.

TOPOJSON and FILEGDB.What each format is.

The formats

From · TOPOJSON

TopoJSON

TopoJSON, GeoJSON's compact cousin that shares borders between shapes, as D3 maps use it.

Extensions
.topojson
MIME type
application/topo+json
Kind
Text and data
To · FILEGDB

Esri File Geodatabase

An ArcGIS file geodatabase, the .gdb folder of feature classes, zipped to send as one file.

Extensions
.gdb.zip
MIME type
application/x-filegdb+zip
Kind
Text and data

In your code.The same TOPOJSON to FILEGDB conversion through the API, for your app or your agent.

terminal
$ cv convert report.topojson report.gdb.zip
$ cv convert report.topojson report.gdb.zip

Questions.What people ask about TOPOJSON to FILEGDB.

01OF 04

A zipped file geodatabase with one feature class for each kind of geometry: points, lines or polygons. The attributes are stored as fields.

Yes. The output stays in the coordinate system of the source.

Lists and nested values become JSON text. They are not split into separate fields.

No. Features without a geometry are left out of the output.

More conversions.Other ways in and out of TOPOJSON and FILEGDB.