LDS file formats in detail

We want LDS data to be accessible to the widest range of users and available for use in as many software packages and applications as possible. That’s why you can download data in eight different file formats - Shapefile, CSV, KML, GeoTIFF, Jpeg, DWG, and MapInfo TAB formats.

Below are descriptions of two of the more complex file formats we support, the specifications and limitations of their implementation in LDS, and what they’re best used for. Visit the GeoMash forum for community discussion on the development of our implementation of these file formats for LDS.

Esri File Geodatabase

Esri File Geodatabase is a default ESRI format for use in the Esri ArcGIS product. LDS support for Esri File Geodatabase has been provided via the closed source File Geodatabase API by Esri.

 The LDS implementation of Esri File Geodatabase supports:

  • Up to 400% more compact that ESRI Shapefile
  • Spatial indexes on geometry fields
  • UTF-8 character encoding
  • Long field names
  • Fields with data larger than 255 characters

  • Large tables and feature classes (up to 1TB)

The LDS implementation of ESRI File Geodatabase has the following limitations:

  • One layer (feature class) per geodatabase
  • Compatible with ArcGIS version 10+ only
  • No attribute indexes on primary and foreign keys (property and ownership layers only)
  • Feature class fields no not contain any constraints (e.g such as NOT NULL)
  • Export and import translation required to copy FGDB features classes into an ArcGIS created FGDB dataset or feature class

CSV/WKT

CSV/WKT is a tabular in plain text format. This format allows simple downloads of bulk data for loading data into a database system. See our advanced user guide for step-by-step instructions on importing CSV files from LDS into PostgreSQL/PostGIS and Microsoft SQL Server 2008 using GDAL and FME.

The LDS implementation of CSV/WKT supports:

The LDS implementation of CSV/WKT has the following limitations:

  • Primary keys and fields constraints (e.g such as NOT NULL) are not listed in the VRT schema
  • Byte Order Mark header (for UTF-8 support) cannot be read by some software packages. For a workaround, see the Importing CSV files from LDS advanced user guide
top