Bulk Data Delivery Formats
Introduction
Regrid provides data in a variety of formats and configurations.
Parcel Data File Formats
Format | Description |
---|---|
CSV | All available data in CSV format, with double-quoted strings. A parcel centroid is provided in the lat and lon columns, but the full parcel geometry is not included. This format is often used in cloud based applications. Spreadsheet applications can make use of this format, but will likely encounter cell and row size limits. |
CSVWKT | All available data, with full geometries provided as Well-Known Text (WKT) in a column called wkt . |
File GDB | Esri-specific spatial format. |
GeoJSON | Web development and JavaScript focused. |
GeoPackage | Open source, QGIS and general interchange format, SQLite based. |
KML | Google Earth native format, does not handle typical county dataset sizes very well. |
Newline-delimited GeoJSON | Each parcel is represented by a GeoJSON feature. Each feature is on a separate line. |
Shapefile | Legacy Esri format. We recommend GeoPackage or FileGDB over Shapefile. The Shapefile format has a maximum data size of 2GB (some clients can read up to 4GB) and will truncate column names. |
SQL | Postgresql SQL for loading into Postgresql databases. |
Parquet | Commonly used in cloud based workflows, please see our parquet FAQ |
Parcel Record Layout Options
Record Layout | Description |
---|---|
Standard Tier | This includes all of the fields listed in our Standard Tier, plus all of the custom columns each county provides. Processing workflows must allow for a variable number of custom columns not in the Regrid schema. |
Standard Tier, Schema Only | This includes only the fields listed in our Standard Tier and none of the custom columns each county provides. Processing workflows can rely on a fixed number of fields. |
Premium Tier | This includes all of the fields listed in our Premium Tier plus all of the custom columns each county provides. Processing workflows must allow for the variable number custom columns. |
Premium Tier, Schema Only | This includes only the fields listed in our Premium Tier and none of the custom columns each county provides. Processing workflows can rely on a fixed number of fields. |
Building Polygon Data File Formats
Compressed size of buildings data ranges between 20G - 45G.
Format | Description |
---|---|
CSVWKT | All the available data, full geometry provided as Well Known Text. |
File GDB | Esri-specific spatial format. |
GeoJSON | Web development and JavaScript focused. |
Newline-delimited GeoJSON | Each parcel is represented by a GeoJSON feature. Each feature is on a separate line. |
GeoPackage | Open source, QGIS and general interchange format, SQLite based. |
Shapefile | Legacy Esri format. We recommend GeoPackage or FileGDB over Shapefile. The Shapefile format has a maximum data size of 2GB (some software can read up to 4GB) and will truncate column names. |
SQL | Postgresql SQL for loading into Postgresql databases. |
Standardized Zoning File Formats
Compressed size of zoning data ranges between 16M - 2G.
Format | Description |
---|---|
CSVWKT | All available data, with full geometries provided as Well-Known Text (WKT) in a column called wkt . |
File GDB | Esri-specific spatial format. |
GeoJSON | Web development and JavaScript focused. |
GeoPackage | Open source, QGIS and general interchange format, SQLite based. |
KML | Google Earth native format, does not handle typical county dataset sizes very well. |
Newline-delimited GeoJSON | Each parcel is represented by a GeoJSON feature. Each feature is on a separate line. |
Shapefile | Legacy Esri format. We recommend GeoPackage or FileGDB over Shapefile. The Shapefile format has a maximum data size of 2GB (some clients can read up to 4GB) and will truncate column names. |
SQL | Postgresql SQL for loading into Postgresql databases. |
Parquet | Commonly used in cloud based workflows, please see our parquet FAQ |
Matched Address Data File Formats
Compressed size of matched address is about 10G.
Format | Description |
---|---|
CSV | All the available data, with comma separated, double-quoted strings, and lat/lon coordinates. Often used in cloud based applications. Spreadsheet applications can make use of this format, but will likely encounter cell and row size limits. |
File Compression
Compression | Description |
---|---|
Zip .zip | All file formats and record layouts are available as zip files. Supported on most platforms. |
Gzip .gz | Only available with CSVWKT formatted files. Intended for use in Google BigQuery and other data-processing applications. |