# Loop through the shapefile data and add it to our new table.
Shape_records = (shp_rec for shp_rec in r.iterShapeRecords()) # PostgreSQL is transactional which is good so nothing # Commit the change to the database or it won't stick. # If this field isn' the last, we'll add a comma # is not comprehensive but it convers the types in # add the name to the query and our string list of fields # get the field name and lowercase it for consistency # Loop throug the fields and build our table # We are going to keep track of the fields as a # one which is a deletion flag used internally # Get the shapefile fields but skip the first # Build a query to create our "cities" table R = shapefile.Reader("MSCities_Geo_Pts/MSCities_Geo_Pts.shp") # Set up a shapefile reader for our shapefile # Get the database cursor to execute queries
#PYSHP PYTHON MULTIPATCH DRIVER#
# Import the database driver and shapefile libraryĬonnection = nnect(database="test", user="test",
#PYSHP PYTHON MULTIPATCH CODE#
The following code will set up a connection to our test geodatabase, create a table based on the fields of the shapefile, and then load the shapefile data into the table. The shapefile we'll use is a point shapefile containing information about some cities in the state of Mississippi. We have pg8000 installed as our database interface and pushup to read a shapefile. In this example we'll use a database named "test" that is spatially enabled by PostGIS. To get started, follow the PostGIS instructions to get up and running with a spatial database. Both modules can be quickly installed using pip or easy_install. In this post, we're going to use the pure Python, dependency-free pg8000, and pyshp modules to load a point shapefile into a posts database. PostGIS is just a collection of PostgresSQL extensions and functions, so any database driver works. One of the main things I like about PostgreSQL is fantastic Python support with several options for database drivers. For a decade we ArcSDE or Oracle Spatial at NVision but over the last few years we have completely switched to PostGIS unless a client forces us to use a commercial solution. PostGIS is the spatial database engine for the open source PostgreSQL database. In addition to being the best spatial databaseĮngine available, PostGIS can be manipulated
0 kommentar(er)
