Content guessing does not require the target columns to be named in a special way (such as “country” or “city”), CARTO inspects the different available columns and identifies which of them can be guessed geospatially.
This automatic geocoding only occurs if there is not a big proportion of repeated, or null values, in a column. Otherwise, double quoted fields are used when enabledįiles that contain country, city, IP address information can be automatically geocoded by the system, if the content guessing option is enabled. Quoted fields guessing: when disabled, avoids double quoted fields for type guessing. If enabled, it generates numeric and boolean columns when appropriate, otherwise, it uses regular string columns Type guessing: determines the type of imported columns from the text contents, available in the CSV file. There are two particular guessing options for these type of files:
The following guessing options are available:įor files whose format does not include type information (usually CSV files), field guessing options can be enabled. This is useful for when files or data are missing some upload information. Import GuessingĬARTO includes guessing functionality during the import process. Any names that conflict with a reserved word are prefixed with an underscore (_) automatically. There are certain words reserved in the system that cannot be used to name columns or datasets, mainly the PostgreSQL reserved words. Names are trimmed if they exceed this length Column and table names can have a maximum of 63 characters.Column names must begin with a letter (a-z) or an underscore (_).Otherwise, “table_” is prepended to the name Table names must begin with a letter (a-z).NamingĪpply the following naming conventions for datasets in CARTO, and avoid using the reserved words as part of your file names. Otherwise, importing datasets which do not meet the requirements (such as a dataset with duplicated integers in its cartodb_id column) will result in an import failure. If these columns are generated by the user, the CARTO table requirements must be followed in order to produce a successful import. This ensures that importing an exported dataset contains the original exported dataset content and row order. When a dataset is exported from CARTO, it includes the cartodb_id and the_geom columns, which will be reused if the dataset is then imported to the system.
This column is automatically created when overview representations of data are created (for datasets containing more than 500,000 points).
#UPLOAD KML TO CSV HOW TO#
It includes how CARTO guesses content during the import process, lists the supported geospatial formats for uploading data, and describes how to upload multilayer datasets or batch file uploads. This section explains how importing a dataset creates columns in CARTO (and the naming conventions that you should use).