Build templates

A good fit when

• Spatial data has to be shared across several systems
• A map service must be operated in-house, but the ground rules are not set
• Spatial data scattered across files is moving into a database

Example components

• Docker composition
• Layer and style conventions
• WMS/WFS service defaults
• Backup and restore procedure

A good fit when

• Each incoming dataset uses a different coordinate system and attribute convention
• Evidence of what failed and why has to remain before the data is loaded
• The same validation has to run again on a regular cycle

Example components

• Conversion pipeline
• Validation rule set
• Validation report
• Load and rollback procedure

A good fit when

• Screens and external systems have to share the same business data
• Existing APIs have grown without shared rules for permissions and error handling
• An integration specification has to be handed over as a document

Example components

• Authentication and authorization layer
• Standard response and error format
• List, detail, and write operations
• Generated API documentation

A good fit when

• The order of what to fix first has to be decided
• A system was inherited without a handover and has to be understood first
• Evidence is needed before an improvement budget is set

Example components

• Review checklist
• Report template
• Prioritisation criteria
• Roadmap draft

A good fit when

• One person performs every deployment by hand
• Development and production differ, so something breaks on each release
• A new server has arrived and the starting point has to be decided

Example components

• Container layout
• HTTPS and domain setup
• Service and restart rules
• Deploy and rollback runbook