PostGIS

Crunchy Bridge comes equipped with PostgreSQL extensions that allow for storing, processing, and analyzing geospatial data:

• PostGIS 3.1
• pgRouting
• PostGIS Raster

Enable PostGIS

The PostGIS extension must first be enabled before enabling the Raster and pgRouting extensions.

Crunchy Bridge enables database auditing by default, however pgAudit must be disabled temporarily in order to install the PostGIS extension. You can do this by running:

SET SESSION pgaudit.log = 'none';
CREATE EXTENSION postgis;
SET SESSION pgaudit.log = 'all';
Copy

PostGIS needs to be enabled in every database where you want to work with geospatial data.

Tip: You can check the full PostGIS version that has been installed by running the following:

SELECT PostGIS_Full_Version();
Copy

Loading vector data

There are a variety of ways to load vector data. Common tools used are:

• shp2pgsql
• ogr2ogr
• QGIS

For more details as well as an interactive tutorial, see:

• Loading Data into PostGIS: An Overview
• Load Data into PostGIS (Crunchy Data Learning Portal)

Raster data storage and processing with PostGIS raster

Enable the PostGIS Raster extension:

CREATE EXTENSION postgis_raster;
Copy

Out-DB raster storage

Because Bridge is hosted in the cloud, you can connect your Bridge PostgreSQL & PostGIS to remote object storage where the raster data is uploaded. This is also known as "out-db" storage, where a pointer (which includes bounds and a reference to the external location) is saved in PostGIS for the raster files. The raster files themselves could be stored in the cloud, such as in an Amazon S3 bucket.

More details are available in PostGIS Raster and Crunchy Bridge.

Working with PostGIS

Many third-party tools are compatible with PostgreSQL/PostGIS as a spatial database:

Desktop GIS

• QGIS
• ArcGIS
• ArcGIS Pro

Web map servers

• GeoServer
• MapServer
• MapNik
• pg_tileserv & pg_featureserv