If we don’t specify the specific columns that the fields in the CSV map to, errors will occur when attempting to copy the data. The CSV does not include either of these columns in the data we are copying. Our table includes a column gid that is an auto-incremented id which is used as a primary key as well as the_geom geometry column. The first argument passed to the copy command specifies the tablename ( landmarks) and the columns which the CSV files map to.

There are a couple of things to note with the copy command: To run the copy command, login to the database and execute the following command : Step 2 - Copy the CSV data into the database Use the following SQL to create a table to hold the landmark data. Step 1 - Create the table in the database You can hide the column by selecting the arrows on the column heading in the table ( shown here) or via the manage screen and deselecting the location column from the list of available columns ( shown here).Ī PostgreSQL database with PostGIS installed. We already have the latitude and longitude and the extra location field isn’t something that we’ll use so I removed the location column prior to exporting the dataset. You can get a copy of the CSV file that I am using for the example here. For this example I’ll be using the Individual Landmarks dataset exported as CSV. In this post I’ll take a look at importing latitude and longitude data from a CSV file into our PostGIS database and transforming those coordinates into geometry data that can be spatially queried against. Sometimes location data isn’t neatly packaged in a SHP file, and it requires some massaging before it can be used in spatial queries.

Import csv to pgadmin 4