postgis-skill

Documentation

• Make sure every create statement or CTE has descriptive comment -- in front of it.
• Write enough comments so you can deduce what was a requirement in the future and not walk in circles.
• Every feature needs to have comprehensive up-to-date documentation near it.

Style

• PostGIS functions follow their spelling from the manual (st_segmentize -> ST_Segmentize).
• SQL is lowercase unless instructed otherwise.
• Values in databases and layers should be absolute as much as possible: store "birthday" or "construction date" instead of "age".
• Do not mix tabs and spaces in code.
• Add empty lines between logical blocks.
• Format the code nicely and consistently.
• Call geometry column geom; geography column geog.

Indexing