Alex Zvoleff azvoleff

Overview

In general, it seems there are roughly five (5) ways to get "file data" (e.g. a GeoTIFF) out of a PostGIS geoprocessing workflow:

Export just the raster field as an ASCII grid
Connect to the database using a desktop client (e.g. QGIS) [1]
Use a procedural language (like PLPGSQL or PLPYthon) [2]
Use the COPY declaration to get a hex dump out and convert it to a binary file
Fill a 2D NumPy array with a byte array and serialize it to a binary file using GDAL or psycopg2 [3, 4]
Use ST_AsTiff() or the more general ST_AsGDALRaster() to get a byte array, which can be written to a binary file

WAL-E needs to be installed on all machines, masters and slaves.

Only one machine, the master, writes WAL segments via continuous archiving. The configuration for the master postgresql.conf is:

archive_mode = on
archive_command = 'envdir /etc/wal-e.d/env wal-e wal-push %p'
archive_timeout = 60

	from osgeo import ogr

	data = ogr.Open('/path/to/vector/file')

	print('Data Name:', data.GetName())

	# get a layer with GetLayer('layername'/layerindex)
	for layer in data:
	print('Layer Name:', layer.GetName())
	print('Layer Feature Count:', len(layer))

	import requests

	def doi2bib(doi):
	"""
	Return a bibTeX string of metadata for a given DOI.
	"""

	url = "http://dx.doi.org/" + doi

	headers = {"accept": "application/x-bibtex"}