.kml
).geojson
).shp
).fgb
).shp
, .shx
, .dbf
, and .prj
. If you do not import the .prj
file, the coordinate system will be incorrect and you cannot render the shapes on a map.+
icon to select files for upload, or drag and drop the files to the Data Importer screen.heavysql
to define tables with columns that store WKT geospatial objects.heavysql
to insert data as WKT string values.ST_Distance
and ST_Contains
. When location data are stored as a POINT column, they are displayed as such when querying the table:ST_Distance
), the SRID values need to match.COPY FROM
in heavysql. By default, the two columns as consumed as longitude x
and then latitude y
. If the order of the coordinates in the CSV file is reversed, load the data using the WITH option lonlat='false'
:.shp
and associated files).geojson
or .json
).kml
or .kmz
).gdb
)COPY FROM
command with the geo
option:POINT
, LINESTRING
, POLYGON
, or MULTIPOLYGON
).enable-assign-render-groups=false
.POLYGON/MULTIPOLYGON
geo files (and CSVs), if HEAVY.AI detects a POLYGON
type geo file, HEAVY.AI creates a MULTIPOLYGON
column and imports the data as single polygons.POLYGON
or MULTIPOLYGON
data, the spatial distribution of the polygons in the existing rows must be evaluated before the new data is imported. This can take some time with large tables and can cause a geometrical slowdown if a large number of files are appended. To mitigate this slowdown, combine data into the minimum possible number of files.GEOMETRY
.WITH
options in addition to geo='true':
COMPRESSED(32)
- 50% compression (default)None
- No compression4326
- EPSG:4326 (default)900913
- Google Web Mercator3857
- EPSG:3857LINESTRING
, POLYGON
and MULTIPOLYGON
is possible only with data stored in the default lon/lat WGS84 (SRID 4326) format, although the type and encoding are flexible. Unless compression is explictly disabled (NONE
), all SRID 4326 geometries are compressed. For more information, see WSG84 Coordinate Compression..gdb
) provides a method of storing GIS information in one large file that can have one or more "layers", with each layer containing disparate but related data. The data in each layer can be of different types. Importing a .gdb
file results in the creation of one table for each layer in the file. You import an ESRI file geodatabase the same way that you import other geo file formats, using the COPY FROM
command with the geo
option:EMPTY
, GEO
, NON_GEO
or UNSUPPORTED_GEO
:EMPTY
layers are skipped because they contain no useful data.GEO
layers contain one or more geo columns of a supported type (POINT
, LINESTRING
, POLYGON
, MULTIPOLYGON
) and one or more regular columns, and can be imported to a single table in the same way as the other geo file formats.NON_GEO
layers contain no geo columns and one or more regular columns, and can be imported to a regular table. Although the data comes from a geo file, data in this layer does not result in a geo table.UNSUPPORTED_GEO
layers contain geo columns of a type not currently supported (for example, MULTIPOINT
or MULTILINESTRING
). These layers are skipped because they cannot be imported completely.COPY FROM
command can result in multiple tables, one for each layer in the file. The table names are automatically generated by appending the layer name to the provided table name.mydata.gdb
which contains two importable layers with names A
and B
. Running COPY FROM
creates two tables, mydata_A
and mydata_B
, with the data from layers A
and B
, respectively. The layer names are appended to the provided table name. If the geodatabase file only contains one layer, the layer name is not appended.geo_layer_name
option:mydata
, and the layer name is not appended. Use this import method if you want to set a different name for each table. If the layer name from the geodatabase file would result in an illegal table name when appended, the name is sanitized by removing any illegal characters.heavysql
process…ENCODING COMPRESSED(32)
. In the following definition of table geo2, the columns poly2 and mpoly2 are compressed.COMPRESSED(32)
compression maps lon/lat degree ranges to 32-bit integers, providing a smaller memory footprint and faster query execution. The effect on precision is small, approximately 4 inches at the equator.ENCODING NONE
.ENCODING COMPRESSED(32)
. In the following definition of table geo2, the columns poly2 and mpoly2 are compressed.COMPRESSED(32)
compression maps lon/lat degree ranges to 32-bit integers, providing a smaller memory footprint and faster query execution. The effect on precision is small, approximately 4 inches at the equator.ENCODING NONE
.