Postgresql import dbf file

Connect and share knowledge within a single location that is structured and easy to search. I want to import a shp file to postgreSQL.

To create sql file, I run this command in windows cmd:. It seems that PostGIS is not yet installed. PostGIS is an extension of Postgres which allows the use of geographic files.

The ERROR: function addGeometrycolumn unknown, unknown, unknown, unknown,unknown, integer does not exist means that the postgis extension is not installed on your postgresql.

Go here and install it. You have a different projection in your psql; and having a projection is not necessary. Is there a schema you want to add the shape file to? Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. For troubleshooting, feature requests and general help contact Customer Support at. Make sure to include details on your browser, operating system, DBFView version and a link or relevant code.

Free Download Buy Now! How to use. Buy Now! Free Trial Download. The user friendly graphic makes working with databases simple and hassle free. What does shp2pgsql command does? If shp2pgsql is not installed, you should first download the same from the authentic website and then try to follow out the steps provided below.

For inserting shapefile to postgis, we first need to have one shapefile. For instance to demonstrate import shapefile in postgresql, I have downloaded United state administrative boundary shape file. Now this unzip the folder. You can choose any other shape file which contain atleast this 3 files i.

Now to import shape file you first need to create database and table. Now lets create one database using given command as:. We read the DBF metadata again and created a java prepared statement that would insert a single line of data. We "called" that prepared statement for each row in the DBF file. This makes sure we don't have problems with inadvertent SQL injection, e.

In reality we used batches of rows ps. Both dramatically improve performance. We could have gone through an intermediate file and used COPY but it was easier and safer for us to do it programmatically. We also wrote our own DBF reader. It only took a day and we were able to work around some numeric overflow bugs that we found in third-party libraries. You can find enough information on Google that this isn't too hard. One thing to be careful about is that "dbf" is vague.

All dBase files have the same overall structure but there are tweaks from different publishers and versions. They're documented but you'll want to determine what version your file uses and then code to it. If the database files that you have come from database servers that you control or otherwise have access to, then you will find it a lot easier to use some form of ETL tool to pull the data from those servers and pump it into your postgres instance s , instead of trying to decode the data files directly.

Even a manual export from the databases in their natural home to some convenient format and import from there would be preferable to working with the binary data files directly. Sign up to join this community.