Waiting for PostGIS 2.1: Cheatsheets

BostonGIS BostonGIS Home About Postgres OnLine Journal PostGIS in Action

Saturday, February 09. 2013

Posted by Regina Obe in postgis postgresql, postgis_raster, waiting_postgis_21

Comments (0)
Trackbacks (0)

Waiting for PostGIS 2.1: Cheatsheets

We've done a preliminary generation of function cheat sheets for upcoming PostGIS 2.1. We'll regenerate again before PostGIS 2.1 gets released. We've also updated the PostGIS 2.0 cheatsheets with updated doc links and errata. The html versions of these are generated from the PostGIS documentation xml files using the:

make cheatsheets
build command. Then we just do some massaging to it and print it to PDF.

Pay careful attention to the superscripts on the functions:

Here is list of 2.1 sheets.

PostGIS 2.1 cheat sheets

PostGIS geometry/geography: HTML PDF
PostGIS raster: HTML PDF
PostGIS topology: HTML PDF
PostGIS tiger geocoder: HTML PDF

We are pretty excited about the upcoming PostGIS 2.1. This is the first time we said screw it we aren't going to wait for release and going to take the risk and start running in production. We do so still using extension upgrade using the feature we described in How to Use PostGIS Extensions to upgrade to non-released PostGIS versions. The improvements coming in PostGIS 2.1 are just too tempting to resist. So many goodies: new functions, robustness improvements, performance improvements, and usability improvements, particularly in the raster area. As Duncan put elegantly In 10-fold Speed up in PostGIS 2.1: "So I know what I have been missing out on!". You've just got to experience it for yourself.

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

No comments

Add Comment

Name
Email
Homepage
In reply to
Comment	E-Mail addresses will not be displayed and will only be used for E-Mail notifications. To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information? Subscribe to this entry