Convert CSV to FILEGDB

Turn CSV 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 CSV files on the dialor turn it to pick what to do

A geodatabase made from your CSV rows.Each row becomes a point or a shape in a zipped Esri file geodatabase.

  1. What you get

    A single zipped file holding a file geodatabase. It has one feature class for each kind of geometry found among points, lines and polygons. The other columns become attributes, stored as fields.

    When there are several kinds, each kind gets its own .gdb folder. The coordinate system is the source's.

  2. How rows become features

    A row becomes a point when the table has longitude and latitude columns, such as lon and lat or x and y. A row becomes a shape when the table has a WKT column. Coordinates are taken as WGS 84.

    A table with neither fails with unsupported_elements.

  3. What changes

    A column named OBJECTID or SHAPE is renamed with _1, since those names belong to the geodatabase. Lists and nested values become JSON text. Features without a geometry are left out.

    There are no options to set. To combine several tables first, see merge CSV.

CSV and FILEGDB.What each format is.

The formats

From · CSV

CSV

Rows of comma-separated values. The plainest way to move a table between programs.

Extensions
.csv
MIME type
text/csv
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 CSV to FILEGDB conversion through the API, for your app or your agent.

terminal
$ cv convert sheet.csv sheet.gdb.zip
$ cv convert sheet.csv sheet.gdb.zip

Questions.What people ask about CSV to FILEGDB.

01OF 04

It needs longitude and latitude columns, such as lon and lat or x and y. A WKT column with shapes works as well.

Coordinates are taken as WGS 84.

The table has no longitude and latitude columns and no WKT column. Without one of them there is no geometry to build.

They are left out of the geodatabase. Only features with a geometry are written.

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